W3C home > Mailing lists > Public > public-xpointer-registry@w3.org > January to March 2008

RE: New Xpointer scheme proposed: smlxpath1

From: Kumar Pandit <kumarp@windows.microsoft.com>
Date: Mon, 3 Mar 2008 20:36:19 -0800
To: "Henry S. Thompson" <ht@inf.ed.ac.uk>, "public-xpointer-registry@w3.org" <public-xpointer-registry@w3.org>
CC: Michael Sperberg-McQueen <cmsmcq@w3.org>, "C. M. Sperberg-McQueen" <cmsmcq@acm.org>, Pratul Dublish <PRATULD@microsoft.com>, John Arwe <johnarwe@us.ibm.com>, Kumar Pandit <kumarp@windows.microsoft.com>
Message-ID: <0E4B701746DBB9418A6747852F8B9CA13837AD7BE7@NA-EXMSG-W602.wingroup.windeploy.ntdev.microsoft.com>

Hi Henry,
Thank you for your email asking for clarification on the smlxpath1() scheme..

The smlxpath1() scheme is defined to meet the specific needs of the SML specification. It uses only a subset of the full xpath1 functionality. To be specific, it only allows xpath1 location paths to be used. The SML working group decided to define smlxpath1 scheme for the following main reasons:
1. The SML group did not want the SML specification to take normative dependence on xpointer schemes that are not W3C recommendations. The xpath1() scheme is not a W3C recommendation.
2. The xpointer schemes that is a W3C recommendations (namely, element()) does not meet the needs of SML.
3. The xpath1() scheme allows any xpath expression. The SML working group did not want that. The group wanted only xpath location paths.
4. The smlxpath1() scheme inherits namespace bindings from the containing element which greatly reduces verbosity of SML models because xmlns() portions do not need to be added to each SML reference.

It appears that Syd's email is seeking clarification and is not a formal objection. I hope the explanation presented above provides sufficient clarification. Were any formal objections to smlxpath1() scheme received within the two week public review period?

I am not clear on the precise nature of the concerns about the smlxpath1() scheme causing dilution of the effectiveness of the xpath1() scheme. If it is the scheme name that is at the root of the confusion, the SML working group is open to changing the name to something like sml() scheme or the smlref() scheme (or any other name that you may suggest). Alternatively, since smlxpath1() scheme is for the specific needs of SML, would you recommend some other change to its registration to make it more acceptable to you?

Kumar

More info:
1. Email messages that may provide more context on this:
a.      http://lists.w3.org/Archives/Public/public-sml/2007Nov/0264.html
b.      http://lists.w3.org/Archives/Member/w3c-xml-cg/2007Oct/0021.html

2. The full definition of smlxpath1() scheme from the SML specification (http://www.w3.org/TR/2008/WD-sml-20080114/#SMLXPath1_Scheme).


-----Original Message-----
From: Henry S. Thompson [mailto:ht@inf.ed.ac.uk]
Sent: Thursday, February 28, 2008 12:19 PM
To: public-xpointer-registry@w3.org
Cc: Kumar Pandit
Subject: Re: New Xpointer scheme proposed: smlxpath1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Syd Bauman writes:

> How is this [smlxpath1] different than xpath1()?

The registrar invites discussion of this registration -- I am tending
towards rejecting it, on the grounds that it  unnecessarily duplicates
an existing scheme and would dilute the effectiveness of both the
existing scheme and the new scheme if it were allowed.

ht
- --
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFHxxclkjnJixAXWBoRApp0AJ4v/PsEgd3whNuASNGafzpLEkioyQCfcP0K
PZVDqQrV/kjur7Mh1sSCzL0=
=OddC
-----END PGP SIGNATURE-----
Received on Tuesday, 4 March 2008 04:55:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 March 2008 04:55:12 GMT