Direct, never thought of RDDL. But don't expect many people to actually use the link. Putting a decent search engine on the repository remains the most important thing.
Steve On 17 July 2010 03:31, Tsao, Scott <[email protected]> wrote: > > > Steve, > > Thanks for the reply! > > Do you use the URL for the targetNamespace of your WSDL to link directly to > the formal documentation in your service repository, or through some kind of > intermediary such as RDDL <http://en.wikipedia.org/wiki/RDDL>? > > Scott > > ------------------------------ > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Steve > Jones > *Sent:* Tuesday, July 13, 2010 11:17 PM > > *To:* [email protected] > *Subject:* Re: [service-orientated-architecture] URI for targetNamespace > Attribute Value > > You can use it in the same way to link from the technical interface > (WSDL) to the formal documentation for the interface. I've used it to link > into the service repository documentation set. > > However as with the XSD URI I've found that probably only 1 in 20 people > actually find and use the link. > > Steve > > > > On 14 July 2010 14:51, Tsao, Scott <[email protected]> wrote: > >> >> >> As I understand, it is a preferred practice to use URL instead of URN for >> the targetNamespace attribute value of an XML schema. And the primary >> reason is that one could use the XSD namespace URL to document the use of an >> XML schema. >> >> See: http://xsd.stylusstudio.com/2009Sep/post01000.htm >> >> However, I wonder if this practice should also be applied to the >> targetNamespace attribute value of a WSDL document. I don't see as strong a >> reason to do so as for XML schema. >> >> What do you think? >> >> Thanks, >> >> Scott Tsao >> The Boeing Company >> >> > >
