Talk:Discovery Change Proposal-6

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

-- Rduerr 17:29, 16 March 2012 (MDT)

On Mar 14, 2012, at 12:13 PM, Ian Truslove wrote:

There's an OpenSearch time extension (http://www.opensearch.org/Specifications/OpenSearch/Extensions/Time/1.0/Draft_1) that I believe is what's included currently in the ESIP spec. DCP-6 says "The current ESIP Discovery specification uses a non-standard element for specifying date-time" which I'm not sure is true - what's non-standard about the OS Time extension?

The OGC OpenSearch doc I found (https://portal.opengeospatial.org/files/?artifact_id=35983) indicates that the OpenSearch time extension is what they want to use - contrary to what DCP-6 says.

The stated rationale on DCP-6 doesn't make sense to me any more. Whilst adopting Dublin Core dates isn't necessarily a bad thing, I can't see what's wrong with the current spec. This all makes me wonder whether the move to DC's date range is necessary, and what the driver (_really_) is.

I feel like I have incomplete or inaccurate info.