Re: OBJECT Pattern Page Updated

From: Ben Ward <listsben-ward.co.uk>
> This is a big edit, but the page was not in a good
state and this 
> needed doing. I ask that people take a little time to
read the new 
> version, compare it to the old and raise any remaining
issues.

The hyperlink example shows that

    <a href="#j"
class="include">Ben Ward</a>

is replaced by

    <span class="fn n" id="j">
      <span
class="given-name">James</span> <span
class="family-name">Levine</span>
    </span>


The text that follows states that the hyperlink "can
require repeating a small piece of information (such as a
person's name in an hCard)"
If the names in the examples were consistent, they would
help to reinforce the stated requirement.
The names (ben ward and james levine) should be consistant
with each other.

It may also be a good idea to use more meaningful id names
in both the hyperlink and obect examples, so that those who
implement this pattern are encouraged to use good id naming
schemes too. We don't want to encourage bad behaviour.

Further down there is "OBJECT elements referencing
fragments of the same document erroneously cause the browser
to make additional HTTP requests. For scenarios where HTTP
requests are a sensitive performance measure, this makes the
hyperlink pattern inappropriate."

If the object element cause additional HTTP requests,
shouldn't this make the object pattern inappropriate, and
not the hyperlink one?

-- 
Paul Wilkins



_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

On 11/6/07 12:22 PM, "paul_wilkinsxtra.co.nz" <paul_wilkinsxtra.co.nz>
wrote:

> From: Ben Ward <listsben-ward.co.uk>
>> This is a big edit, but the page was not in a good
state and this
>> needed doing. I ask that people take a little time
to read the new
>> version, compare it to the old and raise any
remaining issues.
> 
> The hyperlink example shows that
> 
>   <a href="#j"
class="include">Ben Ward</a>
> 
> is replaced by
> 
>   <span class="fn n" id="j">
>     <span
class="given-name">James</span> <span
> class="family-name">Levine</span>
>   </span>
> 
> 
> The text that follows states that the hyperlink
"can require repeating a small
> piece of information (such as a person's name in an
hCard)"
> If the names in the examples were consistent, they
would help to reinforce the
> stated requirement.
> The names (ben ward and james levine) should be
consistant with each other.

Indeed. In addition, the whole reason the include-pattern
was developed was
to NOT to have to repeat such text in the content of the
document.

Thus I've changed it to use the 'title' attribute instead,
which is
simultaneously a less invasive / content-affecting
requirement on the
author, and still available to assistive technologies (same
citation in the
section, Clark, 2007).

http://microformats.org/wiki/include-pattern#accessibi
lity


> It may also be a good idea to use more meaningful id
names in both the
> hyperlink and obect examples, so that those who
implement this pattern are
> encouraged to use good id naming schemes too. We don't
want to encourage bad
> behaviour.

That's reasonable.  Updated.


> Further down there is "OBJECT elements referencing
fragments of the same
> document erroneously cause the browser to make
additional HTTP requests. For
> scenarios where HTTP requests are a sensitive
performance measure, this makes
> the hyperlink pattern inappropriate."
> 
> If the object element cause additional HTTP requests,
shouldn't this make the
> object pattern inappropriate, and not the hyperlink
one?

Good catch.

Please have another read:

 http://m
icroformats.org/wiki/include-pattern

Thanks!

Tantek


_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss