[georss] proposal for country code in GeoRSS

[Carl Reed OGC Account]

Marc -

A bit more information. There is also an Internet Draft for enhancing DHCP 
(4 and 6) for location - both a point geometry and address (civic location) 
the civic location expression is identical to that used in the civic-lo 
document I mentioned in the previous email. In both documents, the Examples 
and inspiration were drawn from the Street Address Data Standard of the 
Federal Geographic Data Committee and URISA. Please note that the civic-lo 
document uses XML for expressing address. The DHCP Internet Draft does not. 
This is because the DHCP payload is quite restricted in terms of the number 
of bytes allowed and is therefore predominantly a binary format.

The DHCP reference is: Dynamic Host Configuration Protocol (DHCPv4 and 
DHCPv6) Option for Civic Addresses Configuration Informatio 
draft-ietf-geopriv-dhcp-civil-09 - 
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-09.txt .

>From all I can tell, the FGDC Address Standard is gaining traction. In terms 
of expressing a address content standard as XML, I would look at the OGC 
OpenLS Core Spec Document as well as the OASIS xal draft. In terms of GML 
and GeoRSS GML, here is a snippet

<gml:featureMember>

<SampleFeature>

  <gml:location priority="1">

<gml:StreetAddress>

  <gml:addressee>John Q. Smith</gml:addressee>

  <gml:primaryAddressNumber>123</gml:primaryAddressNumber>

  <gml:streetName>Main Street</gml:streetName>

  <gml:city>Anytown</gml:city>

  <gml:state>MD</gml:state>

  <gml:zipCode>20910</gml:zipCode>

  <gml:countryCode>USA</gml:countryCode>

  </gml:StreetAddress>

  </gml:location>

  </SampleFeature>

  </gml:featureMember>

If the tags were changed to use those in the FGDC address standard, then we 
would be compatible.

Just some more thoughts. I also need to check out the OASIS Xal draft spec. 
However, that spec is targeted more toward e-Business processsing (such as 
purchase orders, invoices, and so forth)

Regards

Carl



----- Original Message ----- 
From: "Marc" <marc at geonames.org>
To: "Carl Reed OGC Account" <creed at opengeospatial.org>
Cc: <georss at lists.eogeo.org>
Sent: Saturday, May 06, 2006 2:15 AM
Subject: Re: [georss] proposal for country code in GeoRSS


> Hi Carl
>
> Thanks for the link. I was hoping someone would come up with information 
> of this kind.
> I don't think we should reinvent the wheel and this draft makes sense to 
> me. Do you think it would be possible to include it in GeoRSS?
>
> It would be really useful if GeoRSS offered a standard way of encoding 
> addresses. Otherwise every feed producer will come up with proprietary 
> address encoding in RSS. Yahoo, Google and others are already using their 
> own way of encoding addresses in RSS.
>
> Cheers,
>
> Marc
>
> Carl Reed OGC Account wrote:
>
>> All -
>>
>> I am not opposed. However, before going down this road I would strongly 
>> encourage the group to look at the work on civic address by the IETF 
>> (based on ISO 3166-1), specifically 
>> http://www.ietf.org/internet-drafts/draft-ietf-geopriv-revised-civic-lo-02.txt . 
>> PIDF -LO is another internet standard (draft) that uses two ways to 
>> express location - civic and geometry. The Geometry version uses GML 
>> 3.1.1.
>>
>> Anyway, the IETF location group has had considerable discussion and 
>> investigation into civic address and location enabled internet payloads. 
>> This has been going on for some 18 months.
>>
>> Would be silly to ignore all their hard work.
>>
>> Cheers
>>
>> Carl
>