/being_brave_wit.html
S. Sriram
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
From: Ryan King [EMAIL PROTECTED]
On Dec 5, 2006, at 8:48 AM, S. Sriram wrote:
From: Mike Schinkel [EMAIL PROTECTED]
http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2006-
December/00
8462.html
I wonder if his issues can be addressed?
How about a distributed parser-discovery
From: Mike Schinkel [EMAIL PROTECTED]
S. Sriram wrote:
This is not a scarce resource, people can
(and are) naming classes as they choose.
Any constraint happens at the parsing stage,
since microformat-aware parsers look for
specific class names etc. (see below)
If it is not a scarce resource
vendors, where custom format developers would
have the burden/opportunity of rolling their own renderers.
[1] http://www.w3.org/TR/xhtml-rdfa-primer/
S. Sriram
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http
)
might
help understand this relationship better.
S. Sriram
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
: The parser needs to be 'hosted', incurring bandwidth costs.
PROS: Roll your own microformat and parser - or - *leave your html
as is and just build a parser for it and point tothe parser from within the
page.*
S. Sriram
___
microformats-discuss mailing list
://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2006-December/008500.html
S. Sriram
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
up in a babel of xml namespaces that their clients
output.
If anything, a map between microformats and googles namespace
declarations at http://base.google.com/base/base.xsd could be
considered.
Thanks
S. Sriram
___
microformats-discuss mailing list
