hcard-examples-zh - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:25:50Z

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

← Older revision		Revision as of 16:25, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~hCard 範例~~</entry-title>~~		{{DISPLAYTITLE:hCard 範例}}

	範例 [[hcard-zh\|hCards]].		範例 [[hcard-zh\|hCards]].

Achi: /* 作者 */

2011-04-21T03:07:36Z

作者

← Older revision		Revision as of 03:07, 21 April 2011
Line 6:		Line 6:
	* [http://tantek.com/ Tantek Çelik]		* [http://tantek.com/ Tantek Çelik]
	* Brian Suda		* Brian Suda

			== 譯者 ==
			* [http://job.achi.idv.tw/ ㄚ琪]

	== 啟發性的例子 ==		== 啟發性的例子 ==

Achi: /* Related Pages */

2011-04-21T03:03:10Z

← Older revision		Revision as of 03:03, 21 April 2011
Line 490:		Line 490:
	X2V(2005-12-18)目前不能解析/匯出GEO屬性。		X2V(2005-12-18)目前不能解析/匯出GEO屬性。

	== ~~Related Pages~~ ==		== 相關網頁 ==
	* [[hcard-examples-issues]]		* [[hcard-examples-issues]]
	{{hcard-related-pages}}		{{hcard-related-pages}}

Achi: /* Test Cases */

2011-04-21T03:02:36Z

Test Cases

← Older revision		Revision as of 03:02, 21 April 2011
Line 394:		Line 394:
	見：[[hcard-examples-rfc2426]]		見：[[hcard-examples-rfc2426]]

	== ~~Test Cases~~ ==		== 測試用例 ==

	~~These are~~ [[hcard\|hCard]] ~~examples which have been found to be particularly useful in finding bugs in hCard parsers (e.g. X2V).~~		這是[[hcard\|hCard]]的例子，都被認為是在hCard分析器裡在尋找錯誤時特別有用（例如X2V）。

	=== ~~Problem with BDAY Information~~ ===		=== BDAY資訊的問題 ===

	~~this example:~~		這個例子：

	<pre>		<pre>
Line 412:		Line 412:
	</pre>		</pre>

	~~ought to produce~~ "BDAY:1985-10-27T00:00:00Z" ~~but it produces~~ "BDAY:Birthday October 27\, 1985" [~~in what? this statement appears meaningless~~]~~. interesting is that the apple addressbook is still willing to accept it in this way.~~		應該產生"BDAY:1985-10-27T00:00:00Z"，但是它卻產生"BDAY:Birthday October 27\, 1985" [在哪？這像敘述好像毫無意義]，有趣的是apple的通訊錄還是希望接受這樣的方式。

	* ~~Perhaps caused by an HTML parsing error, as~~ <code><dt></code> ~~and~~ <code><dd></code> ~~are not allowed as children of~~ <code><div></code>.		* 也許造成HTML的解析錯誤，就像<code><dt></code>跟<code><dd></code>不允許作為 <code><div></code>子標籤一樣。

	=== ~~case-INSENSITIVITY of type values~~ ===		=== 型態值不靈敏的例子 ===

	* "home" vs. "Home"		* "home" vs. "Home"

	~~this example works with X2V:~~		這個例子在X2V可以運作：

	<pre>		<pre>
Line 429:		Line 429:
	</pre>		</pre>

	~~this does not, but should. but instead it becomes just TEL without a type in the vcard~~		這不行，但是應該可以吧，它只會變成在vcard裡沒有的型態TEL。

	<pre>		<pre>
Line 438:		Line 438:
	</pre>		</pre>

	=== ~~GEO parsing~~ ===		=== GEO解析 ===
	~~The following hCard:~~		下面的hCard：

	<pre><nowiki>		<pre><nowiki>
Line 472:		Line 472:
	</pre>		</pre>

	~~Should be translated into the following vCard:~~		應該可以轉換為下面的vCard：

	<pre><nowiki>		<pre><nowiki>
Line 488:		Line 488:
	</nowiki></pre>		</nowiki></pre>

	X2V ~~currently~~ (2005-12-18) ~~fails to parse~~/~~export the GEO property at all.~~		X2V(2005-12-18)目前不能解析/匯出GEO屬性。

	== Related Pages ==		== Related Pages ==

Achi: /* RFC 2426 examples in hCard */

2011-04-21T02:40:34Z

RFC 2426 examples in hCard

← Older revision		Revision as of 02:40, 21 April 2011
Line 391:		Line 391:
	</nowiki></pre>		</nowiki></pre>

	== <nowiki>RFC 2426</nowiki> ~~examples in hCard~~ ==		== hCard裡<nowiki>RFC 2426</nowiki>的範例 ==
	~~See:~~ [[hcard-examples-rfc2426]]		見：[[hcard-examples-rfc2426]]

	== Test Cases ==		== Test Cases ==

Achi: /* Lists of Organizations */

2011-04-21T02:39:48Z

Lists of Organizations

← Older revision		Revision as of 02:39, 21 April 2011
Line 352:		Line 352:
	請注意在位址裡的org的巢狀結構，我們要避免有重複的部門名稱。		請注意在位址裡的org的巢狀結構，我們要避免有重複的部門名稱。

	=== ~~Lists of Organizations~~ ===		=== 組織列表 ===
	~~Similar to~~ [[hcard-examples#References_to_People_in_Blogrolls\|lists of people]]~~, lists of organizations (e.g. music bands) should use a list (unordered unless there is a specific reason to order it) with list items and hyperlink to the respective organization home pages.~~		類似[[hcard-examples#References_to_People_in_Blogrolls\|lists of people]]，組織列表（例如樂隊）應該使用一個有列表項目跟超連結到各自的組織首頁的列表（無序的，除非有理由要排序）。

	~~E.g. this simple~~ [[POSH]]:		例如，這個簡單的[[POSH]]：

	<pre><nowiki>		<pre><nowiki>
Line 373:		Line 373:
	</nowiki></pre>		</nowiki></pre>

	~~can be easily enhanced with hCard:~~		可以很容易地使用hCard來加強：

	<pre><nowiki>		<pre><nowiki>

Achi: /* Organizations and Departments */

2011-04-21T02:34:52Z

Organizations and Departments

← Older revision		Revision as of 02:34, 21 April 2011
Line 320:		Line 320:
	這件工作已開發進[[representative-hcard\|representative hCards]]，到那裡有最新這類的思維。		這件工作已開發進[[representative-hcard\|representative hCards]]，到那裡有最新這類的思維。

	=== ~~Organizations and Departments~~ ===		=== 組織跟部門 ===

	~~Departments are marked up using the~~ "organization-unit" ~~class name inside the~~ "org" ~~element, with the~~ "organization-name" ~~specifically marked up to distinguish it from the department:~~		部門使用"organization-unit"類別名稱在"org"元素裡，明確的"organization-name"標記可以與其他部門區隔：

	<pre><nowiki>		<pre><nowiki>
Line 333:		Line 333:
	</nowiki></pre>		</nowiki></pre>

	~~The department may also be part of the address, in which case, you may want to explicitly mark it up as the~~ "~~extended~~-~~address~~" ~~in addition to the~~ "~~organization~~-~~unit~~".		該部門也可以是位址的一部分，在這種情況下，你會想要明確的標記它作為除了"organization-unit"以外的"extended-address"。

	<pre><nowiki>		<pre><nowiki>
Line 350:		Line 350:
	</nowiki></pre>		</nowiki></pre>

	~~Note that by nesting the org inside the address we avoided having to duplicate the department name.~~		請注意在位址裡的org的巢狀結構，我們要避免有重複的部門名稱。

	=== Lists of Organizations ===		=== Lists of Organizations ===

Achi: /* Canonical Profiles on Sites */

2011-04-21T02:27:17Z

Canonical Profiles on Sites

← Older revision		Revision as of 02:27, 21 April 2011
Line 296:		Line 296:
	像這種明確以使用者為導向的身份合併也是建構[[social-network-portability]]區塊的一個關鍵，這會在[[hcard-xfn-supporting-friends-lists]]這節有更多的解釋。		像這種明確以使用者為導向的身份合併也是建構[[social-network-portability]]區塊的一個關鍵，這會在[[hcard-xfn-supporting-friends-lists]]這節有更多的解釋。

	=== ~~Canonical Profiles on Sites~~ ===		=== 典型的網站簡介 ===
	~~Sites sometimes have different pages for the~~ "~~home~~" ~~page for a person, and that person's user profile page.~~		網佔有時後會對一個人有很多不同的頁面作為"首頁"，以及那個人的使用者個人資料頁。

	~~For example Flickr has:~~		舉Flickr的例子：
	* ~~your home page is at a URL like:~~ <code>http://flickr.com/photos/</code> ~~followed by your username, e.g.:~~		* 你的首頁在一個網址像：<code>http://flickr.com/photos/</code>後跟著你的使用者名稱，例如：
	** http://flickr.com/photos/tantek/		** http://flickr.com/photos/tantek/
	* ~~your profile page is at a URL like:~~ <code>http://flickr.com/people/</code> ~~followed by your username, e.g.:~~		* 你的個人資料頁在一個網址像：<code>http://flickr.com/people/</code>後跟著你的使用者名稱，例如：
	** http://flickr.com/people/tantek/		** http://flickr.com/people/tantek/

	~~In addition, sites often have a~~ <em>~~canonical~~</em> ~~URL for a person, and several alternate URLs.~~		此外，網站通常有一個他個人<em>典型</em>的網址及幾個備用網址。

	~~As noted above, links to these URLs inside hCards that represent those people should have classname~~ "url".		如上所述，在hCard裡連到這些網址的連結會表示那些人應該有classname "url"。

	~~In addition, such link(s) in hCards to the canonical URL for a person on that site should also have the classname of~~ "uid"~~. This technique was proposed Ryan King at the first~~ [[events/2007-08-28-social-network-portability-today\|Social Network Portability Today lunchtime meetup]].		此外，在hCard裡站上像這樣的連結到一個人的典型網址應該也有"uid"這個classname，這個技術是Ryan King第一次在[[events/2007-08-28-social-network-portability-today\|Social Network Portability Today lunchtime meetup]]提出。

	~~Building on the example(s) from the previous section:~~		上一節建構的例子：
	* [http://flickr.com Flickr]:		* [http://flickr.com Flickr]:
	** <code><a class="url" href="http://flickr.com/photos/tantek/">See my photos</a></code>		** <code><a class="url" href="http://flickr.com/photos/tantek/">See my photos</a></code>
	** <code><a rel="me" class="url uid" href="http://flickr.com/people/tantek/">Flickr profile</a></code>		** <code><a rel="me" class="url uid" href="http://flickr.com/people/tantek/">Flickr profile</a></code>

	~~Such a~~ "url" + "uid" ~~property could also be used by a site as that person's~~ [[OpenID]] ~~URL.~~		這樣的"url" + "uid"屬性也被網站使用作為個人的[[OpenID]]網址。

	~~This work has been developed into~~ [[representative-hcard\|representative hCards]]~~. Go there for the latest on this line of thinking.~~		這件工作已開發進[[representative-hcard\|representative hCards]]，到那裡有最新這類的思維。

	=== Organizations and Departments ===		=== Organizations and Departments ===

Achi: /* Site profiles */

2011-04-21T02:11:25Z

Site profiles

← Older revision		Revision as of 02:11, 21 April 2011
Line 268:		Line 268:
	將[ICQNUMBER]取代為使用者真正的ICQ號碼。		將[ICQNUMBER]取代為使用者真正的ICQ號碼。

	=== ~~Site profiles~~ ===		=== 網站專頁 ===
	Bloggers often indicate their identity on content hosting services using the URL to their home page, feed or profile on those services. By labeling them as URL properties, these additional facets of identity can be published in an hCard as well.		部落客通常會在內容託管服務上使用網址到他們的首頁、饋送或專頁來顯示他們的身份在這些服務上，他們透過標籤作為URL屬性，這些額外的身份也可以在hCard發佈。

	* <code>[http://del.icio.us delicious]:</code>		* <code>[http://del.icio.us delicious]:</code>
Line 278:		Line 278:
	* <code>[http://technorati.com/ Technorati]:</code>		* <code>[http://technorati.com/ Technorati]:</code>
	** <code><a class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>		** <code><a class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>
	* ~~Add more here~~...		* 在這裡增加更多...
	** ....		** ....

	==== ~~listing your other profiles~~ ====		==== 列出你其他的專頁 ====
	The most common case of sites listing other profiles is a blogger listing their own other profiles, or a site enabling a user to list on his or her profile on that site, links to his or her other profiles. Since clearly the author/~~user is indicating that all those profiles mean the same person, it's best to mark them up with~~ [[XFN]]'s <code>rel="me"</code> ~~for explicit identity consolidation, e.g. if those links were on Tantek's blog or other social network profile:~~		列出其他個人資料的網站最常見的情況是部落客列出自己其他的個人資料，或網站允許使用者列出他在站上的個人資料，連結到其他人的個人資料，使用戶要列出其個人資料在該網站上，鏈接到他或她的其他個人資料，由於很清楚地這個作者/使用者表示所有那些個人資料指德是同一個人，使用[[XFN]]的<code>rel="me"</code>將他們標記起來做明確的身份合併是最好的，例如，在Tantek的部落格或其他社交網路的個人資料的那些連結：

	* <code>[http://del.icio.us delicious]:</code>		* <code>[http://del.icio.us delicious]:</code>
Line 291:		Line 291:
	* <code>[http://technorati.com/ Technorati]:</code>		* <code>[http://technorati.com/ Technorati]:</code>
	** <code>my <a rel="me" class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>		** <code>my <a rel="me" class="url" href="http://technorati.com/profile/tantek/">Technorati profile</a></code>
	* ~~Add more here~~...		* 在這裡增加更多...
	** ....		** ....

	~~Such explicit user-driven identity consolidation is also a key building block for~~ [[social-network-portability]] ~~that is further explained in the context of~~ [[hcard-xfn-supporting-friends-lists]].		像這種明確以使用者為導向的身份合併也是建構[[social-network-portability]]區塊的一個關鍵，這會在[[hcard-xfn-supporting-friends-lists]]這節有更多的解釋。

	=== Canonical Profiles on Sites ===		=== Canonical Profiles on Sites ===

Achi: /* ICQ */

2011-04-21T01:38:34Z

ICQ

← Older revision		Revision as of 01:38, 21 April 2011
Line 255:		Line 255:

	==== ICQ ====		==== ICQ ====
	[http://www.icq.com/ ICQ] ~~does not have a URL scheme. Rather ICQ links on the web use HTTP hyperlinks to download a resource of content-type~~ <code>application/x-icq</code> ~~which then the operating system opens with the user's ICQ client.~~		[http://www.icq.com/ ICQ]沒有URL的結構，反而在web上ICQ的連結使用HTTP超連結來下載一種內容類型<code>application/x-icq</code>的資源，之後作業系統接著就會打開使用者的ICQ客戶端。

	~~Thus we can markup those HTTP hyperlinks with the content-type set explicitly to communicate the ICQ semantic:~~		因此我們可以標記那些有內容類型的HTTP超連結明確地設定來跟ICQ語義溝通：

	<pre><nowiki>		<pre><nowiki>
Line 266:		Line 266:
	</nowiki></pre>		</nowiki></pre>

	~~Replacing~~ [ICQNUMBER] ~~with the user's actual ICQ number.~~		將[ICQNUMBER]取代為使用者真正的ICQ號碼。

	=== Site profiles ===		=== Site profiles ===