Pedigree and Provenance Model and Notation Avatar
  1. OMG Specification

Pedigree and Provenance Model and Notation — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
PPMN_-27 Line 1006 refers to a class that does not exist. PPMN 1.0a1 open
PPMN_-72 AdornmentValue and tAdornmentValue defined in both SCE and PPMN PPMN 1.0a1 open
PPMN_-29 Update PMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 open
PPMN_-74 Annotation and tAnnotation is defined in both PPMN and SCE Sematics XSD. PPMN 1.0a1 open
PPMN_-13 Lines 960/961 imply that SCEElements have an attribute URI. It does not exist in the SCE Metamodel PPMN 1.0a1 open
PPMN_-28 Update PPMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 open
PPMN_-19 Remove Section 12 (SCE Metamodel) and Section 13 (SCE Library) from the specification PPMN 1.0a1 open
PPMN_-1 In section 8.7 Extensions, Adornment Value and Annotation links are circular PPMN 1.0a1 open
PPMN_-73 Occurrence Aggregation PPMN 1.0a1 open
PPMN_-77 StringValue and tStringValue defined in both PPMN and SCE XSD PPMN 1.0a1 open
PPMN_-78 IntegerValue and tIntegerValue defined in SCE and PPMN XSD PPMN 1.0a1 open
PPMN_-68 No Graphical Notation for Properties PPMN 1.0a1 open
PPMN_-79 DateTimeValue and tDateTimeValue defined Twice PPMN and SCE Sematics PPMN 1.0a1 open
PPMN_-76 tImport and Import defined in both SCE and PPMN xsd PPMN 1.0a1 open
PPMN_-75 Refactor PPMN XSDs based updated method of translating from UML Metamodel Diagrams PPMN 1.0a1 open
PPMN_-5 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 open
PPMN_-3 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 open
PPMN_-12 Sections 7 and 8 (opening paragraphs) are redundant PPMN 1.0a1 open
PPMN_-8 PPMN Elements Specialize SCERootElement not BaseElement PPMN 1.0a1 open
PPMN_-9 Line 908/909 are incorrect. The SEC Metamodel has neither BaseElement nor NamedElement PPMN 1.0a1 open
PPMN_-71 Line 984 Table 5 Description of attribute part is ambiguous PPMN 1.0a1 open
PPMN_-69 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_-70 Clarify constraints on PPMN Import inherited from SCE Import PPMN 1.0a1 open
PPMN_-67 Line 1042 Table 11 description of attribute part is ambiguous PPMN 1.0a1 open
PPMN_-66 Section 6.2 Typographical and Linguistic Conventions and Style are not consistently implemented in the document PPMN 1.0a1 open
PPMN_-63 Packages in metamodel are missing URIs and ns prefixes PPMN 1.0a1 open
PPMN_-62 Ontology needs revamping to make it usable PPMN 1.0a1 open
PPMN_-64 Package Imports not reflected in the metamodel PPMN 1.0a1 open
PPMN_-65 PMN should support Org Chart notation PPMN 1.0a1 open
PPMN_-60 In the metamodel all comments seem to start with a single space PPMN 1.0a1 open
PPMN_-61 No formal mapping to PROV-O ontology PPMN 1.0a1 open
PPMN_-30 Line 1105 refers to property outputEntities (plural). The property is singular output Entity and represents a collection PPMN 1.0a1 open
PPMN_-32 Line 1103 refers to inherited property OccurenceRole which does not exist PPMN 1.0a1 open
PPMN_-31 Line 1074 to 1077 are repeated at lines 1081 to 1084. PPMN 1.0a1 open
PPMN_-26 Line 1006 specifies that EntityRelationshipType inherits a property from ElementRelationship. There is no such inheritance. PPMN 1.0a1 open
PPMN_-25 At line 993, Table 6 the text refers to a .formatRegistry which is not defined anywhere. PPMN 1.0a1 open
PPMN_-23 Line 969, Fig 3 Entities and EntityTypes UML diagram, the name of the association end owned by EntityType, snapshotType, is incorrectly named. PPMN 1.0a1 open
PPMN_-24 At line 1015, sentence starting wtih "Additonally, ..." wording is incorrect. PPMN 1.0a1 open
PPMN_-21 EntityComposition and EntityTypeComposition relationships are not defined PPMN 1.0a1 open
PPMN_-22 *EntitySnapshot* property creationDate at line 1021 Table 9 already exists in parent class *Entity* PPMN 1.0a1 open
PPMN_-20 Line 1006 refers to a class "EntityTypeRelationship" which is not defined. PPMN 1.0a1 open
PPMN_-17 The statement in line 959, "Entities may represent some other thing of interest through EntityURI property," is ambiguous PPMN 1.0a1 open
PPMN_-18 At line 3574, bookmark link "RelationshipKinds" is incorrect. PPMN 1.0a1 open
PPMN_-14 EntityTypeSnapshot class in Fig. 3 Entities and Entity Types UML diagram is incorrectly named EntitySnapshotType PPMN 1.0a1 open
PPMN_-15 Lines 961, 963, 965, and 1016 all refer to an "EntityComposition" relationship which is not defined. PPMN 1.0a1 open
PPMN_-16 Line 991, link to "SemanticReference" is incorrect. PPMN 1.0a1 open
PPMN_-11 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_-10 Line 969 Figure 3 attribute CreationDate is specified for EntitySnapshot when it already exists in its parent class Entity. PPMN 1.0a1 open
PPMN_-7 Line 906 uses "number of packages" which may not be the intended meaning PPMN 1.0a1 open
PPMN_-6 Figures 1 and 2 should be more consistent PPMN 1.0a1 open
PPMN_-4 The content of 8.1 Entities lines 955 to 966 overlap with the content of 8.1.1 Entity PPMN 1.0a1 open
PPMN_-2 Section 6.5 Abbreviations, Table 4 Acronyms contains unused or incorrect entries PPMN 1.0a1 open

