Internet2 is investigating a security incident involving a compromise to a confluence server that affected https://spaces.at.internet2.edu on April 10, 2019, which was successfully mitigated on April 12, 2019. If you did not receive an email from us, it’s unlikely that any of the content you submitted to the Internet2 Spaces Wiki needs to be re-entered. We apologize for any inconvenience this may have caused. Should you have any questions or require further assistance, please email collaboration-support@internet2.edu.
Child pages
  • Ignoring Unrecognized Schema Fragments in a Received Resource Representation
Skip to end of metadata
Go to start of metadata

Research Topic

  • 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?

Leveraging JSON-LD

https://lists.w3.org/Archives/Public/public-schemaorg/2016Jan/0004.html

...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):

{
"@context": {
"geo": "http://schema.org/geo",
"polygon": "http://schema.org/polygon"
},
"@type": "http://schema.org/Place",
"ID": 1,
"MUNICIPALITY": "Leeuwarden",
"WATER": "NO",
"geo": {
"@type": "http://schema.org/GeoShape",
"polygon": "53.24330130 ... 2536921"
}
}

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.

  • No labels