Re: [xml-dev] YPath, ZPath?

["HILLMAN, Tomos" <tomos.hillman@oup.com>]

Impolite and irrelevant to the topic of conversation: a state of the art
comparison between markup query languages and schema may well make an
interesting paper - I invite Daniela to write it - but I fail to see what
it has to do with Michael¹s attempt to write a new mark-up language with
different constraints than either JSON or XML.

On the topic of FtanML, am I the only person disappointed with the lack of
namespaces?  I feel that the inconvenience and mess of the namespace
implementation is more than balanced by the ability to do cool things with
RDFa and REST like concepts of self documenting semantic data models - but
I seem to be in a minority in that viewŠ

Tom

On 13/04/2016 07:18, "Dave Pawson" <dave.pawson@gmail.com> wrote:

>Oh dear. First impolite reply.
>How boring.
>
>On 12 April 2016 at 22:43, daniela florescu <dflorescu@me.com> wrote:
>> Dear Michael,
>>
>> given that the paper you cite doesn¹t seem to bother doing a decent
>> comparison with the state
>> of the art, I¹m asking the question here:
>>
>> How does this compare with the JSONiq query language
>>(http://jsoniq.org), as
>> well with the JSound JSON Schema
>> language (https://github.com/cezarfx/jsound/blob/master/JSoundSpec.md)
>>
>> Both of which precede with at least 2 years this paper.
>>
>> P.S. Next time, maybe a thorough and comprehensive state of the art
>> comparison would help advance the
>>  technology better, Michael.
>>
>> Thanks
>> Dana
>>
>> On Apr 12, 2016, at 11:14 AM, Michael Kay <mike@saxonica.com> wrote:
>>
>>
>> If the XSLT, XQUERY constraints were removed (MK comments "I wouldn't
>> start from here") what might such a model look like and would it have
>> a significant use case?
>>
>>
>> I made an attempt at this with my FtanML paper at Balisage two or three
>> years ago.
>>
>> 
>>http://www.balisage.net/Proceedings/vol10/html/Kay01/BalisageVol10-Kay01.
>>html
>>
>> Starting with a markup language that tried to combine what XML and JSON
>>do
>> well into a unified scheme, which could be described as JSON plus mixed
>> content, or as XML with typed attributes.
>>
>> Then defined a simple data model on top of this, and then a query
>>language
>> (I rather like the name, FtanSkrit) and schema language on top of the
>>data
>> model.
>>
>> I think it showed that it can be done. But of course, the fact that
>> something can be done doesn't mean that you can achieve uptake.
>>
>> Michael Kay
>> Saxonica
>>
>>
>>
>>
>>
>> _______________________________________________________________________
>>
>> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>> to support XML implementation and development. To minimize
>> spam in the archives, you must subscribe before posting.
>>
>> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>> subscribe: xml-dev-subscribe@lists.xml.org
>> List archive: http://lists.xml.org/archives/xml-dev/
>> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>>
>>
>
>
>
>-- 
>Dave Pawson
>XSLT XSL-FO FAQ.
>Docbook FAQ.
>http://www.dpawson.co.uk
>
>_______________________________________________________________________
>
>XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>to support XML implementation and development. To minimize
>spam in the archives, you must subscribe before posting.
>
>[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
>subscribe: xml-dev-subscribe@lists.xml.org
>List archive: http://lists.xml.org/archives/xml-dev/
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents to anyone. You may use and apply the information for the intended purpose only. OUP does not accept legal responsibility for the contents of this message. Any views or opinions presented are those of the author only and not of OUP. If this email has come to you in error, please delete it, along with any attachments. Please note that OUP may intercept incoming and outgoing email communications.