1. OMG Mailing List
  2. Pedigree and Provenance Model and Notation (PPMN) Finalization Task Force 2

Open Issues

  • Issues not resolved
  • Name: ppmn-ftf
  • Issues Count: 79

Issues Summary

Key Issue Reported Fixed Disposition Status
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-68 At line 1015, sentence starting wtih "Additonally, ..." wording is incorrect. PPMN 1.0a1 open
PPMN-65 At line 993, Table 6 the text refers to a .formatRegistry which is not defined anywhere. PPMN 1.0a1 open
PPMN-67 Line 1006 refers to a class that does not exist. PPMN 1.0a1 open
PPMN-66 Line 1006 specifies that EntityRelationshipType inherits a property from ElementRelationship. There is no such inheritance. PPMN 1.0a1 open
PPMN-59 *EntitySnapshot* property creationDate at line 1021 Table 9 already exists in parent class *Entity* PPMN 1.0a1 open
PPMN-49 Line 1006 refers to a class "EntityTypeRelationship" which is not defined. PPMN 1.0a1 open
PPMN-26 EntityComposition and EntityTypeComposition relationships are not defined PPMN 1.0a1 open
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 open
PPMN-45 Line 991, link to "SemanticReference" is incorrect. PPMN 1.0a1 open
PPMN-48 Lines 961, 963, 965, and 1016 all refer to an "EntityComposition" relationship which is not defined. PPMN 1.0a1 open
PPMN-43 EntityTypeSnapshot class in Fig. 3 Entities and Entity Types UML diagram is incorrectly named EntitySnapshotType PPMN 1.0a1 open
PPMN-34 At line 3574, bookmark link "RelationshipKinds" is incorrect. PPMN 1.0a1 open
PPMN-35 Remove Section 12 (SCE Metamodel) and Section 13 (SCE Library) from the specification 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-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-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-23 Lines 960/961 imply that SCEElements have an attribute URI. It does not exist in the SCE Metamodel PPMN 1.0a1 open
PPMN-112 Line 1105 refers to property outputEntities (plural). The property is singular output Entity and represents a collection PPMN 1.0a1 open
PPMN-110 Line 1074 to 1077 are repeated at lines 1081 to 1084. PPMN 1.0a1 open
PPMN-111 Line 1103 refers to inherited property OccurenceRole which does not exist PPMN 1.0a1 open
PPMN-109 EntitySnapshotType is redundant PPMN 1.0b1 open
PPMN-108 Unclear how to use EntitySnapshot and whether it includes EntityRelationships PPMN 1.0b1 open
PPMN-107 Inconsistent and redundant model for DerivedFrom PPMN 1.0b1 open
PPMN-106 Documentation for AlternateOf lacks how the properties are used PPMN 1.0b1 open
PPMN-105 Specializes mentioned but not modeled PPMN 1.0b1 open
PPMN-104 Missing OccurrenceDependencyKind for Guide PPMN 1.0b1 open
PPMN-103 No capability to distinguish creation/generation from output PPMN 1.0b1 open
PPMN-102 Confusion between OccurrenceRelationship and OccurrenceDependency PPMN 1.0b1 open
PPMN-101 Mentions of non-existent class ActivityType PPMN 1.0b1 open
PPMN-100 Definition unnecessarily excludes a person being an Entity. PPMN 1.0b1 open
PPMN-99 Need more precise definition of Custody PPMN 1.0b1 open
PPMN-98 AttributedTo could be useful when Occurrences are known PPMN 1.0b1 open
PPMN-97 isUnique properties need more explanation PPMN 1.0b1 open
PPMN-96 The Parties model is missing typical identification and contact information PPMN 1.0b1 open
PPMN-95 Locations are independent of Parties PPMN 1.0b1 open
PPMN-94 Grammar error in definition of Input PPMN 1.0b1 open
PPMN-93 Unclear difference between Output and Product OccurrenceDependencyKinds PPMN 1.0b1 open
PPMN-92 The word derivee means the opposite from its usage in DerivedFrom PPMN 1.0b1 open
PPMN-84 Unclear semantics of OccurrenceDependency::time PPMN 1.0b1 open
PPMN-81 OccurrenceChain should be a subclass of Occurrence PPMN 1.0b1 open
PPMN-91 InterestedParty could be better defined and related to other Roles PPMN 1.0b1 open
PPMN-88 Should provide a Library of common EntityFormats PPMN 1.0b1 open
PPMN-89 (Structural) split out types from instance modeling PPMN 1.0b1 open
PPMN-87 Metamodel diagram for AcquisitionKind does not show SCE inhteritance PPMN 1.0b1 open
PPMN-86 DerivedFrom::role should use a Kind not a String PPMN 1.0b1 open
PPMN-85 No Vocabulary Terms in the PPMN Library have a conceptURI PPMN 1.0b1 open
PPMN-82 Unclear semantics of sequence in occurrenceHistory PPMN 1.0b1 open
PPMN-73 In the metamodel all comments seem to start with a single space PPMN 1.0a1 open
PPMN-72 No formal mapping to PROV-O ontology PPMN 1.0a1 open
PPMN-71 Ontology needs revamping to make it usable PPMN 1.0a1 open
PPMN-70 Packages in metamodel are missing URIs and ns prefixes PPMN 1.0a1 open
PPMN-69 Package Imports not reflected in the metamodel PPMN 1.0a1 open
PPMN-74 PMN should support Org Chart notation PPMN 1.0a1 open
PPMN-56 Section 6.2 Typographical and Linguistic Conventions and Style are not consistently implemented in the document PPMN 1.0a1 open
PPMN-57 Line 1042 Table 11 description of attribute part is ambiguous PPMN 1.0a1 open
PPMN-8 Sections 7 and 8 (opening paragraphs) are redundant PPMN 1.0a1 open
PPMN-21 Line 908/909 are incorrect. The SEC Metamodel has neither BaseElement nor NamedElement PPMN 1.0a1 open
PPMN-20 Line 906 uses "number of packages" which may not be the intended meaning PPMN 1.0a1 open
PPMN-7 Figures 1 and 2 should be more consistent PPMN 1.0a1 open
PPMN-6 PPMN Elements Specialize SCERootElement not BaseElement PPMN 1.0a1 open
PPMN-37 No Graphical Notation for Properties 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-32 Clarify constraints on PPMN Import inherited from SCE Import PPMN 1.0a1 open
PPMN-29 Line 984 Table 5 Description of attribute part is ambiguous PPMN 1.0a1 open
PPMN-16 AdornmentValue and tAdornmentValue defined in both SCE and PPMN PPMN 1.0a1 open
PPMN-9 In section 8.7 Extensions, Adornment Value and Annotation links are circular 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-36 Occurrence Aggregation PPMN 1.0a1 open
PPMN-15 Annotation and tAnnotationis defined in both PPMN and SCE Sematics XSD. PPMN 1.0a1 open
PPMN-3 Section 6.5 Abbreviations, Table 4 Acronyms contains unused or incorrect entries 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-2 Section 6.6 is a copy/paste of the same section in SDMN dtc/22-01-03 PPMN 1.0a1 open
PPMN-30 Refactor PPMN XSDs based updated method of translating from UML Metamodel Diagrams 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-14 DateTimeValue and tDateTimeValue defined Twice PPMN and SCE Sematics PPMN 1.0a1 open

