JSON-LD: Compaction and Expansion

[@ManuSporny]

*JSON-LD: Compaction and Expansion* An overview of JSON-LD's compaction and expansion features and how you can use them to merge data from multiple sources. For more information, see json-ld.org/ or follow @manusporny on Twitter.

[@JamesStansell]

Thanks Manu Sporny These are very similar concepts to ones from an inhouse system I worked on around 1990. Fun stuff! :)

[@CharlesDibsdale]

Such clarity! - thank you for making this so easy to understand.

[@ugolorusso661]

Thanks for the video. I also watched some other video you made about linked data and json-ld, everything is explained clearly with nice sketches, great job.

[@DanielBeeke]

Thank you very much! Very clear and good information!

[@florianwege7563]

How are the output short identifiers when compacting determined? Is this the last segment of the URL? But that might conflict with the target programming language, maybe need another normalization then like converting dashes to camel case.

[@angusmcallister8831]

Thanks for the vid; really helped to consolidate my understanding of how contexts are used for linking otherwise disparate data. Just one thing wasn't quite clear: does the expansion mechanism just replace the context that an existing KVP datum comes with, or does it actually provide context that wasn't previously there (by associating it with schema.org/name, for example)?

[@ManuSporny]

Angus McAllister I don't quite understand the question, but I'm going to try to answer it anyway. Expansion will take the current document and expand all the keys (and some of the values) out into full URLs. At that point, there will be no context, but all the data will be expanded and very specific. Compacting that same data w/ a different JSON-LD Context will shrink the keys that are now full URLs (and some of the values) back down into short values that developers like. So, visually, it looks like this: { "name": "Angus" } -> expand() -> { "schema.org/name": "Angus" } -> compact(my_context) -> { "myname": "Angus" }

[@800pieds]

Clear explanation.

[@unlink1649]

This is exactly what I need