Pedigree and Provenance Model and Notation Avatar
  1. OMG Specification

Pedigree and Provenance Model and Notation — Open Issues

  • Acronym: PPMN
  • Issues Count: 28
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
PPMN-34 At line 3574, bookmark link "RelationshipKinds" is incorrect. PPMN 1.0a1 open
PPMN-26 EntityComposition and EntityTypeComposition relationships are not defined PPMN 1.0a1 open
PPMN-21 Line 908/909 are incorrect. The SEC Metamodel has neither BaseElement nor NamedElement PPMN 1.0a1 open
PPMN-30 Refactor PPMN XSDs based updated method of translating from UML Metamodel Diagrams PPMN 1.0a1 open
PPMN-32 Clarify constraints on PPMN Import inherited from SCE Import PPMN 1.0a1 open
PPMN-28 Line 969 Figure 3 attribute CreationDate is specified for EntitySnapshot when it already exists in its parent class Entity. PPMN 1.0a1 open
PPMN-23 Lines 960/961 imply that SCEElements have an attribute URI. It does not exist in the SCE Metamodel PPMN 1.0a1 open
PPMN-20 Line 906 uses "number of packages" which may not be the intended meaning PPMN 1.0a1 open
PPMN-3 Section 6.5 Abbreviations, Table 4 Acronyms contains unused or incorrect entries PPMN 1.0a1 open
PPMN-2 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 open
PPMN-1 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 open
PPMN-24 Line 2356 shows UUID as a PPMN primitive. From observations, it does not appear to be used anywhere in the document PPMN 1.0a1 open
PPMN-29 Line 984 Table 5 Description of attribute part is ambiguous PPMN 1.0a1 open
PPMN-27 The content of 8.1 Entities lines 955 to 966 overlap with the content of 8.1.1 Entity PPMN 1.0a1 open
PPMN-25 The statement in line 959, "Entities may represent some other thing of interest through EntityURI property," is ambiguous PPMN 1.0a1 open
PPMN-22 Line 855 Table 3 specifications for class colors and borders are not consistent within the table and with the diagrams in the document. This issue also addresses other topics with Table 3. PPMN 1.0a1 open
PPMN-19 tImport and Import defined in both SCE and PPMN xsd PPMN 1.0a1 open
PPMN-18 StringValue and tStringValue defined in both PPMN and SCE XSD PPMN 1.0a1 open
PPMN-17 IntegerValue and tIntegerValue defined in SCE and PPMN XSD PPMN 1.0a1 open
PPMN-16 AdornmentValue and tAdornmentValue defined in both SCE and PPMN PPMN 1.0a1 open
PPMN-15 Annotation and tAnnotationis defined in both PPMN and SCE Sematics XSD. PPMN 1.0a1 open
PPMN-14 DateTimeValue and tDateTimeValue defined Twice PPMN and SCE Sematics PPMN 1.0a1 open
PPMN-4 Update PPMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 open
PPMN-5 Update PMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 open
PPMN-9 In section 8.7 Extensions, Adornment Value and Annotation links are circular PPMN 1.0a1 open
PPMN-6 PPMN Elements Specialize SCERootElement not BaseElement PPMN 1.0a1 open
PPMN-7 Figures 1 and 2 should be more consistent PPMN 1.0a1 open
PPMN-8 Sections 7 and 8 (opening paragraphs) are redundant PPMN 1.0a1 open

Issues Descriptions

At line 3574, bookmark link "RelationshipKinds" is incorrect.

  • Key: PPMN-34
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    At line 3574, the bookmark "RelationshipKinds" jumps to section 12.1.2 SCEElement. It does not provide any additional information about RelationshipKinds.

  • Reported: PPMN 1.0a1 — Mon, 30 Jan 2023 16:17 GMT
  • Updated: Mon, 30 Jan 2023 16:17 GMT

