☜	OMI - Implementations Draft MDC Standard					☞

A.1 Implementations

A conforming implementation shall

• correctly execute all requests and responses conforming to both this standard and the implementation-defined extensions to this standard;
• reject all messages that contain errors, where such error detection is required by this standard;
• be accompanied by a document which provides a definition of all implementation-defined extensions and a conformance statement of the form:
  • xxx version v implements X11.2‑yyyy with the following conformance specification:
  followed by a table or equivalent presentation of the features shown in table A.1 with the implementation’s options or values supplied.

An MDC conforming implementation shall be a conforming implementation except that the conforming document shall be this standard together with any such current MDC documents that the vendor chooses to implement. The conformance statement shall be of the form:

• xxx version v implements X11.2‑yyyy as modified by the following MDC documents:
  ddd (MDC status sss)
  with the following conformance specification:

followed by a table or equivalent presentation of the features shown in table A.1 with the implementation’s options or values supplied.

An MDC strictly conforming implementation is an MDC conforming implementation whose MDC modification documents only have MDC Type A status.

A <National Body> conforming implementation is an implementation conforming to 1 of the above options in which any requirements are replaced by the <National Body> requirements and other extensions required by the <National Body> are implemented.

An implementation may claim more than 1 level of conformance if it provides a switch by which the user is able to select the conformance level.

Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.

Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.

This page most recently updated on 14-Nov-2023, 21:50:41.

For comments, contact Ed de Moel (demoel@jacquardsystems.com)