Seed contribution inspecjs schemas

[sthagen]

Seed Contribution InspecJS Schemas

The three JSON files in this contrinution are used as input for the quicktype schema generator
quicktype in the Heimdall2 repository
to build the corresponding libs/inspecjs apps.

The license at the source site is replicated
within this contribution as LICENSE to provide complete innformation.

The revision of the source repository at which the three JSON files have been taken from
is 70632b92e087903ee7afffaa00a21bf4e445a39f

Checksums

BLAKE3

abd52fd44a9a531d870f31873e497dbc1731576cec9356addeab30b9fdc92d4d  exec-json.json
4c46e2423b66baf8c4f92a43ee242f171256c299a0ef184f0fbf3b721495f4e3  exec-jsonmin.json
82a318b505576530bf3cc03c43aec0bb0c4c307a07d8062810d11239a94b119c  profile-json.json

SHA256

cca6f58a4e0f5acebd6b7b69114208fd59fa404af97f85741d9b4dd22ca107c8  exec-json.json
3ada4044bc03f0e585968812b61e0d73b0276876a94711574682e08093ce72f7  exec-jsonmin.json
7cd7bd8f6d32f1ce21598c584140d28e8524cae3a753ffaa6a2be9dc29c26e55  profile-json.json

SHA512

4b1270ddc77a6d5743da612097c284119b6b0a0b2517f0e8fc27b78747c005663610c5d86fedd98f047ec259c0ff751eec48507f4daecc63c2619b269495ac32  exec-json.json
8184a7bbb3c0065560e7d2031f030691e5a34d8c114a138bd997e2f2fc2523080f659cdcbbd043362a4ebf9e3ff3c0303c876cd5407e661fb2293070a252b5ca  exec-jsonmin.json
d0b74f50f7aebc5837b7f4581b77419ac051d01ef4fad3e6b905638eccba1738c9f8259aed694cf16e26f16309a017ad7e511fa2acb92b793e62d35ee5a0db91  profile-json.json

[aaronlippold]

Is the folder structure of seed-contribution a regular practice in this domain?

[sthagen]

Is the folder structure of seed-contribution a regular practice in this domain?

Not sure if I understood the question, but I try to provide the rationale behind the two level tree:

Name of Top-Level Folder

These JSON files are a contribution to seed the specification work and not the final spec itself.

Also, we already have a TC member that agreed with the motion to add the contribution, because we put it in such a clearly specified place.

Subfolders Naming the Origins

Maybe other contributions will come along, so I think having a namespace hinting at the origins per folder structure is a future proof way to store contributions.

[sthagen]

An additional idea has been named in the draft agenda for the TC meeting on 2023-01-10 which proposes to use NIST Metaschema for capturing and formalizing the current Heimdall schema.

INO this new idea can go side by side with this change set (already contributed to OASIS OHDF per the kavi / OASIS workplace system).

Note: When using "NIST Metaschema" (or "JSON Schema" directly) the TC will want to staart from some model ideas of a working implementation regardless.

I propose to finally merge this PR as the place (directory) has already been carefully chosen to allow other contributions side-by-side and by merging we merely document the fact of the already contributed data also here in the GitHub TC repository and keep the OASIS TC workplace in sync with this GitHub OASIS TC "workplace".