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 6237 - is SMLIF locator/documentURI content a URI reference?
Summary: is SMLIF locator/documentURI content a URI reference?
Alias: None
Product: SML
Classification: Unclassified
Component: Interchange Format (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: PR
Assignee: Virginia Smith
QA Contact: SML Working Group discussion list
Keywords: resolved
Depends on:
Reported: 2008-11-19 16:04 UTC by John Arwe
Modified: 2009-01-13 00:42 UTC (History)
1 user (show)

See Also:


Description John Arwe 2008-11-19 16:04:47 UTC
In a nutshell, this boils down to whether relative references are allowed, and whether support for them is required.

I can find nothing in the LC2 draft answering this question definitively, although I suspect the working group's intent was that the content was a URI reference (i.e. relative URIs are allowed, and support for them is required).

The working group might also consider making explicit the contextual expectation that the content of documentURI is usually a URL (a subset of all URIs).
Comment 1 John Arwe 2008-11-20 19:48:52 UTC
Discussed on telecon of 2008-11-20.

Change 5.2.2 from: 
SML-IF specifies one way that MAY be used to provide the location of the referenced document, the documentURI element.

To add the following to the sentence above:
It is a consequence of documentURI's schema definition that it contains a URI reference, i.e that it may be an absolute URI or relative reference.  When it is a relative reference, the [base URI] property SHOULD be used to transform it to an absolute URI, as stated in [5.3.2 Base URIs].
Comment 2 Virginia Smith 2009-01-13 00:42:21 UTC
Fixed per comment #1.