EntityComposition and EntityTypeComposition relationships are not defined

  • Key: PPMN-26
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Section 8.1 starting at line 965 contains references to EntityComposition and EntityTypeComposition relationships. These are not defined or modeled in bmi/22-09-01 or dtc/22-01-04.

  • Reported: PPMN 1.0a1 — Sat, 14 Jan 2023 19:03 GMT
  • Updated: Mon, 30 Jan 2023 14:08 GMT

Line 908/909 are incorrect. The SEC Metamodel has neither BaseElement nor NamedElement

  • Key: PPMN-21
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Lines 908 and 909 specify that all elements in PPMN are specializations of SCE BaseElement or NamedElement. The SCE Metamodel has neither.

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 20:40 GMT
  • Updated: Mon, 30 Jan 2023 13:00 GMT

Refactor PPMN XSDs based updated method of translating from UML Metamodel Diagrams

  • Key: PPMN-30
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The current PPMN XSDs were developed with a faulty translation of UML class relationships to the XSD elements.
    To resolve this issue we need to specify the XSD patterns that correspond to the UML class relationships and then update the XSDs.

  • Reported: PPMN 1.0a1 — Mon, 23 Jan 2023 20:15 GMT
  • Updated: Sat, 28 Jan 2023 14:56 GMT
  • Attachments:
    • solution.docx 568 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)

Clarify constraints on PPMN Import inherited from SCE Import

  • Key: PPMN-32
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    The spec doesn't clearly specify the constraints on the types of items that can be imported for a PPMN model.

  • Reported: PPMN 1.0a1 — Sat, 28 Jan 2023 00:05 GMT
  • Updated: Sat, 28 Jan 2023 00:05 GMT

Line 969 Figure 3 attribute CreationDate is specified for EntitySnapshot when it already exists in its parent class Entity.

  • Key: PPMN-28
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    EntitySnapshot specifies an attribute creationDate when it already exists in its parent class Entity.

  • Reported: PPMN 1.0a1 — Sat, 14 Jan 2023 19:29 GMT
  • Updated: Fri, 27 Jan 2023 18:16 GMT

Lines 960/961 imply that SCEElements have an attribute URI. It does not exist in the SCE Metamodel

  • Key: PPMN-23
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Lines 960/961 state "All entities-related classes are ultimately SCEElements and as such have a name, id, URI." SCEElement in the SCE Metamodel has the following attributes: name, id, aliasID, and humanID. There is no URI.

  • Reported: PPMN 1.0a1 — Fri, 13 Jan 2023 19:25 GMT
  • Updated: Fri, 27 Jan 2023 12:33 GMT

Line 906 uses "number of packages" which may not be the intended meaning

  • Key: PPMN-20
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Line 906 specifies: The PPMN specification is organized into a "number" of packages. Although minor and perhaps subjective, the statement might be clearer and more meaningful by stating "set of packages".

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 20:22 GMT
  • Updated: Fri, 27 Jan 2023 12:08 GMT

Section 6.5 Abbreviations, Table 4 Acronyms contains unused or incorrect entries

  • Key: PPMN-3
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Table 4 includes the following acronyms:
    BHMN : not used anywhere in this specification
    SDMNDI: not used anywhere in this specification
    RFC: the acronym is used but refers to "Request for Comments" rather than "Remote Function Call"

  • Reported: PPMN 1.0a1 — Fri, 7 Oct 2022 15:39 GMT
  • Updated: Mon, 23 Jan 2023 20:21 GMT

Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03

  • Key: PPMN-2
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    PPMN section 6.6: Structure of this Document incorrectly copied section 6.6 of SDMN and its clauses.

  • Reported: PPMN 1.0a1 — Mon, 3 Oct 2022 20:03 GMT
  • Updated: Mon, 23 Jan 2023 20:21 GMT
  • Attachments:

Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03

  • Key: PPMN-1
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Section 6.6 Structure of this Document overviews SDMN dtc/22-01-03 and its clauses. Rather, its topic should be PPMN and its clauses.

  • Reported: PPMN 1.0a1 — Tue, 4 Oct 2022 14:57 GMT
  • Updated: Mon, 23 Jan 2023 20:21 GMT

