Benjamin Hawkes-Lewis wrote:
An author element might kill several of these birds with one stone.
I'd rather see an attribution element than an author element.
It is more generally useful.
~fantasai
fantasai wrote:
I'd rather see an attribution element than an author element.
It is more generally useful.
Can you explain what the difference would be? Would an attribution
element include copyright holders as opposed to creators? If so, I think
bundling them together makes gathering citation
Simon Pieters wrote:
* Providing contact details of any type for any person or organisation.
Would generalizing address to that extent would prevent automated agents
being able to distinguish an address for a article (e.g. a blog
comment) from an address mentioned in a article? This would make
On Tue, 27 Feb 2007 09:03:49 +0100, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
Simon Pieters wrote:
* Providing contact details of any type for any person or organisation.
Would generalizing address to that extent would prevent automated agents
being able to distinguish an address for
Simon Pieters wrote:
Do UAs need to know the scope of the address? What could they do
with this information? (If it is important, then we could use a class name
or a new attribute for this IMHO.)
Using address in this way has been difficult since it's hard for
agents to infer document
In message [EMAIL PROTECTED], Simon Pieters
[EMAIL PROTECTED] writes
should address be more general-purpose?
what benefit would that have, over the adr microformat?
http://microformats.org/wiki/adr
The latter has better granularity, allowing for street-address,
locality, region,
Hi; This is my first post to the list.
Andy - one of my first thoughts when reading through the HTML5 spec was
that one of the benefits of dramatically improving available markup
would be getting rid of the need for microformats-type approaches.
With all possible respect to microformats, I
On Tue, 27 Feb 2007 19:35:50 +0100, Benjamin Hawkes-Lewis
[EMAIL PROTECTED] wrote:
[...]
Isn't it better to make address more general so that its semantics
is more like how most authors use it so that it becomes a convenient
styling hook for authors?
[snip]
I don't think it's a good
On Tue, 27 Feb 2007 20:40:46 +0100, Andy Mabbett
[EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Simon Pieters
[EMAIL PROTECTED] writes
should address be more general-purpose?
what benefit would that have, over the adr microformat?
http://microformats.org/wiki/adr
Ease
Simon Pieters wrote:
Ease of use, mostly. It's simpler to say:
address665 3rd St.br
Suite 207br
San Francisco, CA 94107br
U.S.A./address
...than:
div class=adr
div class=street-address665 3rd St./div
div class=extended-addressSuite 207/div
span
Benjamin Hawkes-Lewis and Simon Pieters are having a discussion that I
understand (at last... at least, sort of, or at least ... I think I do) .
The discussion concerns the meaning of the word address and the tag
address. How much of the meaning of the word should reflect (for good or
for ill)
On Wed, 28 Feb 2007 04:42:58 +0100, ddailey [EMAIL PROTECTED]
wrote:
Benjamin Hawkes-Lewis and Simon Pieters are having a discussion that I
understand (at last... at least, sort of, or at least ... I think I do)
. The discussion concerns the meaning of the word address and the tag
Posting this to the list so that it won't be forgotten.
From http://forums.whatwg.org/viewtopic.php?t=5
| In HTML4, the address element was defined as this:
|
| | The ADDRESS element may be used by authors to supply contact
| | information for a document or a major part of a document such as a
13 matches
Mail list logo
