FW: User Documentation (L&M Component)

[Emmanuel Huchet]

FYI

 

From: Emmanuel Huchet [mailto:emmanue...@virtually-here.com]
Sent: January 15, 2009 10:25 AM
To: 'Clay Howey'
Cc: 'stewar...@virtually-here.com'
Subject: RE: User Documentation

 

Hi Clay,

 

Here’s a  summary description of the Location & Mapping Component:

 

---

The Location and Mapping (aka L&M) Component allows mobile users to register their current geographic location on the Mobile MUSE Platform by sending a simple text message or by making a voice call.  Cultural developers can use the L&M component to define a set of landmarks specific to their needs, and assign each landmark a unique code and a geographic location.  These codes can then be displayed (on publicly-visible signs near each landmark for example) so that mobile users can text in that code to indicate their location at that landmark.  Alternatively, mobile users can make a voice call to specify their location by uttering the name of that landmark.

 

This location information may be useful to add geographic context to cultural events.  Besides allowing end users to specify their locations directly, the L&M component provides an API that allows cultural developers to update and retrieve location information programmatically. In that way cultural developers can integrate geographic functionality into their programs and events.

 

Mobile users may request a map showing their current location in relation to other landmarks (maps are displayed on their mobile device), and maps may also be requested programmatically for display within other applications.

 

The L&M component relies on other Muse components and service points to provide interaction with mobile users.  The two main interaction methods are text message and voice – cultural developers may choose to allow either or both of these methods.  To allow mobile users to specify locations via text message, the cultural developer must first create an instance of the Mobile Dialog component.  To support voice interaction the cultural developer must have available two Muse Service Points: VoiceXML to support incoming voice calls, and outgoing SMS to support the acknowledgement text message that is sent to the user.

---

 

Hope this is satisfactory.

 

Emmanuel

 

From: muse3-p...@googlegroups.com [mailto:muse3-p...@googlegroups.com] On Behalf Of Clay Howey
Sent: January 14, 2009 10:55 AM
To: muse3-p...@googlegroups.com
Subject: User Documentation

 

Hello Mobile MUSE 3 Platform Developers,

Jim, Jean, Stephen, David, Roland & I met at New Media BC on Monday and discussed the current documentation available on the platform to cultural partners.  We agreed that more is needed to help folks who are completely new to Mobile MUSE understand what the various components do and how they are useful.  Therefore, for each component, we would like descriptive text (about 2/3 of a page) that outlines:

    - Here's what it does
    - Here's why it's useful
    - Here are the requirements
    - Here are the dependencies (e.g. Mobile Dialog, etc.)

We will be revising the main page for developers.mobilemuse.ca to show a list of all the components, and this descriptive text will hide behind a 'Tell me more' button beside each component.

Please send the descriptive text for your components to this group by Monday, January 19th.

Many thanks,

Clay Howey
Platform Integrator
Mobile MUSE