- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Wed, 17 May 2006 22:11:37 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <873bf813qe.fsf@nwalsh.com>
/ Alex Milowski <alex@milowski.org> was heard to say:
| I think the simple fact that XPath 2.0 exists should make
| us think about a compatibility story. The minimum is some
| kind of forwards compatibility statement.
Maybe. Possibly we'll have to say something about a 2.0 processor
operating in backwards compatibility mode, but I'm not sure about
that.
| In addition, we're using XPath to control steps and so
| we need to have some way of a user/language identifying what
| kind of XPath they wrote or to which version they
| conform. That way, when XPath 2.0 is available, we
| know what kind of XPath semantics were expected.
No. We can say 1.0 uses XPath 1.0. Version 1.1 can say something else
and can provide such a mechanism if it's necessary.
| Maybe we have an Xpath version able to be declared in
| the pipeline that defaults to 1.0. If a user specifies
| version 2.0, they are in a forwards compability mode which
| won't be covered by the first specification. ???
If we aren't covering it, we don't have to mention it.
Be seeing you,
norm
--
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.
Received on Thursday, 18 May 2006 03:44:17 UTC