Difference between revisions of "Talk:Linguistic Literature GEO Search"

From MPDLMediaWiki
Jump to navigation Jump to search
m (New page: ==Linking of ISO language codes to geographical coordinates== : How should this database service look like? Is it enough only to publish the table online? --Kristina 09:...)
 
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Linking of ISO language codes to geographical coordinates==
===Table with geographical coordinates for all ISO 639-3 codes ===


: How should this database service look like? Is it enough only to publish the table online? --[[User:Kristina|Kristina]] 09:42, 15 January 2010 (UTC)
This table consists of the following columns:
 
: Yes, a basic table is sufficient. However, the table should be accessible for an automatic query. --[[User:MCysouw|MCysouw]] 20:38, 7 February 2010 (UTC)
 
Michael Cysouw has a large table with geographical coordinates for all ISO 639-3 codes. It is available here [[Image:geo.zip]]. This table consists of the following columns:


* NAME_OLD: nur ein String zur identifikation, kan ignoriert werden
* NAME_OLD: nur ein String zur identifikation, kan ignoriert werden
Line 14: Line 10:
* LONG: longitude
* LONG: longitude


To be checked:
==> Michael Cysouw hat die Tabelle im Mai 2010 noch mal überarbeitet, aktuelle Version : [[Image:Geo_cleaned_noduplicates2010-05-25.txt]]
 
'''FAQs:'''
* Are all ISO 639-3 codes available?
*: Ahould be checked automatically as the table consists of more than 7000 codes.
* What is going on if ISO 639-3 fields are missing in this table?
*: MPI Library EVA or Michael Cysouw will hand in the missing codes later.


* are all ISO 639-3 codes available?
===CoNE extension===
* what is going on with the missing ISO 639-3 fields in this table?
*CoNE contains all ISO 639-3 codes and is a web service including presentation
**these could be extended with predicates for ETNOLOGUE, LAT and LONG fields
**CoNE can be extended with search based on coordinates for languages
**data currently present for one ISO 639-3 language http://cone.mpdl.mpg.de/iso639-3/resource/aaa?format=rdf
**cone service http://cone.mpdl.mpg.de


Given these locations, each book on the LDH blog can get a little Google-Maps with the approximate location of the language being described. Also, we could make a separate page on the blog showing all locations of the languages available through the LDH.


:could we imagine this as a CoNE extension?--[[User:Natasab|Natasa]] 11:12, 10 March 2010 (UTC)
Just a note: like some of the other data sets already in cone, iso-639-3 is also not a static resource, i.e. code points can (and do) change. the same is true for the coordinates, and in this case even worse, because there is no defined change process associated with it. anyway, when we do put more and more data like this in cone, we'd have to come up with a concept of how to maintain this data.--[[User:Robert|Robert]] 11:45, 10 March 2010 (UTC)
**CoNE contains all ISO 639-3 codes and is a web service including presentation
:As of next CoNE (and PubMan) version - CoNE allows vocabulary moderation and editing for particular users. What is usually done in such cases: ISO-639-3 vocabulary is static to CoNE in sense that these are modified when official iso-639-3 vocabulary is modified. Geo Codes will be additional vocabulary (related to ISO-639-3) but fully owned by LDH Administrator for example. In this case LDH Administrator only modifies LDH specific data - and not ISO-639-3 vocabulary data. --[[User:Natasab|Natasa]] 12:34, 11 March 2010 (UTC)
***these could be extended with predicates for ETNOLOGUE, LAT and LONG fields
::I'm less concerned about the technical feasibility of vocabulary maintenance than about who is actually going to do it.--[[User:Robert|Robert]] 12:48, 11 March 2010 (UTC)
***CoNE can be extended with search based on coordinates for languages
***data currently present for one ISO 639-3 language http://cone.mpdl.mpg.de/iso639-3/resource/aaa?format=rdf
***cone service http://cone.mpdl.mpg.de
::just a note: like some of the other data sets already in cone, iso-639-3 is also not a static resource, i.e. code points can (and do) change. the same is true for the coordinates, and in this case even worse, because there is no defined change process associated with it. anyway, when we do put more and more data like this in cone, we'd have to come up with a concept of how to maintain this data.--[[User:Robert|Robert]] 11:45, 10 March 2010 (UTC)
:::as of next CoNe (and PubMan) version - CoNE allows vocabulary moderation and editing for particular users. What is usually done in such cases: iso-639-3 vocabulary is static to CoNE in sense that these are modified when official iso-639-3 vocabulary is modified. GeO Codes will be additional vocabulary (related to iso-639-3) but fully owned by LDH Administrator for example. In this case LDH Administrator only modifies LDH specific data - and not iso-639-3 vocabulary data. --[[User:Natasab|Natasa]] 12:34, 11 March 2010 (UTC)
::::i'm less concerned about the technical feasibility of vocabulary maintainance than about who is actually going to do it.--[[User:Robert|Robert]] 12:48, 11 March 2010 (UTC)

Latest revision as of 12:59, 3 August 2011

Table with geographical coordinates for all ISO 639-3 codes[edit]

This table consists of the following columns:

  • NAME_OLD: nur ein String zur identifikation, kan ignoriert werden
  • NAME_NEW: ich weiß nicht, was der Unterschied zu NAME_OLD ist
  • ETHNOLOGUE: der alte drei-Buchstaben code des Ethnologue, in Kapitalen
  • ISO 639-3: die neuene ISO codes, hier scheinen ein par zu Fehlen
  • LAT: latitude
  • LONG: longitude

==> Michael Cysouw hat die Tabelle im Mai 2010 noch mal überarbeitet, aktuelle Version : File:Geo cleaned noduplicates2010-05-25.txt

FAQs:

  • Are all ISO 639-3 codes available?
    Ahould be checked automatically as the table consists of more than 7000 codes.
  • What is going on if ISO 639-3 fields are missing in this table?
    MPI Library EVA or Michael Cysouw will hand in the missing codes later.

CoNE extension[edit]


Just a note: like some of the other data sets already in cone, iso-639-3 is also not a static resource, i.e. code points can (and do) change. the same is true for the coordinates, and in this case even worse, because there is no defined change process associated with it. anyway, when we do put more and more data like this in cone, we'd have to come up with a concept of how to maintain this data.--Robert 11:45, 10 March 2010 (UTC)

As of next CoNE (and PubMan) version - CoNE allows vocabulary moderation and editing for particular users. What is usually done in such cases: ISO-639-3 vocabulary is static to CoNE in sense that these are modified when official iso-639-3 vocabulary is modified. Geo Codes will be additional vocabulary (related to ISO-639-3) but fully owned by LDH Administrator for example. In this case LDH Administrator only modifies LDH specific data - and not ISO-639-3 vocabulary data. --Natasa 12:34, 11 March 2010 (UTC)
I'm less concerned about the technical feasibility of vocabulary maintenance than about who is actually going to do it.--Robert 12:48, 11 March 2010 (UTC)