...
The following tags are defined for EntityML, tag names are case sensitive:
WORK IN PROGRESS, INCOMPLETE
Tag | Description | Can Be Nested Within |
|---|---|---|
<entity> <format type="type.id1" attr1="value1" attr2="value2"/> <format type="type.id2" attr3="value3" attr4="value4"> <any><tags with="any attributes"></tags></any> </format> PresentationML </entity> | A custom entity with one or more entity formats and a default rendering expressed in PresentationML. Following the opening <entity> tag there MUST be one or more <format> tags. Each <format> tag MUST have a type attribute which contains a format identifier in Java package name format. Only the owner of the equivalent domain in DNS should define that ID. Each format tag MAY then have any number of additional attributes, but each attribute name MUST be unique within that tag. Each format tag MAY contain an arbitrary set of sub-tags, each of which MAY have zero or more attributes and further sub tags. Only tags may be contained within a <format> tag, text content outside of an attribute MUST NOT appear within a <format> tag. Format tags are listed in descending order of preference, when displaying an entity the formats will be checked in order and the first format for which a valid renderer exists will be used and all other formats will be ignored. In the event that multiple renderers exist for the same format then the presentation engine will select its preferred renderer according to its own rules. Finally after all <format> tags there SHOULD be a sequence of valid PresentationML tags which represent the default presentation in the event that no appropriate renderer for any provided format can be found. | <MessageML> <p><b><i><td><th><li> |