|
|
Application module:
Property as definition |
ISO/TS 10303-1399:2018-11(E)
© ISO
|
This clause specifies the information requirements for the
Property as definition
application module. The information requirements are specified as the
Application Reference Model (ARM) of this application module.
NOTE 1 A graphical representation of the information
requirements is given in
Annex C.
NOTE 2 The mapping specification is specified in
5.1. It shows how
the information requirements are met by using common resources and
constructs defined or imported in the MIM schema of this application
module.
This clause defines the information requirements to which implementations shall
conform using the EXPRESS language as defined in ISO 10303-11.
The following begins the
Property_as_definition_arm
schema and identifies the necessary external references.
EXPRESS specification:
*)
SCHEMA Property_as_definition_arm;
(*
The following EXPRESS interface statement specifies the elements
imported from the ARM of another application module.
EXPRESS specification:
*)
USE FROM
Product_view_definition_properties_arm;
--
ISO/TS 10303-1034
(*
NOTE 1
The schemas referenced above are specified in the following
part of ISO 10303:
| Product_view_definition_properties_arm |
ISO/TS 10303-1034 |
NOTE 2
See Annex C,
Figures
C.1and C.2
for a graphical representation of this schema.
This subclause specifies the ARM entity for this
module. The ARM entity is an atomic element that
embodies a unique application concept and contains attributes
specifying the data elements of the entity. The ARM
entity and definition is specified below.
A Single_property_is_definition is a type of
Assigned_property
that identifies this property as being the Product_view_definition
itself.
Any other property that is associated with the Product_view_definition
is assumed to be a non-defining property, such as an annotation etc.
This allows direct represent the definition by assigning representations to this property.
EXAMPLE
A single property is definition attached to a Requirement view definition would allow us to provide multiple
representations of the same requirement view definition, such as the string representation "weight must be 4Kg" and
a numeric representation "4Kg" specified as a value with units. Without this capability we would only be
able to identify a text property representing the string and a weight property identifying value with unit.
EXAMPLE
A single property is definition attached to an analysis view definition would allow us to provide a representation
of that analysis view definition without having specific structures defined for all possible analysis techniques
(a task much too large for STEP). For example a collection of scheme entry relationships representing the
critical path of a critical path analysis for a scheme.
EXPRESS specification:
*)
ENTITY Single_property_is_definition
SUBTYPE OF (Assigned_property);
SELF\Assigned_property.described_element : Product_view_definition;
UNIQUE
UR1: described_element;
END_ENTITY;
(*
Attribute definitions:
described_element:
the inherited attribute described_element is constrained to only be of type
Product_view_definition.
Formal propositions:
UR1:
The described element can only have one self-describing property.
*)
END_SCHEMA; -- Property_as_definition_arm
(*
© ISO 2018 — All rights reserved
