- From: Sergey Beryozkin <sberyozkin@zandar.com>
- Date: Thu, 1 May 2003 10:40:53 +0100
- To: <www-ws-desc@w3.org>, "Arthur Ryman" <ryman@ca.ibm.com>
- Message-ID: <009001c30fc5$c2786570$1800a8c0@BERYOZKIN>
Hello, As you mentioned, the recommended way is to use XML Base[1]. It seems, though, that requiring xml:base be used in the context of the proposal [2] as the only means of resolving relative URIs might complicate things a little bit. Probably often enough, the referenced resources will only exist in the context of the referencing resource/service, and as such, its endpoint URI can serve as the base. When it's not the case, then absolute URIs, as shown at [2], can always be used. Using xml:base requires schema changes (unless it's placed on the envelope body), which in turn might lead to some interoperability problems with respect to using attributes on complex types. Also, it might not be easy for simple message parts of type anyURI to hold relative URIs as well. So, in the context of [2], xml:base may be used, but its presence should probably be optional. Cheers Sergey Beryozkin [1] http://www.w3.org/TR/xmlbase [2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Apr/att-0088/R085-2003-04-22.html ----- Original Message ----- From: Arthur Ryman To: www-ws-desc@w3.org Sent: Wednesday, April 30, 2003 6:11 PM Subject: R085, Relative URIs, and XML Base Since R085 involves messages that contain URIs, it is natural to allow relative URIs. The recommended way to send relative URIs is XML Base [1]. XLink uses XML Base. XML Base uses the xml:base attribute, e.g.: <?xml version="1.0"?> <doc xml:base="http://example.org/today/" xmlns:xlink="http://www.w3.org/1999/xlink"> <head> <title>Virtual Library</title> </head> <body> <paragraph>See <link xlink:type="simple" xlink:href="new.xml">what's new</link>!</paragraph> <paragraph>Check out the hot picks of the day!</paragraph> <olist xml:base="/hotpicks/"> <item> <link xlink:type="simple" xlink:href="pick1.xml">Hot Pick #1</link> </item> <item> <link xlink:type="simple" xlink:href="pick2.xml">Hot Pick #2</link> </item> <item> <link xlink:type="simple" xlink:href="pick3.xml">Hot Pick #3</link> </item> </olist> </body> </doc> Do we need to do anything in WSDL to describe this or is this handled somewhere else, e.g. in XSD or in the XML spec? [1] http://www.w3.org/TR/xmlbase/ Arthur Ryman
Received on Thursday, 1 May 2003 05:40:43 UTC