Should there be a way for people to have this information but not make
it available as a vcard or vevent?
The user-action class or new protocols proposed in the Firefox 3
thread could address this problem (10 hCards in an hResume). Since
these pieces of microformatted content probably would not contain a
user-action (or link with a particular protocol), the browser would
not expose them to the user.
-Alex
On Aug 27, 2007, at 7:14 PM, Mike Kaply wrote:
I wanted Jason to bring this up on the list because it is an
interesting discussion.
We display lots of stop in Operator (especially in hResume) that can't
actually be used.
hCalendars for experience are interesting, but unuseful as hCalendars.
And hCards for
my employment at a past employer aren't terribly interesting either.
Should there be a way for people to have this information but not make
it available
as a vcard or vevent?
Mike
On 8/27/07, Jason Calabrese <[EMAIL PROTECTED]> wrote:
I've recently started to look into using some microformats on one
of my
projects and have been playing with Operator to get an idea of how
they are
being used elsewhere.
Operator is a great way to see what microformats are contained on
a page, but
I think it might confuse the average user when a page contains a
lot of
nested data using core microformats such as hCard, adr, hCalendar,
etc.
For example on a LinkedIn public profile:
http://www.linkedin.com/in/steveganz
You see 1 hResume, 1 adr, 10 hCard's, and 7 hCalendar's.
In this case all the hCalendar events are from the experience part
of the
resume. I don't see any use for adding these to Google Calendar
or exporting
them. Also 9 of the hCard's wouldn't make sense to export or add
to Yahoo
Contacts since they contain only very basic information.
An other example is a Google Maps search. In this case each
result produces a
hCard and contains an adr. Ideally these would be combined and
shown as
Contacts with addresses. Then each contact could be exported or
viewed in
Google or Yahoo maps.
Have these types of issues been discussed before? Is there a way
that a user
script can hide nested data?
I understand the value of reusing the core microformats and
creating composite
microformats. I think that in many cases users will want to
interact with
the primary composite format while still preforming actions based
on the
nested content.
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
