[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPath for Infoset extensions [was Annotations in XPath-NG?

• To: "David Rosenborg" <darolst@p...>
• Subject: Re: XPath for Infoset extensions [was Annotations in XPath-NG?]
• From: ht@c... (Henry S. Thompson)
• Date: 07 Oct 2002 10:54:07 +0100
• Cc: "Uche Ogbuji" <uche.ogbuji@f...>, "Jeni Tennison" <jeni@j...>, "Eric van der Vlist" <vdv@d...>, <xml-dev@l...>
• In-reply-to: <005801c26de5$272f60f0$6500000a@KENNY>
• References: <E17yS6Q-0005C3-00@m...><f5b65wed6dd.fsf@e...><005801c26de5$272f60f0$6500000a@KENNY>
• Sender: ht@i...
• User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Informed Management)

"David Rosenborg" <darolst@p...> writes:

> Henry S. Thompson wrote:
> 
> > John Cowan and I have been pushing around the idea that it should be a
> > requirement on 'official' infoset extensions that they come with a
> > serialisation.  I'd like to see this happen, for example along the
> > lines of the various reflections Richard Tobin and I have explored for
> > the PSVI.  It would be a simple step to allow XPaths to navigate
> > extensions via a pretend reflection.  All that's required is a
> > function 'reflect(property)', whose value would be a reflection of the
> > value of an infoset property of the current node.  So, for instance,
> > to access the appinfo annotation of the type used to validate an
> > 'apple' element child of the current node, you'd say:
> > 
> >   apple/reflect("type_definition")/annotation/appinfo
> > 
> > You could of course navigate the vanilla infoset this way.  The
> > equivalent of /*/apple/@banana would look like
> > 
> >   /property("document_element")/children/element[local_name="apple"]/attributes/attribute[local_name="banana"]
> 
> Yes, direct PSVI access would be one possible application of an annotation axis or function
> (as Jeni suggested with foo/#psvi:type-definition in an earlier post), but I see no
> point in limiting it to PSVI and PSVI only access as your reflect function suggests.

There was no implication of such a restriction -- the idea is the the
'reflect' function would give you access to _any_ infoset property
supported by your processor.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2002, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@c...
		     URL: http://www.ltg.ed.ac.uk/~ht/
 [mail really from me _always_ has this .sig -- mail without it is forged spam]

• References:
  • Re: Annotations in XPath-NG? (Re: XPath/XSLT 2.0 concerns)
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • XPath for Infoset extensions [was Annotations in XPath-NG?]
    • From: ht@c... (Henry S. Thompson)
  • Re: XPath for Infoset extensions [was Annotations in XPath-NG?]
    • From: "David Rosenborg" <darolst@p...>

• Prev by Date: Re: XPath for Infoset extensions [was Annotations in XPath-NG?]
• Next by Date: Re: XPath/XSLT 2.0 concerns
• Previous by thread: Re: XPath for Infoset extensions [was Annotations in
• Next by thread: Re: XPath for Infoset extensions [was Annotations in XPath-NG?]
• Index(es):
  • Date
  • Thread