ISO/TC 184/SC 4/WG 11 - Implementation methods and conformance methods

This document specifies the transformation of SysML (ISO/IEC 19514:2017) constructs to XSD (World Wide Web Consortium's XML schema definition language) constructs for the purpose of representing the SysML model represented in XMI (ISO/IEC 19509:2014) as XML (World Wide Web Consortium's XML) schemas. The specified mapping is a one-way transformation from SysML information model represented in XMI into an XML schema. These limitations make the mapping unsuitable for the transformation of arbitrary SysML models to XML schemas. The following are within the scope of this document: —   the specification of the structure, components, and conventions of the XSD for the STEP (ISO 10303-1) XML implementation method; —   the transformation of SysML metamodel constructs represented in XMI to XSD constructs for the purpose of representing SysML information models as XML schemas. The following are outside the scope of this document: —   the transformation of SysML metamodel constructs into XSD constructs that are not used in the STEP extended architecture; —   the transformation of SysML metamodel constructs into XSD constructs for other purposes than representing SysML constructs as STEP concepts; —   codes and scripts to transform SysML XMI to XSD schema; —   the transformation of SysML constraints (OCL, see ISO/IEC 19507) into Schematron (see ISO/IEC 19757‑3).

This document specifies a mapping of SysML (ISO/IEC 19514:2017) constructs to EXPRESS (ISO 10303-11:2004) elements for the purpose of representing SysML model represented in XMI (ISO/IEC 19509:2014) as EXPRESS (ISO 10303-11:2004) schemas. The specified mapping is a one-way transformation from SysML information model represented in XMI into an EXPRESS schema. NOTE      Due to this limitation 10303-16 does not define the transformation of arbitrary SysML models to EXPRESS. The following are within the scope of this document: —   the transformation of SysML metamodel constructs represented in XMI to EXPRESS elements for the purpose of representing SysML information models as EXPRESS schemas. The following are outside the scope of this document: —   the transformation of SysML metamodel constructs into EXPRESS elements that are not used in the STEP Extended Architecture. NOTE      The STEP Extended Architecture is defined in References [8], [9] and [10]. —   the transformation of SysML metamodel constructs into EXPRESS elements for other purposes than representing SysML constructs as STEP concepts; —   codes and scripts to transform SysML XMI to EXPRESS schema; —   the transformation of SysML constraints (OCL[5]) into EXPRESS global and local rules; —   the transformation of EXPRESS elements into SysML constructs.

This document specifies the definition for services at the point of interaction between a client and server. The following are within the scope of this document: —   the specification of the structure, components and conventions for domain- and technology-independent services implementation methods for STEP (ISO 10303-1); —   transformation of the SysML metamodel constructs to OpenAPI constructs for RESTful web services (see OpenAPI:3.0.0[25] and IETF RFC7231). The following are outside the scope of this document: —   domain specific services definitions; —   the transformation of SysML metamodel constructs into OpenAPI constructs that are not used in the STEP extended architecture[12][13]; —   the transformation of SysML metamodel constructs into OpenAPI constructs for other purposes than representing SysML constructs as STEP concepts; —   codes and scripts to transform SysML XMI to OpenAPI schema; —   the transformation of SysML constraints into OpenAPI schema; —   implementation of technology-specific services definitions other than RESTful OpenAPI; —   definition of management and maintenance of information and data on a server.

ISO/TS 10303-26:2011 specifies a binary representation of EXPRESS-driven data using the Hierarchical Data Format Version 5 (HDF5).

ISO 10303-28:2007 specifies the way in which an XML representation described by an XML schema can be used in the exchange of data that is described by an EXPRESS schema.

ISO/TS 10303-25:2005 specifies a mapping from the EXPRESS data specification language into the Object Management Group's (OMG) Unified Modeling Language (UML), for the purpose of generating files conforming to the OMG XML Meta-data Interchange standard.

ISO 10303-14:2005 specifies a language for specifying relationships between data that are governed by EXPRESS schemas, and for specifying alternate views of data that are governed by EXPRESS schemas. The language is called EXPRESS-X. EXPRESS-X is a structural data mapping language. It consists of language elements that allow an unambiguous specification of a relationship between EXPRESS schemas. The following are within the scope of ISO 10303-14:2005: - mapping of data governed by one EXPRESS schema to data governed by another EXPRESS schema; - mapping of data governed by one version of an EXPRESS schema to data governed by another version of that EXPRESS schema, where the two schemas have different names; - specification of requirements for data translators for data sharing and data exchange applications; - specification of alternate views of data defined by an EXPRESS schema; - an alternate notation for application protocol mapping tables; - bidirectional mappings where mathematically possible; - specification of constraints that may be evaluated against data produced by mapping.

