W3C home > Mailing lists > Public > public-sdw-wg@w3.org > April 2015

Re: Requirements from UC-19

From: Ubaldino, Marc C. <ubaldino@mitre.org>
Date: Wed, 29 Apr 2015 14:25:51 +0000
To: Frans Knibbe <frans.knibbe@geodan.nl>, "Svensson, Lars" <L.Svensson@dnb.de>
CC: "public-sdw-wg@w3.org" <public-sdw-wg@w3.org>
Message-ID: <C9F4CE0C-D473-40A4-8E5C-238EC2012BB4@mitre.org>
(I have not had the extra time to participate in the telecons (much to my regret), but have been following the chatter since February.  I may have to continue just listening to stay aware.)

I see the mentions of inexactness of time and space references below in the use case and on wiki (currently numbered “4.9 Enabling publication, discovery and analysis of spatiotemporal data in the humanities”.  Bullet 2 to be exact.).     I’ve tracked some of our MITRE research in this area and am aware of the ISO-Space standard which deals with this topic;  A recent conference on the standard:
  https://sites.google.com/site/wikiisospace/,  and such research applying the standard: http://www.researchgate.net/profile/Marc_Verhagen/publication/260345114_Using_ISO-Space_for_Annotating_Spatial_Information/links/53fb6de20cf22f21c2f32657.pdf

Other than calling it “ISO-Space” I do not have exact references to the ISO identifier for that effort/standard — It is mentioned typically as a WG, itself under ISO committee TC 37.

And for time, things like TIMEX/TIMEX2 markup language etc. offer years of research for capturing the metadata about any date or time reference.

At this time the standards work may be worth a mention in the use case write-up.  If more work is required to find more exact connections of ISO Space and related work to this WG, that is something I would be interested in.   My current work is in information extraction, geocoding, and representing this space/time fuzziness in practical terms.

Marc Ubaldino
MITRE Corporation

From: Frans Knibbe
Date: Wednesday, April 29, 2015 at 8:49 AM
To: "Svensson, Lars", "public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>"
Subject: Re: Requirements from UC-19
Resent-From: <public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>>
Resent-Date: Wednesday, April 29, 2015 at 8:56 AM

Lars, thank you for your input. Some comments:

About the proposed requirement "It must be possible to state that the spatial coverage is inexact ("north of", "close to", "coordinates are approximate")": We have the Spatial Metadata<http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#SpatialMetadata> requirement. One of the spatial characteristics is spatial resolution. For geometric data (expressed in coordinates), spatial resolution could have a straightforward expression, which would be a measure of exactness. Would that cover the "coordinates are approximate" bit? I think "North of" is actually rather exact, it indicates a well defined area. "Close to" is yet another matter...without any other context the expression seems meaningless. Would it be possible to give an example that can show that it would be beneficial to have some kind of standardisation for "close to"?

As for time, I do not yet see a requirement like the Spatial Metadata<http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#SpatialMetadata> requirement for temporal data, but I think there could be. I can think of temporal extent, temporal resolution and temporal reference systems. Well, the temporal reference system is a separate requirement in the spreadsheet (column H).


2015-04-21 18:17 GMT+02:00 Svensson, Lars <L.Svensson@dnb.de<mailto:L.Svensson@dnb.de>>:
Dear Ed and Frans,

For my Use Case 19 (Publishing Cultural Heritage Data), I identified the following existing and new requirements:

- Best Practice
-- existing

1) There should be a common encoding/serialisation for spatial data as RDF
2) It should be possible to validate data

- Coverage
-- existing

1) Temporal context
2) geospatial alignment (not sure about this one, what it means is the alignment of a named entity to its geospatial feature)

-- new

1) It must be possible to state that the spatial coverage is inexact ("north of", "close to", "coordinates are approximate")

- Time
-- existing

1) temporal granularity flexibility
2) temporal vagueness [fuzzy dates/periods]
3) temporal reasoning and relations (xsd formats)
4) nominal temporal references [e. g. " Vormärz", "La Tène period"]

Can you please insert those into the spreadsheet?



*** Lesen. Hören. Wissen. Deutsche Nationalbibliothek ***
Dr. Lars G. Svensson
Deutsche Nationalbibliothek
Informationsinfrastruktur und Bestanderhaltung
Adickesallee 1
D-60322 Frankfurt am Main
Telefon: +49-69-1525-1752<tel:%2B49-69-1525-1752>
Telefax: +49-69-1525-1799<tel:%2B49-69-1525-1799>

Frans Knibbe
President Kennedylaan 1
1079 MB Amsterdam (NL)

T +31 (0)20 - 5711 347
E frans.knibbe@geodan.nl<mailto:frans.knibbe@geodan.nl>

Received on Wednesday, 29 April 2015 14:26:20 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:16 UTC