Line 2356 shows UUID as a PPMN primitive. From observations, it does not appear to be used anywhere in the document

  • Key: PPMN-24
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    Section 8.11 Primitives shows UUID as a primitive (line 2356). However it does not appear anywhere in the document and may be unecessary.

  • Reported: PPMN 1.0a1 — Fri, 13 Jan 2023 19:53 GMT
  • Updated: Mon, 23 Jan 2023 14:00 GMT

Line 984 Table 5 Description of attribute part is ambiguous

  • Key: PPMN-29
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    The description of Entity attribute part which is a derived attribute says: the Entity or Entities that is/are contained by the Entity.
    This may be ambiguous and misleading since the notion of containment differs from the notion of composition. The attribute part is derived so we should be explicit about its computation which in this case is the collection of all EntityRelationships of kind Composition from SCE ElementRelationship RelationshipKind.

  • Reported: PPMN 1.0a1 — Sat, 14 Jan 2023 20:20 GMT
  • Updated: Sat, 14 Jan 2023 20:20 GMT

The content of 8.1 Entities lines 955 to 966 overlap with the content of 8.1.1 Entity

  • Key: PPMN-27
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    The content of 8.1 Entities lines 955 to 966 overlap with the content of 8.1.1 Entity.

  • Reported: PPMN 1.0a1 — Sat, 14 Jan 2023 19:17 GMT
  • Updated: Sat, 14 Jan 2023 19:17 GMT

The statement in line 959, "Entities may represent some other thing of interest through EntityURI property," is ambiguous

  • Key: PPMN-25
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    The statement in line 959, "Entities may represent some other thing of interest through EntityURI property," is ambiguous. What kind of relationship is "represent"? Is it a reference, correlation, or some undefined relationship? Depending on the definition of this relationship, we may introduce some inconsistencies in the metamodel.
    Furthermore, table 5 in line 984 defines "entityURI" as "A URI to the Entity". This is ambiguous and difficult to reconcile with line 959.

  • Reported: PPMN 1.0a1 — Fri, 13 Jan 2023 20:18 GMT
  • Updated: Fri, 13 Jan 2023 20:18 GMT

Line 855 Table 3 specifications for class colors and borders are not consistent within the table and with the diagrams in the document. This issue also addresses other topics with Table 3.

  • Key: PPMN-22
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    1. PPMN Class specifies a fill of light yellow. It is, in fact, a radial gradient. The border is a solid black line, but there is a bottom-right shadow that is not mentioned. If it is immaterial, it should be explicit, like "may or may not have a bottom-right shadow."

    2. Parties Class is specified correctly and is consistent with the diagrams, but it differs from all others. For example, it has no fill gradient or shadow.

    3. Why "Parties General Class"? Why not just "Parties Class"?

    4. "Parentheses" is misspelled.

    5. SCE Class has a radial gradient fill rather than solid, as implied. The figure in the table features a grey line. In diagrams, when an SCE class appears in a PPMN diagram, it has a solid black line. When shown in a diagram belonging to the SCE package, it has a grey line.

    6. External class fill is light-colored radial gradient grey.

  • Reported: PPMN 1.0a1 — Fri, 13 Jan 2023 15:29 GMT
  • Updated: Fri, 13 Jan 2023 15:29 GMT

tImport and Import defined in both SCE and PPMN xsd

  • Key: PPMN-19
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    Remove from PPMN. PPMN reuses SCE

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:15 GMT
  • Updated: Thu, 12 Jan 2023 18:15 GMT

StringValue and tStringValue defined in both PPMN and SCE XSD

  • Key: PPMN-18
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    Remove from PPMN, PPMN reuses SCE's definition

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:14 GMT
  • Updated: Thu, 12 Jan 2023 18:14 GMT

IntegerValue and tIntegerValue defined in SCE and PPMN XSD

  • Key: PPMN-17
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    PPMN should reuse SCE definitions, remove from PPMN

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:13 GMT
  • Updated: Thu, 12 Jan 2023 18:13 GMT

