Difference between revisions of "misconceptions"

From Microformats Wiki
Jump to navigation Jump to search
m (Add links)
(broke out additional profile text as a mix of misconception and moved one to criticism.)
Line 5: Line 5:
 
== misconceptions ==
 
== misconceptions ==
  
=== microformats use non-URI based extensibility ===
+
=== microformats use unscoped class names ===
 +
misconception:  ''Microformats definitions use unqualified/scoped class attribute strings as semantic tags.''
 +
 
 +
This is incorrect on two counts. 
 +
 
 +
First, microformats make use of profile URLs to define class name semantics.  Thus it is entirely possible (though both unlikely, and undesirable) for someone to redefine class names with their own definitions in their own profile URL.
 +
 
 +
Second, [[compound microformats]] (e.g. [[hCard]], [[hCalendar]], [[hReview]]) use a fairly uniquely chosen string for the "root element" (e.g. <code>vcard</code>, <code>vcalendar</code>, <code>vevent</code>, <code>hreview</code>) and then generic terms only inside that root element.  Thus use of any generic terms are scoped (some might even say "namespaced") within the fairly uniquely chosen "root element" class name.
 +
 
 +
=== microformats use non URI based extensibility ===
 
misconception: ''Microformats use non-URI based extensibility.''
 
misconception: ''Microformats use non-URI based extensibility.''
  
Line 14: Line 23:
 
What we have found is that, just like HTML was often used in the wild without explicit DOCTYPE URIs (and tools e.g. browsers supported it), microformats are often used in the wild without explicit profile URLs (and tools e.g. browser plugins support it).
 
What we have found is that, just like HTML was often used in the wild without explicit DOCTYPE URIs (and tools e.g. browsers supported it), microformats are often used in the wild without explicit profile URLs (and tools e.g. browser plugins support it).
  
However, missing a DOCTYPE does little or no damage, as (modulo tag soup issues) the DOCTYE is a link in the chain of reasoning about what the document means.  The HTML profile for microformats is however a crucial link.
+
Missing a DOCTYPE does little or no damage today, as (modulo tag soup issues) the DOCTYPE is a link in the chain of reasoning about what the document means.  It's been asserted that the HTML profile for microformats is however a crucial link, which perhaps similar to the assertion made by the SGML community back when HTML was introduced that the DOCTYPE for HTML is a crucial link. The parallels are nearly identical.
There are two dangers is it is omitted:
 
  
One danger is that, because tools such as browser plugins support microformats without checking for a profile, then those tools will erroneously pick up data from pages which use classes for a completely unrelated purpose. This attributes to the author information which they never meant to give.
+
However, despite how browsers make good sense of HTML sans DOCTYPEs today, witness how nearly no general <em>user-centric</em> user agents have been built to make sense of the babel of XML sans DOCTYPEs that is being published.  Given the failure of XML use in practice to make use of URI based extensibility, and the subsequent failure for there to be any widespread user-centric user agents (e.g. browsers) that make use of that content, the lesson to learn here is that it is therefore important to <em>use</em> the profile attribute for microformats, and encourage its use.
  
