West M. Developing High Quality Data Models
Подождите немного. Документ загружается.
consists_of_Aconsists_of relationship type where a
representation_by_sign consists of one or more
recognizing_language_community.
consists_of A consists_of relationship type where one or more
sign is used in the representation_by_sign.
17.45.11 Sign
A state_of_sign, that is also a socially_constructed_object,
and a participant that represents some thing for some commu-
nity in one or more representations_by_sign.
EXPRESS specification:
*)
ENTITY sign
SUBTYPE OF(socially_constructed_object, state_of_sign,
participant);
SELF\socially_constructed_
object.member_of :OPTIONAL SET [1:?] OF
class_of_sign;
member_of_ :SET [1:1] OF pattern;
SELF\participant.
participant_in :SET [1:?] OF representation_
by_sign;
END_ENTITY;
(*
Attribute definitions:
member_of A member
_of relationship type where a sign may
be a member_of one or more class_of_sign.
member_of_Amember_of relationship type where a sign is a
member_of one or more pattern.
participant_in A participant_in relationship type where a sign is a
participant_in one or more
representation_by_sign.
17.45.12 State_of_sign
A state_of_socially_constructed_object that is a sign or a
temporal_part_of a sign.
EXPRESS specification:
*)
ENTITY state_of_sign
SUBTYPE OF(state_of_socially_constructed_object);
342 Chapter 17 HQDM_FRAMEWORK
SELF\state_of_socially_constructed_
object.temporal_part_of :OPTIONAL SET [1:?] OF
sign;
SELF\state_of_socially_
constructed_object.member_of :OPTIONAL SET [1:?]
OF class_of_state_
of_sign;
END_ENTITY;
(*
Attribute definitions:
temporal_part_of A tempo
ral_part_of relationship type where a
state_of_sign may be a temporal_part_of one
or more sign.
member_of A member_of relationship type where a
state_of_sign may be a member_of one or
more class_of_state_of_sign.
17.46 Requirement and
Requirement Specification
Figure 17-46 shows the data model for requirement and
requirement-specification.
A plan is a possible_world that some party would like to bring
about.
A requirement is a spatio_temporal_extent that is part_of_
plan of at least one plan and is defined_by exactly one
requirement_specification, where the part_of_plan relationship
type is a subtype of the part_of relationship type and the
defined_by relationship type is a subtype of the member _of
relationship type.
A requirement_specification is a class_of_spatio_temporal_
extent that is the intersection_of one or more class_of_state.
A physical_property_range is a class_of_state that ranges_
over (is a superset of) one or more physical_property of the
same kind_of_physical_property.Astate is a member_of a
property_range when its value for the kind_of_physical_
property falls within the range.
A physical_quantity_range is a physical_prope rty_range
where the kind_of_physical_property is a kind_of_physical_
quantity and where the physical_quantity_range has an
upper_bound and a lower_bound that are a physical_quantity.
Chapter 17 HQDM_FRAMEWORK 343
17.46.1 Physical_property_range
A class_of_state where each member of the set is a member
of a physical_property within the range.
Note: The physical_property_range is the supertype of each
physical_property in the range.
EXPRESS specification:
*)
ENTITY physical_property_range
SUBTYPE OF(class_of_state);
ranges_over :SET [1:?] OF physical_property;
END_ENTITY;
(*
Attribute definitions:
ranges_over A supe
rtype_of relationship type where the members
of each physical_property in
the physical_property_range are members of the
physical_property_ range .
plan
46,2 (11)
requirement
46,2 (4)
physical_
property_range
physical_
quantity_range
46,3 (6)
requirement_
specification
46,1 (4,43)
6,2 class_of_state
12,3 physical_property
defined_by S[1:1]
part_of_plan S[1:?]
ranges_over S[1:?]
12,4 physical_quantity
upper_bound
12,4 physical_quantity
lower_bound
intersection_of S[1:?]
Figure 17-46 HQDM_
FRAMEWORK EXPRESS-G
diagram 46 of 46.
344 Chapter 17 HQDM_FRAMEWORK
17.46.2 Physical_quantity_range
A physical_property_range that ranges over physical_quantity
values.
EXPRESS specification:
*)
ENTITY physical_quantity_range
SUBTYPE OF(physical_property_range);
upper_bound :physical_quantity;
lower_bound :physical_quantity;
END_ENTITY;
(*
Attribute definitions:
upper_bound A superty
pe_of relationship type where each
physical_quantity_range must have as
upper_bound exactly one physical_quantity.
lower_bound A supertype_of relationship type where each
physical_quantity_range must have as
lower_bound exactly one physical_ quantity.
17.46.3 Plan
A possible_world that some party would like to bring about.
EXPRESS specification:
*)
ENTITY plan
SUBTYPE OF(possible_world);
END_ENTITY;
(*
17.46.4 Requirement
A spatio_temporal_extent that is part _of_plan at least one
plan and is defined_by exactly one requirement_specification.
EXPRESS specification:
*)
ENTITY requirement
SUBTYPE OF(spatio_temporal_extent);
defined_by :SET [1:1] OF requirement_specification;
part_of_plan :SET [1:?] OF plan;
END_ENTITY;
(*
Chapter 17 HQDM_FRAMEWORK 345
Attribute definitions:
defined_by A mem
ber_of relationship type where a
requirement is defined_by exactl y one
requirement_specification.
part_of_plan A part_of relationship type where a requirement
must be part_of one or more plans.
17.46.5 Requirement_specification
A class_of_spatio_temporal_extent that is the intersection_of
one or more class_of_state.
EXPRESS specification:
*)
ENTITY requirement_specification
SUBTYPE OF(class_of_spatio_temporal_extent);
intersection_of :SET [1:?] OF class_of_state;
END_ENTITY;
(*
Attribute definitions:
intersection_of A subt
ype_of relationship type where each
requirement_specification is the intersection_of
one or more class_of_state.
Note: the requirement_specification is a
subtype of each of the related class_of_state.
*)
END_SCHEMA;
346 Chapter 17 HQDM_FRAMEWORK
APPENDIX
A MAPPING BETWEEN THE
HQDM SCHEMA AND ISO
15926-2
A.1 Introduction
This book presents a data model that is a different take on
the same ontological principles behind the ISO 15926 -2 data
model. As I explained earlier, the reason for the different take is
the diffe rent purpose that this book has from the ISO standard.
In developing the ISO standard, there was considerable pressure
to keep the number of entity types as small as possible. This
perhaps led to the standard being harder to interpret and use
than a larger, more explicit model. By contrast, in the HQDM
schema, I present the same ontological principles in such a way
that my data model makes it easier to see how the data model
should be populated. This produces a data model with a larger
entity type count but that covers only the core of the ISO
15926-2 data model.
The purpose of this appendix is to show how the entity types
in the two data models relate to each other. I do this both
graphically and textually. The graphical conventions are illus-
trated in Figure A-1, where the double-ended lollypop shows
the entity types are equivalent, the subtype symbol shows that
an HQDM entity type is a subtype of an ISO 15926-2 entity
type, and the arrow shows the ISO 15926-2 entity type of which
the HQDM entity type is an instance (so the entity type can be
placed in the ISO 15926 RDL). An instanc e of relationship is
required unless the entity types are equivalent.
Not all entity types are mapped, but those that are critical to
understanding the relationship between the HQDM data model
and the ISO 15926-2 data model are.
347
A.2 Thing
• HQDM: thing is equiv alent to ISO15926-2: thing.
A.3 Spatio_temporal_extent
ISO 15926-2HQDM
thingthing
Figure A-2 Mapping for thing.
ISO 15926-2HQDM
thingthing
state
possible_
individual
HQDM: thing is equivalent to ISO15926-2: thing
HQDM: state is a subtype of ISO15926-2:
possible_individual.
HQDM: individual is an instance of ISO15926-2:
class_of_individual
class_of_
individual
Figure A-1 Example notation for mapping HQDM
entity types to ISO 15926-2 entity types.
ISO 15926-2HQDM
possible_
individual
spatio_
temporal_
extent
Figure A-3 Mapping for spatio_temporal_extent.
348 Appendix A MAPPING BETWEEN THE HQDM SCHEMA AND ISO 15926-2
• HQDM: spatio_temporal_extent is equivalent to ISO15926-2:
possible_individual.
A.4 Abstract_object
• HQDM: abstract_object is equivalent to ISO15926-2:
abstract_object.
A.5 Class
ISO 15926-2HQDM
classclass
Figure A-5 Mapping for class.
• HQDM: class is equivalent to ISO15926-2: class.
A.6 Class_of_spatio_temporal_extent
ISO 15926-2HQDM
abstract_
object
abstract_
object
Figure A-4 Mapping for abstract_object.
ISO 15926-2HQDM
class_of_
individual
class_of_spatio_
temporal_extent
Figure A-6 Mapping for class_of_spatio_temporal_extent.
Appendix A MAPPING BETWEEN THE HQDM SCHEMA AND ISO 15926-2 349
• HQDM: cl ass_of_spatio_temporal_ext ent is equivalent to
ISO15926-2: class_of_in dividual.
A.7 Class_of_abstract_object
• HQDM: class_of_abstract_object is equivalent to ISO15926-2:
class_of_abstract_object.
A.8 Class_of_class
• HQDM: class_of_class is equivalent to ISO15926-2:
class_of_class.
A.9 Class_of_class_of_spatio_temporal_extent
ISO 15926-2HQDM
class_of_
class_of_
individual
class_of_
class_of_spatio_
temporal_extent
Figure A-9 Mapping for class_of_class_of_class_of_spatio_temporal_extent.
ISO 15926-2HQDM
class_of_
abstract_object
class_of_
abstract_object
Figure A-7 Mapping for class_of_abstract_object.
ISO 15926-2HQDM
class_of_
class
class_of_
class
Figure A-8 Mapping for class_of_class.
350 Appendix A MAPPING BETWEEN THE HQDM SCHEMA AND ISO 15926-2
• HQDM: class_of_class_of_spatio_temporal_extent is equiv-
alent to ISO15926-2: class_of_class_of_individual.
A.10 Event
ISO 15926-2HQDM
eventevent
Figure A-10 Mapping for event.
• HQDM: event is equivalent to ISO15926-2: event.
A.11 Point_in_time
ISO 15926-2HQDM
point_in
time
point_in
time
Figure A-11 Mapping for point_in_time.
• HQDM: point_in_time is equivalent to ISO15926-2:
point_in_time.
A.12 Class_of_event
ISO 15926-2HQDM
class_of_
event
class_of_
event
Figure A-12 Mapping for class_of_event.
Appendix A MAPPING BETWEEN THE HQDM SCHEMA AND ISO 15926-2 351