Re: [regrep] [Fwd: [wsrp] Groups - wsrp faq (wsrp-faq-draft-0.30.html) uploaded]

Farrukh,

It's a nice FAQ (from Web Portlets) but their use case is much narrower than
registry.

I think we would need a set of "threads" or so - for registry - based on who
the
typical audience / user might be - and provide that top level menu that
branches down.

Brainstorming on this:

1) Data analyst / DBA user - creating Registry and searching content - FAQ

2) Programmer - User Interface Developer - FAQ

3) Librarian - installing registry, downloading a skin interface, loading
content,
    federating to other registry - FAQ

4) B2B marketplace service provider - installing registry, creating portal
for
    business partners.

5) End user - connecting to registry with thin client - FAQ

I'm not volunteering for any of these! ; -)

Cheers, DW

----- Original Message ----- 
From: "Farrukh Najmi" <>
To: <>
Sent: Wednesday, January 12, 2005 4:53 PM
Subject: [regrep] [Fwd: [wsrp] Groups - wsrp faq (wsrp-faq-draft-0.30.html)
uploaded]


> FYI...
>
> Here is a great example of what an FAQ for our specs could look like.
>
> We have a good starting point taht Carl did a while back:
>
>     http://www.ebxml.org/ebusinessxmlregistry.pdf
>
> Addition FAQ material can be extracted (after removing product specific
> material) from a product specific FAQ I have at:
>
>     http://ebxmlrr.sourceforge.net/aboutFAQ/About_freebXML_Registry.html
>
> I propose that we recast Carl's  excellent brochure into something that
> takes inspiration from the WSRP FAQ.
> the advantage is that it is more accessible, not constrained by real
> estate issues and much easier to
> read when not folded as a trifold brochure.
>
> Would any one be willing to take a stab at doing this?
>
> -- 
> Regards,
> Farrukh
>
>


----------------------------------------------------------------------------
----


> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.