[Draft] Statement of relationship with other standards

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Dear colleagues,

As Kathryn mentioned, in order to submit our specs for OASIS standardization process next week we need
a statement of relationship of our specs with other standards. Per my ACTION from previous meetings I am
providing the draft text below.

Please share comments on this thread. Thanks.

<draft text>

[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 other OASIS 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 OASIS ebXML Registry 3.0 specifications have some similarities with the OASIS UDDI 3.0 standard in that both specifications define a registry standard.
Both specifications define a registry that is a web service. Both specifications define a registry that may be used as a registry for web services.
The two specifications have been independently developed and neither specifications uses the other as a dependency.

While UDDI 3.0 specifies a registry only, ebXML Registry 3.0 specifies both a registry and a repository.
In addition the OASIS ebXML Registry 3.0 specifications provide several other features that are not provided by UDDI 3.0. These include:

• Custom domain specific artifact discovery queries using SQL-92 and XML Filter Query syntax
• Life cycle management and governance of artifacts
  
• Automatic version control of artifacts
• Content based event notification using domain specific queries
• Parameterized registry-resident (stored) queries
• User-defined, domain specific, taxonomies
• Domain specific custom relationships between artifacts
• Ability to group related artifacts in packages
• Automatic, content specific, content validation
• Automatic, content specific, content cataloging
• Federated queries across multiple registries
• Linking artifacts in one registry to artifacts in any other registry
• Federated identity management based on SAML 2
  
• Single Sign On based on SAML 2
• HTTP Binding to registry protocol
• Extensible API and protocol that allows custom request / response messages
  

There are currently no activities or plans to converge ebXML Registry 3.0 and UDDI 3.0.
 
</draft text>

BTW, I would like to also include features in UDDI 3.0 that are not provided by ebXML Registry 3.0. My reading of the UDDI 3.0 specs
returned no such candidate items. Paul since you are a member of UDDI TC could you take an ACTION to provide us with a list of UDDI 3.0 features
that ebXML Registry 3.0 does not support? It would be good to state the features in terms of end user relevant functionality rather than something like
"UDDI has tModels and ebXML Registry does not". Thanks in advance for your help.

-- 
Regards,
Farrukh