Skip to content
Charles Moad edited this page Sep 20, 2012 · 3 revisions

The PropertySetType allows for the embedding of arbitrary application specific data on various elements.

Specification (v1.0.0)

PropertySetType found inside: [[TourMetadataType]], [[AssetType]], [[StopType]], [[AssetSourceType]], [[AssetContentType]]

  • elem: Property - xsd:anyType extension (1..*)
    • attr: name (required)

    • attr: xml:lang (optional)

      name = An identifier string for this Property. Should be unique to this PropertySet.

      xml:lang = A language identifier for this Property.

Description

PropertySets are usually the answer to those 20% of things that are very specific to an application, including navigation methods. As a rule of thumb, it is also useful for information that is not 100% critical or required for the Tour contents. For example, a keypad driven application might require a 3-digit number to load a stop. Those keypad codes can be embedded as Stop properties, because the are not critical to the Tour content. The same tour content can be made accessible by other means, like a simple listing, without the use of the keypad codes. This example highlights why TourML avoids the problem of trying to represent navigational methods. It would require constant revisions to the specification as technology changes.

Clone this wiki locally