Re: simple weather observation example illustrating complex column mappings (ACTION-11)

Sorry to be late in responding, I’m in a conference.

For converting values, such as dateTime strings, to URIs, I’ve been presuming that we would perform standard %-escaping mechanism on the result of creating a value (or key) to be interpreted as a URI. For example, in your case you might simply use the following: 

{
  ...
  "@id": "site/22580943/date-time/{Date-time}”,
  …
}

This would yield values such as  <site/22580943/date-time/2013-12-13T08%3A00%3A00Z>, although “:” is a valid character within a path, so there is really no need to do such escaping. It may be that we would want to add some information to assist such escaping by defining a set of characters to be encoded.

Otherwise, this looks great!

Gregg

On Apr 2, 2014, at 11:04 AM, Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk> wrote:

> All, 
> 
> (related action #11 <https://www.w3.org/2013/csvw/track/actions/11>)
> 
> I've created an "Example" directory in the github repo <https://github.com/w3c/csvw/tree/gh-pages/examples>, within which I have placed the example requested by AndyS et al in today's teleconference:
> 
> simple-weather-observation <https://github.com/w3c/csvw/blob/gh-pages/examples/simple-weather-observation.md>
> 
> It provides:
> - CSV example
> - RDF encoding (in TTL)
> - JSON-LD encoding (assuming my manual conversion is accurate)
> - CSV-LD mapping frame (or at least my best guess)
> 
> In the mapping frame I couldn't figure out how to construct the @id for the weather observation instances as I wanted to use a simplified form of the ISO 8601 date-time syntax used in the "Date-time" column.
> 
> Would be happy for folks to correct/amend what I've done :)
> 
> AndyS / Greg - if this meets your need could you close the action? (I left it in "pending review" state)
> 
> Jeremy
>

Received on Thursday, 3 April 2014 16:49:50 UTC