RE: Ballot results - Approval of ebXML Registry specs, version 3.0

["Breininger, Kathryn R" <kathryn.r.breininger@boeing.com>]

Thank you Jamie!  The team has put in a lot of hard work and dedication
to produce these documents, and we appreciate your compliments!  We are
planning to move forward rapidly as we know a number of communities are
awaiting the version 3.0 specs but of course the timing will depend on
the type of comments we receive and if there are any substantial changes
required.  If the revised processes go into effect while we are in the
middle of this process, will that impact our specs?  I assume that if we
are in the middle of things we complete them under the guidelines in
effect when we started, is this correct?

Here is a list of features and enhancements with the version 3.0 ebXML
Registry specs. Please let me know if you have any questions about these
or would like additional detail:

-HTTP bindings

-Registry Managed Version Control

-Query Enhancements:
    * Iterative query
    * Parameterized stored queries
    * Improved filter query syntax

-Content Management Services
    * automatic semantic content validation
    * automatic content cataloging, and plug-in support
    * content based queries

-Federated Registry
    * federated query support
    * linking of content and metadata across registry boundaries
    * replication of content and metadata among registries
    * moving of content and metadata from one registry to another

-Access control and authorization based on the XACML 1.0 standard

-Content based Event Notification

-Federated Identity Management support using SAML 2.0 Single Sign On
(SSO)

-Alignment with recent standards
    * Web Services Security: SOAP Message Security 1.0
    * Web Services Security: SOAP Message with Attachments (SwA) Profile

1.0
    * WS-I: Basic Security Profile 1.0
    * WS-I: Basic Profile 1.1
     * SAML 2.0
    * XACML 1.0.

-Extensibility of  registry protocol where new types of requests and 
responses may
be defined easily.

-Human friendly URNs as the id of a content or meta data item

-A new standard meta data type Person has been added to represent
persons.

-The XML Filter Query syntax has been greatly simplified to make the
query more expressive while requiring less verbiage

Additionally, I just found Robin Cover's article, which summarizes most
of this.
http://xml.coverpages.org/ni2005-02-14-a.html




Kathryn Breininger






-----Original Message-----
From: James Bryce Clark [mailto:jamie.clark@oasis-open.org] 
Sent: Monday, February 14, 2005 6:41 AM
To: Breininger, Kathryn R
Cc: regrep@lists.oasis-open.org; carol.geyer@oasis-open.org
Subject: RE: Ballot results - Approval of ebXML Registry specs, version
3.0


     Kathryn, congratulations to you and your team.
     Your public review will expire on 14 March.  Under current rules it
is 
possible -- but somewhat tight timing -- that the TC could act to
confirm 
the drafts, elect not to make any changes, and submit it the next day
(15 
Mar), with the result of an April OS vote.  Of course, this makes the 
untested assumption that no changes will be requested during public
review 
that the committee wishes to incorporate.  And it assume that the
mandated 
10-item package [1] would be assembled during that period, and so
completed 
by 15 March.  Among other things those rules require successful use 
statements from three organizational members of OASIS.
    The rules will change quite soon, FYI.  See [2].
    Your short list of enhancements/changes from v2 to v3 would be a 
significant help to Carol as we compose a public message.  Also, it's 
likely to be a useful input to the 10-item list mentioned above.
    While I am officially somewhat neutral about these things, obviously
my 
longtime acquaintance and friendship with your team makes me doubly
pleased 
for you about this achievement.   The Registry is an excellent example
of 
how we *should* create standards:  concrete, useable work that met its 
well-crafted business requirements and goals, and deservedly enjoys
broad 
early adoption as a result.  There is a significant community of users
who 
I know will be pleased to see this update.
     Best regards JBC

~   James Bryce Clark
~   Director, Standards Development, OASIS
~   jamie.clark@oasis-open.org

[1]  Current Rules =
http://www.oasis-open.org/committees/process.php#standard
New Rules, what's coming, in draft = 
http://www.oasis-open.org/apps/org/workgroup/members-only/download.php/9
623/TC%20Process20041007.pdf
[2]Good, recent example of compliant 10-item submission = 
http://lists.oasis-open.org/archives/tc-announce/200502/msg00002.html

>From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com]
>To: James Bryce Clark; Carol Geyer
>Subject: Ballot results - Approval of ebXML Registry specs, version 3.0
>Importance: High
>
>Jamie and Carol,
>The ebXML Registry TC has approved the ebXML RS and ebXML RIM version 
>3.0
>documents as Committee Drafts.  We also have approved submission of the

>specs for the 30 day public review.  Attached are the minutes from our 
>meeting this morning documenting the voting and the results.  Please
let 
>me know if there is anything else that we need to do to move these
forward 
>for the 30 day public review.  We have been compiling a short list of
the 
>enhancements to the specs with version 3.0, and I can forward that to
you 
>as well for inclusion in the public announcements.