epcis-context-simple

[VladimirAlexiev]

• key file: epcis-context-simple.jsonld
  • because of a bug in jsonld-cli not present in JSONLD Playground: https://github.com/digitalbazaar/jsonld-cli/issues/18
  • I had to use "@context": {"type": {"@id":"epcis:bizTransactionType", "@type":"@vocab", "@context":{"@vocab":"https://ns.gs1.org/cbv/BTT-"}}}},
  • instead of the simpler "@context": {"type": {"@id":"epcis:bizTransactionType", "@type":"@vocab", "@context":{"@vocab":"cbv:BTT-"}}}},
• for now I've only edited Example-Type-sourceOrDestination,measurement,bizTransaction.jsonld to:
  • point to that context https://vladimiralexiev.github.io/EPCIS/epcis-context-simple.jsonld
  • use bare words
• the result Example-Type-sourceOrDestination,measurement,bizTransaction.ttl appears correct

@mgh128 , @jmcanterafonseca-iota As decided at the end of the meeting:

• I'll make folders JSONLD-simple-context and Turtle-simple-context and change all examples in these folders to use the simpler context
• Then we can compare Turtle/* to Turtle-simple-context/*: the two must be identical
• Any discrepancy will be due to a bug in one of the contexts

[mgh128]

OK - as Craig and I offered on the call, we can also make any multi-file search/replace changes on a set of examples - but perhaps best if you convert just one example to exactly how you would like it to appear (I think we agreed on bare string values only for the standard CBV code values) and we can convert all the other examples. The offer is there if it saves you time.

[VladimirAlexiev]

• I copied JSON to JSONLD-simple-context and changed all examples in this folder to use the simpler context.
• Produced Turtle-simple-context: all appear to be correct
• @jmcanterafonseca-iota, @mgh128 and @CraigRe: I'll be happy if you find bugs in Turtle-simple-context

The question to JSONLD gurus should be cast in neutral terms: which of epcis-context.jsonld and epcis-context-simple.jsonld do they like better.

Cheers!

[VladimirAlexiev]

@jmcanterafonseca-iota @CraigRe @mgh128 To make the Turtle examples:

• install jena (for riot)
• install up to date jsonld-cli (0.3.0): npm install -g jsonld-cli
• then

  cd Turtle
  make clean
  make

[dakbhavesh]

Hi @VladimirAlexiev, In EPCIS 2.0, we are moving away from providing support for master data as master data will be provided through DigitalLink as forward-looking approach.

Considering DigitalLink approach, Shouldn't we remove all examples related to master data to avoid any confusion?

Note: After discussions at length in our previous calls, we have removed master data-related endpoints from REST bindings.

FYI: @mgh128 , @domguinard

[VladimirAlexiev]

• @mgh128, @CraigRe, @domguinard Should I delete the MasterData examples then?
• Should I also convert and commit Turtle using @jmcanterafonseca-iota's context in this PR?
• @mgh128 or @CraigRe when can you merge this PR?

[CraigRe]

@VladimirAlexiev merging now.

[VladimirAlexiev]

Let's keep it, I hope if I push some more changes they'll also be merged.

In particular, should I switch from https://vladimiralexiev.github.io/EPCIS/epcis-context-simple.jsonld to https://gs1.github.io/EPCIS/epcis-context-simple.jsonld ?