- From: <bugzilla@jessica.w3.org>
- Date: Thu, 16 Dec 2010 12:50:24 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11562 Summary: address tag definition has no relation to it's name Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5: The Markup Language (editor: Michael(tm) Smith) AssignedTo: mike@w3.org ReportedBy: arieh.glazer@gmail.com QAContact: public-html-bugzilla@w3.org CC: public-html-wg-issue-tracking@w3.org, public-html@w3.org Hey I wanted to comment on the definition of the address tag. I recommend that the address tag will be used to describe an address or location, virtual or physical. Following are the reasons why I think this is important. There are 3 main issues: 1. HTML needs a tag to specify a location, as this is a common meaningful information. It is absurd that the only way for us as developers do this is by 3rd party data structures, sch as microformats or microdata. 2. As I see it, literally speaking, the address tag indicates it's content has something to do with an address, or a location. Making it mean something else entirely is completely counter-intuitive. 3. The specification tells us that the tag should be used for contact information. That has nothing to do with the word "address", which makes the document very vague. A "contact" tag would be much more appropriate. Another important point is that the phrase "contact information" is a little too vague. It can easily stretch to a point where any existing address can be considered a contact information. As a side note, I have seen the tag used as a location indicator on many accounts, and have seen search engines recognize it as such. If we take the H5 philosophy of describing what is as well as innovating, the address tag should be allowed to contain addresses, as it already does in reality. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 16 December 2010 12:50:27 UTC