Application Profiles

Charles Moad edited this page Sep 14, 2012 · 5 revisions

TourML as a specification strives to remain agnostic of technology or how tour content might be consumed by users. This approach helps to ensure the longevity of the specification and makes it easier to share and reuse content down the road.

This level of flexibility can pose potential hurdles for moving tour content from one application to another, however. An application might expect certain asset references in order to render a Stop in an application, for example. More generally, one would want to know what types of Assets or Stops you expect to find in a Tour document.

Enter application profiles. (Wikipedia reference)

Specific to TourML, Application profiles are a way to express a set of metadata that an application expects to be present in TourML instance documents. For example, the TAP applications support certain types of stop views (e.g. video, image, audio, etc.) and additionally expects to find specific asset usages within those stops (e.g. primary for the main video file in a video stop).

Application profiles are also the answer to the question, "How do I import TourML into another content management system?"

It is up to each vendor, community, application, and/or individual to collaboratively agree upon an application profile for a specific domain. A great example of this tooling can be seen around the Geography Markup Language (GML). GML is a specification for geographic information. Like TourML, it is a very open and flexible specification. Specific domains have thus created specific application profiles for the GML specification.

For information on how to build on top of the TourML specification, refer to the extending TourML documentation

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.