- From: Christian Timmerer (ITEC) <christian.timmerer@itec.uni-klu.ac.at>
- Date: Mon, 9 Nov 2009 15:29:01 +0100
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-device-apis <public-device-apis@w3.org>, Matt Womer <matt@w3.org>
Dear all,
MPEG-21 DIA Usage Environment Description defines Mobility
Characteristics for a User. The excerpt from the schema you can find
below and the full schema is available at [1]. As this is somewhat
related it might be helpful for (some of) you. If you need information
on the semantics, please let me know.
Thank you.
Best regards,
-Christian
[1] http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG-21_schema_files/dia-2nd/UED-2nd.xsd
Schema excerpt for Mobility Characteristics:
<!-- ################################################ -->
<!-- Definition of MobilityCharacteristics -->
<!-- ################################################ -->
<complexType name="MobilityCharacteristicsType">
<complexContent>
<extension base="dia:UserCharacteristicBaseType">
<sequence>
<element name="UpdateInterval"
type="dia:UpdateIntervalType" minOccurs="0"/>
<element name="Directivity" type="dia:DirectivityType"
minOccurs="0"/>
<element name="Erraticity" type="dia:ErraticityType"
minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="UpdateIntervalType">
<complexContent>
<extension base="dia:DIABaseType">
<sequence>
<element name="LastUpdatePoint"
type="mpeg7:GeographicPointType" minOccurs="0"/>
<element name="LastUpdateBinIndex" type="integer"
minOccurs="0"/>
<element name="LastUpdateTime" type="mpeg7:TimeType"
minOccurs="0"/>
<element name="Lmax" type="integer" minOccurs="0"/>
<element name="Values" minOccurs="0">
<simpleType>
<restriction base="mpeg7:probabilityVector">
<length value="32"/>
</restriction>
</simpleType>
</element>
</sequence>
<attribute name="xRadius" type="integer" use="optional"/>
<attribute name="yRadius" type="integer" use="optional"/>
</extension>
</complexContent>
</complexType>
<complexType name="DirectivityType">
<complexContent>
<extension base="dia:DIABaseType">
<sequence>
<element name="Mean" type="float" minOccurs="0"/>
<element name="Variance" type="float" minOccurs="0"/>
<element name="Values" minOccurs="0">
<simpleType>
<restriction base="mpeg7:probabilityVector">
<length value="16"/>
</restriction>
</simpleType>
</element>
</sequence>
<attribute name="measuredInterval" type="integer"
use="optional"/>
</extension>
</complexContent>
</complexType>
<complexType name="ErraticityType">
<complexContent>
<extension base="dia:DIABaseType">
<sequence>
<element name="Values" minOccurs="0">
<simpleType>
<restriction base="mpeg7:probabilityVector">
<length value="128"/>
</restriction>
</simpleType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
On Nov 9, 2009, at 3:12 PM, Dominique Hazael-Massieux wrote:
> Hi,
>
> The Geolocation WG is taking up work on defining an API for getting
> orientation and acceleration data from devices:
> http://www.w3.org/2009/11/03-geolocation-minutes.html
>
> This suggests our Working Group doesn’t need to tackle it, although we
> will likely want to coordinate with them on these work items.
>
> Note also their ongoing work on defining an interface for civic
> addresses:
> http://www.w3.org/2009/11/03-geolocation-minutes.html#item03
>
> Dom
>
Received on Monday, 9 November 2009 14:29:40 UTC