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] New OASIS TC FAQ Pages


Breininger, Kathryn R wrote:

>Thanks Joe.  I will send these to Carol.
>  
>
mm1: Potential OOPS, we did correct for non-XML artifacts; however, in 
(3)-(6) we only reference XML artifacts (sorry I used to copyedit in a 
former life).

>Kathryn
>
>-----Original Message-----
>From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
>Sent: Tuesday, September 09, 2003 2:22 PM
>To: Breininger, Kathryn R
>Cc: ebXML Regrep (E-mail)
>Subject: Re: [regrep] New OASIS TC FAQ Pages
>
>
>Here are my modified answers:
>
>WHAT IS AN XML REGISTRY?
>
>An XML registry is an information system that stores XML artifacts
>(e.g., XML schemas, data elements, etc.) and non-XML artifacts (e.g.
>supporting documents), as well as details (metadata) about the
>artifacts. The storage facility (e.g., a filesystem or database) that
>holds registered objects is known as a repository, while the part of the
>information system that maintains the metadata for the registered
>objects is known as a registry.  
>
>WHAT ARE THE BENEFITS OF AN XML REGISTRY?
>
>The benefits of an XML Registry are numerous and include:
>
>(1) Promotes efficient discovery and maintenance of registered objects
>
>(2) Enables efficient version control for registered objects
>
>(3) Promotes unified understanding of registered objects-Because
>metadata for registered objects is accessible from a single location, a
>unified understanding of the purpose of the registered objects will be
>promoted  
>
>(4) Ensures availability and reuse of authoritative XML-A controlled
>registration and validation of XML artifacts from authoritative sources
>promotes interoperability between trading partners, and facilitates
>greater reuse
>
>(5) Enables collaborative development-Users can create XML artifacts and
>submit them to an XML registry for use and potential enhancement by
>authorized parties. The enhanced versions can then be made available for
>access by other authorized parties.
>
>Thanks,
>Joe
>
>"Breininger, Kathryn R" wrote:
>  
>
>>Here is the note from Carol.  Yes, we do indeed have a link on our public page as a place holder.  Joe, if you modify the answer to the one question as Monica suggested, I will send those two questions to Carol.  We can have more added as we develop them.  Sound okay to everyone?
>>
>>Kathryn
>>
>>-----Original Message-----
>>From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
>>Sent: Wednesday, August 13, 2003 1:17 PM
>>To: TC chairs
>>Cc: Sharon Burbine
>>Subject: [chairs] RE: New OASIS TC FAQ Pages
>>
>>OASIS TC chairs,
>>We've extended the deadline on OASIS TC FAQ pages to 2 September.
>>
>>At that time, Sharon will add an "FAQ" link to all the TC navs (those
>>links on the main TC page in the upper right purple box, "Charter, IPR
>>Statement, etc."). It's a blanket move that will affect all the TCs at
>>once. If you have not submitted FAQ content by 2 Sept, we'll create a
>>placeholder page for your TC's FAQ (that says something like 'content
>>coming soon').
>>
>>Please let us know if you will be unable to meet the 2 Sept deadline or
>>if there's anything we can do to assist you. Keep in mind, you can
>>always edit the FAQ at any time.
>>
>>Thanks,
>>Carol
>>
>>-----Original Message-----
>>From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
>>Sent: Thursday, August 07, 2003 3:55 PM
>>To: TC chairs
>>Cc: Sharon Burbine
>>Subject: New OASIS TC FAQ Pages
>>
>>On 25 August, OASIS will be adding a new FAQ page to each TC's public
>>website. This will make it easier for prospective users, editors, people
>>who may be considering joining the TC, and others to find answers to
>>some basic questions on your work.
>>
>>Each TC will be responsible for creating its own FAQ content. The
>>following are just general suggestions to get you started; obviously
>>each TC will have specific FAQ appropriate for its work.
>>
>>  What is the need for this specification?
>>
>>  Who should be involved in this development?
>>
>>  Who will benefit from this work and how?
>>
>>  How does this work compare with related efforts at other standards
>>organizations?
>>
>>  When will this specification be completed?
>>
>>Please let me know if you need assistance in writing an FAQ for your TC.
>>Completed FAQs should be sent to support@oasis-open.org before 25 Aug
>>for posting. You may edit your FAQ at any time after it's posted.
>>
>>Regards,
>>Carol
>>
>>____________________________________________
>>Carol Geyer
>>Director of Communications
>>OASIS
>>http://www.oasis-open.org
>>carol.geyer@oasis-open.org
>>Voice: +1 978.667.5115 x209
>>
>>You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/chairs/members/leave_workgroup.php
>>
>>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.
>>    
>>
>
>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.
>
>
>  
>




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