Page Comparison

Tag

Description

Can Be Nested Within

<entity type=”type.id”

 name=”entity.name”

version="major.minor"

enrichment="positive-integer">

  <attribute>…..</attribute>

  <entity>…..</entity>

<presentationML

enrichment="positive-integer">

    default representation

  </

presentationML

enrichment="positive-integer">

</entity>

An Entity describes some type of complex object which is referenced from within a message. All Entity elements MUST include a type XML-attribute which defines the format and semantics of the Entity.

All Entity elements MAY contain child Entity and Attribute elements which are considered to make up the Entity by composition.

All Entity elements MAY contain a presentationML element which contains a default representation of the Entity in PresentationML mark up.

Entity elements which are not children of another entity element MUST contain a presentationML element.

<messageML>

<p><b><i><td><th><li>

<entity>

<attribute type=”type.id”

  name=”attribute.name”

  priority=

”non-negative-integer”

enrichment="positive-integer"

  value=”value.string”

/>

An Attribute describes an attribute of a complex object. All Attribute elements MUST include a type XML-attribute which defines the format and semantics of the Attribute.

All Attribute elements MUST contain a value XML-attribute which defines the value of the Attribute.

Where there are multiple Attributes within an Entity with the same name a priority XML-attribute MUST be present, indicating which value is preferred.

Priority and enrichment MUST NOT both be specified on a single attribute. Recipients of messages where this is the case MUST ignore the priority.

When a renderer is presented with an entity with multiple attributes with the same name they SHOULD use the value with the lowest priority value which they can understand. If there is no such value then they SHOULD select the value with the highest enrichment value which they can understand.

<entity>