ISO 10303 specifies a language by which aspects of product data can be defined. The language is called EXPRESS. ISO 10303-11:2004 also specifies a graphical representation for a subset of the constructs in the EXPRESS language. This graphical representation is called EXPRESS-G. EXPRESS is a data specification language as defined in ISO 10303-1. It consists of language elements that allow an unambiguous data definition and specification of constraints on the data defined. The following are within the scope of ISO 10303-11:2004: data types; constraints on instances of the data types. The following are outside the scope of this part of ISO 10303: definition of database formats; definition of file formats; definition of transfer formats; process control; information processing; exception handling. EXPRESS is not a programming language.

ISO/TS 10303-35:2003 specifies the abstract test methods and requirements for conformance testing of an implementation of a language binding of the Standard Data Access Interface (SDAI). Since the SDAI is specified independently of any programming language, the abstract test methods presented in ISO/TS 10303-35:2003 are applicable to all SDAI language bindings. The abstract test methods support as well the various implementation classes as specified in ISO 10303-22:1998. The following are within the scope of ISO/TS 10303-35:2003: abstract test methods for software systems that implement the SDAI; the specification, in a manner that is independent of any SDAI language binding, of the methods and approaches for testing of various SDAI operations; the specification and documentation of abstract test cases. The following are outside the scope of ISO/TS 10303-35:2003: the development of test data and/or test programs for specific language bindings; the specification of test methods, algorithms, or programs for the conformance testing of applications that interact with SDAI implementations; the architecture and implementation approach for a conformance test system that realizes the test methods specified in ISO/TS 10303-35:2003.

This part of ISO 10303 specifies a C programming language late binding of the capability specified in ISO 10303-22 - Standard data access interface (SDAI). This binding is a late binding and as such, none of the constants, data types, and functions depend on the application schema being accessed. The following are within the scope of this part of ISO 10303: — access to and manipulation of data types and entities which are specified in ISO 10303-22; — convenience functions suitable to this language binding; — late binding requirements specified in ISO 10303-22. The following are outside the scope of this part of ISO 10303: — memory arrangement of data structures used by implementations of this part of ISO 10303; — early binding requirements as specified in ISO 10303-22; — all items listed as out of scope in ISO 10303-22.

This part of ISO 10303 specifies the abstract test methods for conformance testing of an implementation of an ISO 10303 Application Protocol (AP). The scope is limited to the following implementation methods: — preprocessors that claim to generate 10303 schema instances represented as exchange structures as defined by ISO 10303-21; — postprocessors that claim to accept and process 10303 schema instances represented as exchange structures as defined by ISO 10303-21; — preprocessors that claim to generate 10303 schema instances and use the SDAI interface as defined in ISO 10303-22 to populate an SDAI implementation with these schema instances; — postprocessors that claim to accept 10303 schema instances and use the SDAI interface as defined in ISO 10303-22 to extract schema instances from an SDAI implementation. The following are within the scope of this part of ISO 10303: — the conformance assessment process undertaken to evaluate the conformity of an implementation of an ISO 10303 application protocol. The abstract test methods are independently applicable to implementation methods based on ISO 10303-21 and ISO 10303-22; — the methods to be followed by the testing laboratory using executable test cases (ETC). The methods presented are abstract, that is, they are independent of the implementation under test (IUT). The method descriptions cover the different steps from abstract test case (ATC) selection to test case report production. The following is outside the scope of this part of ISO 10303: — the generation of executable test cases from abstract test cases. This part of ISO 10303 does not include abstract test methods for conformance testing of application protocol independent implementations of the Standard Data Access Interface (SDAI) -- ISO 10303-22.

