-
Notifications
You must be signed in to change notification settings - Fork 19
Use the same example for JSON-LD and RDFa #80
Comments
I have run the RDFa Generation algorithm by hand, and this is what I got:
I have also run it through my RDFa converter to produce turtle. I do not think that the turtle result should be in the document, but I have put it up in a separate gist. |
@gkellogg, can you compare the Turtle output of your JSON-LD tool with the the example in turtle via RDFa? The two graphs should be equivalent... (B.t.w., we may want to think about a testing environment whereby the conversions to RDFa and the conversions to JSON-LD would be compared as for their RDF representations to see whether they are equivalent. If not, we have a problem...) |
(Just a small editorial remark: in the example above I added a |
Think it makes sense to have several examples, and definitely work the same ones for each conversion. I've assigned myself (but please feel free to generate Pull Requests that do some of the work me ;) )... |
Fix #78, #80 The JSON-LD direct conversion algorithm is harder to get right, and is redundant in practice. Clarify that the "JSON" conversion is explicitly for `application/microdata+json` and mark it as obsolete but conforming since it seems to have been removed from current versions of known implementations. (And update status)
Fix #78, #80 The JSON-LD direct conversion algorithm is harder to get right, and is redundant in practice. Clarify that the "JSON" conversion is explicitly for `application/microdata+json` and mark it as obsolete but conforming since it seems to have been removed from current versions of known implementations. (And update status)
JSON-LD section has gone, so this is no longer needed. |
I believe it would be better to use the same example for JSON-LD, RDFa (and JSON). It is better for the readability of the document...
(There may be several examples; the current RDFa example contains the
itemref
trick, which is great because RDFa can indeed reproduce that...)The text was updated successfully, but these errors were encountered: