Well, I also think querying is a good idea. I think I will need the equivalent of XPath or perhaps XQuery for indexing stuff in JSON. I think I'm targetting my stuff to replace XSLT, if that is possible. I'd like it to be done with end-user programming inside and between editors. Something more concrete than XSLT. On Jul 22, 2013 6:14 PM, "Chris Gahan" <[email protected]> wrote:
> Hey John, > > If you don't mind me asking, what's the higher level goal of this tool > you're making? Are you interested in transforming JSON? Querying JSON? > > If you're interested in queries, Freebase has a very nice graph query > system (called MQL) where the user gives it a JSON structure as a query > template, and the database does some graph traversal and returns a > collection of JSON structures that match the template. > > I think it's a really nice system; you can see some examples here: > http://www.freebase.com/query > > The basic idea is that your JSON query template has some key/values for it > to match (eg: "artist": "The Police"), and whatever values are left blank > (eg: "album": []) gets populated with results. It has the littany of > standard database query features as well, like ordering and limits and > ranges and whatnot: http://mql.freebaseapps.com > > Hope this helps! > -- Chris > > > On Sun, Jul 21, 2013 at 4:45 PM, John Carlson <[email protected]> wrote: > >> Or numbers for pointers... >> On Jul 21, 2013 3:43 PM, "John Carlson" <[email protected]> wrote: >> >>> I think what would be more difficult would be identifying what is >>> persistent and what is runtime values. Also, JSON doesn't contain >>> pointers, so one would have to use strings for pointers. >>> On Jul 21, 2013 3:22 PM, "James McCartney" <[email protected]> wrote: >>> >>>> >>>> I thought about this briefly. One issue is how to distinguish literal >>>> strings from identifiers. >>>> >>>> On Sun, Jul 21, 2013 at 10:28 AM, John Carlson <[email protected]>wrote: >>>> >>>>> Hmm. I've been thinking about creating a macro language written in >>>>> JSON that operates on JSON structures. Has someone done similar work? >>>>> Should I just create a JavaScript AST in JSON? Or should I create an AST >>>>> specifically for JSON manipulation? >>>>> >>>>> Thanks, >>>>> >>>>> John >>>>> >>>>> _______________________________________________ >>>>> fonc mailing list >>>>> [email protected] >>>>> http://vpri.org/mailman/listinfo/fonc >>>>> >>>>> >>>> >>>> >>>> -- >>>> --- james mccartney >>>> _______________________________________________ >>>> fonc mailing list >>>> [email protected] >>>> http://vpri.org/mailman/listinfo/fonc >>>> >>>> >> _______________________________________________ >> fonc mailing list >> [email protected] >> http://vpri.org/mailman/listinfo/fonc >> >> > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > >
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
