process-faq: Difference between revisions
(started using a question from Michael Smethurst that has been implicitly asked before.) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
<h1>microformats process FAQ</h1> | <h1>microformats process FAQ</h1> | ||
This page is for documenting Q&A about the microformats [[process]]. If you have a new question to ask, please consider first asking your question on the [irc://irc.freenode.net/#microformats microformats irc channel] (preferably) or [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] mailing list. New questions and answers should be added to the end of the list. If you have a new question but not an answer, please add it to [[process-issues]]. | This page is for documenting Q&A about the microformats [[process]]. If you have a new question to ask, please consider first asking your question on the [irc://irc.freenode.net/#microformats microformats irc channel] (preferably) or [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] mailing list. New questions and answers should be added to the end of the list. If you have a new question but not an answer, please add it to [[process-issues]]. | ||
| Line 7: | Line 6: | ||
<h2> Q&A </h2> | <h2> Q&A </h2> | ||
__TOC__ | |||
=== Why waste time wading through flakey HTML === | === Why waste time wading through flakey HTML === | ||
''Would it not be better for microformats to standardize markup based on the domain model than waste time wading through flakey html?'' | ''Would it not be better for microformats to standardize markup based on the domain model than waste time wading through flakey html?'' | ||
Revision as of 00:31, 13 September 2007
microformats process FAQ
This page is for documenting Q&A about the microformats process. If you have a new question to ask, please consider first asking your question on the microformats irc channel (preferably) or microformats-discuss mailing list. New questions and answers should be added to the end of the list. If you have a new question but not an answer, please add it to process-issues.
Editing this Page
Please do not use "?" or other punctuation in the headers - it helps to keep the URLs to their fragment identifiers shorter and easier to read, copy/paste etc. See how-to-play for more wiki editing guidelines.
Q&A
Why waste time wading through flakey HTML
Would it not be better for microformats to standardize markup based on the domain model than waste time wading through flakey html?
- The "gather real world examples" for analysis step of the process is specifically focusing on the data published, and not the markup patterns (or lack thereof). This is why the *-examples step says:
Every word in that sentence matters. implicit schemas, that is, you have to look at the content of the examples and note what abstract notions/fields/properties that people are publishing. That's very deliberate in that it is much less important (if at all) what flakey html is being used."Document the implicit schemas that the content examples imply."
Analysis of current publishing practices helps us prioritize what problems are worth solving (i.e. there is already demonstrated incentive for people to publish such information) as opposed to what problems are purely theoretical, or wishful thinking (e.g. if only everyone would publish metadata ABC then we could build applications XYZ). In fact, this is probably one of the most important parts of the process. Domain models that don't account for what is published on the real web tend to be less useful on the real web as has been demonstrated by the numerous a priori XML formats that have been proposed but never got any adoption. The XML formats that have gained adoption are those that modeled the data of existing content publishing behaviors (e.g. the Atom format).