hatom-hints-fr

2008-12-19T20:40:57Z

DarroLrolc: aczelrolric

racreldoma
= Trucs hAtom =

[[hatom-fr|hAtom]] est un microformat pour le contenu qui peut Ãªtre syndiquÃ©, originellement mais pas exclusivement pour les billets de blogs. Cette page donne des astuces sur la faÃ§on d'utiliser, d'implÃ©menter et embarquer hAtom, de l'historique et d'autres informations Ã©troitement en rapport avec la spÃ©cification hAtom mais n'appartient pas strictement Ã la page principale.

S'il existe un conflit entre cette page et la spÃ©cification, la spÃ©cification est correcte.

{{out-of-date-fr}}

__TOC__

== Notes de SchÃ©ma ==
==== Nomenclature ====

'''Note :''' Regardez svp le document [[hatom-issues-fr|hatom-problÃ©matiques]] pour une discussion sur les noms de propriÃ©tÃ©.

{| width="100%" border="1" cellspacing="0"
|-
! width="150" | Concept
! Atom Identifier
! hAtom Microformat Usage
|-
| Feed
| <code>atom:feed</code>
| Add class name <code>"hfeed"</code>
|-
| Entry
| <code>atom:entry</code>
| Add class name <code>hentry</code>; if practical, also define <code>id="unique-identifier"</code> to the Entry.
|-
| Entry Title
| <code>atom:title</code>
| Add class name <code>headline</code>. Using <code><h#></code> also is encouraged.
|-
| Entry Content
| <code>atom:content</code>
| Add class name <code>content</code> to all appropriate blocks. Multiple Entry Content blocks are logically considered one concatenated <code>atom:content</code> equivalent.
|-
| Entry Summary
| <code>atom:summary</code>
| Add class name <code>excerpt</code> to all appropriate blocks. Multiple Entry Summary blocks are logically considered one concatenated <code>atom:summary</code> equivalent.
|-
| Entry Permalink
| <code>atom:link</code>
| Add a rel value of <code>bookmark</code>.
|-
| Entry Published
| <code>atom:published</code>
| Use class name <code>published</code>, optionally with the [[datetime-design-pattern-fr]].
|-
| Entry Updated
| <code>atom:updated</code>
| Use class name<code>updated</code>, with an ISO8601 absolute datetime, optionally with the [[datetime-design-pattern-fr]].
|-
| Entry Author
| <code>atom:author</code>
| Add class name <code>"author</code>. Using an <code>address</code> element is recommended. A [[hcard-fr|hCard]] SHOULD be added.
|}

==== RÃ¨gles d'Imbrication ====

{| width="100%" border="1" cellspacing="0"
|-
! Concept
! Nests In
! hAtom Opaque
! Cardinality
! Logical Cardinality Informative
|-
| Feed
| HTML document
| No
| 1-N
| 1-N
|-
| Entry
| Feed
| No
| 0-N
| 0-N
|-
| Entry Title
| Entry Entry Permalink
| No
| 0-N
| 0-1
|-
| Entry Content
| Entry
| Yes
| 0-N
| 0-1
|-
| Entry Summary
| Entry
| Yes
| 0-N
| 0-1
|-
| Entry Permalink
| Entry Entry Title Entry Published
| No
| 0-N
| 1
|-
| Entry Published
| Entry Entry Permalink
| No
| 0-N
| 0-1
|-
| Entry Updated
| Entry Entry Permalink
| No
| 0-N
| 1
|-
| Entry Author
| Entry
| Yes
| 0-N
| 1-N
|}

===== hAtom Opaque =====

"hAtom Opaque" specifies whether a hAtom parser should not "look inside" the element for further hAtom content. If there are multiple rules applied to the same element take the OR of the two (i.e. "Yes/Opaque" always wins)

: ''hAtom Opaque is designed to make parsing rules less ambiguous. In particular, it allows "quoted" hAtom elements (from another blog being blockquoted, for example) ti be ignored. It also allows 'embedded' hAtom to be potentially delivered within hAtom itself, and to prevent accidental 'leaking' of other microformat information up into the hAtom container. A general concept of opaqueness (need link) has also been proposed but it will complement, not replace this.''

===== CardinalitÃ© =====

How many times can an element of the given type appear in it's nesting/parent element.

===== CardinalitÃ© Logique =====

''This column is informative -- Atom has a number of rules for deciding what is required depending on the context and other elements, many which aren't strictly applicable to here.''

From a modeling/logical perspective, the number of times can an element appear.

: ''This is all rule dependent, see below. For example, an Entry Permalink may appear 6 times, but each one must be the same value; an Entry Content element may appear 3 times, but they are all concatenated together to make a single logical element.''

=== Element notes ===
===== Feed =====

* you could have multiple feeds on news pages, or weblogs with "mini-blogs" on the sidebar.
* class="hfeed hentry" is OK for feeds with a single entry.

===== EntrÃ©e Permalink =====
* Entry Permalinks SHOULD be the same as the <code>atom:link</code> (or <code>rss:link</code>) used in syndication feeds
: ''The intention of the previous two rules to gently force people to use strings that can be byte compared for equivalence. In general, the canonical URI should be the link used in an Atom entry.''
* if an Entry has multiple elements marked as the Entry Permalink, they MUST have exactly the same URI

==Voir aussi ==
* [[hatom-fr|hAtom]] - la proposition brouillon
* [[hatom-hints-fr|hAtom trucs]] - aide pour l'implÃ©mentation
* [[hatom-issues-fr|hatom-problÃ©matiques]] - problÃ¨mes ? rÃ©clamations ? idÃ©es ? Mettez-les ici
* [[hatom-faq-fr|hAtom-faq]] - base de connaissance
* [[blog-post-brainstorming-fr|blog-post-brainstorming]]
* [[blog-post-formats-fr|blog-post-formats]]
* [[blog-post-examples-fr|blog-post-examples]]
* [[blog-description-format-fr|blog-description-format]] - comment dÃ©crire un blog (Ã l'opposÃ© des entrÃ©es individuelles, ce qui est ce que nous faisons ici)

Microformats Wiki - User contributions [en]

hatom-hints-fr