small fixes to examples

[VladimirAlexiev]

• move Example_9.6.1-ObjectEvent-with-error-declaration.jsonld to WithErrorDeclaration
• declare rdfs prefix in Example_9.6.1-with-comment.jsonld (for rdfs:comment)
• fix schemaVersion in ErrorDeclarationAndCorrectiveEvent.jsonld
• remove format from Example-Type-sourceOrDestination,measurement,bizTransaction.jsonld
• add epcis context to Example_9.8.1-improved.jsonld

@CraigRe, @mgh128 and @jmcanterafonseca-iota : should I start stripping URI prefixes from lookup values and leaving only "bare words" in the same branch fix-examples?

[VladimirAlexiev]

@CraigRe, @mgh128 and @jmcanterafonseca-iota : should I start stripping URI prefixes from lookup values and leaving only "bare words" in the same branch fix-examples?

[mgh128]

@CraigRe, @mgh128 and @jmcanterafonseca-iota : should I start stripping URI prefixes from lookup values and leaving only "bare words" in the same branch fix-examples?

Let's discuss on the call today to be sure, but I think we were intending to promote "bare words" for standard CBV values, to provide greater consistency to JSON-only users - e.g. "bizStep" : "shipping" rather than bare words, full URI or CURIE - though I may have misremembered from the last time I was on a call.