process-faq-fr

microformats processus FAQ

Cette page est là pour documenter les Q&R concernant le processus des microformats. Si vous avez une nouvelle question à poser, considérez svp de la poser tout d'abord sur le canal irc microformats (de préférence) ou sur la liste de discussion microformats-discuss. Les nouvelles questions et réponses devraient être ajoutées en fin de liste. Si vous avez une nouvelle question mais pas de réponse, ajoutez-là svp à processus-problématiques.

Editer cette Page

SVP, n'utilisez pas de "?" ou tout autre signe de ponctuation dans les titres - cela aide à maintenir les URLs vers leurs identifiants fragments plus courts et plus faciles à lire, copier/coller. Voir comment jouer pour en savoir plus sur les lignes de conduite de modification du wiki.

Q&R

Pourquoi perdre du temps à barboter dans le HTML friable

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:

  "Document the schemas implied by the content examples."

  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.

  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).

En rapport

• processus
• processus-problématiques
• processus-brainstorming