Issues Descriptions

Line 1006 refers to a class that does not exist.

  • Key: PPMN_-27
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Lines 1006 uses the class name EntityTypeRelationship which does not exist.

  • Reported: PPMN 1.0a1 — Fri, 30 Jun 2023 19:08 GMT
  • Updated: Sun, 19 May 2024 20:16 GMT

AdornmentValue and tAdornmentValue defined in both SCE and PPMN

  • Key: PPMN_-72
  • Status: open  
  • Source: University of Utah ( Mr. Robert Lario)
  • Summary:

    PPMN should reuse SCE definition, remove from PPMN

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:12 GMT
  • Updated: Wed, 15 May 2024 00:04 GMT

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

  • Key: PPMN_-29
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. 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: Wed, 15 May 2024 00:04 GMT

Annotation and tAnnotation is defined in both PPMN and SCE Sematics XSD.

  • Key: PPMN_-74
  • Status: open  
  • Source: University of Utah ( Mr. 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: Wed, 15 May 2024 00:04 GMT

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

  • Key: PPMN_-13
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Wed, 15 May 2024 00:04 GMT

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

  • Key: PPMN_-28
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. 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: Wed, 15 May 2024 00:04 GMT

Remove Section 12 (SCE Metamodel) and Section 13 (SCE Library) from the specification

  • Key: PPMN_-19
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. Stephen White)
  • Summary:

    The SCE content is defined in the SCE specification (bmi/21-12-09).

  • Reported: PPMN 1.0a1 — Tue, 28 Feb 2023 01:02 GMT
  • Updated: Wed, 15 May 2024 00:04 GMT

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

  • Key: PPMN_-1
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Wed, 15 May 2024 00:04 GMT

