[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Draft] Statement of relationship with other standards
Dear colleagues, As Kathryn mentioned, in order to submit our specs for OASIS
standardization process next week we need Please
share comments on this thread. Thanks. <draft text> [3.] A statement regarding the relationship of this specification to The OASIS ebXML Registry 3.0 specifications are aligned with a variety of other OASIS standards as described below. similar work of other OASIS TCs or other standards developing organizations.
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:
</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 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]