[
Lists Home |
Date Index |
Thread Index
]
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"]
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@cogsci.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]
|
