1        Definition

The description of the capabilities of an M-Environment, an Identified subset of an M-Instance.

2        Functional Requirements

E-Capabilities may not exceed the M-Capabilities of the M-Instance it is part of.

An E-Environment may make none, some, or all its M-Capabilities available, e.g.,:

  • Profile supported by the M-Environment.
  • Data Formats supported by the Items.
  • Data Formats supported by the Basic Data.
  • Services supported (from a Taxonomy).

3        Syntax


4        Semantics

Label Size Description
Header N1 Bytes
·         Standard 9 Bytes The characters “MMM-ECP-V”
·         Version N2 Bytes Major version – 1 or 2 Bytes
·         Dot-separator 1 Byte The character “.”
·         Subversion N3 Bytes Minor version – 1 or 2 Bytes
MInstanceID N4 Bytes Identifier of M-Instance.
MEnvironmentID N5 Bytes Identifier of M-Environment.
ECapabilitiesID N6 Bytes Identifier of the M-Environment’s E-Capabilities
ECapabilitiesData N7 Bytes Set of E-Capabilities Data
·         Profile N8 Bytes  “Baseline”, “Finance”, “Management”, or “High”
·         ItemFormats[] N9 Bytes List of Item Formats supported by M-Environment
o  ItemFormatID N10 Bytes Identifier of Item Format
·         BasicDataFormats N11 Bytes Basic Data Formats supported by M-Environment
o  BasicDataFormatID N12 Bytes Identifiers of Basic Data Format
DescrMetadata N13 Bytes Descriptive Metadata

1.1.5        Data Formats

E-Capabilities require Item Format IDs which are handled Item by Item and Basic Data Format ID.

1.1.6        To Respondents

MPAI requests comments on the Functional Requirements and JSON Syntax and Semantics of E-Capabilities.