Definition

Consider an instance P of <Geometry Representation> or <Feature Representation>, where P has a <Property Set Index> component X that references a <Property Set> instance S.

• Let S have a component C that is an instance of any of the following:

  • <Classification Data>,
  • <Data Quality>,
  • <Identification>,
  • <Light Rendering Properties>,
  • <Presentation Domain>,
  • <Rendering Priority Level>,
  • <Rendering Properties>, or
  • <Time Constraints Data>.

  If P has a component D belonging to the same class as C, D takes precedence over C, such that C is not treated as a directly attached component of P.

• Let S have a component C that is a <Property Table> instance, and let P have a <Property Table> component D such that C and D have matching <Classification Data> components. D takes precedence over C, such that C is not treated as a directly attached component of P.

• Let S have a component C that is a <Property Table Reference> instance, and let P have a <Property Table Reference> component D such that C and D refer to <Property Table> instances having matching <Classification Data> components. D takes precedence over C, such that C is not treated as a directly attached component of P.

• Let S have a component C that is a <Property Value> instance, and let P have a <Property Value> component D such that C and D have matching meaning field values. D takes precedence over C, such that C is not treated as a directly attached component of P.

• Let S have a component C that is a <Colour> instance. Let P have a component D that belongs to the same class as C. If C and D specify conflicting <Presentation Domain> components, D takes precedence over C, such that C is not treated as a directly attached component of P.

• Let S have one or more <Image Mapping Function> components Ci. If P specifies one or more <Image Mapping Function> components Di, the DRM objects of Di take precedence over those of Ci, such that no DRM object in Ci is treated as a directly attached component of P.

Rationale

Objects contained directly by <Geometry Representation> or <Feature Representation> instances are more closely related to the <Geometry Representation> or <Feature Representation> instances than those contained in a <Property Set> instance; they will be specific while those in a <Property Set> instance will be more generic.

The order of the list of <Property Set Index> instances implies an order of precedence.

Example

1. A <Feature Representation> instance contains a <Data Quality> instance with fictional set to SE_TRUE. It also references a <Property Set> instance that contains a <Data Quality> instance with fictional set to SE_FALSE. As a <Feature Representation> instance may have only one <Data Quality> component, the <Data Quality> instance with fictional set to SE_TRUE is used, as it is contained directly by the <Feature Representation> instance.

2. A <Geometry Representation> instance contains two <Property Table Reference> instances and references a <Property Set> instance that contains another three. As a <Geometry Representation> instance may contain many <Property Table Reference> instances, all five are used by the <Geometry Representation> instance as required. The two that are contained directly are used first, then the three that are contained in the <Property Set> instance.

3. Consider a <Geometry Representation> instance that has two <Image Mapping Function> components and references a <Property Set> instance that contains another two. As a <Geometry Representation> instance may contain many ordered <Image Mapping Function> instances, all four are used by the <Geometry Representation> instance as required. The two that are contained directly are used in order first, then the three that are contained in the <Property Set> instance, again in order.

4. Consider a <Geometry Representation> instance that contains two <Property Table Reference> components and references two <Property Set> instances. The first <Property Set> instance contains another <Property Table Reference> instance and the second <Property Set> instance contains another three <Property Table Reference> instances. As a <Geometry Representation> instance may contain many <Property Table Reference> instances, all six are used by the <Geometry Representation> instance as required. The two that are contained directly are used first, then that contained in the first <Property Set> instance, and finally the three that are contained in the second <Property Set> instance.

FAQs

No FAQs supplied.