<p>All good then. </p>
<p>I started writing some ideas but I couldn´t get much done yet. I will try to add it to the wiki tomorrow.</p>
<p>On another front, I see that there has been some activity regarding Location (which will come handy for this). Have Postal Codes been considered? I understand that the problems of Postal Codes are:</p>
<p>. it´s ambiguous data, since Postal Code '15456' might reffer to a location in the US, Tailand, Egipt, etc. <br>. Postal Codes have different sintax according to country.</p>
<p>However a combination of Country Code (like the one for domain names, I believe there is an ISO for this) - Postal Code should be considered.</p>
<p>for example: <abbr class="postalcode" title="US 90210">90210</abbr> (Please excuse the cheesy reference!)</p>
<p>would probable solve the issue, since:</p>
<p>. A Postal Code is precise within a Country´s Postal system. (I´m guessing this but otherwise would be Kafkian)<br>. One could parse the Postal Code side according to the Country side. Which would solve the syntax issues.
</p>
<p>This may not be as sexy or precise as Latitude, Longitude coordinates but it would provide a simple, intuitive, easy to implement, non ambiguous, time tested, way of refering to locations.</p>
<p>What do you people think of this? I just wanted to add this to the discussion on locations, though I guess some further research is needed. </p>
<p>I´ll try to add tomorrow what I´ve been working on.</p>
<p>Emiliano Martínez Luque<br>TheThingsIWant.com<br></p><br><br>
<div><span class="gmail_quote">On 9/1/05, <b class="gmail_sendername">Ryan King</b> <<a href="mailto:ryan@technorati.com">ryan@technorati.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Sep 1, 2005, at 11:48 AM, Emiliano Martinez Luque wrote:<br>> Thank you Dr. Prabhakar for answering and thank you Tantek for the
<br>> guidance and encouragement. I was a little scared that I might have<br>> annoyed the people at this list. (Sometimes I try to sound polite<br>> or humble and it ends up sounding rude. The worst part is I then
<br>> try to correct it and it comes out even worse. :-) And then I get<br>> really paranoid... I guess I'm a little scared since I'm new to<br>> this kind of thing and I have read and studied documents writen by
<br>> people on this list. So it's kind of scary. Well.. you know, There<br>> is a human side to all of this!! :-).. )<br>><br>>> <snip><br>><br>> Yes, a pattern seems to be emerging. This makes sense as
<br>> methodology. Will start working on this today. I hope Trevor will<br>> be happy to join me and we will be able to get this going.<br><br>Awesome.<br><br>>> The next step, the art of taking that analysis and coming up with
<br>>> a proposed<br>>> schema, is a bit more challenging and can often use the experience/<br>>> expertise<br>>> of someone who has done at least some format design. There are<br>>> several such
<br>>> folks here, so once you have gotten the "listing-brainstorming"<br>>> document to<br>>> that point, ask again on this list, and hopefully one or more<br>>> folks will<br>>> help out.
<br>><br>> I was scared you were expecting us to get this all on our own!!!<br>> (Or that I might have given that impression. )<br><br>Yeah, this part is definitely the more difficult part. Let me know if<br>you need any assistance.
<br><br>-ryan<br><br>> Again Tantek thank you for your kindness and understanding. I'm<br>> just a little insecure since I'm new to this kind of thing. I was<br>> really scared I might freaked you people out. It's a relief to see
<br>> I didn't (or at least not that much) :-)<br>><br>> Emiliano Martinez Luque<br>> TheThingsIWant.com<br>_______________________________________________<br>microformats-discuss mailing list<br><a href="mailto:microformats-discuss@microformats.org">
microformats-discuss@microformats.org</a><br><a href="http://microformats.org/mailman/listinfo/microformats-discuss">http://microformats.org/mailman/listinfo/microformats-discuss</a><br></blockquote></div><br>