Need ability for inheritance on json schema

[mprorock]

In an ideally world we could use allof or similar in JSON Schema to represent a class - subclass relationship - this type of thing is well handled in JSON-LD, less so in JSON Schema. We should pick a best practice on this, and document it, etc.

[mprorock]

for example, in terms of the ag use case, we cannot type check that ppq203 is a subclass of aginspection in the repo

[Therecanbeonlyone1969]

Recommend to strive for a composable structure that is like:

1. General structure of properties we deem as common and decide if those are to be required
2. Extension schemas through $ref for verticals with these schemas to be composable and thus extensible again to other sub-schemas

example of an approach is:

• https://github.com/w3c-ccg/traceability-vocab/blob/main/packages/traceability-schemas/schemas/EcommerceWayBillRegistrationEvidenceDocument.json
• https://github.com/w3c-ccg/traceability-vocab/blob/main/packages/traceability-schemas/schemas/EcommerceWayBillCommodityContent.json
• https://github.com/w3c-ccg/traceability-vocab/blob/main/packages/traceability-schemas/schemas/EcommerceWayBillTotals.json
• https://github.com/w3c-ccg/traceability-vocab/blob/main/packages/traceability-schemas/schemas/PriceSpecification.json

[mprorock]

note: hardening any type enforcement should likely come into play once it is known that the object fully represents the contents of the type - e.g. paper based form that does not change or changes only on a long time scale, and is being digitized (e.g. digital form of a regulatory document)

[OR13]

JSON Schema that use inheritance do not generate JSON-LD context properly.

Would be good to get a set of examples we wished were possible on the ticket.

[OR13]

We still need examples.

[mprorock]

Per Call: This is resolved via #220

[VladimirAlexiev]

@OR13

JSON Schema that use inheritance do not generate JSON-LD context properly.

JSON Schema does not generate JSON-LD context of its own. So can you please illustrate the problem?

@mprorock

resolved via #220

Can you please explain how this is resolved by pointing to schemas that use inheritance?

I'm asking in relation to 2 of the issues I posted:

• use inheritance not aggregation #277 asks to use inheritance rather than composition, and gives an example of need for inheritance ("SeafoodProduct inherits from AgProduct and MarineProduct"),
• conflation of identifier: use class traceability:Identifier #571 gives another example ("NaturalGasProduct inherits from Product and adds HSCode; and changes facility to OilAndGasFacility").

[OR13]

JSON Schema does not generate JSON-LD context of its own. So can you please illustrate the problem?

We do this in this repo, its part of our build step today:

https://github.com/w3c-ccg/traceability-vocab/blob/main/packages/traceability-schemas/package.json#L17