external tourml instance (hosted tourml.xml) with TAP-iOS

[Gautier Michelin]

Hi,

I've tested hosting tourml xml file and defining it through TapConfig.plist TourMLEndpoint.
It works quite great but we have no indication when external assets are loaded. I've customized the AudioStop to display a pic, with a spinning wheel until external mp3 is loaded and then play/pause buttons when mp3 is fully loaded.

Image is taken from an image asset with usage "image" defined.

Here come the questions :

- is there any one using external (web hosted) assets with TAP-iOS ?
- can't remember if TAP-CMS does, as I self-generate the tourml files, do you like the idea of having a picture in audio stop display ? is that already done in TAP-CMS ?

Bye,

Gautier
----------
check http://tourguide.io if not already done :-)

[Kyle Jaebker]

Gautier,

We have only experimented with the externally hosted TourML in the iOS app. I do not know of anyone using it in production at the moment.

As for the Audio stop, yes we have added images to them through the CMS. For the web app we have this implemented and are using an asset with usage of image just as you are. So the cms generated TourML should work with the change you have made.

Kyle 

--
You received this message because you are subscribed to the Google Groups "TAP Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tap-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

---

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact Kyle Jaebker by reply email and destroy all copies of the original message.

[Glen Barnes]

Hi,

I'm just putting together a TourML file for some content how which includes a stop with audio, images and text. It looks something like this at the moment:

<tourml:Stop tourml:id="stop-8">
<tourml:Title>Cook Landing Site (1769)</tourml:Title>
<tourml:AssetRef tourml:id="location-stop-8"/>
<tourml:AssetRef tourml:id="content-stop-8"/>
<tourml:AssetRef tourml:id="audio-stop-8"/>
<tourml:AssetRef tourml:id="image-stop-file-8-cook-landing-monument-2"/>
<tourml:AssetRef tourml:id="image-stop-file-8-cook-landing-monument-3"/>
<tourml:AssetRef tourml:id="image-stop-file-8-cook-landing-monument-4"/>
<tourml:AssetRef tourml:id="image-stop-file-8-cook-landing-monument-5"/>
</tourml:Stop>

<tourml:Asset tourml:id="location-stop-8">
.
.
.


The one issue I haven't resolved is how to attach captions to images. It seems that Assets can have a source _or_ content but not both. How do you resolve adding captions to images when there are multiple images per stop? Right now I have them as 2 separate assets but that seems messy as there is no link between them:

<tourml:Asset tourml:id="image-stop-file-98-auckland-harbour-bridge-3">
<tourml:Source tourml:format="image/jpg" tourml:uri="http://www.nzhistory.net.nz/files/images/auckland-harbour-bridge-3.jpg"/>
</tourml:Asset>

<tourml:Asset tourml:id="image-caption-98-auckland-harbour-bridge-3">
<tourml:Content>
<tourml:Data>The Auckland harbour bridge looking from the South </tourml:Data>
</tourml:Content>
</tourml:Asset>

Any pointers? Also has anybody who is using TourML in anger willing to publish a full working TourML file online?

Thanks,
Glen

[Alan Wecker]

A possibility that we have used is to make the asset a piece of HTML which can contain both text and image . the map tag in HTML can also be useful

[Kyle Jaebker]

I believe that due to how we are wrapping the choice in a sequence:

<xsd:complexType name="AssetType">
    <xsd:sequence>
        <xsd:choice minOccurs="1" maxOccurs="unbounded">
            <xsd:element name="Source" type="tourml:AssetSourceType" />
            <xsd:element name="Content" type="tourml:AssetContentType" />
        </xsd:choice>
	<xsd:element name="PropertySet" type="tourml:PropertySetType" minOccurs="0" maxOccurs="1" />
    </xsd:sequence>
    <xsd:attribute ref="tourml:id" use="required" />
    <xsd:attribute ref="tourml:type" use="optional" />
</xsd:complexType>

It is valid to have both Source elements and Content elements in an asset. Here is some output from one of our TourML files that does validate.

<tourml:Asset tourml:id="asset-image_stop-image_asset-7" tourml:type="image_asset">

