Systems Modeling API and Services Avatar
  1. OMG Specification

Systems Modeling API and Services — Open Issues

  • Acronym: SystemsModelingAPI
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Description of deletion in createCommit row seems wrong

  • Key: SYSMOAS-39
  • Status: open  
  • Source: The MathWorks ( Mr. Alan Moore)
  • Summary:

    The spec says: "DataVersion.identity should be populated with the DataIdentity that will be deleted in the new commit. When a DataIdentity is deleted in a commit, all its versions (DataVersion) are also deleted,"

    This sounds wrong - presumably DataVersions referenced by earlier Commits need to be maintained. This does seem to be the way that the reference implementation behaves.

  • Reported: SystemsModelingAPI 1.0b1 — Wed, 20 Dec 2023 09:45 GMT
  • Updated: Wed, 14 Feb 2024 00:23 GMT

No easy way to retrieve all elements under specified model scope

  • Key: SYSMOAS-14
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Vileiniskis)
  • Summary:

    In the API PIM, under ElementNavigationService, there's a getElements service which is dedicated for dumping the entire model content at a given commit.

    This is an overkill for a use case when only part of the model content (e.g. a package) is required to do analysis (or any other task) on.

    While theoretical a workaround could be used via getRelationshipsByRelatedElement by retrieving all of the owned elements under specified owner, this would result in gazillion separate calls and would not be efficient under slower networks.

    Proposal - introduce a new service getOwnedElements with an ability to collect all of the owned elements recursively under specified root or enrich getElements with optional arguments allowing to achieve the same.

  • Reported: SystemsModelingAPI 1.0b1 — Fri, 14 Jul 2023 10:43 GMT
  • Updated: Wed, 14 Feb 2024 00:22 GMT
  • Attachments:

humanIdentifier attribute is missing in API JSON schema for Commit entity

  • Key: SYSMOAS-11
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Vileiniskis)
  • Summary:

    The API PIM specification has a Record entity with humanIdentifier attribute. Commit entity inherits from Record, therefore it is expected for humanIdentifier attribute to exist in Commit entity as well. This is not the case at the moment when looking at the API JSON schema.

    humanIdentifier is crucial for tool vendors to be able to relate commit UUIDs to version identifiers that are specific to the different versioning schemas used by different tool vendors.

  • Reported: SystemsModelingAPI 1.0b1 — Fri, 14 Jul 2023 09:32 GMT
  • Updated: Wed, 14 Feb 2024 00:22 GMT
  • Attachments: