Re: Requirements from UC-19

Hi Lars,

the definition of vague locations should be covered now with the following
requirement: Spatial vagueness
<http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#SpatialVagueness>
.

Regards,
Alejandro

On 5 May 2015 at 11:36, Alejandro Llaves <allaves@fi.upm.es> wrote:

> Hi Lars,
>
> I have checked the requested existing requirements in the spreadsheet for
> your use case Publishing cultural heritage data
> <http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#PublishingCulturalHeritageData>.
> The new requirement you suggested for Coverage is related to representing
> uncertain spatio-temporal data. This is partially covered in the Time
> deliverable ("It must be possible to describe time points and intervals in
> a vague, imprecise manner", tab Time, column C). For the spatial
> uncertainty, I am wondering if you have cases of uncertain/fuzzy coverage
> data or the problem is just on referencing vague locations in space. In
> case of the latter, this could be covered with the requirement at tab
> Coverage, column M. Otherwise, we can discuss whether a new requirement is
> needed.
>
> Best regards,
> Alejandro
>
> On 29 April 2015 at 23:05, Andrea Perego <andrea.perego@jrc.ec.europa.eu>
> wrote:
>
>> Hi, Frans.
>>
>> > [snip]
>> >
>> > As for time, I do not yet see a requirement like the Spatial Metadata
>> > 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).
>>
>> Just to note that we do have a metadata-related use case including
>> temporal resolution and temporal reference systems in the
>> requirements. It's the in Section 4.42:
>>
>>
>> http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html#h-geospatialextensionstodomainindependentmetadataschemas
>>
>> The requirements are listed in the UC description.
>>
>> BTW, these are still open issues in the work on GeoDCAT-AP described
>> by the UC. The GeoDCAT-AP WG is currently maintaining an XSLT to
>> transform ISO 19139 metadata records into RDF, and mappings for the
>> metadata elements under discussion are still missing (along with the
>> one concerning CRSs):
>>
>>
>> https://webgate.ec.europa.eu/CITnet/stash/projects/ODCKAN/repos/iso-19139-to-dcat-ap/
>>
>> >From what reported by members of the GeoDCAT-AP WG, it is apparent
>> that many organisations dealing with spatial data and their
>> publication on cross-domain data catalogues are using provisional
>> approaches to deal with this problem, while waiting for the
>> publication of best practices.
>>
>> Cheers,
>>
>> Andrea
>>
>>
>
>
> --
> Alejandro Llaves
>
> Ontology Engineering Group (OEG)
>
> Artificial Intelligence Department
>
> Universidad Politécnica de Madrid
>
> Avda. Montepríncipe s/n
>
> Boadilla del Monte, 28660 Madrid, Spain
>
>
> http://www.oeg-upm.net/index.php/phd/325-allaves
>
>
> allaves@fi.upm.es
>



-- 
Alejandro Llaves

Ontology Engineering Group (OEG)

Artificial Intelligence Department

Universidad Politécnica de Madrid

Avda. Montepríncipe s/n

Boadilla del Monte, 28660 Madrid, Spain


http://www.oeg-upm.net/index.php/phd/325-allaves


allaves@fi.upm.es