- From: Yarik <Iaroslav.Sheptykin@hs-bremen.de>
- Date: Thu, 27 Oct 2011 21:18:22 +0200
- To: "public-poiwg@w3.org W3C" <public-poiwg@w3.org>
- Cc: Raj Singh <rsingh@opengeospatial.org>
Hi everyone!
In one of the last emails Raj has found the idea of having a
review of time specs good.
http://lists.w3.org/Archives/Public/public-poiwg/2011Oct/0029.html
I gave it a try but didn't go far. I have started from taking a
look what GML and KML did in support of temporal attributes of
their data.
KML has two time types: TimeStamp and TimeSpan. Both extend
abstract TimePrimitive. TimePrimitive is included into the
Feature type and inherited by PlaceMark, NetworkLink, Overlays,
Folder and Document. The geometry is not temporally enabled.
more at
http://code.google.com/apis/kml/documentation/kmlreference.html
Learning from KML we could add an abstract type Time to the
POIBaseType. Created, Modified, Deleted could extend Time. We
could allow Created and Deleted appear 1 and 0..1 respectively
within its parent. Modified could appear 0 .. *. Ex:
<created>...</created>
<modified id="" />...</modified>
<modified id="upgraded">...</modified>
<modified id="rebooted">...</modified>
<modified id="decorated">...</modified>
<deleted>...</deleted>
GML takes it more seriously. Similarly to KML it has TimeInstant
and TimePeriod types. Additionally it allows defining relations
between time instances. It implements calendars.
GML Temporal XSD
http://schemas.opengis.net/gml/3.2.1/temporal.xsd
Learning from GML we could consider using calendars and
relations. Also, as the model already suggest, we could add
temporal dimension to the geometry as well, which I believe GML
developers would find a great idea.
I am interested in reviewing other sources such as standards or
papers which provide guidelines for the temporal modeling. If
you have any in mind, or know a community that could provide
further hits please share. I could summarize it afterwards in a
wikipage.
Greets,
Yarik
Received on Thursday, 27 October 2011 19:19:02 UTC