Re: ISA Core Location Vocabulary

Hi again, Frans.

My comments inline.

[snip]

> By the way, perhaps it would help to publish something about the
> connection between LOCN and LocAdd on the LocAdd home page (
> http://www.w3.org/community/locadd/)? Perhaps that would solicit some
> more feedback.
>

Thanks for the suggestion. I'll take care of that.


> With regard to interoperability of INSPIRE data: Isn't geometry generally
>> defined as GM_Object (from ISO 19107)  in INSPIRE?  And shouldn't that mean
>> that any geometry encoding should support all subtypes of GM_Object?
>
>
>  Sorry, Frans, I'm missing the point here - probably because of the late
> hour ;)
>
>  Could you please articulate it more explicitly?
>
> Yes, I will try. I think the point I wanted to make is that GM_Object
> allows many kinds of exotic geometries that are not supported by some of
> the geometry encodings that are allowed by LOCN. So a data publisher having
> INSPIRE-compliant data, based on GM_Object, could not make use of encodings
> like KML or GeoShape because they are not able to express all the kinds of
> geometries that should be possible according to INSPIRE. So perhaps the
> ability to handle GM_Object should be a criterion in the way locn:geometry
> is defined?
>

I'm not sure this is an issue to be addressed by the LOCN voc. I see this
more in the scope of work on RDF inside INSPIRE. Any possible requirements
coming out from such work might then be taken into account in the LOCN voc,
if possible.

Andrea