[georss] [OWS-4-SWE] Georss extension

Tue Oct 10 11:45:47 EDT 2006

Thanks, Simon.

Yes, there are several key ISO standards in common usage in the ICT/internet 
worlds that are free of charge. 3166 is one of these. Another one is 8601 - 
Date and Time. This document can be downloaded for free from 
http://en.wikipedia.org/wiki/ISO_8601 . Also, both the W3C and the IETF have 
developed profiles of ISO 8601 for their respective communities. 
http://www.w3.org/TR/NOTE-datetime and 
http://www3.ietf.org/proceedings/02jul/I-D/draft-ietf-impp-datetime-05.txt .

That said, you can also buy many ISO standards through ANSI at a much 
reduced cost.

Cheers

Carl

----- Original Message ----- 
From: <Simon.Cox at csiro.au>
To: <mike.botts at nsstc.uah.edu>; <georss at highearthorbit.com>; 
<marc at geonames.org>
Cc: <georss at lists.eogeo.org>; <ows-4-swe at opengeospatial.org>; 
<Stuart.Frye at gsfc.nasa.gov>; <creed at opengeospatial.org>; 
<dan.mandl at gsfc.nasa.gov>
Sent: Monday, October 09, 2006 9:08 PM
Subject: RE: [OWS-4-SWE] [georss] Georss extension

> That is correct in general, but not in this case - the 3166 codes are
> freely available from multiple sources:
> http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists
> /index.html
> http://www.iso.org/iso/en/prods-services/iso3166ma/index.html
> http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html
> http://en.wikipedia.org/wiki/ISO_3166
>
> This information is not hidden - see:
> http://www.google.com.au/search?q=ISO+3166
>
> Simon
>
>> -----Original Message-----
>> From: ows-4-swe-bounces+simon.cox=csiro.au at opengeospatial.org
>> [mailto:ows-4-swe-bounces+simon.cox=csiro.au at opengeospatial.or
> g] On Behalf Of Mike Botts
>> Sent: Tuesday, 10 October 2006 10:51 AM
>> To: Cox, Simon (E&M, Kensington); 'Andrew Turner'; 'Marc'
>> Cc: georss at lists.eogeo.org; ows-4-swe at opengeospatial.org;
>> 'Stuart Frye'; 'Carl Reed OGC Account'; 'Dan Mandl'
>> Subject: Re: [OWS-4-SWE] [georss] Georss extension
>>
>> Simon.
>>
>> The lack of knowledge about ISO specifications is really the
>> fault of ISO. I realize that "selling" the specification is
>> the way ISO funds itself, but the decision not to make these
>> specs readily available through soft copy is to me a major
>> problem with ISO. Basing the spec cost based on the number of
>> pages is equally stupid. I really wish they would reconsider
>> their "business" plan and make ISO specs more readily available.
>>
>> Done griping.
>> Mike Botts
>>
>>
>> --------------------------------------------------------
>> Mike Botts, Ph.D.                   mike.botts at uah.edu
>> Principal Research Scientist          http://vast.uah.edu
>> NSSTC
>> University of Alabama in Huntsville (256) 961-7760
>> Huntsville, AL 35899 USA            (256) 652-0165 cell
>> --------------------------------------------------------
>>
>>
>> -----Original Message-----
>> From: ows-4-swe-bounces+mike.botts=uah.edu at opengeospatial.org
>> [mailto:ows-4-swe-bounces+mike.botts=uah.edu at opengeospatial.or
> g] On Behalf Of Simon Cox
>> Sent: Sunday, September 24, 2006 7:59 AM
>> To: Andrew Turner; Marc
>> Cc: georss at lists.eogeo.org; Linda Derezinski;
>> ows-4-swe at opengeospatial.org; Stuart Frye; Carl Reed OGC
>> Account; Dan Mandl
>> Subject: Re: [OWS-4-SWE] [georss] Georss extension
>>
>> <brokenRecord>
>>
>> ISO 3166 is an easily available and broadly accepted standard
>> for 2-letter country codes - see
>> http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-
>> code-lists/lis
>> t-en1.html
>>
>> "AU" is Australia, "AT" is Austria, "BR" is Brazil, etc.
>>
>> [Still surprised when people don't seem to be able (or
>> willing) to find pre-existing resources that already scratch
>> their itch ...]
>>
>> </brokenRecord>
>>
>> Simon
>>
>> ----- Original Message -----
>> From: "Andrew Turner" <georss at highearthorbit.com>
>> To: "Marc" <marc at geonames.org>
>> Cc: <georss at lists.eogeo.org>; "Linda Derezinski"
>> <linda at innovatesolutions.com>;
>> <ows-4-swe at opengeospatial.org>; "Stuart Frye"
>>
>> <Stuart.Frye at gsfc.nasa.gov>; "Carl Reed OGC Account"
>> <creed at opengeospatial.org>; "Dan Mandl" <dan.mandl at gsfc.nasa.gov>
>> Sent: Saturday, September 23, 2006 9:39 PM
>> Subject: Re: [OWS-4-SWE] [georss] Georss extension
>>
>>
>> > On 9/23/06, Marc <marc at geonames.org> wrote:
>> >> The point I am trying to make is : 'How does Joe Average
>> Programmer
>> >> know this?' Don't we need a simple and bulletproof specification
>> >> understandable also for non gis-specialists?
>> >> Maybe we can agree on a subset of xAL, a kind of "Simple xAL". The
>> >> xAL specification clearly says : "Important: Use only elements and
>> >> attributes that make sense to you. Ignore the rest that
>> are needless
>> >> for you. "
>> >
>> > I agree that this is the issue at hand (as well as the
>> question if xAL
>> > supports non-inhabited areas like the ocean). Like georss:point vs.
>> > GML, a simple format makes the entire idea digestable to the large
>> > community that will actually implement the spec in publishing and
>> > consuming. Making something *full featured*, but difficult to use
>> > makes it very difficult for adoption.
>> >
>> > I think we talked about a simplified xAL - similar to your geonames
>> > namespace perhaps? - at FOSS4G.
>> >
>> > There are issues with your proposed geonames however. You
>> still suffer
>> > from the country code problem. Pat's example used BR, where
>> did that
>> > come from? Also, the countryName, is that assumed to be the English
>> > country name?
>> >
>> > So how to have a simplified format, for easy
>> adoption/understanding,
>> > and allow easy 'growth' into xAL for complex naming?
>> >
>> > Andrew
>> > _______________________________________________
>> > OWS-4-SWE mailing list
>> > OWS-4-SWE at opengeospatial.org
>> > https://mail.opengeospatial.org/mailman/listinfo/ows-4-swe
>> >
>> _______________________________________________
>> OWS-4-SWE mailing list
>> OWS-4-SWE at opengeospatial.org
>> https://mail.opengeospatial.org/mailman/listinfo/ows-4-swe
>>
>> _______________________________________________
>> OWS-4-SWE mailing list
>> OWS-4-SWE at opengeospatial.org
>> https://mail.opengeospatial.org/mailman/listinfo/ows-4-swe
>>
> 