Problems re EPCIS TraceabilityEvents

Created by: VladimirAlexiev

• Is https://uncefact.github.io/spec-untp/docs/specification/DigitalProductPassport#traceabilityevent conformant to https://uncefact.github.io/spec-untp/docs/specification/TraceabilityEvents ?
• https://uncefact.github.io/spec-untp/docs/specification/TraceabilityEvents links to the EPCIS home page where one can download a 200p PDF.
  • Also link to https://ref.gs1.org/epcis/ where one can browse and search classes, props and code lists
• https://uncefact.github.io/spec-untp/docs/specification/DigitalProductPassport#eventtypecode (can be edited in https://jargon.sh/user/unece/DigitalProductPassport/v/working/editor#) has brief event descriptions, eg aggregation: "event describing the grouping of products such as placing bales of cotton on a pallet" Shouldn't you use official descriptions as per eg https://ref.gs1.org/epcis/AggregationEvent? As a minimum, the same eventType describes aggregation and disaggregation @nissimsan Should the rest be here in UNTP, or in the Traceability project?
• https://jargon.sh/user/unece/traceabilityEvents is an attempt to remodel https://ref.gs1.org/epcis. EPCIS indeed it can take plenty of refactoring since it carries a heavy backward-compatibility baggage. (I was deeply involved in the semantic efforts of EPCIS 2.0, so can provide some feedback)

Eg comparing https://jargon.sh/user/unece/traceabilityEvents/v/working/artefacts/readme/render#transactionevent to https://ref.gs1.org/epcis/TransactionEvent

• sourceParty, destinationParty are imprecise:
  • should be multiple
  • can be Party or Location (i.e. Organization or Place), see https://ref.gs1.org/epcis/SourceOrDestination
  • has a role from https://ref.gs1.org/cbv/SDT
  • applies to all events
• eventTime, readPoint are missing but these are the fundamental dimensions WHEN and WHERE
• etc etc etc