This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5523 - Discuss the behavior of GET on URI
Summary: Discuss the behavior of GET on URI
Status: RESOLVED FIXED
Alias: None
Product: SML
Classification: Unclassified
Component: Core (show other bugs)
Version: LC
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Kumar Pandit
QA Contact: SML Working Group discussion list
URL:
Whiteboard:
Keywords: externalComments, reviewerSatisfied
Depends on:
Blocks:
 
Reported: 2008-03-04 16:49 UTC by Pratul Dublish
Modified: 2008-06-25 09:16 UTC (History)
2 users (show)

See Also:

Attachments

Description Pratul Dublish 2008-03-04 16:49:26 UTC 
Minor comment from http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0001.html

4.3.1.1 should discuss what happens if
 a) the Content-Type of the response to the GET of the URI is not an
    XML media type;
 b) the entity body of the response to the GET of the URI is not
    well-formed XML.
Comment 1 Pratul Dublish 2008-03-06 17:31:32 UTC 
I believe that this bug is about Section 4.3.1. We should treat the reference as unresolved in the two cases mentioned in the bug
Comment 2 Kumar Pandit 2008-03-07 03:17:53 UTC 
resolution (3/6 conf call): mark editorial once proposal accepted

Proposal:
[1]
Change the last sentence in section 4.3.1 SML URI Reference Scheme bullet 2.b,

from:
If there is no document retrieved, the SML reference scheme instance is unresolved.

to:
If it does not retrieve a document in the current model, the SML reference scheme instance is unresolved.

The updated sentence will have the word document as a link to its definition in the terminology section.

[2]
Add the following non-normative note immediately after the changed sentence:

Note:
As a result of the above definition, if the retrieved object is not of is not of XML media type or if it is not well-formed XML then, by definition, that object is not a document as defined by this specification. In this case, the SML reference scheme instance is unresolved.

===
The SML WG believes that the above proposal resolves this issue fully.  I'm changing its status accordingly.

The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed.

Please review the changes adopted and let us know if you agree with this resolution of your issue, by adding a comment to the issue record. Or, if you do not agree with this resolution, please add a comment explaining why. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
Comment 3 Kumar Pandit 2008-03-07 19:15:03 UTC 
'is not of' is repeated by mistake in the non-normative note. Thanks to Kirk for catching it.
Comment 4 Virginia Smith 2008-04-10 18:22:21 UTC 
Resolution 4/10 - fix per comment #2 as amended by comment #3.
Comment 5 Kumar Pandit 2008-04-16 04:23:12 UTC 
fixed per comment# 4
Comment 6 Kumar Pandit 2008-05-15 19:49:38 UTC 
Henry, can you please let us know if the resolution in comment# 2 is acceptable to you?
Comment 7 Henry S. Thompson 2008-06-24 14:39:46 UTC 
I am happy that the text now in the draft addresses my concern.