Closed jyutzler closed 10 years ago
I disagree that there exists a gamut of temporal types. Is there anything to Multi-instants and multi-intervals other than analogy to geometry types? I don't see them in other temporal ontologies (though I confess I haven't made an exhaustive search). Let's leave them out of an event-like features context.
Background: @sgillies stated that "moving features and feature succession/events should be different efforts." In response, I set up this issue to discuss the concept directly.
As I get more familiar with JSON-LD itself, I think it becomes easier, not harder, to support the gamut of temporal types including MultiInstant and MultiInterval. For example, the following works as a MultiInstant:
This parses correctly in the JSON-LD Playground. A similar approach could be used for MultiInterval. What I can't evaluate is the cost of support for these elements compared to the cost of
earliest
,latest
,start
, andstop
. It seems to me that the thing for a client to do is evaluate the @type entries - if it supports the type then great; if not it is simply ignored. It looks like an easy way to do core/extensions.This is what I'm looking for personally because I don't care about
Interval
but I do care aboutMultiInstant
.