[ http://issues.apache.org/jira/browse/WODEN-115?page=comments#action_12459801 ] Arthur Ryman commented on WODEN-115: ------------------------------------
1. Here's a trivial example myroot.xml: <?xml version="1.0"?> <root> <description xml:id="wsdesc" xmlns="http://....";> .... </description> </root> The URI to reference the description is, e.g. http://www.example.org/myroot.xml#wsdesc 2. Here's how frag ids work. A) a processor gets the resource and determines its MIME type, e.g. this is the content type in the HTTP header. B) the processor looks at the MIME type registration to interpret the meaning of the fragment, e.g. HTML and XML documents support "bare names" like #wsdesc. XML documents should also support XPointer. WSDL 2.0 registered its own XPointer scheme (see the appendix of the WSDL 2.0 spec.) C) the processor accesses the part of the document referenced by the fragment id (e.g. a Web browser would scroll to that location) 3. Low priority for now. However, other specs may inline WSDL 2.0 and we want Woden to support that. Recall that WSDL inlines XSD and this breaks Xerces when you give it the URI reference to the inlined XSD. > Support WSDL 2.0 <description> nested within other XML documents > ---------------------------------------------------------------- > > Key: WODEN-115 > URL: http://issues.apache.org/jira/browse/WODEN-115 > Project: Woden > Issue Type: Bug > Reporter: Arthur Ryman > > Woden should be able to parse a WSDL 2.0 <description> element nested in > another XML document. This means that the URI passed to the parser may have a > fragment identifier. > Woden should support bare names at least, and perhaps other XPaths. e.g. > http://www.example.org/mydocument.xml#mydescription -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