Occurrence Aggregation

  • Key: PPMN_-73
  • Status: open  
  • Source: Auxilium Technology Group ( Mr. John C. Butler)
  • Summary:

    Occurrences need the ability to aggregate Occurrences sub-Occurrences without having them necessarily be in a sub-chain. This supports the tying together of different types of Occurrences such as a Custody Occurrence and a Pedigree Occurrence. An example is the loading of grain from a farm into a shipping truck that already has grain in it. This is a combination of the grain as well as custody of the grain passing from the farm or depot to the shipping company.

  • Reported: PPMN 1.0a1 — Sun, 5 Mar 2023 21:00 GMT
  • Updated: Mon, 13 May 2024 19:58 GMT

StringValue and tStringValue defined in both PPMN and SCE XSD

  • Key: PPMN_-77
  • Status: open  
  • Source: University of Utah ( Mr. Robert Lario)
  • Summary:

    Remove from PPMN, PPMN reuses SCE's definition

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:14 GMT
  • Updated: Mon, 13 May 2024 19:54 GMT

IntegerValue and tIntegerValue defined in SCE and PPMN XSD

  • Key: PPMN_-78
  • Status: open  
  • Source: University of Utah ( Mr. Robert Lario)
  • Summary:

    PPMN should reuse SCE definitions, remove from PPMN

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:13 GMT
  • Updated: Mon, 13 May 2024 19:53 GMT

No Graphical Notation for Properties

  • Key: PPMN_-68
  • Status: open  
  • Source: Auxilium Technology Group ( Mr. John C. Butler)
  • Summary:

    PPMN doesn't have a way to graphically show relationships between elements that are otherwise captured as attributes. An example is the location of an Entity or a Party. The metamodel supports capturing the fact that an Entity is at a location and while locations do have a graphical representation, there isn't any given graphical notation for showing that the Entity is at that location. This significantly degrades the ability to graphically show where things are in relation to one-another.

  • Reported: PPMN 1.0a1 — Sun, 5 Mar 2023 21:06 GMT
  • Updated: Mon, 13 May 2024 19:36 GMT

DateTimeValue and tDateTimeValue defined Twice PPMN and SCE Sematics

  • Key: PPMN_-79
  • Status: open  
  • Source: University of Utah ( Mr. 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: Mon, 13 May 2024 19:31 GMT

tImport and Import defined in both SCE and PPMN xsd

  • Key: PPMN_-76
  • Status: open  
  • Source: University of Utah ( Mr. Robert Lario)
  • Summary:

    Remove from PPMN. PPMN reuses SCE

  • Reported: PPMN 1.0a1 — Thu, 12 Jan 2023 18:15 GMT
  • Updated: Mon, 13 May 2024 19:30 GMT

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

  • Key: PPMN_-75
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. 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: Mon, 13 May 2024 19:25 GMT
  • Attachments:
    • solution.docx 568 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)

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

  • Key: PPMN_-5
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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, 13 May 2024 19:22 GMT

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

  • Key: PPMN_-3
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Sat, 4 May 2024 19:32 GMT
  • Attachments:

