produce a holistic JSON example

[VladimirAlexiev]

(cc @mristin)

In https://github.com/VladimirAlexiev/aas-core-codegen/tree/main/test_data/jsonld_context/trials#next-steps
and admin-shell-io/aas-specs#386 (comment)
I asked for some more holistic examples, so I can experiment with langString, datatyped literals, and maybe framing.

@ethieblin referred to JSON examples.
But if we take one of those eg https://github.com/admin-shell-io/aas-specs/blob/master/schemas/json/examples/generated/LangStringPreferredNameTypeIec61360/maximal.json,
it doesn't look like complete AAS data, so I'm not sure whether I can expect to get "complete" turtle out of it.

I think that having a bigger realistic example will be very useful for implementers and users alike.

Eg see the hundreds of examples in these folders (Turtle and Diagrams are automatically generated from JSON):

• https://github.com/gs1/EPCIS/tree/master/JSON
• https://github.com/gs1/EPCIS/tree/master/Turtle
• https://github.com/gs1/EPCIS/tree/master/Diagrams

[VladimirAlexiev]

KenWenzel:

can also find examples at: https://admin-shell-io.com/samples/
But those are random samples and they may not reflect all constructs the AAS has to offer.

[mristin]

KenWenzel:

can also find examples at: https://admin-shell-io.com/samples/
But those are random samples and they may not reflect all constructs the AAS has to offer.

Please note that admin-shell-io samples are really outdated (AAS V1 and V2), and probably also incorrect.

[VladimirAlexiev]

I picked a random one https://admin-shell-io.com/samples/aasx/08_SchneiderElectric.aasx
and the AAS payload inside
08_SchneiderElectric.aasx::aasx\wwwcompanycomidsaas2520_6010_8091_1277\wwwcompanycomidsaas2520_6010_8091_1277.aas.xml
is XML not JSON.

@kenwenzel please see above.

Today at the IDTA WG were discussed several proposals to make IRIs (what I would call "URL Policy") instead of blank nodes.
Such example(s) will be needed to see how IRIs mesh together.

[kenwenzel]

KenWenzel:

can also find examples at: https://admin-shell-io.com/samples/
But those are random samples and they may not reflect all constructs the AAS has to offer.

Please note that admin-shell-io samples are really outdated (AAS V1 and V2), and probably also incorrect.

@mristin Does this also count for https://v3.admin-shell-io.com/

@VladimirAlexiev You can download JSON-based documents via https://v3.admin-shell-io.com/submodels/
The endpoint implements the AAS HTTP API.

[mristin]

@mristin Does this also count for https://v3.admin-shell-io.com/

Sorry, I don't know that. You have to check the format & constraints yourself -- I wasn't aware of that subdomain.

[VladimirAlexiev]

https://v3.admin-shell-io.com/submodels/

• The first two are submodel templates with empty elements.
• But the third one is an instance of "Nameplate" (a Linear motor axis by WEISS) with useful info.
• And googling for several of the IRDIs finds submodel PDF specifications ("manual linked data" ;-))

Here are indexes of useful examples (can be extracted with jq)

• 2 Nameplate-Weiss
• 3 ContactInformation
• 4 HandoverDocumentation
• 5 TechnicalData
• 9 ArticleInformation
• 11 ServiceNotifications
• 12 Nameplate-Festo

These are empty

• 6 MCAD https://admin-shell.io/sandbox/idta/handover/MCAD/0/1/
• 7 Electrical_and_Fluid_CAD https://admin-shell.io/sandbox/idta/handover/EFCAD/0/1/
• 8 PLC_Programming https://admin-shell.io/vdi/2770/1/1/Documentation
• 10 BillOfMaterial

Some more googling turns up Submodel definitions and examples, but these are in XML not JSON:

• https://github.com/admin-shell-io/submodel-templates/tree/main/published/Digital%20nameplate/2/0 , with 19 siblings
• https://github.com/admin-shell-io/submodel-templates/tree/main/published/ZVEI_Digital_Nameplate/1/0 with 2 variants (pure/qualified)

[VladimirAlexiev]

There are 229 models.

curl https://v3.admin-shell-io.com/submodels/ > submodels-v3.json
jq ".result[].idShort" submodels-v3.json | wc -l
229

Here is a count by type:

jq ".result[].idShort" submodels-v3.json | sort | uniq -c
      2 "ArticleInformation"
      1 "AssetIdentification"
      4 "BillOfMaterial"
      1 "CarbonFootprint"
      1 "CertificatesAndDeclarations"
      8 "ContactInformation"
      2 "ContactInformations"
      1 "cynapseTeachInService"
      6 "DeviceDescriptionFiles"
      1 "DeviceInfo"
     19 "Document"
     11 "Documentation"
      6 "Electrical_and_Fluid_CAD"
      1 "Electrical_and_FluidCAD"
      1 "FluidCAD"
      8 "HandoverDocumentation"
     33 "Identification"
      1 "ingredients"
      2 "ManufacturerDocumentation"
     16 "MCAD"
     44 "Nameplate"
      1 "nutrition_facts"
      1 "OperationalData"
      1 "PLC_Programming"
      1 "SecurityMetaModelForServer"
      1 "SecuritySettingsForServer"
     27 "Service"
      3 "ServiceNotifications"
     22 "TechnicalData"
      3 "TechnicalSpecification"

To extract the first few useful submodels:

jq ".result[2]"  submodels-v3.json > Nameplate-Weiss.json
jq ".result[3]"  submodels-v3.json > ContactInformation.json
jq ".result[4]"  submodels-v3.json > HandoverDocumentation.json
jq ".result[5]"  submodels-v3.json > TechnicalData.json
jq ".result[9]"  submodels-v3.json > ArticleInformation.json
jq ".result[11]" submodels-v3.json > ServiceNotifications.json
jq ".result[12]" submodels-v3.json > Nameplate-Festo.json
# jq ".result[170]" submodels-v3.json > CarbonFootprint.json # empty

[mristin]

@VladimirAlexiev I moved the issue to admin-shell-io/aas-specs#405 as this is not related to the generation.