- From: James M Snell <jasnell@gmail.com>
- Date: Tue, 22 Jul 2014 11:59:19 -0700
- To: Owen Shepherd <owen.shepherd@e43.eu>
- Cc: public-socialweb@w3.org
On Tue, Jul 22, 2014 at 10:46 AM, Owen Shepherd <owen.shepherd@e43.eu> wrote: > > [snip] > > It seems like a relatively niche use case for what is a considerable increase in the difficulty in processing the content (i.e. it's no longer sufficient for the processor to just walk the attributes to find objects). > > I don't think the use cases justify the complexity (and, as said, it doesn't mesh well at all with JSON-LD processing) > > [snip] Keep in mind also that AS2 is not *based* on JSON-LD. It's *aligned* with JSON-LD in that it defines specific rules on how someone can process AS2 using JSON-LD and how certain key attributes can be mapped into that model. It's not a clean fit. Using an @context we can most of the way there, but in order to get a pure JSON-LD processing model, one has to do a bit of massaging of the data. There are two primary reasons for this: 1. AS2 has the express goal that all valid AS 1.0 documents MUST also be valid AS 2.0 documents 2. There are a number of existing AS implementers who have absolutely no desire to do JSON-LD processing. - James
Received on Tuesday, 22 July 2014 19:00:06 UTC