Sections 7 and 8 (opening paragraphs) are redundant

  • Key: PPMN_-12
  • Status: open  
  • Source: Auxilium Technology Group ( Mr. John C. 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, 15 Apr 2024 19:02 GMT

PPMN Elements Specialize SCERootElement not BaseElement

  • Key: PPMN_-8
  • Status: open  
  • Source: Auxilium Technology Group ( Mr. John C. 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, 15 Apr 2024 19:00 GMT

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

  • Key: PPMN_-9
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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, 25 Mar 2024 19:24 GMT

Line 984 Table 5 Description of attribute part is ambiguous

  • Key: PPMN_-71
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 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_-69
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

Clarify constraints on PPMN Import inherited from SCE Import

  • Key: PPMN_-70
  • Status: open  
  • Source: BPM Advantage Consulting ( Dr. 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: Tue, 9 Jan 2024 18:36 GMT

Line 1042 Table 11 description of attribute part is ambiguous

  • Key: PPMN_-67
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    The description of attribute part of EntityType is ambiguous and needs elaboration. Additionally, part refers to the notion of composition while containment, a different concept, is mentioned in the text.

  • Reported: PPMN 1.0a1 — Mon, 5 Jun 2023 17:31 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Section 6.2 Typographical and Linguistic Conventions and Style are not consistently implemented in the document

  • Key: PPMN_-66
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Section 6.2 in bmi/22-09-01 (PPMN), section 6.2 in dtc/22-01-04 (SCE), and section 6.1.1 in formal/2011-01-03 (BPMN) show identical typographical conventions about references to graphical, non-graphical elements, and references to attributes or model associations. However, it appears that PPMN and SCE do not implement these conventions properly, certainly not in the manner observed in BPMN.

  • Reported: PPMN 1.0a1 — Mon, 5 Jun 2023 16:56 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Packages in metamodel are missing URIs and ns prefixes

  • Key: PPMN_-63
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    Without those, interchange becomes less predictable.
    The nsPrefixes need adding as mof:tags org.omg.xmi.nsPrefix.

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:44 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Ontology needs revamping to make it usable

  • Key: PPMN_-62
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The initial version was created using MOF2RDF rules, which are intended for metamodel management, not a deployable ontology.
    Further, the ontology could use some documentation in the specification.

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:47 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Package Imports not reflected in the metamodel

  • Key: PPMN_-64
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    They are shown on Figure 2.

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:42 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

PMN should support Org Chart notation

  • Key: PPMN_-65
  • Status: open  
  • Source: Auxilium Technology Group ( Mr. John C. Butler)
  • Summary:

    Parties models should support creation of Org Chart type diagrams.

  • Reported: PPMN 1.0a1 — Mon, 10 Jul 2023 18:57 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

In the metamodel all comments seem to start with a single space

  • Key: PPMN_-60
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    This is odd and unnecessary, and could causes glitches in processing/searching

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:51 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

No formal mapping to PROV-O ontology

  • Key: PPMN_-61
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    Annex A contains an informal mapping, but there should also be a mapping ontology, mapping to the PROV-O ontology from W3C.

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:50 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 1105 refers to property outputEntities (plural). The property is singular output Entity and represents a collection

  • Key: PPMN_-30
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Line 1105 refers to property outputEntities (plural). The property is singular output Entity and represents a collection. It must be noted that the symmetrical propety inputEntity is written in the singular form within the same paragraph.

  • Reported: PPMN 1.0a1 — Thu, 20 Jul 2023 15:04 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 1103 refers to inherited property OccurenceRole which does not exist

  • Key: PPMN_-32
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Line 1103 refers to an inherited property OccurrenceRole which does not exists. Rather, it should refer to inherited propery role which is of type OccurrenceRole

  • Reported: PPMN 1.0a1 — Thu, 20 Jul 2023 14:59 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 1074 to 1077 are repeated at lines 1081 to 1084.

  • Key: PPMN_-31
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    The repeated text lines are next to each other. Figure 7 which uses lines 1078 and 1080 is the only thing that separated the identical verbiage.

  • Reported: PPMN 1.0a1 — Thu, 20 Jul 2023 13:44 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 1006 specifies that EntityRelationshipType inherits a property from ElementRelationship. There is no such inheritance.

  • Key: PPMN_-26
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Line 1006 reads as follows: "The kind of EntityTypeRelationship is specified by the type property inherited from ElementRelationship". There is no inheritance between these two classes.

  • Reported: PPMN 1.0a1 — Fri, 30 Jun 2023 18:59 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

At line 993, Table 6 the text refers to a .formatRegistry which is not defined anywhere.

  • Key: PPMN_-25
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    At line 993, Table 6 the text refers to a .formatRegistry, seemingly a class, which is not modeled or referenced in the text anywhere in PPMN or SCE.

  • Reported: PPMN 1.0a1 — Wed, 14 Jun 2023 19:59 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 969, Fig 3 Entities and EntityTypes UML diagram, the name of the association end owned by EntityType, snapshotType, is incorrectly named.

  • Key: PPMN_-23
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    In figure 3, UML diagram Entities and EntityTypes, the name of the association owned by EntityType should be named "typeSnapshot" rather than "snapshotType". This naming format will also maintain consistency with the name "snasphot", the association end owned by Entity.

  • Reported: PPMN 1.0a1 — Tue, 16 May 2023 20:35 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

At line 1015, sentence starting wtih "Additonally, ..." wording is incorrect.

  • Key: PPMN_-24
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    There are several issues with line 1015 sentence starting with: "Additionally, ...": the word "contain" (spelled "conain" in the doc) is used to mean composition, the attribute "parts" is used (no need to make part plural, it is already a collection), and finally it mentions an EntityComposition relationship which does not exist.

  • Reported: PPMN 1.0a1 — Sat, 1 Jul 2023 18:07 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

EntityComposition and EntityTypeComposition relationships are not defined

  • Key: PPMN_-21
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

*EntitySnapshot* property creationDate at line 1021 Table 9 already exists in parent class *Entity*

  • Key: PPMN_-22
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    The property creationDate in Table 9, line 1021, is unnecessary. It already exists in parent class Entity.

  • Reported: PPMN 1.0a1 — Mon, 5 Jun 2023 18:28 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 1006 refers to a class "EntityTypeRelationship" which is not defined.

  • Key: PPMN_-20
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Line 1006 is the only reference to EntityTypeRelationship. This raises the question around the two class names "EntityRelationshipType" and "EntityTypeRelationship" mentioned in the same section 8.1.4. Combined with the fact that fig. 3 shows a derived attribute "part" for EntityTypes, i.e. an aggregation of Composition RelationshipKind amongst associations of an EntityType instance suggest we are missing some constructs in the diagram. At the very least, I believe a clearer text explanation is warranted.

  • Reported: PPMN 1.0a1 — Fri, 19 May 2023 19:21 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

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

  • Key: PPMN_-17
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

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

  • Key: PPMN_-18
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

EntityTypeSnapshot class in Fig. 3 Entities and Entity Types UML diagram is incorrectly named EntitySnapshotType

  • Key: PPMN_-14
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    In Fig. 3 UML diagram Entities and Entity Types, the class representing a snapshot of an Entity Type is incorrectly named EntitySnapshotType. The correct name should be EntityTypeSnapshot, i.e. a snapshot of an entity type rather than the type of an entity snapshot. This is further underscored in line 964, where the term EntityTypeSnapshots is used.

  • Reported: PPMN 1.0a1 — Tue, 16 May 2023 20:19 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Lines 961, 963, 965, and 1016 all refer to an "EntityComposition" relationship which is not defined.

  • Key: PPMN_-15
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    The "EntityComposition relationship is referred to in the text at lines 961, 963, 965, and 1016, but is not defined in the specification and does not exist. The mechanism of composition is defined by SCE RelationshipKind class Composition.

  • Reported: PPMN 1.0a1 — Fri, 19 May 2023 18:44 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

Line 991, link to "SemanticReference" is incorrect.

  • Key: PPMN_-16
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. Yvon Lacasse)
  • Summary:

    Line 991, link to "SemanticReference" lands on section 10 "Parties Model" when it should land on section 12.6.2 SemanticReference. Perhaps it simply can be removed since section 12 SCE Model will be removed from bmi/22-09-01 and a reference to SCE might suffice.

  • Reported: PPMN 1.0a1 — Tue, 16 May 2023 20:41 GMT
  • Updated: Tue, 9 Jan 2024 18:36 GMT

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

  • Key: PPMN_-11
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

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


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

  • Key: PPMN_-7
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

Figures 1 and 2 should be more consistent


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

  • Key: PPMN_-4
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT

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

  • Key: PPMN_-2
  • Status: open  
  • Source: Infinity Technology Incorporated ( Mr. 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: Tue, 9 Jan 2024 18:36 GMT