<tourml:Source tourml:format="image/jpeg" tourml:lastModified="2013-03-29T12:34:48-04:00" xml:lang="en" tourml:uri="http://www.imamuseum.org/tap-tours/sites/default/files/landonwedding_smaller.jpg" tourml:part="image">

<tourml:PropertySet>

<tourml:Property tourml:name="width">1195</tourml:Property>

<tourml:Property tourml:name="height">938</tourml:Property>

</tourml:PropertySet>

</tourml:Source>

<tourml:Source tourml:format="image/jpeg" tourml:lastModified="2013-03-29T12:34:48-04:00" xml:lang="en" tourml:uri="http://www.imamuseum.org/tap-tours/sites/default/files/styles/thumbnail/public/landonwedding_smaller.jpg" tourml:part="thumbnail">

<tourml:PropertySet>

<tourml:Property tourml:name="width">100</tourml:Property>

<tourml:Property tourml:name="height">78</tourml:Property>

</tourml:PropertySet>

</tourml:Source>

<tourml:Source tourml:format="image/jpeg" tourml:lastModified="2013-03-29T12:34:48-04:00" xml:lang="en" tourml:uri="http://www.imamuseum.org/tap-tours/sites/default/files/styles/1150x1100/public/landonwedding_smaller.jpg" tourml:part="1150x1100">

<tourml:PropertySet>

<tourml:Property tourml:name="width">1150</tourml:Property>

<tourml:Property tourml:name="height">903</tourml:Property>

</tourml:PropertySet>

</tourml:Source>

<tourml:Source tourml:format="image/jpeg" tourml:lastModified="2013-03-29T12:34:48-04:00" xml:lang="en" tourml:uri="http://www.imamuseum.org/tap-tours/sites/default/files/styles/550x500_square/public/landonwedding_smaller.jpg" tourml:part="550x500_square">

<tourml:PropertySet>

<tourml:Property tourml:name="width">550</tourml:Property>

<tourml:Property tourml:name="height">500</tourml:Property>

</tourml:PropertySet>

</tourml:Source>

<tourml:Content tourml:part="caption">

<tourml:Data>

<![CDATA[

<p>Oldfields was the setting for a double wedding ceremony in June of 1920. IMA Archives.</p>

]]>

</tourml:Data>

</tourml:Content>

<tourml:Content tourml:part="title">

<tourml:Data>

<![CDATA[ Landon Wedding Photo ]]>

</tourml:Data>

</tourml:Content>

</tourml:Asset>

From: Alan Wecker <ajwe...@gmail.com>
Reply-To: "tap-d...@googlegroups.com" <tap-d...@googlegroups.com>

[Glen Barnes]

That all makes sense. All the examples only had one item per asset which confused me. It might be a good idea to update the examples with a more complex example like below?

Also way back in the day I think we discussed have some standards for things like tourml:part. Is there a standard set of tags we should be looking at? For example for an image asset we could have the following:

• For the source files:
• original: Original image at full quality 
• thumbnail: Square cropped thumbnail
• For the content:
• title: Short title of the image
• caption: Longer description
• attribution: WHo the image is attributed to
• copyright: What copyright is on the image. e.g. CC-BY
• href: Pointer to a source page in a collections DB or other page.

The idea was to not limit people to using one set of tags but for these to evolve as more people started using them. This is kind of how things work in Open Street Map.

Thanks,

Glen 

[Kyle Jaebker]

Glen,

We have not documented these yet, but this type of documentation is discussed here:

https://github.com/IMAmuseum/tourml/wiki/Application-Profiles

We are working on docs around the apps that we have built, but what you have below is a good start.

For the example TourML docs, I will add a task to get more complex examples in place.

Thanks,

Kyle

[MOE]

For testing, I tried your example XML, as well that posted @ https://tap-tours.googlecode.com/svn/trunk/tourml/TourMLExample.xml

When I ran the IOS simulator the App opens up but only says "Select a Tour" - it does not seem to recognize the tour data via XML file.

Advise?

Moe

[JR]

I'm having this same issue. I've tried including the URL to the TourML.xml file, but when I test using the simulator all I see is the 'Select a Tour' option (no tours actually listed, though).

Any thoughts on what might be missing here?