The other danger is that no generic data-gathering device can be builtThe web ceases to be self-describing, in that there then would be no one common algorithm for deriving the data from a given page.    Web client software has to be all updated for the latest microformats which they want to supportWhile this would scale for a small number of well-known global microformats, it does not scale when domain-specific, or culture-specific, or company-specific microformats are added.
+
The [http://gmpg.org/xmdp/description XMDP spec] and the [http://www.w3.org/2003/g/data-view GRDDL] spec show how to make a profile, and how generic data clients to follow, to either ground the data into RDF, or use the data directly as microformats with terms defined by their XMDP+ID URIsThis will maximize re-use of the data, in combination wit other data.  There is a growing class of [http://esw.w3.org/topic/GrddlImplementations grddl-aware systems] which will use GRDDL-enabled microformat data without any alteration.
  
It is therefore important to <em>use</em> the profile attribute.  
+
=== microformats tools will erroneously pick up data ===
 +
''One danger of omitting profiles is that, because tools such as browser plugins support microformats without checking for a profile, then those tools will erroneously pick up data from pages which use classes for a completely unrelated purpose. This attributes to the author information which they never meant to give. '''
  
The [http://www.w3.org/2003/g/data-view GRDDL] spec shows how to make a profile, and how generic data clients to follow, to ground the data into RDF.  This will maximize re-use of the data, in combination wit other data.  There is a growing class of [http://esw.w3.org/topic/GrddlImplementations grddl-aware systems] which will use GRDDL-enabled microformat data without any alteration.
+
This scenario is highly unlikely and has yet to occur in the real web due to the fairly uniquely chosen root class names for microformats which tools look for before they look for the more generically named classes inside microformats.
  
=== microformats use unscoped class names ===
+
=== no generic data gathering device can be built ===
misconception: ''Microformats definitions use unqualified/scoped class attribute strings as semantic tags.''
+
''The other danger of omitting profiles is that no generic data-gathering device can be built. The web ceases to be self-describing, in that there then would be no one common algorithm for deriving the data from a given page.'''
 +
 
 +
It is difficult to disprove a negative statement as the first sentence, and, this is strictly a theoretical problem, as no generic data-gathering device <em>has</em> been built.
 +
 
 +
Similarly, the web is not self-describing currently with widespread use of HTML, tag soup, invalid XML, etc. thus saying it ceases to be self-describing is misleading, because there is no "ceasing".  If anything, by increasing the semantics expressed on the existing web, the use of microformats increases how much each page self-describes its own semantics.
 +
 
 +
=== do not scale when domain specific microformats are added ===
 +
''microformats do not scale when domain-specific, or culture-specific, or company-specific microformats are added.''
  
This is incorrect on two counts.   
+
Microformats are not trying to solve all problems, in fact, that is a specific non-goalSee the microformats [[principles]].  In practice, one does not have to solve all problems, nor even make it possible to solve all problems.
  
First, as above, microformats make use of profile URLs to define class name semantics.  Thus it is entirely possible (though both unlikely, and undesirable) for someone to redefine class names with their own definitions in their own profile URL.
+
Microformats are trying to represent the 80/20 of semantics on the public web, and thus solve most problems that will actually help most people on the public web.
  
Second, [[compound microformats]] (e.g. [[hCard]], [[hCalendar]], [[hReview]]) use a fairly uniquely chosen string for the "root element" (e.g. <code>vcard</code>, <code>vcalendar</code>, <code>vevent</code>, <code>hreview</code>) and then generic terms only inside that root element.  Thus use of any generic terms are scoped (some might even say "namespaced") within the fairly uniquely chosen "root element" class name.
+
For domain-specific, or culture-specific, or company-specific semantics, those authors should simply make use of the best [[POSH]] that they can, with their own profiles and profile URLs, and if their domain-specific, or culture-specific, or company-specific semantics become widely adopted on the web, then that may provide a good case for taking their [[POSH]] through the microformats [[process]] to develop a new microformat.
  
 
== see also ==
 
== see also ==
 
* [[faq]]
 
* [[faq]]
 
* [[xmdp]]
 
* [[xmdp]]
 +
* [[criticism]]

Revision as of 22:48, 27 September 2007

misconceptions about microformats

Some misconceptions either appear often enough, or may have been held by people that are experts in the fields of markup, web standards etc., and thus it is useful to document and debunk them.

misconceptions

microformats use unscoped class names

misconception: Microformats definitions use unqualified/scoped class attribute strings as semantic tags.

This is incorrect on two counts.

First, microformats make use of profile URLs to define class name semantics. Thus it is entirely possible (though both unlikely, and undesirable) for someone to redefine class names with their own definitions in their own profile URL.

Second, compound-microformat (e.g. hCard 1.0, hCalendar 1.0, hReview 0.4 (in progress)) use a fairly uniquely chosen string for the "root element" (e.g. vcard, vcalendar, vevent, hreview) and then generic terms only inside that root element. Thus use of any generic terms are scoped (some might even say "namespaced") within the fairly uniquely chosen "root element" class name.

microformats use non URI based extensibility

misconception: Microformats use non-URI based extensibility.

Microformats make use of the profile attribute, in the <head> element to reference one or more profiles (this is all per HTML4 spec) to an XMDP profile document (XMDP is derived from the "hints" in HTML4 as to what a profile document "could" be), to define specific rel (e.g. XFN 1.1 profile and class (e.g. hCard profile) values.

Thus microformats are built upon a form of URI based extensibility. Tantek did this by design for XFN - The XHTML Friends Network, his first experiment into formally extending HTML, and before he even coined the word "microformat" (XMDP & XFN were developed in 2003, "microformats" were first proposed in 2004).

What we have found is that, just like HTML was often used in the wild without explicit DOCTYPE URIs (and tools e.g. browsers supported it), microformats are often used in the wild without explicit profile URLs (and tools e.g. browser plugins support it).

Missing a DOCTYPE does little or no damage today, as (modulo tag soup issues) the DOCTYPE is a link in the chain of reasoning about what the document means. It's been asserted that the HTML profile for microformats is however a crucial link, which perhaps similar to the assertion made by the SGML community back when HTML was introduced that the DOCTYPE for HTML is a crucial link. The parallels are nearly identical.

However, despite how browsers make good sense of HTML sans DOCTYPEs today, witness how nearly no general user-centric user agents have been built to make sense of the babel of XML sans DOCTYPEs that is being published. Given the failure of XML use in practice to make use of URI based extensibility, and the subsequent failure for there to be any widespread user-centric user agents (e.g. browsers) that make use of that content, the lesson to learn here is that it is therefore important to use the profile attribute for microformats, and encourage its use.

The XMDP spec and the GRDDL spec show how to make a profile, and how generic data clients to follow, to either ground the data into RDF, or use the data directly as microformats with terms defined by their XMDP+ID URIs. This will maximize re-use of the data, in combination wit other data. There is a growing class of grddl-aware systems which will use GRDDL-enabled microformat data without any alteration.

microformats tools will erroneously pick up data

One danger of omitting profiles is that, because tools such as browser plugins support microformats without checking for a profile, then those tools will erroneously pick up data from pages which use classes for a completely unrelated purpose. This attributes to the author information which they never meant to give. '

This scenario is highly unlikely and has yet to occur in the real web due to the fairly uniquely chosen root class names for microformats which tools look for before they look for the more generically named classes inside microformats.

no generic data gathering device can be built

The other danger of omitting profiles is that no generic data-gathering device can be built. The web ceases to be self-describing, in that there then would be no one common algorithm for deriving the data from a given page.'

It is difficult to disprove a negative statement as the first sentence, and, this is strictly a theoretical problem, as no generic data-gathering device has been built.

Similarly, the web is not self-describing currently with widespread use of HTML, tag soup, invalid XML, etc. thus saying it ceases to be self-describing is misleading, because there is no "ceasing". If anything, by increasing the semantics expressed on the existing web, the use of microformats increases how much each page self-describes its own semantics.

do not scale when domain specific microformats are added

microformats do not scale when domain-specific, or culture-specific, or company-specific microformats are added.

Microformats are not trying to solve all problems, in fact, that is a specific non-goal. See the microformats principles. In practice, one does not have to solve all problems, nor even make it possible to solve all problems.

Microformats are trying to represent the 80/20 of semantics on the public web, and thus solve most problems that will actually help most people on the public web.

For domain-specific, or culture-specific, or company-specific semantics, those authors should simply make use of the best posh that they can, with their own profiles and profile URLs, and if their domain-specific, or culture-specific, or company-specific semantics become widely adopted on the web, then that may provide a good case for taking their posh through the microformats The microformats process to develop a new microformat.

see also