W3C home > Mailing lists > Public > public-sml@w3.org > December 2007

[Bug 4636] What should SML 3.3.1.1 say about fragment identifiers?

From: <bugzilla@wiggum.w3.org>
Date: Tue, 04 Dec 2007 09:04:22 +0000
CC:
To: public-sml@w3.org
Message-Id: <E1IzThW-0001TO-Pn@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4636


kumarp@microsoft.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
           Keywords|editorial                   |needsReview
         Resolution|                            |FIXED




------- Comment #8 from kumarp@microsoft.com  2007-12-04 09:04 -------
The following changes were made:

----
Removed text related to xpointer() scehem and its profile definition.

----
added the following to 4.3.1 SML URI scheme definition.

4. Scheme syntax:

   SMLURI ::= URI ('#' SMLXPath1_Fragment_ID)? 

   where ,

   URI is a URI reference without a fragment identifier.

   SMLXPath1_Fragment_ID is a production that defines the syntax of the
fragment portion of the SML URI scheme. This is defined in section 4.3.1.1 The
smlxpath1() scheme.

----
added section 4.3.1.1

4.3.1.1 The smlxpath1() scheme
The smlxpath1() scheme is intended to be used with the XPointer Framework
[XPointer] to allow addressing of elements. The 4.3.1 SML URI Scheme uses it to
encode fragment identifiers.

This section describes the syntax and semantics of the smlxpath1() scheme and
the behavior of XPointer processors with respect to this scheme. 

1. Scheme name: smlxpath1. 

2. Scheme syntax:

SMLXPath1_Fragment_ID ::= 'smlxpath1' '(' SMLXPath1_SchemeData ')' 

SMLXPath1_SchemeData ::= XPath1.0_LocationPath 

where,

XPath1.0_LocationPath is the LocationPath production defined in the XPath 1.0
specification [XPath].

3. The deref() XPath extension function MUST NOT be present in the expression
evaluation context function library when processing the location path in
SMLXPath1_SchemeData. 

4. Namespace Binding Context: The smlxpath1() scheme inherits the set of
namespace bindings available to the containing element.

5. Document Context: The document context is set by the URI reference
containing the smlxpath1() scheme instance.

6. The element(s) targeted by a scheme instance are obtained by applying the
location path in SMLXPath1_SchemeData to the root element of the document in
the document context. The result MUST be a set of elements. The set MAY be
empty. If the result of applying the location path is something other than an
element or an element-set, then the XPointer result is an error.

----
Updated the example that previously showed xpointer() scheme usage. 
Received on Tuesday, 4 December 2007 09:04:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:56:08 UTC