This sounds like a reasonable approach, and I think we should probably add
a standard means of labelling the tModel.
Note that the schema could, in a sense, be found via the WSDL, but it's a
bit less than ideal.
-----Original Message----- From: Paul Denning
[mailto:pauld@mitre.org] Sent: Fri 18-Feb-05 3:17 To:
uddi-spec@lists.oasis-open.org Cc: Subject: [uddi-spec]
TN for registration of XSD and XSLT?
It would be nice to register XML Schema files (XSD) in a UDDI
registry. Likewise, it would be nice to register XSLT files in a UDDI
registry.
It would be nice if such registrations are done in a common
way.
The pattern would be similar to others where a tModel is published
with the overviewURL pointing to the XSD or XSLT file, and with the
categoryBag containing a keyedReference. By convention (i.e., TN/BP)
would indicate that the overviewURL points to an XSD file. A TN to
document this convention would need to define the tModel for a taxonomy
that would be used in the keyedReference mentioned above. The
keyValue would indicate the taxon within this taxonomy that indicates an
XSD.
Systinet is using such a technique, but it seems to rely upon a
taxonomy tModel that has not been defined under the uddi.org key space
[1].
[1] http://forums.systinet.com/index.php?t=tree&goto=12095&rid=&S=1eb967d858f3491e37c1f8060952a24f
Is
there an established way of registering XSD and XSLT in a UDDI
registry?
Paul
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/uddi-spec/members/leave_workgroup.php.
|