| Integrated generic resource: Fundamentals of product description and support | ISO 10303-41:2021(E) © ISO |
The subject of the application_context_schema is the applicable usages of product data. This schema provides a mechanism for application protocols to define a frame of reference or context that applies to particular sets of product data.
This schema also provides a means to identify application protocols.
This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following EXPRESS declaration begins the application_context_schema and identifies the necessary external references.Each implementation of an AP that uses this schema and that encodes entity names shall use the encoding specified in Annex A. Each reference to this schema in an open system shall use the identifier encoding specified in Annex B. This schema is illustrated in Annex D using the EXPRESS-G notation.
EXPRESS specification:
*)
SCHEMA application_context_schema;
REFERENCE FROM
basic_attribute_schema
--
ISO 10303-41
(description_attribute,
description_attribute_select,
get_description_value,
get_id_value,
id_attribute,
id_attribute_select);
REFERENCE FROM
date_time_schema
--
ISO 10303-41
(year_number);
REFERENCE FROM
language_schema
--
ISO 10303-41
(language);
REFERENCE FROM
management_resources_schema
--
ISO 10303-41
(identification_assignment);
REFERENCE FROM
person_organization_schema
--
ISO 10303-41
(organization);
REFERENCE FROM
support_resource_schema
--
ISO 10303-41
(identifier,
label,
text);
(*
NOTE 1 The schemas referenced above are specified in the following parts:
basic_attribute_schema ISO 10303-41 date_time_schema ISO 10303-41 language_schema ISO 10303-41 management_resources_schema ISO 10303-41 person_organization_schema ISO 10303-41 support_resource_schema ISO 10303-41
NOTE 2 See Annex D for a graphical representation of this schema.
The meaningful exchange of product data requires the identification of the application context in which that product data is defined. An application context may have several context elements. Each context element may be referenced by a different set of product data.
EXPRESS specification:
*)
TYPE
acs_description_attribute_select
=
SELECT
BASED_ON
description_attribute_select
WITH
(application_context);
END_TYPE;
(*
EXPRESS specification:
*)
TYPE
acs_id_attribute_select
=
SELECT
BASED_ON
id_attribute_select
WITH
(application_context);
END_TYPE;
(*
EXPRESS specification:
*)
TYPE
exchange_identification_context_select
=
SELECT
(identification_assignment,
organization);
END_TYPE;
(*
EXPRESS specification:
*)
ENTITY application_context;
application : label;
DERIVE
description : text := get_description_value(SELF);
id : identifier := get_id_value(SELF);
INVERSE
context_elements : SET[1:?] OF application_context_element FOR frame_of_reference;
WHERE
WR1: SIZEOF(USEDIN(SELF, 'BASIC_ATTRIBUTE_SCHEMA.' + 'DESCRIPTION_ATTRIBUTE.DESCRIBED_ITEM')) <= 1;
WR2: SIZEOF(USEDIN(SELF, 'BASIC_ATTRIBUTE_SCHEMA.' + 'ID_ATTRIBUTE.IDENTIFIED_ITEM')) <= 1;
END_ENTITY;
(*
Attribute definitions:
application: the label by which the application_context is known.
NOTE 1 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
description: the text that characterizes the application_context.
NOTE 2 The description attribute aids in defining the usage of product data in an application_context.
NOTE 3 This attribute is an upwardly compatible addition to application_context as specified in ISO 10303-41:1994.
id: the identifier that distinguishes the application_context.
NOTE 4 This attribute is an upwardly compatible addition to application_context as specified in ISO 10303-41:1994.
NOTE 5 The context in which id is used as a discriminating characteristic can be identified in an annotated Express schema that uses or specializes this entity, or by default, in an agreement of common understanding between partners sharing this information.
context_elements: the set of instances of the entity data type application_context_element that defines the various aspects of the application_context.
Formal propositions:
WR1: Each application_context shall be the described_item in at most one description_attribute.
NOTE 6 The description_attribute data type is defined in basic_attribute_schema of this part of ISO 10303.
WR2: Each application_context shall be the identified_item in at most one id_attribute.
NOTE 7 The id_attribute data type is defined in basic_attribute_schema of this part of ISO 10303.
NOTE 8 A template for constraining the population of the entity data types defined in the basic_attribute_schema is described in annex E.
An application_context_element may be either a library_context or a product_concept_context, or a product_context, or a product_definition_context.
EXPRESS specification:
*)
ENTITY application_context_element
SUPERTYPE OF (ONEOF (library_context,
product_concept_context,
product_context,
product_definition_context));
name : label;
frame_of_reference : application_context;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the application_context_element is known.
EXAMPLE 'Functional definition', 'physical definition', 'usage occurrence', and 'manufacturable definition' are examples of names.
frame_of_reference: the application_context of which this application_context_element is a member.
NOTE 1 The role of application_context_relationship can be defined in the annotated EXPRESS schemas that use or specialize this entity, or by default, in an agreement of common understanding between the partners sharing this information.
NOTE 2 Without any further specialization, this relationship does not imply that the product data associated with relating_context are also associated with the related_context.
NOTE 3 Relationships represented using this entity may be parent child relationship. Annotated EXPRESS schemas that use or specialize this entity specify whether or not the relationship is directed.
NOTE 4 This entity, together with the application_context entity, is based on the relationship template that is described in annex E.3.
EXPRESS specification:
*)
ENTITY application_context_relationship;
name : label;
description :
OPTIONAL
text;
relating_context : application_context;
related_context : application_context;
END_ENTITY;
(*
Attribute definitions:
name: the label by which the application_context_relationship is known.
description: the text that characterizes the application_context_relationship. The value of the attribute need not be specified.
relating_context: one of the instances of application_context that is a part of the relationship.
NOTE 5 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
related_context: the other instance of application_context that is a part of the relationship. If one element of the relationship is dependent upon the other, this attribute shall be the dependent one.
NOTE 6 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
EXPRESS specification:
*)
ENTITY application_protocol_definition;
status : label;
application_interpreted_model_schema_name : label;
application_protocol_year : year_number;
application : application_context;
END_ENTITY;
(*
Attribute definitions:
status: the label that provides a user interpretable designation for the level of completion of the application protocol.
EXAMPLE "IS", "DIS", "TS" or "CD" are examples of application protocol states.
application_interpreted_model_schema_name: the EXPRESS schema name of the application interpreted model.
application_protocol_year: the year when the application protocol attained the status given by the status attribute.
application: the application context of the application protocol.
EXPRESS specification:
*)
ENTITY dependent_product_definition_exchange_context
ABSTRACT SUPERTYPE
SUBTYPE OF (product_definition_context);
WHERE
WR1: SIZEOF (TYPEOF(SELF) * ['APPLICATION_CONTEXT_SCHEMA.INDENTIFICATION_DEPENDENT_PRODUCT_DEFINITION_EXCHANGE_CONTEXT','APPLICATION_CONTEXT_SCHEMA.LANGUAGE_DEPENDENT_PRODUCT_DEFINITION_EXCHANGE_CONTEXT'])
> 0;
END_ENTITY;
(*
Formal propositions:
WR1: at least one of the entities identification_dependent_product_definition_exchange_context or language_dependent_product_definition_exchange_context shall be specified.
EXPRESS specification:
*)
ENTITY identification_dependent_product_definition_exchange_context
SUBTYPE OF (dependent_product_definition_exchange_context);
identification_context : exchange_identification_context_select;
END_ENTITY;
(*
Attribute definitions:
identification_context: specifies the context of the exchange to be either identification_assignment or organization .
EXPRESS specification:
*)
ENTITY language_dependent_product_definition_exchange_context
SUBTYPE OF (dependent_product_definition_exchange_context);
language : language;
END_ENTITY;
(*
Attribute definitions:
language: specifies the default language of the exchange context.
The inherited attribute name identifies or characterizes the type of library.
NOTE 1 The name attribute can represent the nature of the source of the library, the nature of the contents of the library, or both.
EXAMPLE 1 'Dewey Decimal', 'ISO 13584 library', and 'supplier catalogue' are examples of type of library.
EXPRESS specification:
*)
ENTITY library_context
SUBTYPE OF (application_context_element);
library_reference : label;
END_ENTITY;
(*
Attribute definitions:
library_reference: the label that identifies the library.
EXAMPLE 2 'ACME self-propelled rocket sleds catalogue' is an example of a library reference.
A product_concept_context represents information that relates to the characterization of potential purchasers of a product. Such information may affect the meaning and usage of the product data.
EXPRESS specification:
*)
ENTITY product_concept_context
SUBTYPE OF (application_context_element);
market_segment_type : label;
END_ENTITY;
(*
Attribute definitions:
market_segment_type: the label that identifies the kind of consumer preferences associated with a product.
EXAMPLE 'Luxury automobiles', 'laptop personal computers', and 'budget personal stereos' are examples of market_segment_types.
NOTE 1 Different annotated EXPRESS schemas that use or specialize this entity data type can make use of common values for the attributes of the product_context entity data type in order to establish consistency among schemas that relate to the same types or kinds of products.
EXAMPLE 1 Two annotated EXPRESS schemas that specify product data structures for design and construction of buildings respectively can each constrain the values of the name attribute to be 'building', and the discipline_type attribute to be 'architecture'.
The inherited attribute name identifies a particular industry, subject area, or kind of product for which product data is created or used.
NOTE 2 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
EXAMPLE 2 'ship', 'aircraft' and 'building' are examples of names of product contexts.
EXPRESS specification:
*)
ENTITY product_context
SUBTYPE OF (application_context_element);
discipline_type : label;
END_ENTITY;
(*
Attribute definitions:
discipline_type: the label that identifies a particular field of practice involved in creating or using product data.
NOTE 3 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
EXAMPLE 3 'electronics', 'engineering', or 'architecture' are examples of discipline types.
NOTE 1 Different annotated EXPRESS schemas that use or specialize this entity data type can make use of common values for the attributes of the product_definition_context entity data type in order to maintain consistency between schemas that relate to the same or related life-cycle phases.
EXAMPLE 1 Two annotated EXPRESS schemas that specify product data structures for conceptual design and detailed design of process plants respectively can each constrain the values of the name attribute to be 'conceptual design' and 'detailed design', and the life_cycle_stage attribute to be 'design'.
The inherited attribute name identifies a subdivision or characterization of a life cycle stage for which product data is created or used.
NOTE 2 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
EXAMPLE 2 'required' and 'planned' are examples of names of product definition contexts, used in conjunction with a life cycle stage of 'thermal analysis'.
EXPRESS specification:
*)
ENTITY product_definition_context
SUBTYPE OF (application_context_element);
life_cycle_stage : label;
END_ENTITY;
(*
Attribute definitions:
life_cycle_stage: the label that identifies a stage in the life cycle of a product.
NOTE 3 The meaning of this attribute can be defined in the annotated EXPRESS schemas that use or specialize this entity, or in an agreement of common understanding between the partners sharing this information.
EXAMPLE 3 A 'preliminary design' and 'manufacturing planning' are examples of life cycle stages.
*)
END_SCHEMA; -- application_context_schema
(*
© ISO 2021 — All rights reserved