 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
• |
Vodafone’s
internal mark-up for portal integration
|
|
|
• |
Built to satisfy
a set of specific use cases / requirements
|
|
|
• |
Encoding
Metadata and Context (Application) information separately from content
|
|
• |
Cross-references
between
|
|
|
|
content and
metadata elements.
|
|
|
• |
Extensible
approach, incorporating
|
|
|
|
existing metadata
standards (PRISM,
|
|
|
|
Dublin Core) and
proprietary namespaces.
|
|
|
• |
Metadata
available to any upstream processor to enable adaptation.
|
|
|
• |
Enabling
semantics to be linked to presentation elements (e.g. column 2 of this
|
|
|
|
game results
table is the team name and column 5 is their score) means you can
|
|
|
|
adapt content to
the appropriate medium.
|
|
|
|
• |
Showing the
whole table; showing just columns 2 and 5; reading team name and score
|
|
|
|
aloud
|
|