Re: YPath Specification still ongoing?

Considering that YAML is a superset, then operating  at the data model level is better. From what I see I would expect an engine that applies the path on the document and afterwards gives the wanted language-representation of the data. So the path parser is independent of the language-specific representation.

Kind regards
Pieter Heyvaert
Ghent University - imec

________________________________________
From: Carsten Bormann <[email protected]>
Sent: Thursday, June 8, 2017 12:54 PM
To: Peter Murphy
Cc: Pieter Heyvaert; [email protected]
Subject: Re: [Yaml-core] YPath Specification still ongoing?

> On Jun 8, 2017, at 12:26, Peter Murphy <[email protected]> wrote:
>
> Pieter,
>
> Good day. I started working on it in 2011, but I never got around to
> adding anything to it. Too busy with other things, I guess.
>
> So if you are interested in it:
>
> (a) Feel free to fork the spec (or write your own), and:
>
> (b) Work on an implementation of it (possibly in PyYAML or another engine).

Hmm.  Should Ypath be cognizant of (i.e., dependent on) the serialization or really operate at the data model level?
(If equivalent YAML is to stay really equivalent, it needs to be the latter.)
In that case, the actual YAML engine isn’t that relevant to a YPath implementation...

Grüße, Carsten


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot