- From: Raj Singh <rsingh@opengeospatial.org>
- Date: Fri, 21 Oct 2011 19:10:46 +0800
- To: Raj Singh <rsingh@opengeospatial.org>
- Cc: "public-poiwg@w3.org W3C" <public-poiwg@w3.org>
On second thought, no need for a POITimeType. The time functionality can be handled by POITermType. --- Raj On Oct 21, at 6:30 PM, Raj Singh wrote: > new version of the core data model (version 5) posted: > http://www.w3.org/2010/POI/wiki/Data_Model > > This doesn't change anything if you've been writing sample POIs. It's all internal changes to make the model more elegant. This is hopefully a "feature freeze" version before the next draft publication. > > The classes have been modularized a little more to allow for a new time type, and the "POIControlledVocabularyType" has been change to "POITermType"to make the name easier to say (the phrase controlled vocabulary is still useful when defining what this is). > > Also, "Abstract" has been taken out of some type names as I found the right way to specify that a class is abstract in UML2 is just to italicize the name. > > And finally, the big addition is a POITimeType, which allows for specially named times to be added to <pois>, <poi> and <location>. The names we have now are "start" and "end". The administrative time types of "updated", "created", and "deleted" are still in the POIBaseType. > > enjoy, > Raj > > ----- > Raj Singh > rsingh@opengeospatial.org > +1 (617) 642-9372 > The OGC: Making location count... > http://www.opengeospatial.org/contact > > > >
Received on Friday, 21 October 2011 11:11:17 UTC