You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the JSON schemas developed produce JSON that somewhat verbose. In large JSON files, it's clear this is coming from two areas:
@type key is always required, even when it can be inferred
InternationalizedText typed properties use an overly complicated structure
The solution to (1) might be to allow this key to be omitted when the usage is clear (e.g. when the object's type does not have subtypes). For (2), we could look at the structure in JSON-LD for RDF language tags.
The text was updated successfully, but these errors were encountered:
Right now the JSON schemas developed produce JSON that somewhat verbose. In large JSON files, it's clear this is coming from two areas:
@type
key is always required, even when it can be inferredInternationalizedText
typed properties use an overly complicated structureThe solution to (1) might be to allow this key to be omitted when the usage is clear (e.g. when the object's type does not have subtypes). For (2), we could look at the structure in JSON-LD for RDF language tags.
The text was updated successfully, but these errors were encountered: