value-class-pattern-ja - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:34:14Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:34, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Value Class Pattern~~</entry-title>~~		{{DISPLAYTITLE:Value Class Pattern}}
	<!-- english: 2011-08-18T11:20:33 -->		<!-- english: 2011-08-18T11:20:33 -->

KitaitiMakoto: sync: english: 2011-08-18T11:20:33

2011-08-25T16:32:30Z

sync: english: 2011-08-18T11:20:33

← Older revision		Revision as of 16:32, 25 August 2011
Line 1:		Line 1:
	<entry-title>Value Class Pattern</entry-title>		<entry-title>Value Class Pattern</entry-title>
	<!-- english: 2011-07-~~16T07~~:54:07 -->		<!-- english: 2011-08-18T11:20:33 -->

	value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。		value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。
Line 13:		Line 13:
	: <span class="vcard"><span class="fn">[[User:Tantek\|Tantek Celik]]</span></span>		: <span class="vcard"><span class="fn">[[User:Tantek\|Tantek Celik]]</span></span>
	; 短縮 URL		; 短縮 URL
	: <kbd>http://tr.im/valueclass</kbd>		: <kbd>http://ufs.cc/w/valueclass</kbd>

	マイクロフォーマットのプロパティの値として、ある要素の一部だけが使われることがあります。これは [[hcard-ja\|hCard]] の <code>tel: type</code> や <code>tel: value</code> など、任意サブプロパティがある時に起こる可能性があります。また、プロパティの一番適切な構造として他の内容を含むということもあります。		マイクロフォーマットのプロパティの値として、ある要素の一部だけが使われることがあります。これは [[hcard-ja\|hCard]] の <code>tel: type</code> や <code>tel: value</code> など、任意サブプロパティがある時に起こる可能性があります。また、プロパティの一番適切な構造として他の内容を含むということもあります。
Line 190:		Line 190:

	;<span style="font-size:smaller">この節の短縮 URL</span>		;<span style="font-size:smaller">この節の短縮 URL</span>
	:http://tr.im/vcpfso （英語）		:http://ufs.cc/w/vcpfso （英語）

	==== hCalendar の dtend での日付の推測処理 ====		==== hCalendar の dtend での日付の推測処理 ====

KitaitiMakoto: sync: english: 2011-07-16T07:54:07

2011-07-24T11:07:09Z

sync: english: 2011-07-16T07:54:07

← Older revision		Revision as of 11:07, 24 July 2011
Line 1:		Line 1:
	<entry-title>Value Class Pattern</entry-title>		<entry-title>Value Class Pattern</entry-title>
	<!-- english: 2011-03-~~22T01~~:32:18 -->		<!-- english: 2011-07-16T07:54:07 -->

	value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。		value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。
Line 415:		Line 415:

	== 実装 ==		== 実装 ==

	This section is '''informative'''.		This section is '''informative'''.

Line 437:		Line 436:
	* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]		* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]
	== 記事 ==		== 記事 ==
			This section is '''informative'''.

	Articles and <span id="Blog_Posts">blog posts</span> discussing the value class pattern, most recent first.		Articles and <span id="Blog_Posts">blog posts</span> discussing the value class pattern, most recent first.
	When this section gets too big, create a separate page like: [[value-class-pattern-articles]]		When this section gets too big, create a separate page like: [[value-class-pattern-articles]]
