 | | Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
|
(...) Does this solve the "what's near me" problem? Perhaps there's an API someplace that will help figure that out? (...) I figure the same web-app could be written to generate lat/long? Maybe that's not so easy to do, I haven't looked it up? ... (...) (20 years ago, 1-Sep-04, to lugnet.publish)
|
| |
| | Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
|
(...) We could use this format, but it's a little bit harder for computers to parse. Not a big deal, especially for perl (of course :), but maybe we want to go with a more machine-friendly format? 2004-08-30T12:00:00Z This would be the equivilent of (...) (20 years ago, 1-Sep-04, to lugnet.publish)
|
| |
| | Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
|
(...) I did an hour of surfing today, and came up with a few things, none of which really strikes me as being perfect. The most easily-implemented regional listing is the ISO-3166-2 standard: (URL) (Click "Local ISO codes" next to the country in (...) (20 years ago, 1-Sep-04, to lugnet.publish)
|
| |
| | Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
|
An excellent start Kelly. As publisher of RSS for Brickset and brickish.org, here are my comments. (...) I'd vote for once at the top. I appreciate that its inclusion potentially opens up lenni for use by others, but given that much of the spec (...) (20 years ago, 31-Aug-04, to lugnet.publish)
|
| |
| | Re: LENNI Additions to RSS/Atom spec - preliminary proposal
|
|
Great comments, thanks! To recap, here's what I'm gleaning from the comments. I agree with 1-4, am shaky on 5, like leaving 6 alone, need more info for 7, and like the optimism of 8. 1. Namespace "lenni" in lower case - since XML tags are by (...) (20 years ago, 31-Aug-04, to lugnet.publish)
|
