Structured Patterns Metamodel Standard Avatar
  1. OMG Specification

Structured Patterns Metamodel Standard — Closed Issues

  • Acronym: SPMS
  • Issues Count: 2
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Issues Descriptions

Enhance PatternSection body to allow for more than raw strings as content

  • Key: SPMS12-1
  • Status: closed  
  • Source: The Software Revolution ( Jason Smith)
  • Summary:

    Consumers of SPMS have requested the ability to include diagrams, pointers to existing documents, etc., in the section bodies.

  • Reported: IPMSS 1.0 — Mon, 21 Sep 2015 13:42 GMT
  • Disposition: Resolved — SPMS 1.2
  • Disposition Summary:

    Provide guidance on using PatternSection::body as a URI for external resource tracking.

    A request was made to allow for richer descriptions in PatternSections than simple strings. The simplest, backward compatible patch for this is to provide guidance such that, if a user enters a simple URI into the body property, that URI is expected to point to an external resource that contains the description for that PatternSection.

    Specifically, Word files were requested. As we have no functionality within the OMG specs for directly embedding this data within a model in a meaningful manner, the URI method is workable.

  • Updated: Mon, 16 Oct 2017 15:15 GMT

Normative references

  • Key: SPMS12-2
  • Legacy Issue Number: 19886
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The normative references include UML 2.5 but MOF 2.4.1: MOF 2.5.1 should be referenced since it’s mutually dependent with UML 2.5.

    There is also now Diagram Definition, 1.1.

  • Reported: IPMSS 1.0 — Thu, 17 Mar 2016 04:00 GMT
  • Disposition: Resolved — SPMS 1.2
  • Disposition Summary:

    Normative references should be updated to most current referred specifications.

    References to UML, MOF, and DD need to be made consistent through prose and XMI files, and should refer to the most current specification available, if the most recent spec does not change backwards compatibility.

  • Updated: Mon, 16 Oct 2017 15:15 GMT