OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [humanmarkup-comment] Base Schema - locator


I vote for a combination of chronemic and a locator. 
That will map nicely to the way most software represents 
time and space data types.  The markup doesn't really 
care but the implementation code will.

len


From: Rex Brooks [mailto:rexb@starbourne.com]

I also want to ask if we should add a third locator to our current 
count of two, to include Sylvia's suggestion of a geo-temporal 
locator to geolocator and locator, or do we think that combining the 
geolocator element and the chronemic element together to describe an 
object's location physically and temporally is sufficient?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC