RE: [uddi-spec] TN for registration of XSD and XSLT?

["Daniel Feygin" <feygin@unitspace.com>]

I think this would be the right way to go.  In addition to the core solution
Paul outlined, I have on occasion encountered the more peripheral
requirements of:
1. Associating an 'abstract' data model (such as OWL ontology) with its
concrete XSD representation(s).
2. Representing an XSLT-based schema-to-schema mapping (i.e., input
instance's schema to output instance's schema via a given transform).
3. Modeling dependencies between multiple published WSDLs and XSDs, where
some XSDs are imported within various WSDLs and XSDs.

Among the constraints:
1. Supporting V2 through all of this.
2. Minimizing the number of inquiry round-trips to navigate the model.
3. Multiple publishers of various elements of the model.

Daniel
 

-----Original Message-----
From: Von Riegen, Claus [mailto:claus.von.riegen@sap.com] 
Sent: Thursday, February 17, 2005 7:29 PM
To: Paul Denning; uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] TN for registration of XSD and XSLT?

Paul,

I am not aware of any established approach for registering XML schemas or
even XSLT files in UDDI.
Based on a more concrete list of requirements, we should be able to
prioritize this kind of work for our next round of activities. Would you
mind writing up such a list of requirements / use cases?

Thanks,
 Claus

-----Original Message-----
From: Paul Denning [mailto:pauld@mitre.org]
Sent: Donnerstag, 17. Februar 2005 17:17
To: uddi-spec@lists.oasis-open.org
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=1eb967d858
f3491e37c1f8060952a24f

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_wor
kgroup.php.


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_workgro
up.php.

smime.p7s