W3C home > Mailing lists > Public > www-html@w3.org > June 2005

RE: N3 syntax in XHTML 2 [was RE: DC in XHTML2]

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Fri, 10 Jun 2005 07:35:46 +0100
Message-ID: <B7E9CB23-4AFC-45FD-A523-178850DC92BC@S009>
To: "'Jim Ley'" <jim@jibbering.com>, <www-html@w3.org>

Hi Jim,

> "Mark Birbeck" <mark.birbeck@x-port.net> wrote in message 
> news:2604453A-92F5-41C1-8CC7-C49B4E3549C7@S009...
> > One possibility would be to adorn QNames instead, with some 
> characters 
> > that are not from the set of valid URI characters. An example might 
> > be:
> >
> >  href="[x:y]"
> >
> > since '[' and ']' are in the 'excluded' characters list. (Other 
> > characters in that list are '{' and '}' but I think they should be 
> > saved for attribute value templates, as used in XSLT.)
> However using QNames in attribute context makes the document 
> unusable with XSLT anyway, so I cannot see how an XSLT 
> incompatibility can matter?

Sure, although you could still parse the *string* that contains the QName
and make a URI from it (and a future version of XSLT that supports XPath 2
will handle QNames easily).

But what I was more thinking of was the following type of usage:

   action="http://www.example.com/user/{//user/@name}" ...

Here we're using Attribute Value Templates to refer to some instance data,
and although this is not supported in the spec yet it would be good to keep
the squiggly brackets available for this. (As an experiment, this syntax has
already been implemented on xf:submission in formsPlayer 2.)



Mark Birbeck
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
Received on Friday, 10 June 2005 06:36:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:11 UTC