status and use/fulness of the geoloc: attribute
Dear DB-Folks, in preparation for the upcoming WG Meeting in Amsterdam, and following up on dicussions during the previous one, I'd like to start the review and discussion on the geoloc: attribute in IPv4 and IPv6 inetnum objects. To get things going I'd like to solicit input from people and entities who/which have populated objects, and those making use of the information. What was your experience? Is this stuff useful? On a more general basis I'd like the community to review the current (sort of experimental) functionality and comment on the problems - if any - or suggest improvements! At the same time I am asking the NCC to provide us with some insight on the current use of this attribute. Thanks, Wilfried.
Hello all, As of today, 19th September 2012, we have: 3,694,101 "inetnum:" objects in RIPE Database, 366 of them have "geoloc:" attribute and 174 of them have "language:" attribute. 105,155 "inet6num:" objects in RIPE Database, 5 of them have "geoloc:" attribute and 11 of them have "language:" attribute. Please let me know if there are other useful stats we can provide. Kind Regards, Kaveh. --- Kaveh Ranjbar, RIPE NCC Database Group Manager On Sep 19, 2012, at 4:44 PM, Wilfried Woeber <Woeber@CC.UniVie.ac.at> wrote:
At the same time I am asking the NCC to provide us with some insight on the current use of this attribute.
On 19 Sep 2012, at 17:04, Kaveh Ranjbar <kranjbar@ripe.net> wrote:
Hello all,
As of today, 19th September 2012, we have:
3,694,101 "inetnum:" objects in RIPE Database, 366 of them have "geoloc:" attribute and 174 of them have "language:" attribute. 105,155 "inet6num:" objects in RIPE Database, 5 of them have "geoloc:" attribute and 11 of them have "language:" attribute.
To put this in perspective, it should be noted that the existence of these attributes is not advertised or highlighted in any way, shape or form. One has to simply come across them when adding or editing an inetnum or inet6num object. -Alex
Alex Band wrote:
On 19 Sep 2012, at 17:04, Kaveh Ranjbar <kranjbar@ripe.net> wrote:
Hello all,
As of today, 19th September 2012, we have:
3,694,101 "inetnum:" objects in RIPE Database, 366 of them have "geoloc:" attribute and 174 of them have "language:" attribute. 105,155 "inet6num:" objects in RIPE Database, 5 of them have "geoloc:" attribute and 11 of them have "language:" attribute.
To put this in perspective, it should be noted that the existence of these attributes is not advertised or highlighted in any way, shape or form. One has to simply come across them when adding or editing an inetnum or inet6num object.
Sure, that's well understood, but I hope that those parties which proposed the functionality, and those who supported the idea, would give us some feedback. Wilfried
-Alex
Wilfried Woeber wrote:
Dear DB-Folks, [...] What was your experience?
When preparing for this thread, I had a look at the specification for the language: tag. The syntax prescribes "Valid two-letter ISO 639-1 language code" However, this appears to be a sparsely populated list when compared to the three-letter list. What is the difference or what is the motivation for the restriction to the short code. As an aside (I am ignorant with that regard), I have seen language encodings being widely used that look like PT_PT or PT_BR. Difference or applicability? Wilfried.
Language tags has always been, and still are the source of conflicts in standard organisations (ISO and IETF etc.) As an aside (I am ignorant with that regard), I have seen language encodings being widely used that look like PT_PT or PT_BR. Difference or applicability? As far as I remember PT_PT stands for Portugees as spoken in Portugal while PT-BR denotes the Brazailian variant. So one sees American English, UK english etc. jaap
On 19.09.2012 20:58, Jaap Akkerhuis wrote:
Language tags has always been, and still are the source of conflicts in standard organisations (ISO and IETF etc.)
As an aside (I am ignorant with that regard), I have seen language encodings being widely used that look like PT_PT or PT_BR. Difference or applicability?
As far as I remember PT_PT stands for Portugees as spoken in Portugal while PT-BR denotes the Brazailian variant. So one sees American English, UK english etc.
And so on, and so on, and so on - e.g.: de: General German de-de: German German de-at: Austrian German de-ch: Swiss German de-li: Liechtenstein German de-lu: Luxemburgian German de-nl: Dutch German ;-) Have a look at the language prefs of your browser of choice. Best, -C.
participants (5)
-
Alex Band -
Carsten Schiefner -
Jaap Akkerhuis -
Kaveh Ranjbar -
Wilfried Woeber