OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [regrep] ebXML Registry "Brochure" (Was Re: [regrep] PR for specs)


I think that for a) it is best to do it as a presentation.

Obviously, for collaborative commenting, PDF is ideal <grin>. If you want, I
can produce a version of an initial document that is rights enabled so that
even people with only the free Reader can also comment on it.

Also, from our perspective and the use that we have seen in gov't in
conjunction with PDF (particularly forms mgmt), key benefits are

Life cycle management of objects
Security of object management

cheers

pk



-----Original Message-----
From: Duane Nickull [mailto:duane@yellowdragonsoft.com]
Sent: Tuesday, June 24, 2003 2:45 PM
To: Chiusano Joseph
Cc: Farrukh Najmi; Breininger Kathryn R; ebXML Regrep (E-mail)
Subject: Re: [regrep] ebXML Registry "Brochure" (Was Re: [regrep] PR for
specs)


What format do you think is best for this?  Work in MS word then publich
in PDF?

Duane
--
Yellow Dragon Software Corp. - http://www.yellowdragonsoft.com
Service Oriented Architectures - ebXML, Web Services, Registry, SOAP
Project Team lead - United Nations CEFACT eBusiness Architecture
+1 (604) 738-1051
***********************************

Chiusano Joseph wrote:
> I can definitely see that order as well. So far it appears that we all
> agree that "(a) Registry Brochure" would be the highest priority.
>
> I think we should include some information on XML registries (or we can
> call them "E-Business Registries") in general, as well as their
> benefits. Here is an excerpt from the "Requirements for an XML Registry"
> report I wrote for EPA 2 years ago (the points are perhaps too concise
> and need expansion, but they're good for general ideas):
>
> <Excerpt>
> The benefits of an XML registry are numerous:
>
> - Promotes reuse
> - Enables efficient version control
> - Promotes unified understanding of registered objects
> - Ensures consistency across organizational areas
> - Promotes selective access to registered objects
> - Enables collaborative development.
> </Excerpt>
>
> And an excerpt from a WebServices.org article I wrote in April:
>
> <Excerpt>
> An e-business registry is a software product that acts as an organizing
> focal point for the wealth of information and interactions that
> conducting e-business requires. E-business registries serve various
> purposes, including:
>
> - Enabling the discovery of trading partners and their various
> capabilities
> - Classification, association of e-business artifacts such as XML
> schemas, Document Type Definitions (DTDs), and trading partner profiles
> - Registration and discovery of Web service descriptions, such as Web
> Services Description Language (WSDL) documents
>
> E-business registries are central to the execution of e-business because
> they allow for the registration, management, and discovery of those
> critical items that are crucial for the conduct of e-business.
> </Excerpt>
>
> Joe
>
> Farrukh Najmi wrote:
>
>>Chiusano Joseph wrote:
>>
>>
>>><Quote>
>>>How do people see the relative priority of above 3 possibilities?
>>></Quote>
>>>
>>>I see them in the order listed, with (a) highest priority.
>>>
>>>Joe
>>>
>>
>>I almost agree. My order is (a), (c), (b). Here is why.
>>
>>I think (a) is most important because it has the most bang for the buck.
>>We could actually get this done in relatively short time. Bteween (b)
>>and (c) I see close overlap and prefer an web version of (c) as it
>>provides a superset of what (b) may provide.
>>
>>
>>>Farrukh Najmi wrote:
>>>
>>>
>>>
>>>>So far we have:
>>>>
>>>>a) Registry brochure
>>>>
>>>>b) Registry quick start guide
>>>>
>>>>and I would like to add as a possibility
>>>>
>>>>c) Registry Tutorial
>>>>
>>>>I see (a) being very light weight and high impact. I see (b) being a
>>>>litle more meat than (a). I see (c) being quite detailed but designed
>>>>according to use cases and filled with examples. A few good examples
>>>>come to mind:
>>>>
>>>>http://www.w3.org/TR/xmlschema-0/
>>>>http://java.sun.com/webservices/docs/1.1/tutorial/doc/
>>>>
>>>>How do people see the relative priority of above 3 possibilities? It
>>>>would be great to hear from actual users trying to grapple with the
>>>>specs even if they are not TC members.
>>>>
>>>>--
>>>>Farrukh
>>>>
>>>
>>--
>>Farrukh
>




You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
php



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]