Line 445:		Line 446:
	* <span class="hentry"><span class="published">2009-05-12</span> <span class="entry-title">notizblog.org: [http://notizblog.org/2009/05/12/microformats-value-class-pattern/ Microformats: Value Class Pattern]</span> by <span class="author vcard"><span class="fn">Matthias Pfefferle</span></span></span> (german)		* <span class="hentry"><span class="published">2009-05-12</span> <span class="entry-title">notizblog.org: [http://notizblog.org/2009/05/12/microformats-value-class-pattern/ Microformats: Value Class Pattern]</span> by <span class="author vcard"><span class="fn">Matthias Pfefferle</span></span></span> (german)
	* [http://microformats.org/blog/2009/05/12/value-class-pattern/ 2009-05-12 microformats.org: Value Class Pattern]		* [http://microformats.org/blog/2009/05/12/value-class-pattern/ 2009-05-12 microformats.org: Value Class Pattern]

			== 参照 ==
			This section is '''informative'''.
			* [http://www.useit.com/alertbox/9608.html Jakob Nielsen: International Web Usability]

	== 関連ページ ==		== 関連ページ ==
Line 454:		Line 459:
	* [[value-excerption-pattern-brainstorming]]		* [[value-excerption-pattern-brainstorming]]
	* [[machine-data\|Machine Data in Microformats]]		* [[machine-data\|Machine Data in Microformats]]

			== 翻訳 ==
			Read the value-class-pattern specification in additional <span id="languages">languages</span>:
			* [[value-class-pattern\|english]]
			* [[value-class-pattern-fr\|français]]

KitaitiMakoto: sync: english: 2011-03-22T01:32:18

2011-03-22T14:43:14Z

sync: english: 2011-03-22T01:32:18

← Older revision		Revision as of 14:43, 22 March 2011
Line 1:		Line 1:
	<entry-title>Value Class Pattern</entry-title>		<entry-title>Value Class Pattern</entry-title>
	<!-- english: 2011-02-~~26T01~~:24:55 -->		<!-- english: 2011-03-22T01:32:18 -->

	value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。		value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。
Line 440:		Line 440:
	When this section gets too big, create a separate page like: [[value-class-pattern-articles]]		When this section gets too big, create a separate page like: [[value-class-pattern-articles]]
	* <span class="hentry"><span class="published">2009-08-25</span> <span class="entry-summary">MIX Online: <span class="entry-title">[http://visitmix.com/Articles/The-Value-Class-Pattern The Value Class Pattern]</span></span> by <span class="author vcard"><span class="fn">Jeremy Keith</span></span></span>		* <span class="hentry"><span class="published">2009-08-25</span> <span class="entry-summary">MIX Online: <span class="entry-title">[http://visitmix.com/Articles/The-Value-Class-Pattern The Value Class Pattern]</span></span> by <span class="author vcard"><span class="fn">Jeremy Keith</span></span></span>
	* [http://ablognotlimited.com/s/~~106~~ Getting Semantic With Microformats, Part 8: Value Class Pattern] -- A very thorough writeup by Emily Lewis on the value class pattern		* [http://ablognotlimited.com/articles/getting-semantic-with-microformats-part-8-value-class-pattern Getting Semantic With Microformats, Part 8: Value Class Pattern] -- A very thorough writeup by Emily Lewis on the value class pattern
	* [http://adactio.com/journal/1579/ 2009-05-17 Adactio: Microformation]		* [http://adactio.com/journal/1579/ 2009-05-17 Adactio: Microformation]
	* [http://forabeautifulweb.com/blog/about/value_class_pattern/ For A Beautiful Web: Value Class Pattern]		* [http://forabeautifulweb.com/blog/about/value_class_pattern/ For A Beautiful Web: Value Class Pattern]

KitaitiMakoto: sync: english: 2011-02-26T01:24:55

2011-03-02T17:07:02Z

sync: english: 2011-02-26T01:24:55

← Older revision		Revision as of 17:07, 2 March 2011
Line 1:		Line 1:
	<entry-title>Value Class Pattern</entry-title>		<entry-title>Value Class Pattern</entry-title>
	<!-- english: ~~2010~~-04-~~13T04~~:04:57 -->		<!-- english: 2011-02-26T01:24:55 -->

	value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。		value class パターンは hCard の「[[hcard-ja#値の抜粋\|値の抜粋]]」から派生しています。
Line 433:		Line 433:
	* [[Operator]] has some implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.		* [[Operator]] has some implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.
	* [[Optimus]] v0.8 and later implements <code>value-title</code> as [http://twitter.com/DmitryBaranovsk/status/1891253248 announced by Dmitry Baranovskiy].		* [[Optimus]] v0.8 and later implements <code>value-title</code> as [http://twitter.com/DmitryBaranovsk/status/1891253248 announced by Dmitry Baranovskiy].
			* HTML::Microformats and its predecessors support <code>value</code> excerpting. HTML::Microformats (though not its predecessors) supports <code>value-title</code>.
	=== 公開用ツール ===		=== 公開用ツール ===
	* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]		* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]

KitaitiMakoto: unified the translation of 'parse'

2011-02-23T12:46:59Z

unified the translation of 'parse'

← Older revision		Revision as of 12:46, 23 February 2011
Line 424:		Line 424:

	-->		-->
	=== ~~購読と解析用ツール~~ ===		=== 購読とパース用ツール ===
	* [[Google]] parses <code>value-title</code> as part of their [http://googlewebmastercentral.blogspot.com/2010/01/introducing-new-rich-snippets-format.html support for hCalendar rich snippets], as documented specifically in the [https://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=164506 microformats example for rich snippet events].		* [[Google]] parses <code>value-title</code> as part of their [http://googlewebmastercentral.blogspot.com/2010/01/introducing-new-rich-snippets-format.html support for hCalendar rich snippets], as documented specifically in the [https://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=164506 microformats example for rich snippet events].
	* [[Oomph]] Version 2 passes [[value-class-pattern-tests#Date_and_time_values\|Date and time values test cases]] and is a thorough implementation of the value class pattern.		* [[Oomph]] Version 2 passes [[value-class-pattern-tests#Date_and_time_values\|Date and time values test cases]] and is a thorough implementation of the value class pattern.

KitaitiMakoto: sync: english: 2011-02-22T05:24:46

2011-02-23T12:42:00Z

sync: english: 2011-02-22T05:24:46

← Older revision		Revision as of 12:42, 23 February 2011
Line 382:		Line 382:

	<div class='discussion'>		<div class='discussion'>
			* '''Is the value-class pattern supported by any of the microformats tools?'''
			** '''A: Yes'''. See the [[value-class-pattern#Implementations\|implementations]] section.
	* '''Why use an 'empty' element? Why not embed data in the class attribute?'''		* '''Why use an 'empty' element? Why not embed data in the class attribute?'''
	** The class attribute is inappropriate for embedded data values, as per the HTML4 specification, which states <code>class</code> is for ‘general purposing processing’, which is defined as ‘e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.’. ‘General purpose processing’ does not extend to data itself. Furthermore, this method avoids inventing a new string pattern for embedding data.		** '''A: 'class' is for field names, not data.''' The class attribute is inappropriate for embedded data values, as per the HTML4 specification, which states <code>class</code> is for ‘general purposing processing’, which is defined as ‘e.g. for identifying fields when extracting data from HTML pages into a database, translating HTML documents into other formats, etc.’. ‘General purpose processing’ does not extend to data itself. Furthermore, this method avoids inventing a new string pattern for embedding data.
	* '''Why use an 'empty' element? Why not make up a new attribute, like ‘data’?'''		* '''Why use an 'empty' element? Why not make up a new attribute, like ‘data’?'''
	** Microformats exist and function in ''valid'' ~~HTML4 and XHTML1~~. Those are the current standards for web development, and microformats exist for use ''now''. In the future, perhaps revisions of HTML will offer up another solution. For now, this method has been tested against browsers, and creates a consistent document structure (where machine-form and human-form data are siblings).		** '''A: New attributes are invalid.''' Microformats exist and function in ''valid'' HTML. Those are the current standards for web development, and microformats exist for use ''now''. In the future, perhaps revisions of HTML will offer up another solution. For now, this method has been tested against browsers, and creates a consistent document structure (where machine-form and human-form data are siblings).
	* '''~~The~~ <code>title</code> attribute should only be used for content!'''		* '''Shouldn't the <code>title</code> attribute should only be used for content?'''
	** The <code>title</code> attribute "is" used for content and is read by microformats parsers. This exists for cases where data cannot be parsed with sufficient precision from just the commonly published, visible information. This pattern allows both forms of content to be included, whilst keeping it invisible to human consumers.		** '''A: 'title' is used for content, machine readable content.''' The <code>title</code> attribute "is" used for content and is read by microformats parsers. This exists for cases where data cannot be parsed with sufficient precision from just the commonly published, visible information. This pattern allows both forms of content to be included, whilst keeping it invisible to human consumers.
	</div>		</div>

Line 422:		Line 424:

	-->		-->
	* [http://~~getk2~~.com/ ~~K2] (WordPress Theme) is using "value~~-~~title"~~ for the ~~hAtom published property.~~ [~~http~~://~~code~~.google.com/p/~~kaytwo~~/~~issues~~/~~detail~~?id=~~832~~]		=== 購読と解析用ツール ===
			* [[Google]] parses <code>value-title</code> as part of their [http://googlewebmastercentral.blogspot.com/2010/01/introducing-new-rich-snippets-format.html support for hCalendar rich snippets], as documented specifically in the [https://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=164506 microformats example for rich snippet events].
	* [[Oomph]] Version 2 passes [[value-class-pattern-tests#Date_and_time_values\|Date and time values test cases]] and is a thorough implementation of the value class pattern.		* [[Oomph]] Version 2 passes [[value-class-pattern-tests#Date_and_time_values\|Date and time values test cases]] and is a thorough implementation of the value class pattern.
	* [[X2V]] v0.9.3 and later:		* [[X2V]] v0.9.3 and later:
Line 430:		Line 433:
	* [[Operator]] has some implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.		* [[Operator]] has some implementation of the value-class-pattern according to Michael Kaply, but precisely how much is implemented, for which properties (property types) and which microformats is not currently known.
	* [[Optimus]] v0.8 and later implements <code>value-title</code> as [http://twitter.com/DmitryBaranovsk/status/1891253248 announced by Dmitry Baranovskiy].		* [[Optimus]] v0.8 and later implements <code>value-title</code> as [http://twitter.com/DmitryBaranovsk/status/1891253248 announced by Dmitry Baranovskiy].
	* .~~.. add your implementation~~(s) ~~that parse or generate the~~ value-~~class-pattern here, along with which features you support (hopefully all!) and note any limitations if any~~.		=== 公開用ツール ===
			* [http://getk2.com/ K2] (WordPress Theme) is using "value-title" for the hAtom published property. [http://code.google.com/p/kaytwo/issues/detail?id=832]
	== 記事 ==		== 記事 ==
	Articles and <span id="Blog_Posts">blog posts</span> discussing the value class pattern, most recent first.		Articles and <span id="Blog_Posts">blog posts</span> discussing the value class pattern, most recent first.

KitaitiMakoto: /* Atom 生成プログラム */ translated

2010-04-23T18:02:04Z

Atom 生成プログラム: translated

← Older revision		Revision as of 18:02, 23 April 2010
Line 267:		Line 267:

	==== Atom 生成プログラム ====		==== Atom 生成プログラム ====
	~~microformats implementations which consume~~ [[hAtom]] ~~and generate~~		[[hAtom]] を読み込んで Atom を生成するマイクロフォーマット実装は更に以下に従わなければなりません（{{must}}）。
	Atom {{must}} ~~in addition:~~		* 日付と日時の値を全て [[RFC3339]] のフォーマットに正規化する
	* ~~normalize all date and datetime values to~~ [[RFC3339]].

	=== 起源とテスト ===		=== 起源とテスト ===

KitaitiMakoto: /* hAtom の updated での日付の推測処理 */ fixed mistranslation

2010-04-23T17:57:28Z

hAtom の updated での日付の推測処理: fixed mistranslation

← Older revision		Revision as of 17:57, 23 April 2010
Line 255:		Line 255:
	</source>		</source>

	記事を書く人にとってもっと簡単にするため、hAtom 処理プログラムは value-class ~~パターンの日付と時刻のルールを使って正しい時を特定できます。そのため、以下のように~~ "updated" span 要素内にある "value" span 要素を不要にできます。		記事を書く人にとってもっと簡単にするため、hAtom 処理プログラムは value-class パターンの日付と時刻のルールを使って正しい時刻を特定できます。そのため、以下のように "updated" span 要素内にある "value" span 要素を不要にできます。

	<source lang=html4strict>		<source lang=html4strict>

KitaitiMakoto: /* hAtom の updated での日付の推測処理 */ translated

2010-04-23T17:55:36Z

hAtom の updated での日付の推測処理: translated

← Older revision		Revision as of 17:55, 23 April 2010
Line 242:		Line 242:

	==== hAtom の updated での日付の推測処理 ====		==== hAtom の updated での日付の推測処理 ====
	~~Similarly, in blog posts that indicate both when they were~~ "~~published~~" ~~and~~ "~~updated~~"~~, the date is usually only displayed once, typically when~~ "~~published~~" ~~(real world examples with URLs would help for thoroughness).~~		ブログの投稿に於いて日付が普通一度だけ、大抵は "投稿日（published）" として表示されて、それで "投稿日（published）" と "更新日（updated）" の両方を示すのと同じです（URL 付きの実例があれば完璧でしょう）。

	~~Thus it would be convenient if we could imply an~~ [[hAtom]] entry "updated" ~~date from its~~ "~~published~~" ~~date when only the time (and optionally timezone) was specified for its~~ "~~updated~~"~~, e.g. for a blog post that was updated the same day:~~		ですから、[[hAtom]] entry で "updated" として時間（と、任意でタイムゾーン）だけが明記されている時にその "updated" の日付を "published" から推測できるとすると便利でしょう。例えば同じ日に更新されたブログ投稿ではこうなります。

	<source lang=html4strict>		<source lang=html4strict>
	<span class="hentry">		<span class="hentry">
	<span class="entry-summary">~~short blog post example~~</span>		<span class="entry-summary">短いブログ投稿の例</span>
	~~was published on~~ <span class="published">		は<span class="published">
	<span class="value">2009-08-01</span> at <span class="value">12:06</span></span>		<span class="value">2009-08-01</span> の <span class="value">12:06</span></span> に投稿されました。
	~~and updated at~~ <span class="updated"><span class="value">12:10</span></span>.		また、<span class="updated"><span class="value">12:10</span></span> に更新されました。
	</span>		</span>
	</source>		</source>

	~~To simplify this further for authors, hAtom processors could treat the specifying of just the time per the~~ value-class~~-pattern date and time value rules, and thus eliminate the need for the~~ "~~value~~" span ~~inside the~~ "~~updated~~" span:		記事を書く人にとってもっと簡単にするため、hAtom 処理プログラムは value-class パターンの日付と時刻のルールを使って正しい時を特定できます。そのため、以下のように "updated" span 要素内にある "value" span 要素を不要にできます。

	<source lang=html4strict>		<source lang=html4strict>
	<span class="hentry">		<span class="hentry">
	<span class="entry-summary">~~short blog post example~~</span>		<span class="entry-summary">短いブログ投稿の例</span>
	~~was published on~~ <span class="published">		は <span class="published">
	<span class="value">2009-08-01</span> at <span class="value">12:06</span></span>		<span class="value">2009-08-01</span> の <span class="value">12:06</span></span>
	~~and updated at~~ <span class="updated">12:10</span>.		また、<span class="updated">12:10</span> に更新されました。
	</span>		</span>
	</source>		</source>