Open VladimirAlexiev opened 1 year ago
We need a way to visualize this, and break it down into smaller chunks so it can be addressed.
The action to take on this issue would be to write a script to produce the numbers for this issue.
Proposal: introduce a chart similar to undefinedTerms which we can use to track progress on missing datatypes.
This ticket needs to be broken into smaller issues. Somehow.
Assigned myself to produce an example of a relevant schema, so we can get agreement of what a proper, fully datatyped schema should look like.
Very similar to https://github.com/w3c-ccg/traceability-vocab/issues/573
At its most basic, this could be just a couple of counters like this:
In a JSONLD context one can and should declare the datatypes of props, so that a JSON payload string is mapped to the appropriate datatype.
@is
)This is especially important for literals that don't have native JSON type (xsd:date, xsd:dateTime). It's also important for numbers, which are subject to rounding/mangling in JSON. Eg this JSONLD payload:
is converted to this ntriples at https://json-ld.org/playground/. Notice the rounding of
bar1
, and the syntactically incorrect value ofbaz
:It's less important for booleans because the values are not subject to rounding.
Examples:
credentials/USMCACertificationOfOrigin.yml:
could add
common/IATAAirWaybill.yml:
already has
@type
, but maybe the JSON type should be changed fromstring
to something better?common/Transport.yml:
Must change to this ( I assume JSON Schema has type
dateTime
)