[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep] [Before Sending Out Ballot - Please Note!] RE: [regrep]draft of ballot to come
Peter Kacandes wrote: >What?! > >Why are we submitting anything about UDDI? > >Did somebody not cut and paste correctly? > >Better do a better job of proof-reading first. > > I think Jamie had his dates mixed up and thought it was April 1 ;-) He was surely pulling a joke on us ;-) >pk > >-----Original Message----- >From: Chiusano Joseph [mailto:chiusano_joseph@bah.com] >Sent: Friday, April 01, 2005 3:51 AM >To: James Bryce Clark; regrep@lists.oasis-open.org >Subject: [regrep] [Before Sending Out Ballot - Please Note!] RE: [regrep] >draft of ballot to come > >Jamie, > >Wanted to call your attention to this prior to sending OASIS-wide - Please >note the unintentionally embedded additional text in the paragraph below: > ><Quote> >The OASIS ebXML Registry TC has submitted the ebXML Registry Information >Model (RIM) v3.0 and ebMXL Registy sndUniversal Description, Discovery & >Integration (UDDI) specification v3.0.2, an approved Committee Draft, to be >considered as an OASIS Standard. The TC's submission is attached below. ></Quote> > >Joe > >Joseph Chiusano >Booz Allen Hamilton >Visit us online@ http://www.boozallen.com > > > > >>-----Original Message----- >>From: James Bryce Clark [mailto:jamie.clark@oasis-open.org] >>Sent: Thursday, March 31, 2005 7:06 PM >>To: regrep@lists.oasis-open.org >>Subject: [regrep] draft of ballot to come >> >> >> FYI, here's what I plan to post tomorrow afternoon to formally >>launch the OASIS Standard vote. Best regards JBC >> >>==== >>DRAFT (for posting 1 April) >> >>Subject: ebXML Registry specifications submitted for OASIS Standard >>From: James Bryce Clark <jamie.clark@oasis-open.org> >>To: tc-announce@lists.oasis-open.org,members@lists.oasis-open.org >>Date: [1 April] >> >>OASIS members: >> >>The OASIS ebXML Registry TC has submitted the ebXML Registry >>Information Model (RIM) v3.0 and ebMXL Registy sndUniversal >>Description, Discovery & Integration (UDDI) specification v3.0.2, an >>approved Committee Draft, to be considered as an OASIS Standard. The >>TC's submission is attached below. >> >>In accordance with the OASIS Technical Committee Process, the >>specification has already gone through a 30 day public review period. >>(http://lists.oasis-open.org/archives/tc-announce/200502/msg00 >>008.html) >>OASIS members now have until the 15th of April to familiarize >>themselves with the submission below. OASIS members should give their >>input on this question to the voting representative of their >>organization. >> >>By the 16th of the month we will send out a Call For Vote to the >>voting representatives of the OASIS member organizations, who will >>have until the end of the month to cast their ballots on whether this >>Committee Draft should be approved as an OASIS Standard. >> >>The normative TC Process for approval of Committee Drafts as OASIS >>Standards is found at >>http://www.oasis-open.org/committees/process.php#standard >> >>Any statements related to the IPR of this specification are posted at >>http://www.oasis-open.org/committees/uddi-spec/ipr.php >> >>~ James Bryce Clark >>~ Director, Standards Development, OASIS ~ +1 978 667 5115 x >>203 central offiice >> >> >> >>>Submission for OASIS Membership Vote: >>> >>>1. A formal specification that is a valid member of its >>> >>> >>type, together >> >> >>>with appropriate documentation for the specification, both of which >>>must be written using approved OASIS templates. >>> A zip file with both specifications and related files >>> >>> >>is publicly >> >> >>>available from >>>http://www.oasis-open.org/committees/document.php?document_id=12049 >>> >>>The zip file contains: >>>1. The OASIS ebXML Registry Information Model (RIM) >>> >>> >>specification, v3.0 >> >> >>>as "regrep-rim-3.0-cs-02.pdf". >>>2. The OASIS ebXML Registry Services (RS) specification, v3.0 as >>>"regrep-rs-3.0-cs-02.pdf". >>>3. Supporting files and documentation including: >>> a. 10 WSDL description files >>> b. 21 XML scheme files >>> c. 5 XSD files >>> >>>The individual approved Committee Draft specifications in PDF format >>>(same as in zip files) are publicly available from the ebXML >>> >>> >>Registry TC site. >> >> >>>OASIS ebXML Registry Services and Protocols version 3.0 >>> >>> >>Committee Draft: >> >> >>>http://www.oasis-open.org/committees/download.php/12060/regre >>> >>> >>p-rs-3.0-c >> >> >>>d-02.pdf >>> >>>OASIS ebXML Registry Information Model version 3.0 Committee Draft: >>>http://www.oasis-open.org/committees/download.php/12061/regre >>> >>> >>p-rim-3.0- >> >> >>>cd-02.pdf >>> >>>2. A clear English-language summary of the specification: >>> >>>The ebXML Registry provides a stable store where submitted >>> >>> >>content and >> >> >>>the metadata used to describe that content is managed and is >>> >>> >>made persistent. >> >> >>>Such information is used to facilitate business to business >>>relationships and transactions. In the business to business context, >>>submitted content includes but is not limited to XML schema and >>>documents, process descriptions, ebXML Core Components, context >>>descriptions, UML models, information about organizations, >>> >>> >>and software >> >> >>>components. An ebXML Registry is capable of storing any type of >>>electronic content including XML documents, text, images, or sound. >>>Metadata is used to describe the stored content and is >>> >>> >>defined in the >> >> >>>Registry Information Model (RIM). Submitted content may be stored in >>>the content repository provided by the ebXML Registry. The >>> >>> >>interface to >> >> >>>the Registry is defined in the Registry Services and >>> >>> >>Protocols (RS) document. >> >> >>>It provides a set of services that enable sharing of content and >>>metadata between organizations. The RS defines the services >>> >>> >>provided >> >> >>>by an ebXML Registry and the protocols used by clients to >>> >>> >>interact with these services. >> >> >>>The version 2.0 RIM and RS specifications were approved as OASIS >>>Standards in May 2002, and ISO approved them as ISO 15000 part 3 and >>>part 4 standards in March 2004. Version 3.0 of RIM and RS add >>>considerable functionality over version 2.0. New functionality >>>available in version 3.0 include registry federation and federated >>>queries, which enable clients to discover information stored >>> >>> >>in any of >> >> >>>multiple federated registries through one search. To meet >>> >>> >>the needs for >> >> >>>security in a federated environment, version 3.0 utilizes the OASIS >>>SAML 2.0 specifications for identity management, authentication and >>>single sign on across the members. The OASIS XACML 1.0 standard is >>>leveraged to provide access control policies and OASIS WSS >>> >>> >>SOAP Message >> >> >>>Security 1.0 is used to secure the registry's SOAP protocol >>> >>> >>using digital certificates. >> >> >>>Extensible service interfaces and protocols are defined in >>> >>> >>version 3.0 >> >> >>>as plugins to an ebXML Registry that provide content cataloging >>>services and content validation services. The version 3.0 also >>>provides managed version control through the registry. A new HTTP >>>binding to the ebXML Registry Services interfaces is defined >>> >>> >>using a REST style architecture. >> >> >>>This enables any content or meta data in the registry to be >>> >>> >>accessible >> >> >>>over an HTTP URL using a standard web browser. A >>> >>> >>Parameterized Stored >> >> >>>Query feature allows a complex query to be stored in the registry in >>>parameterized form. To invoke the query, the client provides some or >>>all of the query parameters, usually using a web form to fill in the >>>parameters and submit the query. Other query improvements include >>>iterative queries, content based queries, and improved >>> >>> >>filter query syntax. >> >> >>>In version 3.0 subscriptions may be created by the user for >>>content-based event notification of specific events of interest. >>>Notification is sent to a web service or an email address. >>> >>> >>Additional >> >> >>>new features include extensibility of registry protocol for defining >>>new types of requests and responses, incorporation of user defined >>>domain specific taxonomies, and the ability to group related content >>>artifacts in packages. >>> >>>3. a statement regarding the relationship of this specification to >>>similar work of other OASIS TCs or other standards >>> >>> >>developing organizations: >> >> >>> The OASIS ebXML Registry 3.0 specifications are >>> >>> >>aligned with a >> >> >>>variety of OASIS and other standards as described below. >>>* The OASIS Web Services Security: SOAP Message Security 1.0 >>>specification is used to provide Message Security for the >>> >>> >>Registry protocol. >> >> >>>* The OASIS Web Services Security: SOAP Message with >>> >>> >>Attachments >> >> >>>(SwA) Profile 1.0 specification is used to provide Message >>> >>> >>Security for >> >> >>>SOAP attachments within the Registry protocol. >>>* The OASIS XACML 1.0 specification is used to define >>> >>> >>the syntax for >> >> >>>registry Access Control Policies. >>>* The OASIS SAML 2.0 specifications are used to >>> >>> >>support Federated >> >> >>>Identity Management and Single Sign On within the registry. >>>* The registry conforms to the WS-I: Basic Profile 1.1 >>> >>> >>for SOAP and >> >> >>>WSDL conformance. >>>* The registry conforms to the WS-I: Attachments >>> >>> >>Profile 1.0 for >> >> >>>SOAP with Attachments conformance. >>>Limited similarities exist between the OASIS ebXML Registry 3.0 and >>>OASIS UDDI 3.0. Both specifications define a registry for >>> >>> >>web services >> >> >>>and a registry exposed as a web service. UDDI 3.0 specifies >>> >>> >>a registry >> >> >>>only, while ebXML Registry 3.0 specifies both a registry and a >>>repository. No explicit dependencies exist between those two >>> >>> >>OASIS specification efforts. >> >> >>>4. Certification by at least three OASIS member >>> >>> >>organizations that they >> >> >>>are successfully using the specifications consistently with >>> >>> >>the OASIS >> >> >>>IPR >>>Policy: >>> a. ebXMLsoft Inc. has been successfully using the ebXML >>> >>> >>Registry >> >> >>>3.0 specifications consistently with the OASIS IPR Policy. >>> >>> >>ebXMLsoft >> >> >>>considers the ebXML Registry 3.0 specifications an important >>>continuation to delivering functionality necessary to further >>>accommodate its ebXML Federated Enterprise Reference Architecture >>>(eFERA). See >>> >>> >>http://lists.oasis-open.org/archives/regrep/200502/msg00056.html >> >> >>> b. Sun Microsystems Inc. has been successfully using the ebXML >>>Registry 3.0 specifications as approved by the OASIS ebXML Registry >>>Technical Committee. Sun Microsystems Inc. considers that the ebXML >>>Registry 3.0 specifications are ready to be submitted and >>> >>> >>accepted as >> >> >>>an OASIS Standard in accordance with the OASIS IPR Policy. See >>>http://lists.oasis-open.org/archives/regrep/200502/msg00054.html >>> c. Adobe Systems Incorporated has been successfully using the >>>ebXML Registry 3.0 specifications as approved by the OASIS ebXML >>>Registry Technical Committee. See >>>http://lists.oasis-open.org/archives/regrep/200502/msg00059.html. >>> >>>5. An account of each of the comments/issues raised during >>> >>> >>the public >> >> >>>review period, along with its resolution: >>> Available from >>> >>>http://www.oasis-open.org/committees/download.php/11865/regre >>> >>> >>p-3.0-comm >> >> >>>ents.html >>> >>>6. An account of and results of the voting to approve the >>> >>> >>specification >> >> >>>as a Committee Draft: >>> Vote to affirm approval of the specifications as >>> >>> >>Committee Drafts >> >> >>>documented in the meeting minutes for March 15, 2005: >>>http://www.oasis-open.org/committees/regrep/minutes/minutes-0 >>> >>> >>3-15-05.pd >> >> >>>f >>> >>>7. An account of or pointer to votes and comments received in any >>>earlier attempts to standardize substantially the same >>> >>> >>specification, >> >> >>>together with the originating TC's response to each comment: >>> These specifications have not previously been submitted >>> >>> >>to OASIS >> >> >>>for approval as standards. >>> >>>8. A pointer to the publicly visible comments archive for >>> >>> >>the originating TC: >> >> >>> http://lists.oasis-open.org/archives/regrep-comment/ >>> >>>9. A statement from the chair of the TC certifying that all >>> >>> >>members of >> >> >>>the TC have been provided with a copy of the OASIS IPR Policy: >>> I have provided all ebXML Registry TC members with the >>> >>> >>link to the >> >> >>>OASIS IPR Policy. See >>>http://lists.oasis-open.org/archives/regrep/200503/msg00018.html >>> >>>10. Optionally, a pointer to any minority reports submitted >>> >>> >>by one or >> >> >>>more TC members who did not vote in favor of approving the Committee >>>Draft, or certification by the chair that no minority reports exist. >>> There are no minority reports submitted by any TC >>> >>> >>members related >> >> >>>to the ebXML Registry specs. Both the ebXML RS and the ebXML RIM >>>specifications were approved as Committee Drafts unanimously. >>> >>>Kathryn Breininger >>>OASIS ebXML Registry TC Chair >>> >>> >>DRAFT ENDS >> >>Note, I deleted several additional "use certifications" from parties >>who are not organizational members of OASIS and thus, while welcome as >>implementers, do not count towards the rule's minimum quota. >> >>Regards JBC >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe from this mail list, you must leave the OASIS TC that >>generates this mail. You may a link to this group and all your TCs in >>OASIS >>at: >>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr >>oups.php >> >> >> >> > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > -- Regards, Farrukh
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]