Re: Atom Category Document for WSDL?
Arthur Ryman <[email protected]> Wed, 2 Jul 2008 18:13:19 -0400
| Newsgroups | gmane.comp.web.services.description,gmane.network.syndication.atom.protocol,gmane.network.syndication.atom.syntax |
|---|---|
| Message-ID | <OF15CA0B20.A858956A-ON8525747A.00797F15-8525747A.007A1427@ca.ibm.com> |
This is a multipart message in MIME format. --=_alternative 0079AE378525747A_= Content-Type: text/plain; charset="US-ASCII" Paul, I haven't seen this proposed before, but it sounds reasonable. I suppose that UDDI repositories could publish Atom feeds too. Arthur Ryman, Technical Executive (IBM DE) Project and Program Management, Rational Division phone: +1-905-413-3077, TL 313-3077 assistant: +1-905-413-3831, TL 313-3831 fax: +1-905-413-4920, TL 313-4920 mobile: +1-416-939-5063 Paul Denning <[email protected]> Sent by: [email protected] 07/02/2008 04:51 PM To [email protected], [email protected], [email protected] cc Subject Atom Category Document for WSDL? Given things like WSO2 Registry and Mule Galaxy, which provide Atom Publishing Protocol interfaces, it seems that it would be useful to have a "standard" atom:scheme and an associated Atom Category document. Compared to UDDI, Atom is generally considered more lightweight and ubiquitous. However, UDDI has some good aspects that perhaps should be modeled or imitated using Atom. For example, to register a WSDL document in UDDI [0], a tModel is created and some information gleened from the WSDL is used in the categoryBag. So, to find WSDL in UDDI, you search for tModels with a certain well-defined category in the categoryBag. [0] http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm Now that Atom Publishing Protocol (APP) is being used for publishing to a registry/repository, we should look at some conventions for the Atom category element to help users find WSDL and related SOA artifacts across (i.e., aggregation of) a set of heterogenous registry/repository feeds. That is, a large enterprise may have several registry/repositories, each with Atom feeds for WSDL, which I would like to aggregate into one composite feed for WSDL from across the enterprise. Finding the feeds for WSDL from among the many feeds that an enterprise may have should be easier. What I think this boils down to is a standard taxonomy (aka, value set, vocabulary) documented in an Atom Category Document [1]. [1] http://tools.ietf.org/html/rfc5023#section-7 For example, <?xml version="1.0" ?> <app:categories xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom" fixed="yes" scheme="http://example.com/soa"> <atom:category term="wsdlSpec" /> <atom:category term="wspSpec" /> <atom:category term="bpelSpec" /> </app:categories> Obviously @scheme would benefit from an IRI defined by an established standards organization (W3C, OASIS, IETF, ...). Above I define only three terms, but others should be considered. The terms above would be used, respectively, to register/publish WSDL, WS-Policy, and BPEL. Therefore if the 'wsdlSpec' category were to appear in an Atom Entry or Feed Document, it would appear as: <atom:category scheme="http://example.com/soa" term="wsdlSpec"/> If a registry/repository wanted to offer a feed/collection of WSDL documents, then an Atom Service document might look like the following: <?xml version="1.0" encoding='utf-8'?> <service xmlns="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.org/2005/Atom"> <workspace> <atom:title>Registry</atom:title> <collection href="http://example.com/soa" > <atom:title>My Blog Entries</atom:title> <categories href="http://example.org/soa" /> </collection> <collection href="http://feeds.example.org/soa/wsdl" > <atom:title>WSDL</atom:title> <categories fixed="yes"> <atom:category scheme="http://example.com/soa" term="wsdlSpec" /> </categories> <accept>application/wsdl+xml</accept> <accept>text/xml</accept> </collection> </workspace> </service> Has any of the above been considered? Paul --=_alternative 0079AE378525747A_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Paul,</font> <br> <br><font size=2 face="sans-serif">I haven't seen this proposed before, but it sounds reasonable. I suppose that UDDI repositories could publish Atom feeds too.</font> <br> <br><font size=2 face="sans-serif">Arthur Ryman, Technical Executive (IBM DE)<br> Project and Program Management, Rational Division<br> <br> phone: +1-905-413-3077, TL 313-3077<br> assistant: +1-905-413-3831, TL 313-3831<br> fax: +1-905-413-4920, TL 313-4920<br> mobile: +1-416-939-5063</font> <br> <br> <br> <table width=100%> <tr valign=top> <td width=40%><font size=1 face="sans-serif"><b>Paul Denning <[email protected]></b> </font> <br><font size=1 face="sans-serif">Sent by: [email protected]</font> <p><font size=1 face="sans-serif">07/02/2008 04:51 PM</font> <td width=59%> <table width=100%> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">To</font></div> <td><font size=1 face="sans-serif">[email protected], [email protected], [email protected]</font> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">cc</font></div> <td> <tr valign=top> <td> <div align=right><font size=1 face="sans-serif">Subject</font></div> <td><font size=1 face="sans-serif">Atom Category Document for WSDL?</font></table> <br> <table> <tr valign=top> <td> <td></table> <br></table> <br> <br> <br><tt><font size=2><br> Given things like WSO2 Registry and Mule Galaxy, which provide Atom <br> Publishing Protocol interfaces, it seems that it would be useful to <br> have a "standard" atom:scheme and an associated Atom Category document.<br> <br> Compared to UDDI, Atom is generally considered more lightweight and <br> ubiquitous. However, UDDI has some good aspects that perhaps should <br> be modeled or imitated using Atom.<br> <br> For example, to register a WSDL document in UDDI [0], a tModel is <br> created and some information gleened from the WSDL is used in the <br> categoryBag. So, to find WSDL in UDDI, you search for tModels with a <br> certain well-defined category in the categoryBag.<br> <br> [0] <br> http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm<br> <br> Now that Atom Publishing Protocol (APP) is being used for publishing <br> to a registry/repository, we should look at some conventions for the <br> Atom category element to help users find WSDL and related SOA <br> artifacts across (i.e., aggregation of) a set of heterogenous <br> registry/repository feeds.<br> <br> That is, a large enterprise may have several registry/repositories, <br> each with Atom feeds for WSDL, which I would like to aggregate into <br> one composite feed for WSDL from across the enterprise. Finding the <br> feeds for WSDL from among the many feeds that an enterprise may have <br> should be easier.<br> <br> What I think this boils down to is a standard taxonomy (aka, value <br> set, vocabulary) documented in an Atom Category Document [1].<br> <br> [1] http://tools.ietf.org/html/rfc5023#section-7<br> <br> For example,<br> <br> <br> <?xml version="1.0" ?><br> <app:categories<br> xmlns:app="http://www.w3.org/2007/app"<br> xmlns:atom="http://www.w3.org/2005/Atom"<br> fixed="yes"<br> scheme="http://example.com/soa"><br> <br> <atom:category term="wsdlSpec" /><br> <atom:category term="wspSpec" /><br> <atom:category term="bpelSpec" /><br> </app:categories><br> <br> <br> Obviously @scheme would benefit from an IRI defined by an established <br> standards organization (W3C, OASIS, IETF, ...).<br> <br> Above I define only three terms, but others should be considered.<br> The terms above would be used, respectively, to register/publish <br> WSDL, WS-Policy, and BPEL.<br> <br> <br> Therefore if the 'wsdlSpec' category were to<br> appear in an Atom Entry or Feed Document, it would appear as:<br> <br> <atom:category scheme="http://example.com/soa" term="wsdlSpec"/><br> <br> If a registry/repository wanted to offer a feed/collection of WSDL <br> documents, then an Atom Service document might look like the following:<br> <br> <?xml version="1.0" encoding='utf-8'?><br> <service<br> xmlns="http://www.w3.org/2007/app"<br> xmlns:atom="http://www.w3.org/2005/Atom"><br> <workspace><br> <atom:title>Registry</atom:title><br> <collection<br> href="http://example.com/soa" ><br> <atom:title>My Blog Entries</atom:title><br> <categories href="http://example.org/soa" /><br> </collection><br> <collection<br> href="http://feeds.example.org/soa/wsdl" ><br> <atom:title>WSDL</atom:title><br> <categories fixed="yes"><br> <atom:category<br> scheme="http://example.com/soa"<br> term="wsdlSpec" /><br> </categories><br> <accept>application/wsdl+xml</accept><br> <accept>text/xml</accept><br> </collection><br> </workspace><br> </service><br> <br> Has any of the above been considered?<br> <br> Paul<br> <br> <br> <br> </font></tt> <br> --=_alternative 0079AE378525747A_=--