, then it would be easier for
people to build/use tools to extract just that single hCard, leaving
any others on the page alone if desired.
Perhaps this is something that could also be recommended as a best
practice... if enough people start doing it, that is.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i
to extract just the hcards for people in a particular category.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
a elements smells wrong to me. Ideally, it would be nice
to have something self-contained (and self-closing) like the link
element.
But, as you say, it works so it gets my vote.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com
wasn't suggesting it would be appropriate.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
with this, as
Brian said:
There is also a pure DOM Javascript version by Jeremy Keith here: (you
can view source to see how it works) It used hCards/hCalendar and GEO
to mash-up google maps.
http://austin.adactio.com/
It runs through the DOM, looks for elements with a class of vcard,
and then looks
.
Find out just how easy it is for you to start publishing with
microformats and add to the semantic richness of the Web right now.
Fingers crossed that it gets accepted.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com
there,
but talking through it has helped me clarify what I think I need to do.
Before I finally shut up, I wanted to make sure that this link gets
mentioned at least once in this discussion:
http://gmpg.org/xfn/and/#idconsolidation
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http
been discussed before, right? If anybody has some
URLs pointing to previous discussions of this issue, that'd be much
appreciated.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats
on that. Thanks.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
Thanks,
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
as an outsider's
first impression.
As an newcomer, your comments are probably the most valuable and
relevant on this issue. Much appreciated.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats
step we can take now to help mitigate the
confusion that the abbr pattern can cause in screen readers but I'll
start another thread for that.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
of screen reader users, we
should update the wiki to strongly encourage this more verbose
version of datetimes and strongly discourage the contracted version?
Some test results can be found here:
http://dotjay.co.uk/tests/screen-readers/date-time/#test-microformats
Bye,
Jeremy
--
Jeremy Keith
to indicate
where the machine-readable data is being stored. I think that any
such flag would unnecessary complexity for humans. The patterns are
enough.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss
is something that should codified as
soon as possible. I'd be even more interested in hearing if there's
anybody, like Tantek, who feels that it's a bad idea... or to be more
accurate, who feels that the practical benefits don't outweigh the
semantic purity.
Bye,
Jeremy
--
Jeremy Keith
a d
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
/
Bye,
Jeremy
* well, I had to throw a Star Trek reference in there to balance out
the Star Wars.
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
, then that should probably be included
in the test cases:
http://microformats.org/wiki/assistive-technology-abbr-results
Like I said, we shouldn't get our hopes but it's certainly worth
investigating.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com
crossed that it's number 2. ;-)
Again, a big thank you, Lawrence (and Benjamin, James, Patrick and
anyone else taking the time to run these kind of tests).
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss
:
Semantic HTML comes first, microformats after. For POSH to catch
on, it needs to appeal to web development (or certainly web
standards) newcomers. Microformats is an advanced concept - not one
that most beginners are going to latch on to straight away.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
microformat because the required information can
already be marked up using a combination of hCard, hCalendar and XFN:
people+dates+relationships.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing
of combined bday and dtstart values in a class attribute *could*
be used to reinforce that assumption.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
(although
that is also kind of true of the abbr design pattern too).
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo
, offered the
choice of an alternative to abbr, will always go for the alternative.
And others will choose to always stick with abbr. I think that all of
those positions should be accommodated.
Look forward to getting your feedback,
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http
/wiki/hcard-faq#Should_I_use_ADDRESS_for_hCards
If I have time, I'll do some Wiki updating later today.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
for the cite element.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
is not a CITATION element.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
is incorrect though.
In the use case which originally kicked off this discussion,
mentioning someone in the course of a blog post is most definitely
referencing them (even if I'm not quoting from them).
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com
!
Agreed. It's as confusing as the ADDRESS element.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats
don't want to see
the same mistake repeated again. The fact that microformats allow
authors to choose the most semantically meaningful elements
(according to context) is one of the great strengths of microformats,
in my opinion.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http
Andy wrote:
Span is used as an example of a generic paired element.
Good. That's what I was hoping. Then can we say that instead of
saying SPAN? Please? :-)
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats
://adactio.com/;Jeremy
Keith/a
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
Andy Mabbett wrote:
Perhaps someone would like to attend, and talk about microformats?
This looks like a good event and I'm pretty sure I'll be around at
that time so I've submitted a proposal for a quick microformats talk.
http://www.ukuug.org/events/opentech2008/
Bye,
Jeremy
--
Jeremy
any issues.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
the
expanded form in the running text.
Personally, I think that using the title attribute of the abbr element
to provide the expanded human-readable form of what is contained in
the running text is precisely what the abbr element is intended for.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
on existing
publishing behaviour.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
the verb and the noun.
HTH,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.
So basically any criticisms I've got are with the UI, not the
implementation ...which looks great.
Nicely done.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss
property *only* containing the n/fn property of
an hCard, e.g.:
pHello, my name is span class=vcard authorspan
class=fnJeremy Keith/span/span./p
So, is the spec correct and it's just that I'm being slightly misled
by the examples?
Thanks in advance,
Jeremy
--
Jeremy Keith
a d a c t i o
and closing vcard containing elements.
Perhaps I should an example to the hAtom examples page to show this
usage of the author property.
Thanks for the responses,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss
just want to clarify that.
Bye,
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
.37signals.com/basecamp/556-any-chance-of-adding-hcards
Jeremy
--
Jeremy Keith
a d a c t i o
http://adactio.com/
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
43 matches
Mail list logo