Issues Descriptions

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, 30 Oct 2023 19:53 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, 30 Oct 2023 19:53 GMT

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

  • Key: PPMN-68
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-65
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

Line 1006 refers to a class that does not exist.

  • Key: PPMN-67
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-66
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-59
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-49
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 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: Wed, 30 Aug 2023 00:34 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: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

Line 991, link to "SemanticReference" is incorrect.

  • Key: PPMN-45
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-48
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-43
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Wed, 30 Aug 2023 00:34 GMT

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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-35
  • Status: open  
  • Source: BPM Advantage Consulting ( 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, 30 Aug 2023 00:34 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: Wed, 30 Aug 2023 00:34 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: Wed, 30 Aug 2023 00:34 GMT
  • Attachments:

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: Wed, 30 Aug 2023 00:34 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: Wed, 30 Aug 2023 00:34 GMT

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

  • Key: PPMN-112
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Thu, 20 Jul 2023 15:04 GMT

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

  • Key: PPMN-110
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Thu, 20 Jul 2023 15:00 GMT

Line 1103 refers to inherited property OccurenceRole which does not exist

  • Key: PPMN-111
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Thu, 20 Jul 2023 14:59 GMT

EntitySnapshotType is redundant

  • Key: PPMN-109
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It adds nothing over EntityType

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:46 GMT
  • Updated: Tue, 18 Jul 2023 18:46 GMT

Unclear how to use EntitySnapshot and whether it includes EntityRelationships

  • Key: PPMN-108
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's unclear how to use Snapshot generally, and how the creationDate is supposed to tie in with the Occurrence(s) that updated it.

    The scope of a snapshot is not clear, and EntityRelationship is not timestamped in the same way.
    If an Occurrence creates and removes some EntityRelationships involving an Entity, how is that represented? ActivityOccurrence::resultingEntityRelationship is not sufficient.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:45 GMT
  • Updated: Tue, 18 Jul 2023 18:45 GMT

Inconsistent and redundant model for DerivedFrom

  • Key: PPMN-107
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Unlike other relationships this has subclasses for the different types of derivation. But also a DerivationKind (though indirectly linked via DerivationType) with largely the same Library of instances (DerivedFrom, QuotedFrom, RevisionOf, SourcedFrom), though missing subclass DescendantOf (which is self-referentially defined).

    BTW there's a missing word "one" in the following under Figure 24
    "DerivationTypes support the definition of the expected kinds of derivations that might result in the generation of one EntityType from or more others."

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:21 GMT
  • Updated: Tue, 18 Jul 2023 18:21 GMT

Documentation for AlternateOf lacks how the properties are used

  • Key: PPMN-106
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It inherits source and target but does not explain the meaning of the direction. I'd guess that the target is the more canonical and the source is the alternate but it should be spelled out.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:14 GMT
  • Updated: Tue, 18 Jul 2023 18:14 GMT

Specializes mentioned but not modeled

  • Key: PPMN-105
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's described in the text of 8.9 but not shown in a diagram or included in the metamodel. It seems useful, to represent the relationship from PROV.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:12 GMT
  • Updated: Tue, 18 Jul 2023 18:12 GMT

Missing OccurrenceDependencyKind for Guide

  • Key: PPMN-104
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    This is one of the 4 classic types of process communication e.g. https://www.brcommunity.com/articles.php?id=b634 - we have the other 3 (input, output, enabler).

    [IDEF0 uses different terms - Control instead of Guide and Mechanism instead of Enabler. Use of MVF would enable this]

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:09 GMT
  • Updated: Tue, 18 Jul 2023 18:09 GMT

No capability to distinguish creation/generation from output

  • Key: PPMN-103
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Unlike PROV which makes it explicit.
    All we have is creationDate, which could refer to a snapshot.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:03 GMT
  • Updated: Tue, 18 Jul 2023 18:03 GMT

Confusion between OccurrenceRelationship and OccurrenceDependency

  • Key: PPMN-102
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's not helped that the descriptions of the properties of OccurrenceRelationship use "dependent", and the properties of Occurrence (Table 14) use "dependency" for both predecessor (OccurrenceRelationships) and occurrenceDependency. It's pretty hard to determine what's canonical vs what's derived. I think that OccurrenceRelationship is intended to be derived from OccurrenceDependency (which involves the more detailed flow of Entities). Another confusing aspect is that OccurrenceDependency is used for outputs: the source of such Dependencies is the Occurrence rather than the Entity produced. Normally (e.g. in UML) the source of a Dependency would be an Entity and it's dependent on the Occurrence that generated/updated it. I think it might be better to rename it. Further confusing is that the PPMNLibrary has a PPMNRelationshipKind of Dependency.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 18:00 GMT
  • Updated: Tue, 18 Jul 2023 18:00 GMT

Mentions of non-existent class ActivityType

  • Key: PPMN-101
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    3 mentions in the text of 8.2 and 8.2.1: should be ActivityOccurrenceType

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 00:53 GMT
  • Updated: Tue, 18 Jul 2023 00:53 GMT

Definition unnecessarily excludes a person being an Entity.

  • Key: PPMN-100
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    At the moment people would be excluded, based on the definition "An individual concept or informational or physical artifact". However there may be use cases where it's required to track chain of custody of a person e.g. a prisoner, a baby/minor, a patient, a VIP, a witness, an asylum seeker, a dead body, a mummy. All being held and transported and transferred between parties.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 00:12 GMT
  • Updated: Tue, 18 Jul 2023 00:12 GMT

Need more precise definition of Custody

  • Key: PPMN-99
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    At the moment it's self-referential "Custody indicates that the source element has custody of the target element."
    There are nuances and legal aspects to consider.
    For example, if someone is working for a company does the company or the employee have "custody" of the Entity they're working on? Legally it's the Company.
    If an Entity is lost or stolen does the finder, or thief, have custody? Legally they do not, apparently.

  • Reported: PPMN 1.0b1 — Tue, 18 Jul 2023 00:02 GMT
  • Updated: Tue, 18 Jul 2023 00:02 GMT

AttributedTo could be useful when Occurrences are known

  • Key: PPMN-98
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The definition says "The AttributedTo relationship is a kind of AssociatedWith relationship that captures the fact that an Entity was created or transformed by some unknown activity or action of a Party."

    However even if the activity detail is known, there may still be value in giving someone specific (out of all those who may have played some role) credit or responsibility for the Entity e.g. in case of support or other inquiries.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 23:57 GMT
  • Updated: Mon, 17 Jul 2023 23:57 GMT

isUnique properties need more explanation

  • Key: PPMN-97
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's not clear what isUnique means in practice. For example 8.4.9, what does it mean for a ResponsibilityRelationship to be unique?
    I assume it means unique to a specific Entity (it should say) but, if isUnique=true, does it allow any time overlap of responsibilities? What if the responsibility is delegated - won't the original still hold?

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 23:42 GMT
  • Updated: Mon, 17 Jul 2023 23:42 GMT

The Parties model is missing typical identification and contact information

  • Key: PPMN-96
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's not clear whether this should be in scope (probably not), but at minimum something should be said about it. There are other standards that could be used for contact info, e.g. vCard, and OMG Commons has basic support for identifiers, and the GLEIF ontology has registration information. In general there are several aspects not addressed, several important for provenance - especially being able to identify the party.

    • naming
    • registration (for companies)
    • jurisdiction
    • identification (many schemes, including for non-human agents)
    • entity type (for companies, but could be used for minors/prisoners)
    • date created/born and ceased
    • software/hardware version (for non-human agents)
  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 23:33 GMT
  • Updated: Mon, 17 Jul 2023 23:33 GMT

Locations are independent of Parties

  • Key: PPMN-95
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Occurrences may be linked to Locations regardless of a Party, so it does not make sense to include the Locations package in the Parties model.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 23:13 GMT
  • Updated: Mon, 17 Jul 2023 23:13 GMT

Grammar error in definition of Input

  • Key: PPMN-94
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It repeats "is an input":
    Input indicates that the target Entity is an input to the source Occurrence is an input during the course of the Occurrence

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 22:51 GMT
  • Updated: Mon, 17 Jul 2023 22:51 GMT

Unclear difference between Output and Product OccurrenceDependencyKinds

  • Key: PPMN-93
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    One says "Output indicates that the target Entity is an output of some kind of the Occurrence.."
    and the other says "Product indicates that the source Occurrence produces or creates the target Entity during the course of the Occurrence."
    It seems both Product and By-product should be subtypes of Output (should at least be documented if not supported by the metamodel) but there is no definition of what would make a Product.

    It's unclear if either would encompass destroying the Entity.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 22:49 GMT
  • Updated: Mon, 17 Jul 2023 22:49 GMT

The word derivee means the opposite from its usage in DerivedFrom

  • Key: PPMN-92
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    In PPMN DerivedFrom::derivee is used to represent the Entity FROM which something was derived; however in English it means the derived element - which is the other named end.
    Quoting a definition:
    "In linguistics, a derivee is a word that is formed from another word by adding affixes or changing the shape of the root. For example, the word "runner" is a derivee of the word "run".

    In general, the word "derivee" means something that is derived from something else. The specific meaning of the word will depend on the context in which it is used.

    Here are some examples of how the word "derivee" is used in a sentence:

    In mathematics, the derivative of a function is its derivee.
    In linguistics, the word "runner" is a derivee of the word "run"."

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 22:32 GMT
  • Updated: Mon, 17 Jul 2023 22:32 GMT

Unclear semantics of OccurrenceDependency::time

  • Key: PPMN-84
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The definition "The time that the Occurrence had the dependency on the Entityā€¯ is unclear in usage when the Occurrences themselves have both a start and end.
    I think the property could safely be deleted.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:33 GMT
  • Updated: Mon, 17 Jul 2023 19:53 GMT

OccurrenceChain should be a subclass of Occurrence

  • Key: PPMN-81
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    That would allow for treating a whole chain as a single occurrence for purposes of abstraction/drill down, and address inconsistencies in the current metamodel (e.g. it would seem that a single Occurrence cannot have a subject Entity or interestedParty since they are properties specific to OccurrenceChain).

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:24 GMT
  • Updated: Mon, 17 Jul 2023 19:45 GMT

InterestedParty could be better defined and related to other Roles

  • Key: PPMN-91
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    For example, I would have thought a Performer would always have an interest.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 19:24 GMT
  • Updated: Mon, 17 Jul 2023 19:24 GMT

Should provide a Library of common EntityFormats

  • Key: PPMN-88
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    If only as an exemplar. For example, the standard graphical formats, HTML, PDF, programming languages, XML, XMI etc

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 19:00 GMT
  • Updated: Mon, 17 Jul 2023 19:16 GMT

(Structural) split out types from instance modeling

  • Key: PPMN-89
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Many people will want to use PPMN just for tracking occurrences (which is the level that PROV works at). Understanding how to do this is made a lot more complex by the fact that all the metamodels are presented along with the type/process level information.
    Proposal: have the instance/occurrence level information in their own self-contained metamodels and the Type extensions separate.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 19:06 GMT
  • Updated: Mon, 17 Jul 2023 19:06 GMT

Metamodel diagram for AcquisitionKind does not show SCE inhteritance

  • Key: PPMN-87
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Figure 52 should show AcquisitionKind inheriting from SemanticReference. the other vocabs do have this.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:47 GMT
  • Updated: Mon, 17 Jul 2023 18:47 GMT

DerivedFrom::role should use a Kind not a String

  • Key: PPMN-86
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    For best practice and consistency

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:40 GMT
  • Updated: Mon, 17 Jul 2023 18:40 GMT

No Vocabulary Terms in the PPMN Library have a conceptURI

  • Key: PPMN-85
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    These terms all inherit from SCE::SemanticElement which is supposed to have a conceptURI. Though not mandatory in the metamodel it seems bad practice that none of the official library elements have such.

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:37 GMT
  • Updated: Mon, 17 Jul 2023 18:37 GMT

Unclear semantics of sequence in occurrenceHistory

  • Key: PPMN-82
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    It's unclear what the sequence should be, or even the meaning of grouping the Occurrences into a Chain. Is the "succession" to be based on timing, dependency, causation? Is it an error if they are not in time sequence?
    How are the occurrenceHistory related to occurrenceRelationships and/or Dependencies?

    BTW the definition should say "in the life of some Entity" as opposed to "NamedElement"

  • Reported: PPMN 1.0b1 — Mon, 17 Jul 2023 18:30 GMT
  • Updated: Mon, 17 Jul 2023 18:30 GMT

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

  • Key: PPMN-73
  • Status: open  
  • Source: Adaptive ( 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: Mon, 10 Jul 2023 19:50 GMT

No formal mapping to PROV-O ontology

  • Key: PPMN-72
  • Status: open  
  • Source: Adaptive ( 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: Mon, 10 Jul 2023 19:45 GMT

Ontology needs revamping to make it usable

  • Key: PPMN-71
  • Status: open  
  • Source: Adaptive ( 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: Mon, 10 Jul 2023 19:43 GMT

Packages in metamodel are missing URIs and ns prefixes

  • Key: PPMN-70
  • Status: open  
  • Source: Adaptive ( 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: Mon, 10 Jul 2023 19:42 GMT

Package Imports not reflected in the metamodel

  • Key: PPMN-69
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    They are shown on Figure 2.

  • Reported: PPMN 1.0a1 — Thu, 6 Jul 2023 20:42 GMT
  • Updated: Mon, 10 Jul 2023 19:33 GMT

PMN should support Org Chart notation

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

    Parties models should support creation of Org Chart type diagrams.

  • Reported: PPMN 1.0a1 — Mon, 10 Jul 2023 18:57 GMT
  • Updated: Mon, 10 Jul 2023 19:18 GMT

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

  • Key: PPMN-56
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Mon, 5 Jun 2023 19:53 GMT

Line 1042 Table 11 description of attribute part is ambiguous

  • Key: PPMN-57
  • Status: open  
  • Source: Infinity Technology Incorporated ( 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: Mon, 5 Jun 2023 17:32 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: Thu, 1 Jun 2023 00:57 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: Thu, 1 Jun 2023 00:57 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: Thu, 1 Jun 2023 00:57 GMT

Figures 1 and 2 should be more consistent


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: Thu, 1 Jun 2023 00:57 GMT

No Graphical Notation for Properties

  • Key: PPMN-37
  • Status: open  
  • Source: Auxilium Technology Group ( John 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, 15 May 2023 19:46 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: Mon, 15 May 2023 19:44 GMT

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: Mon, 15 May 2023 19:43 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: Mon, 15 May 2023 19:09 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: Mon, 8 May 2023 19:55 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: Wed, 3 May 2023 00:47 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: Wed, 3 May 2023 00:47 GMT

Occurrence Aggregation

  • Key: PPMN-36
  • Status: open  
  • Source: Auxilium Technology Group ( John 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, 17 Apr 2023 19:44 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: Mon, 27 Feb 2023 20:29 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: Tue, 14 Feb 2023 00:01 GMT

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: Tue, 14 Feb 2023 00:01 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: Tue, 14 Feb 2023 00:01 GMT
  • Attachments:

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)

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

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