On Fri, Aug 10, 2012 at 1:39 PM, Markus Lanthaler
markus.lantha...@gmx.net wrote:
Well, I would say there are several advantages. First of all, JSON-LD
is
more flexible and expressive.
More flexible and expressive than what?
Than application/microdata+json.
That's a problem right there.
On Thursday, August 09, 2012 4:53 PM, Ian Hickson wrote:
The only reason there's a MIME type at all (rather than just using
JSON's directly) was to enable filtering of copy-and-paste and
drag-and-drop payloads; would JSON-LD enable that also?
Sure, I see no reason why not.
Could
On Fri, 10 Aug 2012, Markus Lanthaler wrote:
On Thursday, August 09, 2012 4:53 PM, Ian Hickson wrote:
The only reason there's a MIME type at all (rather than just using
JSON's directly) was to enable filtering of copy-and-paste and
drag-and-drop payloads; would JSON-LD enable
On Thursday, August 09, 2012 1:18 AM, Ian Hickson wrote.
On Wed, 8 Aug 2012, Markus Lanthaler wrote:
I was wondering whether it was considered to use JSON-LD [2] instead
of
creating application/microdata+json. The resulting output would be
more
or less the same.
It wasn't. What
On Thu, 9 Aug 2012, Markus Lanthaler wrote:
The only reason there's a MIME type at all (rather than just using
JSON's directly) was to enable filtering of copy-and-paste and
drag-and-drop payloads; would JSON-LD enable that also?
Sure, I see no reason why not.
Could you give an
Hi all,
I just sent this e-mail in response to Michael[tm] Smith's request [1] to
register application/microdata+json to ietf-types but I think this is a
better place to discuss this... so sorry for the cross-post.
I was wondering whether it was considered to use JSON-LD [2] instead of
creating
On Wed, 8 Aug 2012, Markus Lanthaler wrote:
I was wondering whether it was considered to use JSON-LD [2] instead of
creating application/microdata+json. The resulting output would be more
or less the same.
It wasn't. What would be the purpose of doing so?
The only reason there's a MIME
