The primary purpose of this revision of OPM is, based on our experience with the Provenance Challenge 3, to _extend OPM with elements that are necessary to achieve the level of inter-operability required for the challenge_. The timetable for this revision is also tight since we seek to complete a revision of the specification and associated schemas in time for teams to be able to pursue their work, ahead of a special issue related to inter-operability issues around OPM.
Proposed timetable for v1.1:
Please submit your Change Proposal (CP) in this section, according to the ChangeProposalTemplate. The template includes a review section where comments on proposals or counter-proposals can be discussed. Note that Counter Proposals should also appear as a separate page. They are grouped according to the following broad categories.
The proposals were put to the ballot and outcomes are summarised here.
Proposal | Outcome |
---|---|
ChangeProposalFormalization | Adopted |
ChangeProposalMoveCollectionsOut | Adopted |
ChangeProposalMoveTimeToProfile | Rejected |
ChangeProposalRenameWasTriggeredBy | Open: new name required |
ChangeProposalDCNaming | Rejected |
ChangeProposalWasDerivedCannotBeInferred | Adopted |
ChangeProposalDeleteWasDerivedInference | Adopted, but new profile ChangeProposalWasDerivedFromInferrableProfile to work on |
ChangeProposalAnnotations | Work to continue on proposal |
ChangeProposalMultipleRoleLabels | Rejected |
ChangeProposalUseCases | Adopted: please submit use cases. |
ChangeProposalRemoveProcessValues | Adopted |
ChangeProposalRemoveOverlaps | Adopted (Overlaps becomes annotation) |
ChangeProposalRemoveIDs | Rejected |
ChangeProposalDateTime | Adopted |
ChangeProposalDublinCoreMapping | Work to continue |
ChangeProposalMultipleHierarchicalRefinement | Work to continue |
ChangeProposalProfileGuidance | Work to continue |
All information is available from RevisionV1pt1.