Assumption: Whatever schemas our WG comes up with for resources, they will need to be locally extensible.
- Questions: Is it possible to design APIs and Resource representations so that resource properties the recipient doesn’t know about can be ignored/skipped? If so, how?
...I'd also like to expose a JSON-LD representation of my resources. JSON-LD is fine with multiple vocabularies and you can in fact 'ignore' properties by not defining them in the @context. This means this is my source (note that I shortened the polygon value for readability):
From a Linked Data and JSON-LD point of view this is completely correct. The properties ID, MUNICIPALITY and WATER aren't mapped in the @context so the parsers ignore this.
References and Links
- JSON-LD: Core Markup: https://youtu.be/UmvWk_TQ30A
Widget Connector width 100 url https://www.youtube.com/watch?v=UmvWk_TQ30A height 60