W3C home > Mailing lists > Public > www-html@w3.org > September 2004

Re: The status on <address>

From: Trejkaz Xaoza <trejkaz@xaoza.net>
Date: Fri, 17 Sep 2004 00:58:04 +1000
To: www-html@w3.org
Message-Id: <200409170058.04506.trejkaz@xaoza.net>
At Wed, Sep 15, 2004 at 08:43:50PM +0200, Bjoern Hoehrmann wrote:
> http://hades.mn.aptest.com/cgi-bin/xhtml2-issues/Structural?id=7460
> which has been rejected with the note "Superseded by PR#7474" and
> http://hades.mn.aptest.com/cgi-bin/xhtml2-issues/Structural?id=7474
> which has been rejected with the note
>   BAE F2F:we have the structuring facility in XHTML, rather it is more
>   efficient to use the meta data (example use property="") Original idea
>   is described in PR#7460. For more discussion, see
>   http://lists.w3.org/Archives/Public/www-html/2003Dec/thread#3

So what is the intent here, exactly?

Is the idea that we're supposed to use a paragraph for a block address?

    <p property="myns:address">

I gather inline would be a span...

    <p>Contact me at <span property="myns:address">...</span>.</p>

The question then, is... if I wanted to write CSS to match all block
addresses, how do I know which properties represent addresses?  Do I
maintain a large list of all the properties which are addresses?  What
happens if another property is discovered which is an address too?  Do
I just update the CSS every time a new one is found?


             Email: Trejkaz Xaoza <trejkaz@xaoza.net>
          Web site: http://xaoza.net/trejkaz/
         Jabber ID: trejkaz@jabber.xaoza.net
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73

Received on Thursday, 16 September 2004 14:56:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:09 UTC