Re: Property "geographic identifier" in LOCN (was: Re: ISA Core Location Vocabulary)

I agree.  The spatial version of owl:sameAs is important, so is the temporal version.

That "changing the alphabetic sort" part of GNIS ID is my motivation for FedNet [1].  It is necessary, at least conceptually to the "middle born" of the population bloodline.

I wish I had a domain partition type (term) less fascist sounding than "HOMELAND" but the US Census doesn't feel a need to define (NATION)+ and RDF does not feel a need to define (NATION)*.  These two seemingly minor deficiencies lead to data processing (code set) mischief, though ...

For example (issue 4), as a parent of school age children you want education to be both progressive and periodic and linked data to be fair.  As an employer you want work to be periodic and as an employee you want work to be fair.  As an astronomer, you want the sun to keep doing what it is doing.  At some point you have to explain that going to school in the dark or work in excess of (about) a half day is fair because watches and organizations are "people" and not "things".  The calculation [2] is a bit strange - a tiny quantum leap bracketed two half-lives.  And the "tiny" quantum leap, about 16 seconds per decade is an eternity on a Stock Exchange.

Who is Linked Data intended to benefit, presuming that OWL is not intended to benefit anyone ?

R.S.V.P  127.0.0.1@GNIS_ID ;-)

--Gannon 
--------------------------------------------
On Fri, 1/3/14, Kostis Kyzirakos <Kostis.Kyzirakos@cwi.nl> wrote:

 Subject: Re: Property "geographic identifier" in LOCN (was: Re: ISA Core  Location Vocabulary)
 To: "Raphaël Troncy" <raphael.troncy@eurecom.fr>
 Cc: "Frans Knibbe | Geodan" <frans.knibbe@geodan.nl>, "LocAdd W3C CG Public Mailing list" <public-locadd@w3.org>
 Date: Friday, January 3, 2014, 5:13 AM
 
 Hi,
 In the RDF world, every resource is identified by a URI.
 
 In the GIS world, a geographic feature is usually identified
 by a geographic identifier.
 
 
 
 
 In the US for example, "The Geographic Names
 Information System Identifier (GNIS ID) 
 is a variable length, permanent, numeric identifier of up to
 ten digits in length that 
 identifies each entity uniquely within the nation.  The
 GNIS is the new American National 
 
 
 Standards Institute (ANSI) national standard code for
 several entity types.  Because each 
 entity's GNIS ID is permanent, it will not change if the
 entity changes its name or if 
 creation of a new entity changes the alphabetic sort.
 [...]" [1].
 
 
 
 My opinion is that the vocabulary must contain a property
 like the 
 proposed 
 "geographic identifier" to ensure interoperability
 with 
 existing geospatial 
 tools/datasets. We have found this property to be of great
 importance, as far as 
 interoperability and  adoption of Linked Data technologies
 from domain experts are 
 concerned. In the past, we have developed a real-time
 wildfire monitoring service [2] 
 
 
 for the National Observatory of Athens, where we used
 satellite data along with 
 Linked Geospatial Data to produce fire maps. At any given
 point, we were able to 
 export the result of a stSPARQL/GeoSPARQL query as an ESRI
 shape file (that 
 
 
 included geographic identifiers), that allowed the domain
 experts to use the (enriched 
 with Linked Geospatial Data) shape files with their existing
 (I would not call them 
 legacy) tools/datasets/processing chains/infrastructure in
 general. This allowed them 
 
 
 to load the shape files to ArcGIS for example, do a thematic
 join (based on the 
 geographic identifier that was preserved) with auxiliary
 datasets that they are using 
 in a daily basis and are not published as Linked Open Data
 and produce their final 
 
 
 products. 
 
 
 After reading the description of the geographic
 identifier property, I think that this is 
 property is used as spatial version of owl:sameAs between
 identifiers defined by 
 different authorities/publishers. In addition, a publisher
 can use this property to 
 
 
 assert that a location has a specific identifier (e.g., a
 URN) which is very useful in 
 practice in order to ensure interoperability with existing
 infrastructures.
 
 
 Best,
 Kostis
 
 [1] http://www.census.gov/geo/reference/gtc/gtc_gnisid.html
 
 
 [2] http://test.strabon.di.uoa.gr/
   
 
 
 ===================================================
 Kostis E. Kyzirakos, Ph.D.
 Centrum voor Wiskunde en Informatica
 DB Architectures (DA)
 Office L320
 Science Park 123
 1098 XG Amsterdam  (NL)
 
 
 
 tel: +31 (20) 592-4039
 mobile: +31 (0) 6422-95345
 
 
 e-mail:  kostis@cwi.nl
 ===================================================
 
 
 On Thu, Jan 2, 2014 at
 9:23 AM, Raphaël Troncy <raphael.troncy@eurecom.fr>
 wrote:
 
 
 
 Dear all,
 
 
 
 
 Is it possible to give an RDF example of meaningful usage of
 "geographic
 
 identifier"? I think that could help  in understanding
 the issue.
 
 
 
 
 I find myself with the same opinion than Frans. I don't
 yet understand the purpose of this "geographic
 identifier" property, although I understand the need
 for a vocab to have its own way to describe its specific
 identifiers if there are some constraints on how those
 identifiers should be interpreted. When this property was
 introduced in the vocab? Is it a mapping with a specific
 field from the INSPIRE schemas?
 
 
 
 
 Best regards.
 
 
 
   Raphaël
 
 
 
 -- 
 
 Raphaël Troncy
 
 EURECOM, Campus SophiaTech
 
 Multimedia Communications Department
 
 450 route des Chappes, 06410 Biot, France.
 
 e-mail: raphael.troncy@eurecom.fr
 & raphael.troncy@gmail.com
 
 Tel: +33 (0)4 - 9300 8242
 
 Fax: +33 (0)4 - 9000 8200
 
 Web: http://www.eurecom.fr/~troncy/

Received on Friday, 3 January 2014 18:51:17 UTC