Microformats Wiki - User contributions [en]

hatom-ja

2010-06-22T02:14:35Z

Imagedrive: /* Introduction */ テンプレートのリンク先を変更

<entry-title>hAtom-ja</entry-title>

<h1>hAtom 0.1</h1>
{{Template:DraftSpecification-ja}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

<div class="vcard">
;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])
</div>

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[[User:Tantek|Tantek Çelik]] (http://tantek.com/ and before at [http://technorati.com Technorati, Inc.])

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

== Introduction ==
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro-ja}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles-ja}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== Copyright ==
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional languages:
* [[hatom-fr|français]]

hatom-ja

2010-06-22T02:11:35Z

Imagedrive: /* Patents */ テンプレートのリンク先を変更

<entry-title>hAtom-ja</entry-title>

<h1>hAtom 0.1</h1>
{{Template:DraftSpecification-ja}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

<div class="vcard">
;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])
</div>

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[[User:Tantek|Tantek Çelik]] (http://tantek.com/ and before at [http://technorati.com Technorati, Inc.])

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

== Introduction ==
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles-ja}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== Copyright ==
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional languages:
* [[hatom-fr|français]]

hatom-ja

2010-06-22T02:10:27Z

Imagedrive: /* Semantic XHTML Design Principles */ テンプレートのリンク先を変更

<entry-title>hAtom-ja</entry-title>

<h1>hAtom 0.1</h1>
{{Template:DraftSpecification-ja}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

<div class="vcard">
;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])
</div>

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[[User:Tantek|Tantek Çelik]] (http://tantek.com/ and before at [http://technorati.com Technorati, Inc.])

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

== Introduction ==
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles-ja}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== Copyright ==
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional languages:
* [[hatom-fr|français]]

Main Page-ja

2010-06-22T02:09:31Z

Imagedrive: /* ドラフト */ hAtomのリンク先を変更

<entry-title> Microformats Wikiにようこそ！</entry-title>

__TOC__
初めての方は、[[introduction-ja|Microformats の手引き]]からどうぞ。編集を始める前に、[[how-to-play-ja]]を読んでください。

== はじめに ==
この wiki は microformats コミュニティの中心的なリソースです。発表済みの microformats 仕様、仕様ドラフト、発表パターンの現在のバージョンを見つけることができます。新しいフォーマットのプレインストーミングページや、認められたフォーマットや開発中のフォーマットの問題追跡ページといった開発用のリソースもあります。

== スタートするには ==
Microformats を始めるには…

* まず、自分のページやアプリケーションで、意味的に豊かで説明的で、'[[posh-ja|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]' な <abbr title="HyperText Mark-up Language">HTML</abbr> を書くことに慣れましょう。
* 「[http://microformats.org/about/ microformats について]」のページ、[http://microformats.org/ ブログ]、[[press|メディア紹介例]]や[[presentations-ja|プレゼンテーション]]、microformats に関する[[books|書籍]]、[[podcasts|ポッドキャスト]]、[[screencasts|スクリーンキャスト]]ページなどで microformats について学びましょう。
* [[hcard-ja|hCard]] や [[hcalendar|hCalendar]] などの確立した仕様を軽く読み、[[hcard-examples|examples]] に倣って microformats を公開しましょう。
* 質問がある場合は、[[faq|よく聞かれる質問]]や、用語と定義については[[glossary|用語集]]をご覧ください。 {{MicroformatsMailingList}}に投稿することもできます。
* 誰かから直接話を聞きたければ、[[events|microformats のイベント]]に参加してみてください。

== 定義 ==
Microformats とは、[[hcard-ja|人]]や[[hcalendar-ja|イベント]]、[[hatom|ブログ記事]]、[[hreview-ja|レビュー]]、[[rel-tag-ja|タグ]]のような、一般的に公開されているものをWebページ上で記述する際に使う小規模なマークアップの法則です。

Microformats を使えば、さらに詳しい情報をWebで発信することができるようになります。サイト上の情報のフィードやAPIを最も素早く簡単に提供するための手段といえます。

* [[what-are-microformats|Microformats とは何か]]、[[what-can-you-do-with-microformats|これを使って何ができるか]]についてもさらに詳しい説明があります。

== 協力するには ==
Microformats をさらに良くするには、みなさんの協力が必要です。

* Webサイトやサービス、製品で[[get-started|Microformats を利用]]する。
* マイクロフォーマットをもっと使ってもらえるよう、[[advocacy|周りにすすめる]]。
* [[testimonial|Microformats の推薦文]]を書く。
* [[to-do|TO DOリスト]]にあるタスクをこなす。
* [[irc-ja|IRCチャンネル]]や[[mail|メーリングリスト]]で学んだり、質問に答える (メールを送る前に、[[mailing-lists#General_guidelines|一般的なガイドライン]]を読んでください)。
* さまざまな言葉で読めるように、Microformats wikiの翻訳を手伝う ([[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AE Microformats _wiki|他言語での Microformats wiki]])。
* 新しい Microformats を提案する前に、あなたのWebサイトが[[POSH]]であり、[[get-started|すでにある Microformats を利用]]済みである事を確認する。そのあと、[[process|新しいフォーマットを提案する際のプロセス]]について良く読む。

この wiki には microformats の開発と貢献を支援するために多数の改善が含まれています。編集を始める前に [[wiki-2|wiki 紹介ページの説明]]をご覧ください。

== 仕様 ==
以下は最新の安定版 [[microformats-ja|microformats]] の公開標準仕様一覧です。

* [[hcalendar-ja|hCalendar]] (翻訳中!) - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license-ja|rel-license]]
* [[rel-nofollow-ja|rel-nofollow]]
* [[rel-tag-ja|rel-tag]]
* [[vote-links-ja|Vote Links]]
* [[XFN-ja|XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP|XMDP]]
* [[xoxo-ja|XOXO]]

もし自分で microformats を作ってみたい場合は [[process]] ページをまずお読みください。

== ドラフト ==

ドラフトとは、まだ完成していない比較的新しい microformats です。開発過程を経ていくぶん成熟してはいますが、文書の安定性は保証されておらず、実装する側は将来開発と変更に対応する準備をしておくべきです。アップデートに備えて wiki ページに注意しておいてください。

* [[adr|adr]] - 住所のマークアップ
* [[geo|geo]] - [http://en.wikipedia.org/wiki/WGS84 世界測地系]による、緯度と経度のマークアップ
* [[hatom-ja|hAtom]] (翻訳中!) - 更新情報を配信する (例: ブログの投稿)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - オープンな分散的クラシファイド広告
* [[hmedia|hMedia]] - 画像、動画、音声に関する統一メディア公開フォーマット
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe-ja|hRecipe]] (翻訳中!) - お菓子や料理のレシピ
* [[hresume-ja|hResume]] (翻訳中!) - 履歴書の公開
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]]- リンク先が、現在のページへのリンクを含んだディレクトリ一覧であることを表す
* [[rel-enclosure]] - ダウンロードやキャッシュ用の添付（ファイルなど）であることを表す
* [[rel-home]] - サイトのホームページへのリンクであることを表す
* [[relpayment|rel-payment]] - 支払いメカニズムであることを表す
* [[robots-exclusion|robots-exclusion]]
* [[xfolk-ja|xFolk]]

== デザインパターン ==
{{design_patterns-ja}} 

== 予備的な論議 ==
実際の[[examples|利用例]]の調査と分析、既存のフォーマット、Microformats の [[process]] を通じて新しい Microformats となる可能性のあるものについてのブレインストーミングついて、詳しくは[[exploratory-discussions|予備的な論議]]をご覧ください。

== 例 ==
* [[examples-in-the-wild-ja|実際の利用例]]
* [[implementations|ツールの実装]]
* [[zen-garden|Zen Garden]]

== リソース ==
[[resources|リソースページ]]をご覧ください。

== ユーザ中心開発 ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== 共有作業領域 ==
* [[to-do|TODOリスト]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|特別ページ]]
* [[year-in-review]]

== ツール、テストケース、リサーチ ==
例やコード、テストケースなどはそれぞれ個々の Microformats のページに記載しています。
ただほんの少しだけ、複数の Microformats の処理を必要とする分野横断的な[[tools|ツールとサービス]]があります。
[[tools|ツールとサービス]]は、複数の Microformats 全体に関連したエディタ、[[parsers|パーサ]]、[[validators|バリデータ]]、テストケース、およびその他の情報を対象としたページです。

== 他言語の Microformats Wiki ==
色んな言語で Microformats の記事を読んだり編集したりできます。

* 100個以上の記事がある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Français (フランス語)]] {{UpdateMarker-fr}}
* 10個以上の記事がある言語
** [[Main_Page-pt-br|Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
** [[Main_Page-ru|Русский (ロシア語)]]
* 2個以上の記事がある言語
** [[Main_Page-cs|Česky (チェコ語)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-es|Español (スペイン語)]]
** [[Main_Page-gl|Galego (ガリーシア語)]] {{NewMarker}}
** [[Main_Page-pl|Polski (ポーランド語)]]
** [[Main_Page-ro|Română (ルーマニア語)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (中国語)]]
** [[Main_Page-id|Indonesia (バハサ・インドネシア)]] {{NewMarker}}
* 翻訳が始まったばかりの言語
** [[Main_Page-fa|پارسی (ペルシア語)]] {{NewMarker}}
** [[Main_Page-ar|العربية (アラビア語)]]
** [[Main_Page-th|ภาษาไทย (タイ語)]]
** [[Main_Page-it|Italiano (イタリア語)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (韓国語)]] {{NewMarker}}
* その他
**[http://ja.wikipedia.org/wiki/ Microformats Wikipediaの Microformats ページ]は、多くの言語版ができています。

[[other-languages]]や[[how-to-start-new-translation|how-to-start-a-new-translation]]もご覧ください。

hatom-ja

2010-06-22T02:07:08Z

Imagedrive: /* 翻訳開始 */ hatomから前文コピー

<entry-title>hAtom-ja</entry-title>

<h1>hAtom 0.1</h1>
{{Template:DraftSpecification-ja}}

hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is based on a subset of the [http://www.atomenabled.org/ Atom] syndication format. hAtom will be one of several [[microformats]] open standards.
__TOC__
== Draft Specification ==

<div class="vcard">
;Editor/Author
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])
</div>

;Contributors
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[[User:Tantek|Tantek Çelik]] (http://tantek.com/ and before at [http://technorati.com Technorati, Inc.])

[[hatom#Copyright|copyright]] and [[hatom#Patents|patents]] statements apply.

== Status ==
hAtom 0.1 is a microformats.org draft specification. Public discussion on hAtom takes place on [[hatom-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hatom-issues-resolved|resolved]] and [[hatom-issues-closed|closed]] issues. Please check there before reporting [[hatom-issues|issues]].

The hAtom 0.2 update is currently under development and incorporates known errata corrections as well as the [[value-class-pattern]].

== Introduction ==
hAtom is a [[microformat]] for identifying semantic information in weblog posts and practically any other place [http://www.atomenabled.org/ Atom] may be used, such as news articles. hAtom content is easily added to most blogs by simple modifications to the blog's template definitions.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

== Format ==
=== In General ===
The [http://atomenabled.org/developers/syndication/#person Atom Syndication Format] provides the conceptual basis for this microformat, with the following caveats:

* Atom provides a lot more functionality than we need for a "blog post" microformat, so we've taken the minimal number of elements needed.
* the "logical" model of hAtom is that of Atom. If there is a conflict, Atom should be taken as correct.
* the "physical" model of hAtom -- the actual writing of elements -- is a lot more varied than Atom provides for, due to the variety of ways weblogs are actually produced in the wild. The hAtom microformat provides a number of rules for "bridging the gap"

=== Schema ===
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container elements -- the Feed or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read [[blog-post-brainstorming#Discovered_Elements]].

The hAtom schema consists of the following:

* hfeed ('''<code>hfeed</code>'''). optional.
** '''<code>feed category</code>'''. optional. keywords or phrases, using '''[[rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. required. text.
*** '''<code>entry-content</code>'''. optional (see field description). text. [*]
*** '''<code>entry-summary</code>'''. optional. text.
*** '''<code>updated</code>'''. required using [[datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optional using [[datetime-design-pattern]].
*** '''<code>author</code>'''. required using '''[[hcard|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optional, using '''[[rel-bookmark]]'''.
*** tags. optional. keywords or phrases, using '''[[rel-tag]]'''.

[*] Some required elements have defaults if missing, see below.

=== Field and Element Details ===

===== Feed =====
* a Feed element is identified by the class name <code>hfeed</code>
* a Feed element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 Atom feed]
* the Feed element is optional and, if missing, is assumed to be the page
* hAtom documents {{may}} have multiple Feed elements

===== Feed Category =====
* a Feed Category element is identified by [[rel-tag]]
* a Feed {{may}} have a Feed Category
* a Feed Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside a [http://www.atomenabled.org/developers/syndication/#optionalFeedElements feed]
* Feed Category elements {{must}} appear inside a Feed element but not inside an Entry element
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry =====
* an Entry element is identified by class name <code>hentry</code>
* an Entry element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 Atom entry]
* any microformat content inside a <code><blockquote></code> or <code><q></code> element within the Entry should not be considered part of the Entry.
: ''This allows quoting other microformated data without worry of corrupting the model''

===== Entry Category =====
* an Entry Category element is identified by [[rel-tag]]
* an Entry {{may}} have an Entry Category
* an Entry Category element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 Atom category] inside an [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entry]
* the [[rel-tag]] <code>href</code> encodes the atom <code>category:term</code>; the link text defines the atom <code>category:label</code>

===== Entry Title =====
* an Entry Title element is identified by the class name <code>entry-title</code>
* an Entry {{should}} have an Entry Title
* an Entry Title element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 Atom entry title]
* if the Entry Title is missing, use
** the first <code><h#></code> element in the Entry, or
** the <code><title></code> of the page, if there is no enclosing Feed element, or
** assume it is the empty string

===== Entry Content =====
* an Entry Content element is identified by class name <code>entry-content</code>
* an Entry {{should}} have Entry Content
* an Entry Content element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent Atom content]
* an Entry {{may}} have 0 or more Entry Content elements. The "logical Entry Content" of an Entry is the concatenation, in order of appearance, of all the Entry Contents within the Entry
: ''Many web logs split content into multiple sections with a "Read More" link and JavaScript tricks. This is also needed in cases where Entry Titles are coded in-line and are considered part of the content.''
* if the Entry Content is missing, assume it is the empty string

===== Entry Summary =====
* an Entry Summary element is identified by class name <code>entry-summary</code>
* an Entry Summary element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 Atom summary]
* an Entry {{may}} have 0 or more Entry Summary elements. The "logical Entry Summary" of an Entry is the concatenation, in order of appearance, of all the Entry Summarys within the Entry

===== Entry Permalink =====
* an Entry Permalink element is identified by [[rel-bookmark]]
* an Entry {{should}} have an Entry Permalink
* an Entry Permalink element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 Atom link in an entry]
* if the Entry Permalink is missing, use the URI of the page; if the Entry has an "id" attribute, add that as a fragment to the page URI to distinguish individual entries

===== Entry Updated =====
* an Entry Updated element is identified by class name <code>updated</code>
* an Entry Updated element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* an Entry {{should}} have an Entry Updated element
* use the [[datetime-design-pattern]] to encode the updated datetime
* if there is no Entry Updated element,
** use the Entry Published element, if present
** otherwise the page is invalid hAtom

===== Entry Published =====
* an Entry Published element is identified by the class name <code>published</code>
* an Entry Published element represents the concept of [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* use the [[datetime-design-pattern]] to encode the published datetime

===== Entry Author =====
* an Entry Author element is represented by class name <code>author</code>
* an Entry Author element represents the concept of an [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* an Entry Author element {{must}} be encoded in an [[hcard|hCard]]
* an Entry Author element {{should}} be encoded in an <code><address></code> element
* an Entry {{should}} have at least one Entry Author element
* an Entry {{may}} have more than one Entry Author elements
* if the Entry Author is missing
** find the [[algorithm-nearest-in-parent|Nearest In Parent]] <code><address></code> element(s) with class name <code>author</code> and that is/are a valid [[hcard|hCard]]
** otherwise the entry is invalid hAtom

=== XMDP Profile ===
See [[hatom-profile]].

== Examples ==

See [[hatom-examples]].

=== Examples in the wild ===

See [[hatom-examples-in-wild]].

== Implementations ==

This section is '''informative'''.

The following implementations have been developed which either generate or parse hAtom links. If you have an hAtom implementation, feel free to add it to the '''top''' of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://code.google.com/p/spinn3r-client/ spinn3r-client] - implemented in [http://spinn3r.com Spinn3r] and part of [http://code.tailrank.com/feedparser FeedParser] and our announcement of [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom in Spinn3r 2.1]
* the [http://code.google.com/p/aump/ Almost Universal Microformat Parser] can extract hAtom content from webpages ([http://code.davidjanes.com/aumfp/demo/ demo])
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforms hAtom to Atom (as the name suggests.)
* There is now an [http://www.lukearno.com/projects/hatom2atom/ hatom2atom proxy] that uses hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] is a script that provides [http://ranchero.com/netnewswire/ NetNewsWire 2.x] users with the ability to subscribe to hAtom documents as they would any other feed. by [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - has GPL'ed PHP code for reading hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supports subscribing to hAtom as a feed format
* There is a [http://code.google.com/p/transformr/downloads/detail?name=hatom%280.2%29.zip hAtom toolkit] that extracts hAtom, there is also a [http://transformr.co.uk/ demo here]


== Copyright ==
{{MicroFormatCopyrightStatement2005}}
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287: The Atom Syndication Format]
* [[hcard-parsing]]
* [[rfc-2119|RFC 2119]]
* [[iso-8601|ISO8601]]

=== Informative References ===
* [http://www.atomenabled.org/ atomenabled.org]

== Further Reading ==
* [http://www.ablognotlimited.com/articles/getting-semantic-with-microformats-part-5-hatom/ Getting Semantic With Microformats, Part 5: hAtom] by [http://www.ablognotlimited.com/ Emily Lewis]

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:

* [[blog-post-brainstorming|blog-post Brainstorming]]

=== Version 0.1 ===

Version 0.1 was released 28 February 2006.

== Discussions ==

* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].

=== Q&A ===
* If you have any questions about hAtom, check the [[hatom-faq|hAtom FAQ]], and if you don't find answers, add your questions!

=== Issues ===
* Please add any issues with the specification to the separate [[hatom-issues|hAtom issues]] document.

==See Also==
{{hatom-related-pages}}
* [[rel-enclosure]] - how to semantically reference enclosures (e.g. podcasts) in hAtom
* [[blog-post-brainstorming]]
* [[blog-post-formats]]
* [[blog-post-examples]]
* [[blog-post-feed-equivalence]]
* [[blog-description-format]] - how to describe a blog (as opposed to the individual entries, which is what we're doing here)
* [[xhtml-syndication]]

[[Category:Draft Specifications]]
[[Category:hAtom]]

== Translations ==
Read the hAtom draft specification in additional languages:
* [[hatom-fr|français]]

hrecipe-ja

2010-06-21T09:01:52Z

Imagedrive: /* Copyright */ 見出しと本文の翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* もし" author "プロパティがプレーンテキストのみ含んでいるならば、" vcard fn "形式と見なすべきです。

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== コピーライト ===

著者によって2008年11月14日に [[Microformats_Wiki:Copyrights]] を通じ、hRecipe はパブリックドメインになりました。使用、配布、再版またはいかなる種類の他の制限も、この仕様のテキストまたは内容に関して含まれていません。

== 特許 ==
{{MicroFormatPatentStatement-ja}}

=== Public Domain Release ===

このページの著者と編集者はドキュメント上の著作権を放棄することによって　パブリックドメインでこのページの文書を公開しています。

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== 進行中の仕様 ==
この仕様は現在進行中です。更なる特徴が議論され、理解され、書かれた時には追加されるでしょう。

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-06-21T08:24:22Z

Imagedrive: /* Parser Processing Notes */ 本文訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* もし" author "プロパティがプレーンテキストのみ含んでいるならば、" vcard fn "形式と見なすべきです。

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

=== Public Domain Release ===

このページの著者と編集者はドキュメント上の著作権を放棄することによって　パブリックドメインでこのページの文書を公開しています。

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== 進行中の仕様 ==
この仕様は現在進行中です。更なる特徴が議論され、理解され、書かれた時には追加されるでしょう。

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-06-21T07:18:00Z

Imagedrive: /* Work in progress */ 見出しと本文の翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

=== Public Domain Release ===

このページの著者と編集者はドキュメント上の著作権を放棄することによって　パブリックドメインでこのページの文書を公開しています。

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== 進行中の仕様 ==
この仕様は現在進行中です。更なる特徴が議論され、理解され、書かれた時には追加されるでしょう。

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-06-21T07:10:33Z

Imagedrive: /* Public Domain Release */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

=== Public Domain Release ===

このページの著者と編集者はドキュメント上の著作権を放棄することによって　パブリックドメインでこのページの文書を公開しています。

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-06-21T06:52:17Z

Imagedrive: /* Patents */ 見出しの翻訳とテンプレートリンクの修正

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

== 特許 ==
{{MicroFormatPatentStatement-ja}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-06-21T06:48:12Z

Imagedrive: /* 通例 */ 本文翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===

hRecipe フォーマットは多くのレシピサイトで使われている一般的なプロパティのセットと、今日のウェブで使われているフォーマットをベースにしています。プロパティ名は関連する microformat standards で定義済みのものがベースに選ばれました。 
いくつかのプロパティはレシピを説明するのに必要な最小限のセットを上回る''実験的''な記述ですが、ウェブでは一般的に利用されています。それらが（ hRecipe ）フォーマットに含まれるのに十分関連するプロパティかどうかは、わかりません。これらのプロパティの実装と導入は観察され、さらに決定されて提供されるでしょう。それらのプロパティは非推奨ではありません。しかし最終的な仕様から削除される可能があるので注意して使用してください。

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-05-29T16:11:44Z

Imagedrive: /* Examples in the wild */ 見出しの翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== 実装例 ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-05-29T16:09:52Z

Imagedrive: /* References */ 見出しの翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== 参考文献 ==

=== 規範的な参考文献 ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== その他の参考文献 ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T09:01:35Z

Imagedrive: /* Implementations */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
このセクションは'''参考情報'''です。

hRecipe の生成や処理できるツールです。リストが大きくなったら、[[hrecipe-implementations]] といった別のページにて紹介する予定です。

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T08:43:25Z

Imagedrive: /* Examples in the wild */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

このセクションは'''参考情報'''です。

hRecipe が利用されているサイトやページです。リストが大きくなったら、[[hrecipe-examples-in-wild]] といった別のページにて紹介する予定です。

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
* [http://recipe.gnavi.co.jp/ ぐるなびレシピ] レシピ詳細ページで hRecipe をサポート。ただし全レシピ詳細ページに hRecipe はサポートしていない。
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T08:25:38Z

Imagedrive: /* Examples */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

このセクションは参考です。

ここでは実際のウェブサイトからにあるレシピの情報を、簡単に hRecipe として使うことができるいくつかの例がいくつかあります（will be）。差し当たり、以下のように不自然な例である必要があります。

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T07:53:13Z

Imagedrive: /* Notes */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

このセクションは参考です。

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T07:45:45Z

Imagedrive: /* Human vs. Machine Readable */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

もし <code><abbr></code> 要素がプロパティに用いられている場合、要素の内容ではなく <code><abbr></code> 要素の '<code>title</code>' 属性値がプロパティの値となります。要素の内容は、より人間にとって読みやすい値の表現となります。

もし <code><a></code> 要素がひとつまたは複数のプロパティに用いられている場合、次のように処理される必要があります (must)：
# 'photo' プロパティと、他に URL を取るすべてのプロパティでは、<code>href="..."</code> 属性の値がプロパティの値となります。
# その他のプロパティでは、要素の内容がプロパティの値となります。

もし <code><img></code> 要素を 'photo' プロパティに用いる場合、<code>src="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

もし <code><object></code> 要素を 'photo' プロパティに用いる場合、<code>data="..."</code> 属性の値をプロパティの値として使用する必要があります (must)。

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-30T07:08:47Z

Imagedrive: /* Language */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* 自然言語で書かれているレシピを明確に伝えるなら、標準的な (X)HTMLで class="hrecipe" の要素に 'lang' または 'xml:lang' 属性を付加してください。
**例：<code><nowiki>I like Kartoffelknödel best.</nowiki></code>
* もし hRecipe (例えば材料の名前)の一部が異なる言語であるなら、その箇所に 'lang' または 'xml:lang' 属性で言語を指定してください。
* hRecipe が書かれている自国語を取り扱う必要がある hRecipe パーサーは特定の標準的な (X)HTML 'lang' または 'xml:lang' 属性で処理しなければなりません。
* 他のいかなる言語も hRecipe の上で指定されてなく、自国語を取り扱う必要がある hRecipe パーサーはページ内の自国語を発見し、それを hRecipe に適用するために DOM ツリーを横断するかもしれません。

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-29T06:47:11Z

Imagedrive: /* More Semantic Equivalents */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

いくつかのプロパティはよりセマンティックな同義な語で、したがってそれらは例のように特別な処理をできます：

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-29T04:08:43Z

Imagedrive: /* Semantic XHTML Design Principles */ {{semantic-xhtml-design-principles}}を{{semantic-xhtml-design-principles-ja}}に変更

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles-ja}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-27T03:26:26Z

Imagedrive: /* tag */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

主成分や食事の種類などレシピのテーマや重要な面などキーワードに示します。

* プロパティは <code>tag</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>tag</code> プロパティを含めることができます。
* プロパティは [[rel-tag]] のルールに従う必要があります。
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-27T02:43:05Z

Imagedrive: /* nutrition */ 翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

カロリーや脂肪、食物繊維など栄養分情報

* プロパティは <code>nutrition</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>nutrition</code> プロパティを含めることができます。
* プロパティは [[hCard]] の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。この場合、それぞれの栄養分情報の項目は <code>nutrition</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブエレメントは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。
* <code>nutrition</code> は、''実験的''で最終的な仕様から削除される可能性があります。

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-27T02:13:09Z

Imagedrive: /* published */ 翻訳追加

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* プロパティは、''実験的''で最終的な仕様から削除される可能性があります。

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-26T13:22:38Z

Imagedrive: /* published */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

レシピが公開された日付。

* プロパティは <code>published</code> で識別されます。
* レシピは <code>published</code> を含むことができます。
* プロパティは [[value-class-pattern|value-class-pattern]] を使用してエンコードされます：<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-25T11:21:19Z

Imagedrive: /* author */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

著者は、レシピを書いた人です。

* プロパティは <code>author</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>author</code> プロパティを含めることができます。
* 要素の内容は "vcard fn" 標準のプレーンテキスト文字列が利用されます。何よりも [[hCard]] の仕様に従わなければなりません。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-23T18:06:57Z

Imagedrive: /* summary */ の翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

概要はレシピに関する短い紹介または付帯事項を提供します。

* プロパティは <code>summary</code> で識別されます。
* レシピは <code>summary</code> を含むことができます。
* プロパティは [[hCalendar]] のルールに従う必要があります。プレーンテキストはこれらの要件を満たします。
* プロパティは実験的で最終的な仕様から削除される可能性があります。

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-23T08:33:50Z

Imagedrive: /* 書式 */ Template:rfc-2119-intro を翻訳版 Template:rfc-2119-intro-ja へリンク変更

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro-ja}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

Template:rfc-2119-intro-ja

2010-04-23T08:32:24Z

Imagedrive: /* Template:rfc-2119-intro */ を部分訳

この文書内の語句 "{{must}}", "{{must-not}}", "{{required}}", "{{shall}}", "{{shall-not}}", "{{should}}", "{{should-not}}", "{{recommended}}", "{{may}}", and "{{optional}}" は、[[rfc-2119|RFC 2119]] で記述される解釈で使われます。

hrecipe-ja

2010-04-23T08:20:20Z

Imagedrive: /* Scope */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== 範囲 ===

hRecipe は食物と食事の準備ための説明と材料リストに注釈を付けるフォーマットです。レシピは常にいくつもの共通したプロパティを共有します。hRecipe は最小限の一般的なサブセットをベースにしています。

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-23T07:09:54Z

Imagedrive: /* Out of scope */ の翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== 範囲外 ===

人間が食べることのできないレシピは hRecipe の範囲外です。

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-23T07:04:04Z

Imagedrive: /* Inspiration and Acknowledgments */ を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== インスピレーションと謝辞 ===

研究成果やアイデアを提案したり、hRecipe-format やレシピに関係した議論をおこなった様々な人達に感謝しています。

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-23T05:13:30Z

Imagedrive: /* 概要 */ 概要の約完了

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

レシピの集約とシンジケーションおよび流通と共有と促進を可能にするために、作者はレシピのメタデータを分類するオープンスタンダードな hRecipe マイクロフォーマットを提案します。作者は [[recipe-formats]] についてのワイルドで初期の試みにおいて多数の [[recipe-examples]] を研究し、レシピコンテンツのためにシンプルで小さいスキーマである hRecipe を設計しました。フィードバックは [[recipe-feedback|hRecipe feedback]] ページでお願いします。

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-22T15:37:28Z

Imagedrive: /* 概要 */ 3章目を翻訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

そのような情報をマークアップしておくことで閲覧者にいくらかの有益な情報を提供することができます。もしウェブブラウザがそれぞれのウェブページに含まれるレシピに関する固有の意味を理解できれば、豊かな相互作用を生み出すことができます。例えば、特定の検索は材料や著者のために Google や Wikipedia などの一般的な検索サービスで実行されるかもしれません。さらにクローラによる分類は、より正確になることができます。1ページで見つけられたレシピが20ほどあって、ある材料を含んでいるなら、そのページが料理だけではなく、その特定の材料についてのページと仮定することができます。

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-22T10:40:14Z

Imagedrive: /* 概要 */ 一部和訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

マイクロフォーマットの hRecipe は食事や飲み物、食材の調理方法をマークアップするためにデザインされています。

ブラウザがウェブページに記述されているレシピについての意味的な情報を抽出するのは困難です。メタデータはレシピの著者やレシピ名と材料、調理方法、調理時間についての詳細など、レシピに関係する情報を提供します。

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-21T05:02:28Z

Imagedrive: hRecipe is a simple, open...を和訳

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] はシンプル、オープン、分散されたフォーマットで、(X)HTML、Atom、RSS、そして任意の XML で料理のレシピについての情報を埋め込むのに適しています。hRecipe はオープンスタンダードな [[microformats]] の一つです。このページとマイクロフォーマットは、パブリックドメインです。

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-21T03:22:13Z

Imagedrive: entry-title と Template:DraftSpecification を和訳版の Template:DraftSpecification-ja に変更

<entry-title>hRecipe-ja</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification-ja}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

Template:DraftSpecification-ja

2010-04-21T03:20:18Z

Imagedrive: /* Template:DraftSpecification-ja */ 新規作成

''この文書は microformat のドラフト仕様です。ドラフトなので開発段階においてはいくらかは完成していますが、この文書の安定性は保証できません。なので開発者は将来の発展と変化に対応できるよう準備しておく必要があります。最新の情報を得るには、この wiki ページを見るか [http://microformats.org/discuss/ microformats-new mailing list] の議論から学んで下さい。''

hrecipe-ja

2010-04-20T17:06:57Z

Imagedrive: /* プロパティの詳細 */ リンク先を修正

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hcard-ja|hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hcalendar-ja|hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag-ja|rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-20T16:56:48Z

Imagedrive: /* photo */ 和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

添付写真

* プロパティは、<code>photo</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>photo</code> プロパティを含めることができます。
* プロパティは、img 要素を使用してください。a 要素や object 要素など URL を含んだ他の要素を使用することができますが、推奨されていません。[[hRecipe#Semantic_XHTML_Design_Principles|注釈]]を参照してください。
* プロパティは、実験的で最終的な仕様から削除される可能性があります。

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-19T16:33:48Z

Imagedrive: /* プロパティの詳細 */ を和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

<code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> と <code>type</code> のプロパティは [[hCard]] に従います。<code>duration</code> のプロパティは [[hAudio]] に従います。<code>summary</code> のプロパティは [[hCalendar]] に従います。<code>published</code> のプロパティは [[hAtom]] に従います。<code>tag</code> のプロパティは [[rel-tag]] に従います。

hRecipe スキーマのフィールドは次のように表します：

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみ使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-19T16:04:57Z

Imagedrive: /* duration */ 和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみの使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

調理に必要な時間を記述します。例えば生地を準備するための時間、生地の発酵に必要な時間、生地を焼く時間、ケーキ等を飾る時間など、複数の調理時間のプロパティを示すために使用することができます。

* プロパティは <code>duration</code> で識別されます。
* レシピは、ひとつもしくは複数の <code>duration</code> プロパティを含めることができます。
* プロパティは [[value-class-pattern|value-class-pattern]] で略述した期間をコード化してください。調理時間が1時間30分の場合、ISO 8601 形式の"PT1H30M"に変換し、以下のようにコード化することができます：<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-19T05:52:28Z

Imagedrive: /* instructions */ 和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみの使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

レシピの方法手順。

* プロパティは <code>instructions</code> で識別されます。
* レシピは <code>instructions</code> を含むことができます。
* プロパティは妥当な HTML でマークアップされた文章や手順のリストを含むことができます。

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-18T12:27:41Z

Imagedrive: /* yield */ 和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみの使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

このレシピで何人分の分量または数量（個数）を指定します。

* プロパティは <code>yield</code> で識別されます。
* レシピは <code>yield</code> を含むことができます。

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

User:Imagedrive

2010-04-18T04:23:03Z

Imagedrive: /* Wataru Yoshimura */

== Wataru Yoshimura ==

吉村渉と言います。

The Web KANZAKI を読んでセマンティック・ウェブ、マイクロフォーマットに興味を持ちました。

翻訳は上手ではありませんが、理解する手助けになると幸いです。

よろしくお願いします。

My name i Wataru Yoshimura.

The Web KANZAKI website read, I became interested in Microformats and the Semantic Web.

The poor translation, but I hope will help you understand.

Thanks.

{{Template:public-domain-release}}

User:Imagedrive

2010-04-18T04:14:02Z

Imagedrive: プロフィールページを作成

== Wataru Yoshimura ==

吉村渉と言います。

The Web KANZAKI を読んでセマンティック・ウェブ、マイクロフォーマットに興味を持ちました。

翻訳は上手ではありませんが、理解する手助けになると幸いです。

よろしくお願いします。

My name i Wataru Yoshimura.

The Web KANZAKI interested in reading the Semantic Web and microformats.

The poor translation, but I hope will help you understand.

Thanks.

{{Template:public-domain-release}}

hrecipe-ja

2010-04-17T19:43:13Z

Imagedrive: /* ingredient */ 材料を和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみの使用

==== ingredient ====

レシピに使われているひとつまたは複数の材料を記述します。

* プロパティは <code>ingredient</code> で識別されます。
* レシピにはひとつまたは複数の <code>ingredient</code>s を含む必要があります。
* プロパティには（材料のリストなどを）妥当な HTML マークアップで含むことができます。
* プロパティは hCard の規則に従った <code>value</code> (値)と <code>type</code> (型)を含むことができます。<source lang=html4strict>125ml milk</source>この場合、それぞれの材料は <code>ingredient</code> プロパティに含むかたちでマークアップしなければなりません。これらのサブプロパティは実験的で最終的な仕様から削除される可能性か、[[measure|分量]]から"数値(num)”と"単位(unit)"に置き換えられます。

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-17T17:02:28Z

Imagedrive: /* fn */ 和訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

1つのレシピのタイトルです。概要は短いテキストで構成され関連性のあるグループ間を識別するのに使用されます。これは、食事や食材の名前に簡単な説明をします。

* プロパティは <code>fn</code> で識別されます。
* レシピは <code>fn</code> が必須です。
* プロパティは [[hCard]] のルールに従う必要があります。例）プレーンテキストのみの使用

==== ingredient ====

Describes one or more ingredients used in the recipe.

* The property is identified by the name <code>ingredient</code>.
* A Recipe {{must}} include one or more <code>ingredient</code>s.
* The property {{may}} include valid HTML markup (e.g. a list of ingredients).
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]], e.g. <source lang=html4strict>125ml milk</source>In this case each ingredient should be marked up with it's own <code>ingredient</code> property. These subproperties are considered ''experimental'' and may be removed from the final specification or replaced by 'num' and 'unit' from [[measure]].

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

hrecipe-ja

2010-04-16T19:34:53Z

Imagedrive: /* hRecipe */ を訳

<entry-title>hRecipe-ja 0.22</entry-title>
<h1>hRecipe</h1>
{{Template:DraftSpecification}}
{{TOC-right}}

http://www.livingathome.de/test/recipe/hRecipe.png

[[recipe|hRecipe]] is a simple, open, distributed format, suitable for embedding information about recipes for cooking in (X)HTML, Atom, RSS, and arbitrary XML. hRecipe is one of several [[microformats]] open standards. This page and Microformat is in the public domain.

== hRecipe Microformat Draft Specification ==

=== 編者 ===
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])
=== 作者 ===
* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]

=== 貢献者===
[[User:AndyMabbett|Andy Mabbett]], [[User:Phae|Frances Berriman]], [[User:IamCam|Cameron Perry]], [[User:JohnLeMasney|John LeMasney]], [[User:Tantek|Tantek Çelik]], [[User:SudarshanP|SudarshanP]], [[User:CiaranMc|Ciaran McNulty]], [[User:LeeJordan|Lee Jordan]], [[User:RobertBachmann|Robert Bachmann]], [[User:JeffMcNeill|jeffmcneill]], [[User:ManuSporny|Manu Sporny]], [[User:RyanKing|Ryan King]], HollyMarieKoltz, Straup, [[User:ChristopheDucamp|Christophe Ducamp]], Mercman, [[User:Yde|Yde]], [[User:AmeerDawood|Ameer Dawood]], Scottk, [[User:Lee_Jordan|Lee Jordan]], MonroAlmon, EstevaoSamuel, [[User:Brian|Brian Suda]], SteveL, JohnLeMasney,

Microformats [[#Copyright]] and [[#Patents]] statements apply.

== 概要 ==

The hRecipe microformat is designed for the mark-up of instructions for creating meals, drinks or food-based items.

It is difficult for a browser to extract semantic information about a recipe described on a web page. Metadata such as author and name and details such as ingredients, method, preparation time etc provide relevant information about the recipe.

Having such information marked up can provide a number of benefits to the viewer. If a web browser understands that a particular web page contains a recipe with specific characteristics, it can produce richer interactions. For example, specific searches may be performed for ingredients or authors via general search services such as Google and Wikipedia. Additionally, classification by crawlers can become more accurate. If there are 20 recipes found on a page, and they all contain a certain ingredient, it can be assumed that the page is not only about cooking, but also about that particular ingredient.

In order to enable and encourage the sharing, distribution, syndication, and aggregation of recipes, the authors propose the hRecipe microformat, an open standard for distributed recipe metadata. The authors have researched both numerous [[recipe-examples]] in the wild and earlier attempts at [[recipe-formats]], and have designed hRecipe around a simple minimal schema for recipe content. Feedback is encouraged on the [[recipe-feedback|hRecipe feedback]] page.

=== Inspiration and Acknowledgments ===

Many thanks to the various individuals that did research and proposed ideas and discussion related to the hRecipe-format and recipes in general.

=== Scope ===

hRecipe is a format to annotate descriptions and lists of ingredients for the preparation of food and meals. Recipes consistently share several common properties. hRecipe has been based on this minimal common subset.

=== Out of scope ===

Recipes that are not for stuff that's meant to be eaten by humans are out of scope.

== 書式 ==

{{rfc-2119-intro}}

=== 通例 ===
The hRecipe format is based on a set of properties common to numerous recipe sites and formats in use today on the web. Where possible property names have been chosen based on those defined by related microformat standards. 
Some properties are marked ''experimental'' since they exceed the minimum set of properties needed to describe a recipe but still are very commonly used on the web. It's not sure if they are relevant enough for inclusion in the format. Implementation and general uptake of these properties will be observed and inform further decisions. So their use is not at all discouraged - but use them with care and be prepared for their eventual removal from the final spec.

=== スキーマ ===
hRecipe スキーマは以下のプロパティで構成されます:

* '''hrecipe'''
** '''fn'''. 必須。テキスト。レシピの名前。
** '''ingredient'''. 必須。1つ又はそれ以上の任意の妥当な (x)HTML でマークアップされたテキスト。
*** '''''value''''' and '''''type'''''. 任意。（実験的）
** '''''yield'''''.任意。テキスト。
** '''''instructions'''''. 任意。任意の妥当な (x)HTML でマークアップされたテキスト。
** '''''duration'''''. 任意。1つ又はそれ以上のテキスト。
** ''photo''. 任意。1つ又はそれ以上。画像のような任意の要素を含んだ URLを使用。（実験的）
** ''summary''. 任意。テキスト。（実験的）
** ''author''. 任意。1つ又はそれ以上（実験的）
** ''published''. 任意。（実験的）
** ''nutrition''. 任意。1つ又はそれ以上（実験的）
*** ''value'' and ''type''. 任意。（実験的）
** ''tag''. 任意。1つ又はそれ以上（実験的）

=== プロパティの詳細 ===

Property names <code>fn</code>, <code>photo</code>, <code>author</code>, <code>value</code> and <code>type</code> are reused from [[hCard]]. Property name <code>duration</code> is reused from [[hAudio]]. Property name <code>summary</code> is reused from [[hCalendar]]. Property name <code>published</code> is reused from [[hAtom]]. Property name <code>tag</code> is reused from [[rel-tag]].

The fields of the hRecipe schema represent the following:

==== hRecipe ====

hRecipe はレシピの識別や値の記述、メタデータの関連付けに用いられます。　

* hRecipe プロパティは <code>hrecipe</code> 名で識別されます。

==== fn ====

The title of a single recipe. A short textual description used to identify the work among interested parties. This can be the name of a meal or a short description regarding it's ingredients.

* The property is identified by the name <code>fn</code>.
* A Recipe {{must}} include a <code>fn</code>.
* The property {{must}} follow the conventions outlined in [[hCard]] e.g. by using only plain text.

==== ingredient ====

Describes one or more ingredients used in the recipe.

* The property is identified by the name <code>ingredient</code>.
* A Recipe {{must}} include one or more <code>ingredient</code>s.
* The property {{may}} include valid HTML markup (e.g. a list of ingredients).
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]], e.g. <source lang=html4strict>125ml milk</source>In this case each ingredient should be marked up with it's own <code>ingredient</code> property. These subproperties are considered ''experimental'' and may be removed from the final specification or replaced by 'num' and 'unit' from [[measure]].

==== yield ====

Specifies the quantity produced by the recipe, like how many persons it satisfyies or how many pieces can be made of it.

* The property is identified by the name <code>yield</code>.
* A Recipe {{may}} include a <code>yield</code>.

==== instructions ====

The method of the recipe.

* The property is identified by the name <code>instructions</code>.
* A Recipe {{may}} include a <code>instructions</code> property.
* The property {{may}} include valid HTML markup e.g. paragraphs or a list of steps.

==== duration ====

The time it takes to prepare the meal described by the recipe. Multiple duration properties can be used to denote e.g. time for preparing a dough, time needed for the dough to raise, time to bake the dough, time for decorating the cake etc.

* The property is identified by the name <code>duration</code>.
* A Recipe {{may}} include one or more <code>duration</code> properties.
* The property {{may}} encode the timespan as outlined in the [[value-class-pattern|value-class-pattern]]. A duration of 1 hour 30 minutes would translate to "PT1H30M" in ISO 8601 format and can be encoded as follows:<source lang=html4strict> 90 min</source>

==== photo ====

Accompanying image.

* The property is identified by the name <code>photo</code>.
* A Recipe {{may}} include one or more <code>photo</code> properties.
* The property {{should}} use an <img> element. It {{may}} use any other element that contains a URL, such as <a> or <object>, but it is not recommended. See [[hRecipe#Semantic_XHTML_Design_Principles | notes]] below.
* The property is considered ''experimental'' and may be removed from the final specification.

==== summary ====

The summary provides a short introduction to or an accompanying statement about the recipe.

* The property is identified by the name <code>summary</code>.
* A Recipe {{may}} include a <code>summary</code>.
* The property {{must}} follow the conventions outlined in [[hCalendar]]. Plain text fulfills these requirements.
* The property is considered ''experimental'' and may be removed from the final specification.

==== author ====

An author is the person who wrote the recipe.

* The property is identified by the name <code>author</code>.
* A Recipe {{may}} include one or more <code>author</code> properties.
* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]].
* The element is considered ''experimental'' and may be removed from the final specification.

==== published ====

The date the recipe was published.

* The property is identified by the name <code>published</code>.
* A Recipe {{may}} include a <code>published</code> date.
* The property {{may}} be encoded using the [[value-class-pattern|value-class-pattern]], e.g.:<source lang=html4strict>Published 14. Oct 2008</source>
* The property is considered ''experimental'' and may be removed from the final specification.

==== nutrition ====

Nutritional information like calories, fat, dietary fiber etc.

* The property is identified by name <code>nutrition</code>.
* A Recipe {{may}} include one or more <code>nutrition</code> properties.
* The property {{may}} include the properties <code>value</code> and <code>type</code> following the conventions outlined in [[hCard]]. In this case each nutritional information item should be marked up with it's own <code>nutrition</code> property. These subelement are considered ''experimental'' and may be replaced by 'num' and 'unit' from [[measure]].
* The property <code>nutrition</code> itself is also considered ''experimental'' and may be removed from the final specification.

==== tag ====

A keyword indicating a subject or an important aspect of the recipe like it's main ingredient, type of meal etc.

* The property is identified by the name <code>tag</code>.
* A Recipe {{may}} include one or more <code>tag</code>'s.
* The property {{must}} follow the conventions outlined in [[rel-tag]].
* The property is considered ''experimental'' and may be removed from the final specification.

=== Version history ===

* Version 0.22 changed the proposed formatting of time and date from the [[datetime-design-pattern|datetime-design-pattern]], which has [[datetime-design-pattern#Accessibility_issues|accessibility issues]], to the [[value-class-pattern|value-class-pattern]]. Also corrected some errors in the example especially with regard to the correct handling of vcard properties.
* Version 0.21 changed the status of ingredient/value and ingredient/type to ''experimental'', mentioning that there still is discussion if they should be replaced by 'num' and 'unit' from [[measure]] (which is still in brainstorming).
* Version 0.2: From [http://microformats.org/wiki/index.php?title=hrecipe&oldid=37357 Version 0.1] some elements have been renamed to strenghten re-use of established elements: '''fn''' for '''hRecipe-title''', '''summary''' for '''hRecipe-summary''', '''duration''' for '''preparation-time''', '''value''' and '''type''' for '''num''' and '''unit'''. Also some elements have been marked '''experimental''' because of concerns of element bloat. See the [[hrecipe-issues]] page for a more thorough discussion. Draft 0.1 was already a result of long lasting efforts. Nonetheless after publishing of it there has been a lively debate about some properties. Since they mostly could be resolved version 0.2 is considered fairly stable now, although of course you never know ;-)

=== Parser Processing Notes ===

* If the "author" property contains only a plain text string it should be regarded as of type "vcard fn".

=== Semantic XHTML Design Principles ===

{{semantic-xhtml-design-principles}}

==== More Semantic Equivalents ====

For some properties there is a more semantic equivalent, and therefore they get special treatment, e.g.:

* For "photo", use <code><img class="photo" src="..." alt="" /></code>

==== Language ====

* To explicitly convey the natural language that an recipe is written in, use the standard (X)HTML 'lang' or 'xml:lang' attribute on the element with class="hrecipe"
**e.g. <code><nowiki>I like Kartoffelknödel best.</nowiki></code>
*If portions of an hRecipe (e.g. an ingredient name) are in a different language to the rest of the hRecipe, use the 'lang' or 'xml:lang' attribute on those portions.
* hRecipe parsers which need to handle the native language of hRecipe {{must}} process the standard (X)HTML 'lang' or 'xml:lang' attribute as specified.
* hRecipe parsers which need to handle native language {{may}} traverse up the DOM to discover the native language of the page and apply that to the hRecipe if no other language is specified on the hRecipe.

==== Human vs. Machine Readable ====

If an <code><abbr></code> element is used for a property, then its '<code>title</code>' attribute is used for the value of the property, instead of the contents of the element, which can then be used to provide a user-friendly alternate presentation of the value.

If an <code><a></code> element is used for one or more properties, it {{must}} be treated as follows:
# For the 'photo' property and any other property that takes a URL as its value, the <code>href="..."</code> attribute provides the property value.
# For other properties, the element's content is the value of the property.

If an <code><img></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>src="..."</code> attribute as property value.

If an <code><object></code> element is used for the 'photo' property, it {{must}} use the property value provided by the <code>data="..."</code> attribute as property value.

=== Notes ===

This section is informative.

*Non so far.

== XMDP Profile ==

<source lang=html4strict>
<dl class="profile">
<dt>class</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hrecipe</dt>
<dd>
Used to identify and describe metadata associated with instructions for creating meals, drinks or food-based items.
</dd>
<dt>fn</dt>
<dd>
The title of the recipe.
</dd>
<dt>ingredient</dt>
<dd>
Describes the ingredient(s) used in the recipe.
</dd>
<dt>yield</dt>
<dd>
Specifies the quantity produced by the recipe.
</dd>
<dt>instructions</dt>
<dd>
The method of the recipe.
</dd>
<dt>duration</dt>
<dd>
The time it takes to prepare the meal described by the recipe.
</dd>
<dt>photo</dt>
<dd>
Accompanying image.
</dd>
<dt>summary</dt>
<dd>
The summary provides a short introduction or an accompanying statement about the recipe.
</dd>
<dt>author</dt>
<dd>
The person who authored the recipe..
</dd>
<dt>published</dt>
<dd>
The date that the recipe was made available to the public.
</dd>
<dt>nutrition</dt>
<dd>
Nutritional information like calories, fat, dietary fiber etc.
</dd>
<dt>tag</dt>
<dd>
Keyword(s) describing the recipe.
</dd>
</dl>
</dd>
</dl>
</source>

== Examples ==

This section is informative.

Here '''will be''' a few examples of recipes, from real web sites, showing how they could be easily enhanced to use hRecipe. In the meantime the following contrieved example will have to do.

<source lang=html4strict><div class="hrecipe">
<h1 class="fn">Pommes Frites</h1>

Pommes frites originate in outer space. They are served hot. 
This recipe is only an example. Don't try this at home!


Contributed by CJ Tom and the
<a class="url fn" href="http://example.com">Cooky Gang</a>.

Published 14. Oct 2008
<img src="/img/pommes.png" class="photo" width="100" height="100" alt="Pommes Frites"/>
<h2>Ingredients</h2>
<ul>
<li class="ingredient">
500
gramme potatoes, hard cooking.
</li>
<li class="ingredient">
1 spoonful of salt
</li>
<li>
You may want to provide some
Ketchup and Mayonnaise
as well.
</li>
</ul>
<h2>Instructions</h2>
<ul class="instructions">
<li>First wash the potatoes.</li>
<li>Then slice and dice them and put them in boiling fat.</li>
<li>After a few minutes take them out again.</li>
</ul>
<h2>Further details</h2>
Enough for 12 children.
Preparation time is approximately
 90 min

Add half an hour to prepare your homemade Ketchup.
This recipe is <a href="http://www.example.com/tags/difficulty/easy" rel="tag">easy</a> and <a href="http://www.example.com/tags/tastyness/delicious" rel="tag">delicious</a>.


Pommes Frites have more than
1000
Joule
Energy,
while Ketchup and Mayonnaise have
0 vitamins.

</div>
</source>


== Examples in the wild ==

This section is '''informative'''.

Sites and pages that publish hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-examples-in-wild]].

* [http://www.epicurious.com/ Epicurious.com]'s [http://www.epicurious.com/recipesmenus/ recipes] have been marked up with hRecipe as of April 2010. (E.g., [http://www.epicurious.com/recipes/food/views/Chocolate-Almond-and-Banana-Parfaits-357369 Chocolate, Almond, and Banana Parfaits])
* [http://www.williams-sonoma.com/ Williams-Sonoma]'s [http://www.williams-sonoma.com/recipe/ recipes section], e.g. [http://www.williams-sonoma.com/recipe/cherry-almond-bundt-cake.html Cherry Almond Bundt Cake]
* http://foodnetwork.com/ has marked up all their recipes with hRecipe as of 2009-10, e.g. [http://www.foodnetwork.com/recipes/ina-garten/deep-dish-apple-pie-recipe2/index.html Deep-Dish Apple Pie recipe]
* [http://www.plantoeat.com/ Plan to Eat]'s [http://www.plantoeat.com/recipe_book recipe planner] is now in hRecipe format as of April 2010. (E.g., [http://www.plantoeat.com/recipes/4583/1fv1A5vFhjm Pasta With Smashed Peas])
* essen & trinken. As of spring 2009 [http://www.essen-und-trinken.de essen & trinken] publishes all recipes with hRecipe-conformant metadata encoded in RDF. See [[hrecipe-rdf]] for technical details.
* It's Ripe! As of January 2009, [http://itsripe.com/recipes/ http://itsripe.com] supports hRecipe for recipe pages and will soon add support in lists.
*'''Wild Mushroom, Pancetta & Truffle Risotto''' by Toby Inkster
** [http://tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Marked up as hRecipe] using the September 2007 draft format
** [http://srv.buzzword.org.uk/recipebook/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RecipeBook XML] output from Cognition.
** [http://srv.buzzword.org.uk/rdf-xml/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ RDF/XML] and [http://srv.buzzword.org.uk/turtle/tobyinkster.co.uk/blog/2008/10/23/mushroom-risotto/ Turtle] output from Cognition.

== Implementations ==
This section is '''informative'''.

Tools for generating and consuming hRecipes. When it gets too big we can move it to a separate page like [[hrecipe-implementations]].

* Cognition. As of September 2008, [http://buzzword.org.uk/cognition/ Cognition] has experimental support for this format. ([http://buzzword.org.uk/cognition/uf-plus.html#hrecipe Details of support].) Recipes may be exported in [[recipe-formats#RecipeBook_XML|RecipeBook XML]] format or RDF.
* WordPress Plugin. There's a [http://wordpress.org/ WordPress ] [http://wordpress.org/extend/plugins/hrecipe/ hRecipe Plugin] available which makes adding hRecipe metadata to recipes very easy, practically effortless. Very nice!

== References ==

=== Normative References ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://gmpg.org/xmdp/ XMDP]
* [[hcard|hCard]]
* [[abbr-design-pattern]]
* [[datetime-design-pattern]]

=== Informative References ===
* [http://www.w3.org/TR/REC-CSS1 CSS1]
* ISO.8601.1988
** International Organization for Standardization, "Data elements and interchange formats - Information interchange - Representation of dates and times", ISO Standard 8601, June 1988.
* [http://www.w3.org/TR/1998/NOTE-datetime-19980827 W3C NOTE-datetime-19980827]
* [http://www.w3.org/Consortium/Patent-Policy-20040205/ W3C Patent Policy]
* Other recipe metadata efforts. See [[recipe-formats]].
* [[grouping-examples]]
* [[grouping-brainstorming]]
* [[xoxo|XOXO]]

=== Copyright ===

Per [[Microformats_Wiki:Copyrights]], hRecipe was placed into the public domain on 2008-11-14 by the authors. There are no usage, distribution, re-printing, or any other restrictions of any kind with regards to the text or content of this specification.

=== Patents ===

{{MicroFormatPatentStatement}}

=== Public Domain Release ===

The authors and editors of this page due hereby relinquish their copyright on the document and release the text of this page into the public domain.

* [[User:Phae|Frances Berriman]] (BBC)
* [[User:BenWard|Ben Ward]]
* [[User:TobyInk|Toby Inkster]]
* [[User:ThomasLoertsch | Thomas Loertsch]] ([http://www.essen-und-trinken.de Gruner+Jahr])

== Work in progress ==
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.

== derivative works ==
* [[hrecipe-rdf|hRecipe in RDF]] - mapping of hRecipe into a RDF vocabulary called "aRecipe"

==related pages==
* [[hrecipe-issues|hRecipe issues]] - issues regarding the hRecipe draft
* [[hrecipe-feedback|hRecipe feedback]] - general feedback regarding hRecipe

Per the microformats [[process]], the [[recipe]] effort developed
* [[recipe-examples]]
* [[recipe-formats]]
* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
* [[recipe-issues]]
towards the development of this draft.

[[Category:Draft Specifications]]

Main Page-ja

2010-04-16T19:04:41Z

Imagedrive: hrecipe-jaへのリンクミスを修正

<entry-title> Microformats Wikiにようこそ！</entry-title>

__TOC__
初めての方は、[[introduction-ja|Microformats の手引き]]からどうぞ。編集を始める前に、[[how-to-play-ja]]を読んでください。

== はじめに ==
この wiki は microformats コミュニティの中心的なリソースです。発表済みの microformats 仕様、仕様ドラフト、発表パターンの現在のバージョンを見つけることができます。新しいフォーマットのプレインストーミングページや、認められたフォーマットや開発中のフォーマットの問題追跡ページといった開発用のリソースもあります。

== スタートするには ==
Microformats を始めるには…

* まず、自分のページやアプリケーションで、意味的に豊かで説明的で、'[[posh-ja|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]' な <abbr title="HyperText Mark-up Language">HTML</abbr> を書くことに慣れましょう。
* 「[http://microformats.org/about/ microformats について]」のページ、[http://microformats.org/ ブログ]、[[press|メディア紹介例]]や[[presentations-ja|プレゼンテーション]]、microformats に関する[[books|書籍]]、[[podcasts|ポッドキャスト]]、[[screencasts|スクリーンキャスト]]ページなどで microformats について学びましょう。
* [[hcard-ja|hCard]] や [[hcalendar|hCalendar]] などの確立した仕様を軽く読み、[[hcard-examples|examples]] に倣って microformats を公開しましょう。
* 質問がある場合は、[[faq|よく聞かれる質問]]や、用語と定義については[[glossary|用語集]]をご覧ください。 {{MicroformatsMailingList}}に投稿することもできます。
* 誰かから直接話を聞きたければ、[[events|microformats のイベント]]に参加してみてください。

== 定義 ==
Microformats とは、[[hcard-ja|人]]や[[hcalendar-ja|イベント]]、[[hatom|ブログ記事]]、[[hreview-ja|レビュー]]、[[rel-tag-ja|タグ]]のような、一般的に公開されているものをWebページ上で記述する際に使う小規模なマークアップの法則です。

Microformats を使えば、さらに詳しい情報をWebで発信することができるようになります。サイト上の情報のフィードやAPIを最も素早く簡単に提供するための手段といえます。

* [[what-are-microformats|Microformats とは何か]]、[[what-can-you-do-with-microformats|これを使って何ができるか]]についてもさらに詳しい説明があります。

== 協力するには ==
Microformats をさらに良くするには、みなさんの協力が必要です。

* Webサイトやサービス、製品で[[get-started|Microformats を利用]]する。
* マイクロフォーマットをもっと使ってもらえるよう、[[advocacy|周りにすすめる]]。
* [[testimonial|Microformats の推薦文]]を書く。
* [[to-do|TO DOリスト]]にあるタスクをこなす。
* [[irc-ja|IRCチャンネル]]や[[mail|メーリングリスト]]で学んだり、質問に答える (メールを送る前に、[[mailing-lists#General_guidelines|一般的なガイドライン]]を読んでください)。
* さまざまな言葉で読めるように、Microformats wikiの翻訳を手伝う ([[Main_Page-ja#.E4.BB.96.E8.A8.80.E8.AA.9E.E3.81.A7.E3.81.AE Microformats _wiki|他言語での Microformats wiki]])。
* 新しい Microformats を提案する前に、あなたのWebサイトが[[POSH]]であり、[[get-started|すでにある Microformats を利用]]済みである事を確認する。そのあと、[[process|新しいフォーマットを提案する際のプロセス]]について良く読む。

この wiki には microformats の開発と貢献を支援するために多数の改善が含まれています。編集を始める前に [[wiki-2|wiki 紹介ページの説明]]をご覧ください。

== 仕様 ==
以下は最新の安定版 [[microformats-ja|microformats]] の公開標準仕様一覧です。

* [[hcalendar-ja|hCalendar]] (翻訳中!) - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard-ja|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license-ja|rel-license]]
* [[rel-nofollow-ja|rel-nofollow]]
* [[rel-tag-ja|rel-tag]]
* [[vote-links-ja|Vote Links]]
* [[XFN-ja|XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP|XMDP]]
* [[xoxo-ja|XOXO]]

もし自分で microformats を作ってみたい場合は [[process]] ページをまずお読みください。

== ドラフト ==

ドラフトとは、まだ完成していない比較的新しい microformats です。開発過程を経ていくぶん成熟してはいますが、文書の安定性は保証されておらず、実装する側は将来開発と変更に対応する準備をしておくべきです。アップデートに備えて wiki ページに注意しておいてください。

* [[adr|adr]] - 住所のマークアップ
* [[geo|geo]] - [http://en.wikipedia.org/wiki/WGS84 世界測地系]による、緯度と経度のマークアップ
* [[hatom|hAtom]] - 更新情報を配信する (例: ブログの投稿)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - オープンな分散的クラシファイド広告
* [[hmedia|hMedia]] - 画像、動画、音声に関する統一メディア公開フォーマット
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe-ja|hRecipe]] (翻訳中!) - お菓子や料理のレシピ
* [[hresume-ja|hResume]] (翻訳中!) - 履歴書の公開
* [[hreview-ja|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]]- リンク先が、現在のページへのリンクを含んだディレクトリ一覧であることを表す
* [[rel-enclosure]] - ダウンロードやキャッシュ用の添付（ファイルなど）であることを表す
* [[rel-home]] - サイトのホームページへのリンクであることを表す
* [[relpayment|rel-payment]] - 支払いメカニズムであることを表す
* [[robots-exclusion|robots-exclusion]]
* [[xfolk-ja|xFolk]]

== デザインパターン ==
{{design_patterns-ja}} 

== 予備的な論議 ==
実際の[[examples|利用例]]の調査と分析、既存のフォーマット、Microformats の [[process]] を通じて新しい Microformats となる可能性のあるものについてのブレインストーミングついて、詳しくは[[exploratory-discussions|予備的な論議]]をご覧ください。

== 例 ==
* [[examples-in-the-wild-ja|実際の利用例]]
* [[implementations|ツールの実装]]
* [[zen-garden|Zen Garden]]

== リソース ==
[[resources|リソースページ]]をご覧ください。

== ユーザ中心開発 ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== 共有作業領域 ==
* [[to-do|TODOリスト]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|特別ページ]]
* [[year-in-review]]

== ツール、テストケース、リサーチ ==
例やコード、テストケースなどはそれぞれ個々の Microformats のページに記載しています。
ただほんの少しだけ、複数の Microformats の処理を必要とする分野横断的な[[tools|ツールとサービス]]があります。
[[tools|ツールとサービス]]は、複数の Microformats 全体に関連したエディタ、[[parsers|パーサ]]、[[validators|バリデータ]]、テストケース、およびその他の情報を対象としたページです。

== 他言語の Microformats Wiki ==
色んな言語で Microformats の記事を読んだり編集したりできます。

* 100個以上の記事がある言語
** [[Main_Page|English (本家の英語)]]
** [[Main_Page-fr|Français (フランス語)]] {{UpdateMarker-fr}}
* 10個以上の記事がある言語
** [[Main_Page-pt-br|Português (ブラジル系ポルトガル語)]]
** [[Main_Page-ja|日本語]]
** [[Main_Page-ru|Русский (ロシア語)]]
* 2個以上の記事がある言語
** [[Main_Page-cs|Česky (チェコ語)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (ドイツ語)]]
** [[Main_Page-es|Español (スペイン語)]]
** [[Main_Page-gl|Galego (ガリーシア語)]] {{NewMarker}}
** [[Main_Page-pl|Polski (ポーランド語)]]
** [[Main_Page-ro|Română (ルーマニア語)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (中国語)]]
** [[Main_Page-id|Indonesia (バハサ・インドネシア)]] {{NewMarker}}
* 翻訳が始まったばかりの言語
** [[Main_Page-ar|العربية (アラビア語)]]
** [[Main_Page-th|ภาษาไทย (タイ語)]]
** [[Main_Page-it|Italiano (イタリア語)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (韓国語)]] {{NewMarker}}
* その他
**[http://ja.wikipedia.org/wiki/ Microformats Wikipediaの Microformats ページ]は、多くの言語版ができています。

[[other-languages]]や[[how-to-start-new-translation|how-to-start-a-new-translation]]もご覧ください。