Difference between revisions of "question-answer-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
(hFeed)
Line 18: Line 18:
 
==hFeed==
 
==hFeed==
 
FAQs could be marked up as, or using a variant of, [[hfeed|hFeed]], with the question being the entry title and the answer the content. [[User:AndyMabbett|Andy Mabbett]]
 
FAQs could be marked up as, or using a variant of, [[hfeed|hFeed]], with the question being the entry title and the answer the content. [[User:AndyMabbett|Andy Mabbett]]
 +
 +
hfeed (hAtom) is a good candidate, however, one thing is lacking...the key concept of a q/a.  The value of a q/a format is for agregating questions and answers.  If hAtom can indicate that it's contents are q/a it would be perfect.
 +
[[User:TaylorCowan|Taylor Cowan]]
  
 
== See also ==
 
== See also ==

Revision as of 13:24, 1 June 2007

Questions and Answers

Purpose

The "question-answer" microformat proposes to formalize the relationships between questions and answers (including "FAQs") published within a single HTML document (and possibly a set of documents). Such formalization should allow for reuse of questions and answers in new contexts, e.g. search engines, IM bots, etc.

Multi-page FAQs

Based on [1] (extraneous detail omitted)

Current mark-up:

<a href="/england/noappointmentneeded/walkincentres/walkincentreservices.cmsx">What services does a Walk-in Centre offer?</a>

Possible solution (tentative class-names):

<a class="question answer-at" href="/england/noappointmentneeded/walkincentres/walkincentreservices.cmsx">What services does a Walk-in Centre offer?</a>

hFeed

FAQs could be marked up as, or using a variant of, hFeed, with the question being the entry title and the answer the content. Andy Mabbett

hfeed (hAtom) is a good candidate, however, one thing is lacking...the key concept of a q/a. The value of a q/a format is for agregating questions and answers. If hAtom can indicate that it's contents are q/a it would be perfect. Taylor Cowan

See also