Pedigree and Provenance Model and Notation Avatar
  1. OMG Specification

Pedigree and Provenance Model and Notation — Closed Issues

  • Acronym: PPMN
  • Issues Count: 32
  • Description: Issues resolved by a task force and approved by Board
Open Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
PPMN-2 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-9 In section 8.7 Extensions, Adornment Value and Annotation links are circular PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-7 Figures 1 and 2 should be more consistent PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-3 Section 6.5 Abbreviations, Table 4 Acronyms contains unused or incorrect entries PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-20 Line 906 uses "number of packages" which may not be the intended meaning PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-21 Line 908/909 are incorrect. The SEC Metamodel has neither BaseElement nor NamedElement PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-27 The content of 8.1 Entities lines 955 to 966 overlap with the content of 8.1.1 Entity PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-8 Sections 7 and 8 (opening paragraphs) are redundant PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-6 PPMN Elements Specialize SCERootElement not BaseElement PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-1 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-23 Lines 960/961 imply that SCEElements have an attribute URI. It does not exist in the SCE Metamodel PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-35 Remove Section 12 (SCE Metamodel) and Section 13 (SCE Library) from the specification PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-49 Line 1006 refers to a class "EntityTypeRelationship" which is not defined. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-44 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 $issue.fixedSpecification.name Deferred closed
PPMN-68 At line 1015, sentence starting wtih "Additonally, ..." wording is incorrect. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-26 EntityComposition and EntityTypeComposition relationships are not defined PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-25 The statement in line 959, "Entities may represent some other thing of interest through EntityURI property," is ambiguous PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-43 EntityTypeSnapshot class in Fig. 3 Entities and Entity Types UML diagram is incorrectly named EntitySnapshotType PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-48 Lines 961, 963, 965, and 1016 all refer to an "EntityComposition" relationship which is not defined. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-45 Line 991, link to "SemanticReference" is incorrect. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-28 Line 969 Figure 3 attribute CreationDate is specified for EntitySnapshot when it already exists in its parent class Entity. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-34 At line 3574, bookmark link "RelationshipKinds" is incorrect. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-59 *EntitySnapshot* property creationDate at line 1021 Table 9 already exists in parent class *Entity* PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
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 $issue.fixedSpecification.name Deferred closed
PPMN-66 Line 1006 specifies that EntityRelationshipType inherits a property from ElementRelationship. There is no such inheritance. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-65 At line 993, Table 6 the text refers to a .formatRegistry which is not defined anywhere. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-67 Line 1006 refers to a class that does not exist. PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-4 Update PPMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-5 Update PMN to Reflect SCE's Moving from Vocabularies to KindSets PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-29 Line 984 Table 5 Description of attribute part is ambiguous PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-56 Section 6.2 Typographical and Linguistic Conventions and Style are not consistently implemented in the document PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed
PPMN-57 Line 1042 Table 11 description of attribute part is ambiguous PPMN 1.0a1 $issue.fixedSpecification.name Deferred closed

Issues Descriptions

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

  • Key: PPMN-2
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT
  • Attachments:

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

  • Key: PPMN-9
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Figures 1 and 2 should be more consistent


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

  • Key: PPMN-3
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-20
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-21
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-27
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Sections 7 and 8 (opening paragraphs) are redundant

  • Key: PPMN-8
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

PPMN Elements Specialize SCERootElement not BaseElement

  • Key: PPMN-6
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-1
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-23
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-35
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-49
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 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-44
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-68
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

EntityComposition and EntityTypeComposition relationships are not defined

  • Key: PPMN-26
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-25
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-43
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-48
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Line 991, link to "SemanticReference" is incorrect.

  • Key: PPMN-45
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-28
  • Status: closed  
  • Source: Infinity Technology Incorporated ( Mr. 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT
  • Attachments:

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

  • Key: PPMN-34
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-59
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 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: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-66
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-65
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Line 1006 refers to a class that does not exist.

  • Key: PPMN-67
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-4
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-5
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Line 984 Table 5 Description of attribute part is ambiguous

  • Key: PPMN-29
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

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

  • Key: PPMN-56
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT

Line 1042 Table 11 description of attribute part is ambiguous

  • Key: PPMN-57
  • Status: closed  
  • 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
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    This Issue was not resolved in this Task Force and was automatically deferred to the next Task Force

  • Updated: Tue, 9 Jan 2024 18:44 GMT