[uf-discuss] human readable date parsing
With all of the discussion about iso dates being unreadable and that an iso date isn't necessarily required when someone enters a date (i.e. saying 24th June doesn't translate into a single date, neither does 'thursday'). Shouldn't the focus be on trying to standardise date formats rather than trying to hide the iso date? If we can get a parser to recognise 'human readable' dates (which *is* possible, if not totally easy, http://labix.org/python-dateutil for a python version). Just a thought... Tim -- Tim Parkin, Pollenation Internet Ltd, Leeds, UK ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] human readable date parsing
James Craig wrote: Tim Parkin wrote: With all of the discussion about iso dates being unreadable and that an iso date isn't necessarily required when someone enters a date (i.e. saying 24th June doesn't translate into a single date, neither does 'thursday'). Shouldn't the focus be on trying to standardise date formats rather than trying to hide the iso date? If we can get a parser to recognise 'human readable' dates (which *is* possible, if not totally easy, http://labix.org/python-dateutil for a python version). I disagree. If you try to make other, human readable formats into a standard, they will fall short when it comes time to internationaliz(s)e it. If you can come up with a better format readable to all machine and all humans in all languages, I'll recant. I think the ISO 8601 is the best machine data format for the job. I just don't think it should be in abbr. Yes, indeed.. And I was wrong to say shouldn't the focus be.. I was just approaching the problem from a different angle to see if it looked more tractable, not from this angle obviously :-) In the vein of approaching things from a totally different angle, how about using hidden input field for the value? (I realise there are many problems with this but it might be worth documenting some of the negatives for future reference - I'm happy to start by saying Visual Developers propensity to formify the whole page could cause issues.. but then again VD may just be an issue in itself). Tim ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] Re: namespaces discussions off-topic
Ian Davis wrote: On 01/05/2007 07:26, Tantek Çelik wrote: It's been tried by numerous groups, before microformats, and after. It's even been tried in the context of RSS and RDF, and in practice people write scrapers that look for namespace prefixes as if they are part of the element name, not as mere shorthands for namespace URIs. Isn't this a narrow view of namespaces, i.e. the XML viewpoint. There are many types of non-URI/QName namespacing mechanisms such as Java package name conventions, Perl module conventions etc. Are those offtopic too? It would help to clarify the wiki page on namespacing as it seems to cover xml formal namespaces rather than namespacing by convention (to avoid name collision - my worry with the classnames like 'logo' for instance). I'm only an mf newb but I'm hoping my perspective may be useful. Tim Parkin ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: namespaces discussions off-topic (was Re: [uf-discuss] changing abbr-design-pattern to title-design-pattern?)
Ian Davis wrote: On 01/05/2007 17:03, Charles Iliya Krempeaux wrote: Hello Tantek, I think Ian may have meant... what about using (for Microformats) namespaces with pre-defined (and never changing) namespace prefixes (like in Java and Perl), instead of variable namespace prefixes (like in XML). Yes. Of course I understand the distinction between code and content. But I suggested Java and Perl practices as illustrations of conventions for namespacing things. I'm interested in looking at patterns of naming that may allow more decentralised collaboration. I would also be good to ressurect the page called NamespacesChickenLittling, of which I can see no trace but is referred to in vote-links-faq i.e. For followup QA about VoteLinks and namespaces, see NamespacesChickenLittling. this could probably cover the hAudio namespace useage also. Tim p.s. I'm not sure namespaces can be said to have failed when http://microformats.org has two of them.. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss