XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Please stop writing specifications that cannot beparsed/processed by software

It's published (and referenced from the spec) at

https://www.w3.org/TR/2017/REC-xpath-functions-31-20170321/function-catalog.xml

Michael Kay
Saxonica

> On 26 May 2023, at 11:56, Roger L Costello <costello@mitre.org> wrote:
> 
> Michael Kay wrote:
> 
>> the XPath function library is defined in an XML document
>> that contains all the function signatures in a custom
>> vocabulary reflecting the object model for XPath functions,
>> and that data is extremely useful; it can be used for example
>> to create the data used by a type-checker. I'm sure there are
>> cases where an XML format can be standardised across a
>> wide range of specifications (for example, a format for
>> defining BNF grammars) but I'm sure that highly specialized
>> custom formats also have a role to play.
> 
> This is really interesting. Michael, would you expand on this please? I am not entirely clear on what you are saying. What does this mean:  "the XPath function library is defined in an XML document that contains all the function signatures in a custom vocabulary reflecting the object model for XPath functions." Perhaps you would be willing to provide an example to illustrate what you mean?
> 
> /Roger



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS