We've kicked this around as a PitS idea in the past; Erik's point about interoperability with other languages and environments was one motivation. Another potential advantage of encoding ClassAds in pure JSON is that embeddable JS runtimes are very good these days, which has implications both for parsing/lexing/evaluation and (even more PitS) processing.
----- Original Message -----
> From: "Brian Bockelman" <bbockelm@xxxxxxxxxxx>
> To: "Erik Paulson" <epaulson@xxxxxxxxxxx>
> Cc: condor-devel@xxxxxxxxxxx
> Sent: Tuesday, June 25, 2013 1:25:47 PM
> Subject: Re: [HTCondor-devel] idle thoughts: json as classads
>
> - You'd also need to map null to something in classads.
> - ClassAds would still be a superset of JSON.
> - There would be natural guidance for a binary encoding of ClassAds.
> - You could probably update the ClassAds language to have multiple
> representations - classical new ClassAds, JSON ClassAds, binary ClassAds,
> and XML ClassAds. As all would use a different first character, you could
> have a single parser/lexer for all representations.
>
> What's the benefit though - versus just having different converters written
> in C++?
>
> Brian
>
> On Jun 25, 2013, at 1:19 PM, Erik Paulson < epaulson@xxxxxxxxxxx > wrote:
>
>
>
>
> If we flipped the meaning of '[]' and '{}' in ClassAds, and allowed colons as
> an assignment operator*, and maybe checked the different string escapes,
> would every JSON object automatically be a ClassAd?
>
> It'd be kind of slick if ClassAds and JSON were a little more interoperable,
> and we could get some cool stuff somewhat for free.
>
> We could go a little farther, and work out a full syntax for ClassAds in
> JSON, maybe by looking at some of the JSON Referencing ideas:
> http://www.sitepen.com/blog/2008/06/17/json-referencing-in-dojo/
>
> This could all be first-steps towards easier interactions with HTCondor in
> other languages and environments.
>
> -Erik
>
> *which I swore I thought Ye Olde ClassAds could do, but maybe it was just the
> config files
> _______________________________________________
> HTCondor-devel mailing list
> HTCondor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel
>
>
> _______________________________________________
> HTCondor-devel mailing list
> HTCondor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel
|