Rethinking Gazetteers and Interoperability. Greg Janée University of California at Santa Barbara

Size: px

Start display at page:

Download "Rethinking Gazetteers and Interoperability. Greg Janée University of California at Santa Barbara"

Kristian Davidson
5 years ago
Views:

1 Rethinking Gazetteers and Interoperability Greg Janée University of California at Santa Barbara

2 Outline ADL gazetteer protocol Interoperability use cases Gazetteer protocol, revisited Question for the workshop

3 Motivation Protocol history define gazetteer s role in ADL architecture functional definition to complement Gazetteer Content Standard (GCS) Development 2001: co-developed protocol with ESRI 2003: minor additions, deletions Retargetable server full, GCS-compliant schema lite schema Web-based client

4 Protocol characteristics Defines gazetteer model simplified; focus on interoperability compatible with, mappable from GCS Seven query types Abstract specification HTTP+XML instantiation Separate thesaurus protocol Z39.19 thesaurus model

5 Gazetteer model gazetteer description,... each value has a status; one value must be designated primary entry identifier 0+ codes status 1+ names 1+ footprints 1+ types named relationship thesaurus references

6 Limitations/problems No support for qualified placename queries e.g., find Santa Barbara, CA onerous to implement using low-level facilities Conflicting and unpredictable query semantics a tale of two queries: spatially contained within California has relationship PartOf to California results are implementation-specific, unpredictable, and variable

7 Harvest Interoperability use cases aggregate distributed, esp. local gazetteers need protocol (OAI-PMH) representation standard(s) (GCS) Lookup find place by name or other description

13 Lookup Use cases, cont. find place by name or other description broader than gazetteer: find place by anything Reverse lookup find nearby places find nearby places of a given type find nearest place of a given type

15 Reverse lookup Use cases, cont. find nearest place of a given type Geoparse identify & geolocate place references in document eg., GeoNames.org RSS-to-GeoRSS converter

17 Geoparse Use cases, cont. uses gazetteers, but not protocol Ontology inferencing over knowledge base of places requirements: unique Ids, ontology of relationships unification of facts!

18 Gazetteer protocol, revisited Harvest Lookup Reverse lookup Geoparse Ontology already better supported by OAI-PMH too limited, rigid supports near, but not nearest N/A N/A

19 Question Should we rethink gazetteer interoperability? From: have an entity (gazetteer), have a protocol for accessing that entity To: multiple protocols oriented around use cases, functionality that various kinds of entities (gazetteers, geocoders, etc.) participate in, implement to varying degrees

20 Rethinking Gazetteers and Interoperability Greg Janée University of California at Santa Barbara 1

21 Outline ADL gazetteer protocol Interoperability use cases Gazetteer protocol, revisited Question for the workshop 2

22 Motivation Protocol history define gazetteer s role in ADL architecture functional definition to complement Gazetteer Content Standard (GCS) Development 2001: co-developed protocol with ESRI 2003: minor additions, deletions Retargetable server full, GCS-compliant schema lite schema Web-based client 3

23 Protocol characteristics Defines gazetteer model simplified; focus on interoperability compatible with, mappable from GCS Seven query types Abstract specification HTTP+XML instantiation Separate thesaurus protocol Z39.19 thesaurus model 4

24 Gazetteer model gazetteer description,... each value has a status; one value must be designated primary entry identifier 0+ codes status 1+ names 1+ footprints 1+ types named relationship thesaurus references 5

25 Limitations/problems No support for qualified placename queries e.g., find Santa Barbara, CA onerous to implement using low-level facilities Conflicting and unpredictable query semantics a tale of two queries: spatially contained within California has relationship PartOf to California results are implementation-specific, unpredictable, and variable 6

26 Harvest Interoperability use cases aggregate distributed, esp. local gazetteers need protocol (OAI-PMH) representation standard(s) (GCS) Lookup find place by name or other description 7

27 8

28 9

29 10

30 11

31 12

32 Lookup Use cases, cont. find place by name or other description broader than gazetteer: find place by anything Reverse lookup find nearby places find nearby places of a given type find nearest place of a given type 13

33 14

34 Reverse lookup Use cases, cont. find nearest place of a given type Geoparse identify & geolocate place references in document eg., GeoNames.org RSS-to-GeoRSS converter 15

35 16

36 Geoparse Use cases, cont. uses gazetteers, but not protocol Ontology inferencing over knowledge base of places requirements: unique Ids, ontology of relationships unification of facts! 17

37 Gazetteer protocol, revisited Harvest Lookup Reverse lookup Geoparse Ontology already better supported by OAI-PMH too limited, rigid supports near, but not nearest N/A N/A 18

38 Question Should we rethink gazetteer interoperability? From: have an entity (gazetteer), have a protocol for accessing that entity To: multiple protocols oriented around use cases, functionality that various kinds of entities (gazetteers, geocoders, etc.) participate in, implement to varying degrees 19

Chapter 8: Enhanced ER Model

Chapter 8: Enhanced ER Model Subclasses, Superclasses, and Inheritance Specialization and Generalization Constraints and Characteristics of Specialization and Generalization Hierarchies Modeling of UNION