This part of ISO 10303 specifies a binding of the Java1) programming language to application data modelled in EXPRESS, ISO 10303-11 and to the standard data access interface, ISO 10303-22. It also specifies an import and export mechanism for data according to the clear text encoding of the exchange structure, ISO 10303-21. A further extension is that SDAI repositories can be created, deleted and linked while the SDAI session is open. Dynamically linking SDAI repositories through a network like Internet or Intranet allows accessing and changing of remote data. In addition to the scope of ISO 10303-22 the scope of this part of ISO 10303 contains: — creating, deletion and linking of the data repositories during an SDAI session; — specific support for linking a remote data repository through a network like Internet or Intranet; — convenience interfaces, classes, fields and methods suitable to this Java programming language binding; — implementation mechanisms for the handling of errors as specified in ISO 10303-22; — import from and export to the clear text encoding of the exchange structure as specified in ISO 10303-21. 1) Java is the trade mark of a product supplied by Sun Microsystems, Inc. This information is given for the convenience of users of this part of ISO 10303 and does not constitute an endorsement by ISO of the product name. Equivalent products may be used if they can be shown to lead to the same result. TECHNICAL SPECIFICATION ISO/TS 10303-27:2000(E)

This part of ISO 10303 specifies the implementation of the functional interface specified in the standard data access interface (SDAI), ISO 10303-22, in the C++ programming language. The following are within the scope of this part of ISO 10303: — access to and manipulation of data types and entities which are specified in ISO 10303-22; — convenience functions suitable to this language binding; — binding of functions to operations and attributes specified in ISO 10303-22 with the linking of application schema definition at either compile-time or run-time; — implementation mechanisms for the handling of errors as specified in ISO 10303-22; — implementation mechanisms for the validation of constraints as specified in ISO 10303-22. The following is outside the scope of this part of ISO 10303: — all items listed as out of scope in ISO 10303-22.

ISO/TS 10303-28:2003 specifies use of the Extensible Markup Language (XML) to represent schemas specified using the EXPRESS data specification language, ISO 10303-11, and data that is governed by EXPRESS schemas. The following are within the scope of ISO/TS 10303-28:2003: specification of XML markup declarations that enable EXPRESS schemas to be represented using XML; specification of a single XML markup declaration set that is independent of the EXPRESS schema and formally describes the XML representation of data governed by any schema; NOTE 1 XML markup declarations specified using this method are referred to as late bound, in that they may be used without change to represent data governed by any EXPRESS schema. ISO/TS 10303-28:2003 allows for a number of choices in representing the data. for an arbitrary EXPRESS schema, specification of an XML markup declaration set that corresponds to the schema and formally describes the XML representation of data governed by that schema; NOTE 2 XML markup declarations specified using these methods are referred to as early bound, in that they are specific to a given EXPRESS schema. specification of the mapping between XML markup declarations corresponding to a specific schema and the XML markup declarations independent of any schema; specification of the form of XML documents containing EXPRESS schemas and data governed by EXPRESS schemas; specification of the representation of EXPRESS primitive data type values as element content and as XML attribute values. The following are outside the scope of ISO/TS 10303-28:2003: specification of XML markup declarations corresponding to an EXPRESS schema that depend on the semantic intent of the EXPRESS schema; specification of mappings from XML markup declarations to an EXPRESS schema; NOTE 3 Given a set of XML markup declarations and one or more corresponding data sets, it is feasible to create an EXPRESS schema that captures the semantic intent of the data. However, this requires an understanding of the meaning and use of the data that may not be captured by the XML markup declarations. specification of the mapping to an EXPRESS schema from an XML representation of that schema; specification of the mapping to an EXPRESS schema from XML markup declarations that have been derived from that schema; any mapping to or use of XML schema.

Modifies the text of ISO 10303-21:1994. Involves changes, corrections, clarifications and editorial modifications.

La présente partie de l'ISO 10303 définit un langage de modélisation des données de produits. Ce langage s'appelle EXPRESS. La présente partie de l'ISO 10303 définit également une représentation graphique d'un sous-ensemble du langage EXPRESS. Cette représentation graphique s'appelle EXPRESS-G.EXPRESS est un langage de structuration de données tel que défini dans l'ISO 10303-1. Il se compose d'éléments de langage qui permettent une définition des données et une spécification des contraintes sur les données spécifiées, sans ambiguïté. Les éléments suivants figurent dans le domaine d'application : types de données ; contraintes sur les instances des types de données. Les éléments suivants ne figurent pas dans le domaine d'application de la présente partie de l'ISO 10303 : définition des formats de bases de données ; définition des formats de fichiers ; définition des formats de transfert ; contrôle dynamique des informations ; traitement de l'information ; traitement des exceptions.EXPRESS n'est pas un langage de programmation.

Specifies an exchange structure format using a clear text encoding of product data for which the conceptual model is specified in the EXPRESS language. The file format is suitable for the transfer of product data among computer systems. Specifies the mapping from this language to the syntax of the exchange structure.