AdornmentValue and tAdornmentValue defined in both SCE and PPMN

  • Key: PPMN-16
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    PPMN should reuse SCE definition, remove from PPMN

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:12 GMT
  • Updated: Thu, 12 Jan 2023 18:12 GMT

Annotation and tAnnotationis defined in both PPMN and SCE Sematics XSD.

  • Key: PPMN-15
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    Annotation and tAnnotation are defined in both PPMN and SCE Semantics XSD.

    Recommend PPMN remove definitions and reuse SCE definition

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:09 GMT
  • Updated: Thu, 12 Jan 2023 18:09 GMT

DateTimeValue and tDateTimeValue defined Twice PPMN and SCE Sematics

  • Key: PPMN-14
  • Status: open  
  • Source: University of Utah ( Robert Lario)
  • Summary:

    DateTimeValue and tDateTimeValue is defined in both PPMN and SCE Sematics XSD.

    Recommend PPMN remove definition and reuse SCE definition

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:04 GMT
  • Updated: Thu, 12 Jan 2023 18:04 GMT

Update PPMN to Reflect SCE's Moving from Vocabularies to KindSets

  • Key: PPMN-4
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    SCE is replacing the SCEVocabulary element with the SCEKindSet element (and related elements).
    PPMN uses the vocabulary mechanism and thus will need to be updated appropriately.

  • Reported: PPMN 1.0a1 — Tue, 11 Oct 2022 17:14 GMT
  • Updated: Mon, 9 Jan 2023 20:56 GMT

Update PMN to Reflect SCE's Moving from Vocabularies to KindSets

  • Key: PPMN-5
  • Status: open  
  • Source: BPM Advantage Consulting ( Stephen White)
  • Summary:

    SCE is replacing the SCEVocabulary element with the SCEKindSet element (and related elements).
    PMN uses the vocabulary mechanism and thus will need to be updated appropriately.

  • Reported: PPMN 1.0a1 — Tue, 11 Oct 2022 17:15 GMT
  • Updated: Mon, 9 Jan 2023 20:49 GMT

In section 8.7 Extensions, Adornment Value and Annotation links are circular

  • Key: PPMN-9
  • Status: open  
  • Source: Infinity Technology Incorporated ( Yvon LaCasse)
  • Summary:

    All "Adornment Value" links in section 8.7.1 resolve back to the Adornment Value header 8.7.1.1. They do not provide more information.
    All "Annotation" links in section 8.7.2 resolve back to the "Annotation" header 8.7.1.2. They do not provide more information.

  • Reported: PPMN 1.0a1 — Mon, 24 Oct 2022 13:09 GMT
  • Updated: Mon, 14 Nov 2022 20:46 GMT

PPMN Elements Specialize SCERootElement not BaseElement

  • Key: PPMN-6
  • Status: open  
  • Source: Auxilium Technology Group ( John Butler)
  • Summary:

    Specification says "All elements in PPMN are specializations of SCE BaseElement directly or NamedElement." This is not the case. PPMN elements specialize SCERootElement.

  • Reported: PPMN 1.0a1 — Mon, 24 Oct 2022 10:44 GMT
  • Updated: Mon, 24 Oct 2022 19:17 GMT

Figures 1 and 2 should be more consistent

  • Key: PPMN-7
  • Status: open  
  • Source: Auxilium Technology Group ( John Butler)
  • Summary:

    Figure 2 moves the Delegation and Additional Relationships packages beside Pedigree and Provenance packages. The two diagrams should be more consistent or one should be removed.

  • Reported: PPMN 1.0a1 — Mon, 24 Oct 2022 10:55 GMT
  • Updated: Mon, 24 Oct 2022 19:17 GMT

Sections 7 and 8 (opening paragraphs) are redundant

  • Key: PPMN-8
  • Status: open  
  • Source: Auxilium Technology Group ( John Butler)
  • Summary:

    The initial text in chapter 8 is redundant with the text in chapter 7. One or the other should be changed to remove the redundancy.

  • Reported: PPMN 1.0a1 — Mon, 24 Oct 2022 10:58 GMT
  • Updated: Mon, 24 Oct 2022 19:17 GMT