as machine data?

Just a thought:

Haven't thought too much about this, but are there any
obvious  
gotchas to using an anchor element with name attribute as a
potential  
replacement for the abbr-design-pattern? The only things I
can  
foresee are the plus sign (+) in pre-UTC time zones and the
semicolon  
(;) in GEO. Those could both be escaped though, perhaps as 

underscores. It wouldn't leave as much room for growth as a
full  
CDATA attribute, but may be able to

<a class="dtstart"
name="iso8601:20070713">July 13th</a>
<a class="geo"
name="geo:30.300474_-97.747247">Austin</a>
;

http
://www.w3.org/TR/html4/types.html#type-cdata
...NAME tokens must begin with a letter ([A-Za-z]) and may
be  
followed by any number of letters, digits ([0-9]), hyphens
("-"),  
underscores ("_"), colons (":"), and
periods (".").

Anyway, kick it back here if there is something obvious I'm
missing.  
I'm certainly not proposing it as the best solution yet, but
I have  
added it to the wiki and don't want to waste time with an AT
test  
case if I don't have to.

http://microformats.org/wiki/assistive-technology-abbr- 
results#Markup_Possibilities

Cheers,
James

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

On May 10, 2007, at 3:23 PM, James Craig wrote:

> Just a thought:
>
> Haven't thought too much about this, but are there any
obvious  
> gotchas to using an anchor element with name attribute
as a  
> potential replacement for the abbr-design-pattern?

I believe a[name] and id need to be unique across an entire
page.  
This would make it impossible to have two events with the
the same  
dtstart, dtend or dtstamp on the same page. I think that
makes it  
unworkable.

-ryan


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

Ryan King wrote:

> James Craig wrote:
>
>> Haven't thought too much about this, but are there
any obvious  
>> gotchas to using an anchor element with name
attribute as a  
>> potential replacement for the abbr-design-pattern?
>
> I believe a[name] and id need to be unique across
an entire page.  
> This would make it impossible to have two events with
the the same  
> dtstart, dtend or dtstamp on the same page. I think
that makes it  
> unworkable.

Only ID has that restriction. Radio buttons, for example,
require  
elements have unique IDs but the same NAME.

James

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

On May 10, 2007, at 4:45 PM, James Craig wrote:

> Ryan King wrote:
>
>> James Craig wrote:
>>
>>> Haven't thought too much about this, but are
there any obvious  
>>> gotchas to using an anchor element with name
attribute as a  
>>> potential replacement for the
abbr-design-pattern?
>>
>> I believe a[name] and id need to be unique across
an entire page.  
>> This would make it impossible to have two events
with the the same  
>> dtstart, dtend or dtstamp on the same page. I think
that makes it  
>> unworkable.
>
> Only ID has that restriction. Radio buttons, for
example, require  
> elements have unique IDs but the same NAME.

a[name has restrictions that input[name] does not have.

Per [1], id's and a[name] are collectively known as
"anchor names"  
and must be unique, as they share the same name space. A
relevant  
snippet:

> The id and name attributes share the same name space.
This means  
> that they cannot both define an anchor with the same
name in the  
> same document. It is permissible to use both attributes
to specify  
> an element's unique identifier for the following
elements: A,  
> APPLET, FORM, FRAME, IFRAME, IMG, and MAP. When both
attributes are  
> used on a single element, their values must be
identical.

-ryan

1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

Ryan King wrote:

> a[name has restrictions that input[name] does not
have.
>
...snip...
>
> 1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1

Note and removed. Thanks!
http://microformats.org/wiki/assistive-technology-abbr- 
results#Markup_Possibilities

James

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

On 11/05/07, James Craig <jcraigapple.com> wrote:
> Ryan King wrote:
>
> > a[name has restrictions that input[name] does not
have.
> >
> ...snip...
> >
> > 1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1
>
> Note and removed. Thanks!


Well you could always add a _0, _1, _2, ...etc suffix,
couldn't you?

-- 
--
Victor Jalencas <victorcarotena.net>
_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss

On May 11, 2007, at 4:03 AM, victor jalencas wrote:

> On 11/05/07, James Craig <jcraigapple.com> wrote:
>> Ryan King wrote:
>>
>> > a[name has restrictions that input[name] does
not have.
>> >
>> ...snip...
>> >
>> > 1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1
>>
>> Note and removed. Thanks!
>
> Well you could always add a _0, _1, _2, ...etc suffix,
couldn't you?

Putting non-unique data into an attribute that requires
unique data  
is a misuse of HTML.  Adding meaningless suffixes on the end
to make  
the non-unique data appear unique doesn't remove the
mistake; it only  
hides it from validators that don't know any better.

Peace,
Scott

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

Better than a[name] would be a[href], assuming a relevent
URI scheme exists:

<a href="geo:51.36,-0.05">bond, <abbr
title="United
Kingom">UK</abbr></a>

(See: http://geouri.org/)

Disadvantages would be:

1. Involves using a poorly supported URI scheme. People
using browsers
that don't support the scheme would get a link that doesn't
do anything,
or brings up a cryptic message. (This could be worked around
with a
combination of CSS and Javascript, but that seems a bit
hackish to me.)

2. This requires there to always *be* such a URI scheme.
There isn't a URI
scheme for timestamps for instance. URI schemes cannot be
quickly and
easily registered.

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