On Feb 27, 2007, at 4:38 PM, Mike Kaply wrote:
This all points back to the original problem which I still haven't got
a good explanation for.
Microformats that require no custom changes to servers or web page:
XFN
hCard
hCalendar
hAtom
hReview
Address
hResume
xFolk
Microformats that require specific settings on your web server, and
access by the user to configure that web server if necessary and a
very specific syntax that you might not be able to accomplish with
your configuration:
rel-tag
Does anyone see the disconnect or just me?
All rel-* microformats (e.g. XFN, rel-license, vote-links, even rel-
nofollow) require something on the other end of the link. Most
require just a document relevant to the microformat. rel-tag
requires that document be (or appear to be) the index of a
directory. All web servers allow directory indexing by default, so
this does not require any special configuration. It just requires
access to create files on the server, which is no different from what
any other rel-* microformat requires.
I think this requirement is more onerous with rel-tag primarily
because there are a lot more documents involved in rel-tag than any
of the other rel-* microformats, not really because it's a
fundamentally different type of microformat. And this is apparently
a widespread concern, but it will be easy to dismiss as an edge case
until someone has documented a convincingly large number of real-
world examples where rel-tag currently fails. This is the primary
disconnect I see. I think this wiki page is a good place to start
documenting tag space formats to see if the standard format (last
path segment) identified in rel-tag falls short of the 80% mark:
http://microformats.org/wiki/tag-space-formats
Peace,
Scott
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
