W3C home > Mailing lists > Public > xml-dist-app@w3.org > September 2002

RE: [AF] relative URIs for attachments

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Sun, 15 Sep 2002 18:08:16 -0700
Message-ID: <79107D208BA38C45A4E45F62673A434D0861832A@red-msg-07.redmond.corp.microsoft.com>
To: "Herve Ruellan" <ruellan@crf.canon.fr>, <xml-dist-app@w3.org>


From an editorial and consistency point of view, I think it would be beneficial to maintain the separation between the abstract description of the compound SOAP structure and the requirements to a particular binding implementing the feature. Currently we have section 4 describing the model and section 6 describing the requirements to an implementation.

I suggest that relative URIs be mentioned in section 6 and not section 4 as we from a model perspective always are dealing with absolute URIs; relative URIs are meaningless by themselves. Whether the absolute URIs can be represented using a base URI and a relative URI is an implementation issue and not a model issue.

Section 6 already provides requirements for dealing with URIs although it doesn't mention the issue of relative URIs. I would therefore suggest the following slight reorganization of your proposal:

<OldSection4>
Each part is identified by a URI that can be used to reference it from other parts. The URI identifying a part can be of any URI scheme; the particular assignment of URIs to parts in the message MUST be specified by each SOAP binding implementing this feature. It is RECOMMENDED that only IANA registered URI schemes be used.
</OldSection4>

<NewSection4>
Each part is identified by a URI that can be used to reference it from other parts. The URI identifying a part can be of any URI scheme. It is RECOMMENDED that only IANA registered URI schemes be used.
</NewSection4>

<OldSection6>
A mechanism by which each part is identified using a URI reference. While the reference MUST be in the form of a URI, the URI scheme used MAY but need not be the same for all parts.
</OldSection6>

<NewSection6>
A mechanism by which each part is identified using a URI. The URI scheme used MAY but need not be the same for all parts. If a SOAP binding allows the use of relative URIs, it MUST specify how the base URI is established. 
</NewSection6>

Henrik

>-----Original Message-----
>From: Herve Ruellan [mailto:ruellan@crf.canon.fr] 
>Sent: Thursday, September 12, 2002 05:27
>To: xml-dist-app@w3.org
>Subject: [AF] relative URIs for attachments
>
>
>
>Dear all,
>
>I currently have an action item:
>2002/09/11: Herve
>Draft clarifying sentence or two for AF spec that relative URIs are 
>allowed by EOB Friday. Comments are due Monday noon PT. 
>Silence is assent.
>
>Here is some proposal for fulfilling this action item.
>
>Comments are welcomed.
>
>Hervé.
>
>--------------------
>
>Change 5th paragraph of 4. Compound SOAP Structure Model:
><current>
>Each part is identified by a URI that can be used to reference it from 
>other parts. The URI identifying a part can be of any URI scheme; the 
>particular assignment of URIs to parts in the message MUST be 
>specified 
>by each SOAP binding implementing this feature. It is RECOMMENDED that 
>only IANA registered URI schemes be used.
></current>
>
><proposal>
>Each part is identified by a URI reference that can be used to 
>reference 
>it from other parts. The URI reference identifying a part can 
>be of any 
>URI scheme. It can be an absolute or a relative URI. The particular 
>assignement of URI references to parts in the message MUST be 
>specified 
>by each SOAP binding implementing this feature. In addition, if a SOAP 
>binding allows the use of relative URIs, it MUST specify how the base 
>URI is established. It is RECOMMENDED that only IANA registered URI 
>schemes be used.
></proposal>
>
>I don't think we should change the definition of a Secondary 
>Part which 
>is currently (i.e. keep URI, and do not replace it by URI reference):
><current>
>Secondary Part
>
>A document or entity related to the primary SOAP message part in some 
>manner. A secondary part is a resource in the sense that it 
>has identity 
>and is identified by a URI. The representation of the resource 
>can be of 
>any type and size. Secondary parts are informally referred to as 
>attachments.
></current>
>
>
Received on Sunday, 15 September 2002 21:08:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:11 GMT