[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Inherent limitation in the expressability of XML markup?
Hi Roger, Other than the points mentioned, here's a significant capability that's currently achievable using non-xml (the current syntax) XPath syntax, Using XPath expressions as values of attributes (that are computed at runtime). Here's a fictitious example of this, <X a="{sum(for $x in seq return $x mod 2)}"> ... </X> This is used currently both in XSLT and XQuery. On Mon, Mar 21, 2011 at 4:52 PM, Costello, Roger L. <costello@mitre.org> wrote: > Hi Folks, > > XPath is a non-XML syntax. > > XSLT, Schematron, and XML Schema 1.1 make heavy usage of XPath. The role of XPath seems to expand with each new version of these technologies. > > Why? > > Example: consider this XML snippet: > > <meeting> > Â Â <start-time>08:00:00</start-time> > Â Â <end-time>09:00:00</end-time> > </meeting> > > In both Schematron and XML Schema 1.1 the co-constraint between the meeting's start time and end time is expressed using XPath: > > Â meeting/start-time lt meeting/end-time > > Why isn't this co-constrain expressed using XML markup? Why do we resort to non-XML syntax? > > Does it indicate an inherent limitation in the expressability of XML markup? Has anyone characterized this limitation? > > /Roger -- Regards, Mukul Gandhi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|