您的足迹:
差别
这里会显示出您选择的修订版和当前版本之间的差别。
两侧同时换到之前的修订记录 前一修订版 后一修订版 | 前一修订版 | ||
h-card [2018/05/21 11:10] eureka |
h-card [2018/05/21 14:19] eureka [属性] |
||
---|---|---|---|
行 1: | 行 1: | ||
- | ====== h-card ====== | + | ===== h-card ===== |
**h-card** 是用来在WEB上发布人或组织的简单,开放格式。h-card是几个 [[microformats|microformat]] 标准草案中的一个,适合于在HTML中内嵌数据。 | **h-card** 是用来在WEB上发布人或组织的简单,开放格式。h-card是几个 [[microformats|microformat]] 标准草案中的一个,适合于在HTML中内嵌数据。 | ||
行 6: | 行 6: | ||
按照[[http://creativecommons.org/publicdomain/zero/1.0/|CC0创作共用协议]],为在法律上扩展允许范围,编辑放弃了该工作的所有的版权和相关邻权。此外,在2018年5月20日,编辑将该规范置于[[http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0|开放网络基础协议版本1.0]]之下。 | 按照[[http://creativecommons.org/publicdomain/zero/1.0/|CC0创作共用协议]],为在法律上扩展允许范围,编辑放弃了该工作的所有的版权和相关邻权。此外,在2018年5月20日,编辑将该规范置于[[http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0|开放网络基础协议版本1.0]]之下。 | ||
- | == 例子 == | + | ==== 例子 ==== |
这是一个简单的最小的关于一个人的例子: | 这是一个简单的最小的关于一个人的例子: | ||
行 117: | 行 117: | ||
注: 嵌套 h-card 有隐含的 'name' 和 'url' 属性,就象其它在''%%<a href>%%''上的仅根类名(root-class-name-only)h-card那样。 | 注: 嵌套 h-card 有隐含的 'name' 和 'url' 属性,就象其它在''%%<a href>%%''上的仅根类名(root-class-name-only)h-card那样。 | ||
- | === 开始d === | + | === 开始 === |
类 ''h-card'' 是表示存在一个h-card的 //根类名// 。 | 类 ''h-card'' 是表示存在一个h-card的 //根类名// 。 | ||
行 126: | 行 126: | ||
了解更多的属性类名请参见 [[microformats2-parsing]] 。. | 了解更多的属性类名请参见 [[microformats2-parsing]] 。. | ||
- | === 属性 === | + | ==== 属性 ==== |
在类**h-card**中的h-card属性: | 在类**h-card**中的h-card属性: | ||
* ''p-name'' - 一个人或组织的全/格式化名字 | * ''p-name'' - 一个人或组织的全/格式化名字 | ||
* ''p-honorific-prefix'' - 例如 Mrs., Mr. or Dr. | * ''p-honorific-prefix'' - 例如 Mrs., Mr. or Dr. | ||
- | * ''<code>p-given-name</code>'' - 给定 (经常为第一) 名 | + | * ''p-given-name'' - 给定 (经常为第一) 名,中文的名字 |
- | * ''<code>p-additional-name</code>'' - 其它/中间名 | + | * ''p-additional-name'' - 其它/中间名 |
- | * '''<code>p-family-name</code>''' - 家庭名 (经常为最后) 名 | + | * ''p-family-name'' - 家庭名 (经常为最后) 名,中文的姓 |
- | * '''<code>p-sort-string</code>''' - string to sort by | + | * ''p-sort-string'' - 排序字串 |
- | * '''<code>p-honorific-suffix</code>''' - e.g. Ph.D, Esq. | + | * ''p-honorific-suffix</code>''' - e.g. Ph.D, Esq. |
- | * '''<code>p-nickname</code>''' - nickname/alias/handle | + | * ''p-nickname'' - 昵称/别名/操控名 |
- | * '''<code>u-email</code>''' - email address | + | * ''u-email'' - 电子邮件地址 |
- | * '''<code>u-logo</code>''' - a logo representing the person or organisation | + | * ''u-logo'' - 一个代表一个人或组织的图标。 |
- | * '''<code>u-photo</code>''' | + | * ''u-photo'' |
- | * '''<code>u-url</code>''' - home page | + | * ''u-url'' - 主页 |
- | * '''<code>u-uid</code>''' - universally unique identifier, typically canonical URL | + | * ''u-uid'' - 通用唯一识别码,典型的权威URL |
- | * '''<code>p-category</code>''' - category/tag | + | * ''p-category'' - 类别/标签 |
- | * '''<code>p-adr</code>''' - postal address, optionally embed an [[h-adr]] {{main|h-adr}} | + | * ''p-adr'' - 邮政地址,可选 嵌入一个 [[h-adr]] |
- | * '''<code>p-post-office-box</code>''' | + | * ''p-post-office-box'' |
- | * '''<code>p-extended-address</code>''' - apartment/suite/room name/number if any | + | * ''p-extended-address'' - 部门/随员/房间名/号如果有 |
- | * '''<code>p-street-address</code>''' - street number + name | + | * ''p-street-address'' - 街道号 + 名称 |
- | * '''<code>p-locality</code>''' - city/town/village | + | * ''p-locality'' - 城市/城镇/乡村 |
- | * '''<code>p-region</code>''' - state/county/province | + | * ''p-region'' - 州/县郡/省 |
- | * '''<code>p-postal-code</code>''' - postal code, e.g. US ZIP | + | * ''p-postal-code'' - 邮政编码, 例如 US ZIP |
- | * '''<code>p-country-name</code>''' - country name | + | * ''p-country-name'' - 国家名 |
- | * '''<code>p-label</code>''' | + | * ''p-label'' |
- | * '''<code>p-geo</code>''' or '''<code>u-geo</code>''', optionally embed an [[h-geo]] {{main|h-geo}} | + | * ''p-geo'' 或 '''u-geo'', 可选的嵌入一个 [[h-geo]] |
- | * '''<code>p-latitude</code>''' - decimal latitude | + | * ''p-latitude'' - 十进制纬度 |
- | * '''<code>p-longitude</code>''' - decimal longitude | + | * ''p-longitude'' - 十进制经度 |
- | * '''<code>p-altitude</code>''' - decimal altitude | + | * ''p-altitude'' - 十进制海拨高度 |
- | * '''<code>p-tel</code>''' - telephone number | + | * ''p-tel'' - 电话号码 |
- | * '''<code>p-note</code>''' - additional notes | + | * ''p-note'' - 附加注释 |
- | * '''<code>dt-bday</code>''' - birth date | + | * ''dt-bday'' - 生日 |
- | * '''<code>u-key</code>''' - cryptographic public key e.g. SSH or GPG | + | * ''u-key'' - 密码公钥,例如 SSH 或 GPG |
- | * '''<code>p-org</code>''' - affiliated organization, optionally embed an [[h-card]] | + | * ''p-org'' - 隶属组织,可选嵌入一个 [[h-card]] |
- | * '''<code>p-job-title</code>''' - job title, previously 'title' in [[hCard]], disambiguated. | + | * ''p-job-title'' - 工作头衔, 以前在[[hCard]]中的title,消除歧义。 |
- | * '''<code>p-role</code>''' - description of role | + | * ''p-role'' - 角色描述 |
- | * '''<code>u-impp</code>''' per RFC4770, new in vCard4 (RFC 6350) | + | * ''u-impp'' 按照 RFC4770, 新的在 vCard4 (RFC 6350) |
- | * '''<code>p-sex</code>''' - biological sex, new in vCard4 (RFC 6350) | + | * ''p-sex'' - 生物学性,新的在vCard4 (RFC 6350) |
- | * '''<code>p-gender-identity</code>''' - gender identity, new in vCard4 (RFC 6350) | + | * ''p-gender-identity'' - 性别身份,新的在 vCard4 (RFC 6350) |
- | * '''<code>dt-anniversary</code>''' | + | * ''dt-anniversary'' |
- | All properties are optional. | + | 所有的属性都是可选的。 |
- | Experimental properties currently in use in the wild but not (yet) part of the official h-card spec. | + | 当前在外面使用的实验性的属性,但还(没有)成为官方h-card规范的一部分。 |
- | * '''<code>u-sound</code>''' - sound file containing the proper pronunciation of the name property, per vCard (RFC 6350). | + | * ''u-sound'' - 名字(name)属性的恰当发音的声音文件。按照 vCard (RFC 6350). |
- | ** Used by [https://vanderven.se/martijn/ Martijn van der Ven] with a clip of his given name. | + | * 由 [[https://vanderven.se/martijn/|Martijn van der Ven]] 使用,带有它给定名的剪片。 |
- | == Status == | + | ==== 状态 ==== |
- | '''h-card''' is a microformats.org draft specification. Public discussion on h-card takes place on [[h-card-feedback]] and the #microformats [[irc]] channel on irc.freenode.net. | + | **h-card** 是microformats.org的草案规范。在 [[h-card-feedback]] 和irc.freenode.net上的#microformats [[irc]] 频道上可以公开讨论。 |
- | h-card is ready to use and implemented in the wild, but for backwards compatibility you should also mark up top-level h-cards as classic [[hCard]]s. | + | h-card 已经准备好在自然环境下使用和实施,但为了向后兼容,你应该将顶级h-cards 作为经典 [[hCard]]标记。 |
- | == Property Details == | + | ==== 属性细节 ==== |
- | (stub, to be expanded) | + | (留位,等待扩展) |
=== p-adr === | === p-adr === | ||
- | <code>p-adr</code> can optionally embed an [[h-adr]] to cluster associated structured address properties. E.g. adding "p-adr" to the example earlier: | + | p-adr 是可选的内嵌一个 [[h-adr]] 到簇关联结构化地址属性。 例如添加 "p-adr" 到前面的例子: |
- | <source lang=html4strict> | + | <code html4strict> |
<div class="h-card"> | <div class="h-card"> | ||
<p class="p-name">Joe Bloggs</p> | <p class="p-name">Joe Bloggs</p> | ||
行 195: | 行 195: | ||
</p> | </p> | ||
</div> | </div> | ||
- | </source> | + | </code> |
- | Q: Why would you use "p-adr" to cluster associated structured address properties? | + | 问:为什么要使用“p-adr”来聚集相关的结构化地址属性? |
- | A: Because if you have more than one structured address, clustering which properties go with which address keeps them deterministically together, instead of depending on array indices or other heuristics. | + | 答:因为如果你有多个结构化地址,聚簇哪些属性与哪个地址一起可以确定它们能保持在一起,而不是依赖于数组索引或其他启发式。 |
=== p-tel === | === p-tel === | ||
- | Note: use of 'value' within 'p-tel' should be automatically handled by the support of the [[value-class-pattern]]. And for now, the former [[hCard]] 'type' subproperty of 'tel' is dropped/ignored. If there is demonstrable documented need for additional tel types (e.g. fax), we can introduce new flat properties as needed (e.g. p-tel-fax). | + | 注意:'p-tel'中'value'的使用应该由[[value-class-pattern|值类模式]]的支持自动处理。 目前,以前[[hCard]]的'tel'子属性'type'丢弃/忽略。 如果有证据显示需要额外的电话类型(例如传真),我们可以根据需要引入新的直接属性(例如p-tel-fax)。 |
=== dt-bday === | === dt-bday === | ||
- | Using truncated representations of dates for birth date is often good practice as noted in [https://tools.ietf.org/html/rfc6350#section-4.3.1 the vcard spec] eg | + | 使用截短的出生日期表示法通常是很好的做法,如[[https://tools.ietf.org/html/rfc6350#section-4.3.1|the vcard规范]]中所述 |
- | * <code>1985-04</code> for April 1985 | + | * ''1985-04'' 代表1985年4月 |
- | * <code>1985</code> for the year 1985 | + | * ''1985'' 代表年份1985 |
- | * <code>--04-12</code> for April 12th with no specified year | + | * ''--04-12'' 代表没有批定年份的的4月12日 |
- | === Reserved properties === | + | === 保留属性 === |
- | Reserved properties (not used much, if at all, in practice): | + | 保留属性(如果有的话,在实践中用处不大): |
- | * '''<code>p-organization-name</code>''' | + | * ''p-organization-name'' |
- | * '''<code>p-organization-unit</code>''' | + | * ''p-organization-unit'' |
- | * '''<code>p-tz</code>''' - timezone offset, e.g. <code><data class="p-tz" value="-0800">PST</data></code> | + | * ''p-tz'' - 时区偏离例如 ''<data class="p-tz" value="-0800">PST</data>'' |
- | * '''<code>dt-rev</code>''' | + | * ''dt-rev'' |
- | == Examples in the wild == | + | ==== 在自然中的例子 ==== |
- | Real world in the wild examples of sites and services that publish or consume h-card: | + | 现实世界中发布或使用h-card的网站和服务的范例: |
- | * ... add uses of h-card you see in the wild here. | + | * ... 将在自然你看到使用h-card放天这里。 |
- | * [http://www.securityjobslondon.co.uk Security Jobs London] uses h-card with legacy [[hCard]] fallback markup (to satisfy [https://search.google.com/structured-data/testing-tool Google's Structured Data Testing Tool]) in the footer of each page | + | * [[https://eureka.name|Eureka Chen]]陈耀军的主页使用 h-card 标记个人信息。 |
- | * App.net rolled out support for h-card and h-entry on all profile pages and permalink pages as of 2013-08-06 ([https://alpha.app.net/voidfiles example]) | + | * [[http://www.securityjobslondon.co.uk|Security Jobs London]] 在每页的页脚使用 h-card 和传统 [[hCard]] 回退标记 (为满足 [[https://search.google.com/structured-data/testing-tool|Google结构化数据测试工具]]) |
- | * Brett Comnes marks up his posts with h-card ([http://bret.io/2013/06/29/getting-started-with-bower/ example]) | + | * 截至2013年8月6日,App.net在所有个人资料页面和永久链接页面上推出了对h-card和h-entry的支持(示例) ([[https://alpha.app.net/voidfiles | 示例]]) |
- | * Ben Werdmuller marks up his homepage and posts with h-card [http://werd.io/view/51d5097fbed7ded0633a5956 example]) | + | * Brett Comnes 用h-card标记他的贴子 ([[http://bret.io/2013/06/29/getting-started-with-bower/|示例]]) |
- | * [https://joelpurra.com/ Joel Purra] uses a hidden h-card with legacy [[hCard]] fallback markup (to satisfy [https://search.google.com/structured-data/testing-tool Google's Structured Data Testing Tool]) on the front page | + | * Ben Werdmuller 用h-card标记他的主页和帖子 [[http://werd.io/view/51d5097fbed7ded0633a5956|示例]]) |
- | * Sandeep Shetty marks his homepage and posts up with h-card and h-entry ([sandeep.io/101 example]) | + | * [[http://www.w3.org/conf/|W3Conf 2013] 为所有的演讲嘉宾和着名的与会者使用了h-card。 h-cards特别适用于隐含的名称,网址和照片属性。 |
- | * [http://eschnou.com/ Laurent Eschenauer] marks his homepage profile up using h-card | + | * [[http://wordpress.org/extend/themes/sempress|SemPress]]是WordPress主题支持 h-card, h-feed/h-entry 和 h-as-* |
- | * [http://tommorris.org/ Tom Morris] marks himself up with h-card as well as venues he’s checked into ([http://tommorris.org/posts/8408 example]) | + | * [[http://the-pastry-box-project.net/|The Pastry Box Project]] 他们的主页和个人想法页面上使用h-card标记 |
- | * [http://www.w3.org/conf/ W3Conf 2013] uses h-card for all the event speakers and notable attendees. The h-cards make particularly good use of implied name, url, and photo properties. | + | * Mozilla的WebFWD 在 [[https://webfwd.org/about/experts/|专家] 和 [[https://webfwd.org/about/team/|l团队]] 页上使用 h-card 格式。 |
- | * [http://wordpress.org/extend/themes/sempress SemPress] is a WordPress theme that supports h-card, h-feed/h-entry and h-as-* | + | * [[http://indiewebcamp.com|IndieWebCamp]] 给它的组织和地埋位置有 [[microformats2]] h-event 标记内嵌h-card。 |
- | * [http://the-pastry-box-project.net/ The Pastry Box Project] use h-card markup on their homepage and individual thoughts pages | + | * [https://wiki.mozilla.org/Events|Mozilla Events] 页有 [[microformats2]] h-event标记,出席者使用h-card作标记。 |
- | * Tom Morris uses h-card and [[XFN]] to markup [http://tommorris.org/pages/blogroll his blogroll]. | + | |
- | * Aaron Parecki uses h-card to markup both authorship and references to people in his notes permalinks, e.g. [http://aaronparecki.com/2012/230/reply/1 2012/230/reply/1]. | + | |
- | * [http://tantek.com/ Tantek Çelik] uses h-card on his home page as well as within [[h-entry]]s on permalink pages to indicate authorship. | + | |
- | * [http://waterpigs.co.uk/ Barnaby Walters] uses h-card on his home page, as well as within h-entries for notes and articles, both to indicate authorship and also when mentioning people within the body of the notes. | + | |
- | * [http://tantek.com/presentations/2012/06/microformats microformats.org at 7 years] presentation with and h-card markup for people and organizations. | + | |
- | * [http://tantek.com/presentations/2012/06/pdf2012-indieweb.html Rise of the Indie Web hCards] (from Personal Democracy Forum 2012 #pdf12 #pdf2012) has [[microformats2]] h-card markup | + | |
- | * WebMaker by Mozilla has [[microformats2]] h-card on event search (e.g. [https://webmaker.org/en-US/events/near/?lat=45.5234515&lng=-122.6762071 search near Portland Oregon]) and event pages (e.g. [https://webmaker.org/en-US/events/192f56eb9/ IndieWebCamp 2012]).[https://twitter.com/microformats/status/212207925643587585] | + | |
- | * WebFWD by Mozilla has [[microformats2]] h-card markup on [https://webfwd.org/about/experts/ experts] and [https://webfwd.org/about/team/ team] pages | + | |
- | * [http://indiewebcamp.com IndieWebCamp] has [[microformats2]] h-event markup with embedded h-cards for the organizers and the location. | + | |
- | * [https://wiki.mozilla.org/Events Mozilla Events] page has [[microformats2]] h-event markup with attendees marked up with h-card. | + | |
- | * [https://tristanthomas.me Tristan Thomas] uses h-card on his home page | + | |
- | * [http://cold32.com/about-the-author-and-contact.htm Cold32.com] uses h-card (and h-geo) on its about-the-author-and-contact page | + | |
- | * [https://workfrom.co/ Workfrom.co] renders h-cards for venues (e.g. [https://workfrom.co/palio-dessert-and-espresso-house]) | + | |
- | * [http://www.pcwdld.com/ PCWDLD.com] renders h-cards for download pages(e.g. [http://www.pcwdld.com/solarwinds-network-topology-mapper-review Download page example]) | + | |
- | === offline === | + | === 离线 === |
- | * spreadly marks up share permalink pages with minimal h-cards inside h-entry | + | * spreadly marks up share permalink pages with minimal h-cards inside h-entry |
- | == Validating == | + | === 验证 === |
- | * '''[http://indiewebify.me/validate-h-card/ indiewebify.me h-card validator]''' parses [[h-card]] markup and makes suggestions for things to add, with code samples | + | * **[[http://indiewebify.me/validate-h-card/ indiewebify.me h-card validator]]** 解析 [[h-card]] 标记,用代码例子建议添加的东西。[[validators]] |
- | {{h-spec-section-validating}} | + | |
- | == Implementations == | + | 测试和验证[[microformats2]]标记一般有: |
- | Software implementations that publish or consume h-card, including themes, plugins, or extensions: | + | * http://waterpigs.co.uk/php-mf2/ - 直接输入标记 |
+ | * http://pin13.net/ - 输到到页面的URL测试哪里说的“微格式解析器” | ||
- | (This section is a stub that needs expansion! In practice, nearly every CMS on every [https://indieweb.org/ indie web] site supports publishing h-card by default.) | + | === 实现 === |
+ | 发布或使用h-card的软件实现,包括主题,插件或扩展: | ||
- | When adding an implementation, please provide and link to its home page and open source repo if any. | + | (这部分预留,需要扩展!实际上,默认情况下,每个[[https://indieweb.org/|独立网站]]上的几乎每个CMS都支持发布h-card。) |
- | * [https://gnu.io/social/ GNUsocial] [https://git.gnu.io/gnu/gnu-social/ source code] | + | |
- | * [https://hubzilla.org/hubzilla/ Hubzilla] [https://github.org/redmatrix/hubzilla source code] | + | 在添加实现时,请提供并链接到其主页和开放源代码库(如果有的话)。 |
- | * [http://friendica.com/ Friendica] [https://github.org/friendica/friendica source code] | + | * [[https://gnu.io/social/|GNUsocial]] [[https://git.gnu.io/gnu/gnu-social/|源代码]] |
- | * [http://github.com/dissolve/inkblot InkBlot] | + | * [[https://hubzilla.org/hubzilla/|Hubzilla]] [https://github.org/redmatrix/hubzilla|源代码]] |
+ | * [[http://friendica.com/|Friendica]] [https://github.org/friendica/friendica|源代码]] | ||
+ | * [[http://github.com/dissolve/inkblot|InkBlot]] | ||
* ... | * ... | ||
* ... | * ... | ||
- | == Backward Compatibility == | + | ==== 向后兼容性 ==== |
- | === Publisher Compatibility === | + | === 发布商兼容性 === |
- | For backward compatibility, you may wish to use classic [[hCard]] classnames in addition to the more future-proof h-card properties, for example: | + | 为了向后兼容,除了更具前瞻性的h-card属性之外,您还可能希望使用经典的hCard 类名,例如: |
- | <source lang=html4strict> | + | <code html4strict> |
<p class="h-card vcard"> | <p class="h-card vcard"> | ||
<span class="p-name fn">Joe Bloggs</span>, | <span class="p-name fn">Joe Bloggs</span>, | ||
行 278: | 行 267: | ||
... | ... | ||
</p> | </p> | ||
- | </source> | + | </code> |
- | The class '''<code>vcard</code>''' is a ''backward compatible root class name'' that indicates the presence of an [[hCard]]. | + | 类''vcard''是一个向后兼容的根类名称,表示存在一个 [[hCard]]. |
- | '''fn''', '''org''', and all the other backward compatibility hCard property class names are listed below. | + | **fn**,**org**,以及其它向后兼容的hCard属性类名称列在下面。 |
- | === Parser Compatibility === | + | === 解析器兼容性 === |
- | Microformats parsers {{should}} detect classic properties only if a classic root class name is found and parse them as microformats2 properties. | + | 只有找到经典的根类名称并将它们解析为microformats2属性时,微格式解析器才//应//检测经典属性 |
- | If an "h-card" is found, don't look for a "vcard" on the same element. | + | 如果发现 "h-card" ,不用在同一元素中寻找 "vcard" 。 |
- | Compat. root class name: <code id="vcard">vcard</code><br/> | + | Compat. 根类名: ''vcard'' \\ |
- | Properties: (parsed as '''p-''' plain text unless otherwise specified) | + | 属性: (除非令外指定,解析 **p-** 纯文本) |
- | * <code>fn</code> - parse as '''<code>p-name</code>''' | + | * ''fn'' - 解析作 ''p-name'' |
- | * <code>honorific-prefix</code> | + | * ''honorific-prefix'' |
- | * <code>given-name</code> | + | * ''given-name'' |
- | * <code>additional-name</code> | + | * ''additional-name'' |
- | * <code>family-name</code> | + | * ''family-name'' |
- | * <code>honorific-suffix</code> | + | * ''honorific-suffix'' |
- | * <code>nickname</code> | + | * ''nickname'' |
- | * <code>email</code> - parse as '''u-''' | + | * ''email'' - 解析作 ''u-'' |
- | * <code>logo</code> - parse as '''u-''' | + | * ''logo'' - 解析作 ''u-'' |
- | * <code>photo</code> - parse as '''u-''' | + | * ''photo'' - 解析作 ''u-'' |
- | * <code>url</code> - parse as '''u-''' | + | * ''url'' - 解析作 ''u-'' |
- | * <code>uid</code> - parse as '''u-''' | + | * ''uid'' - 解析作 ''u-'' |
- | * <code>category</code> | + | * ''category'' |
- | * <code>adr</code> - parse as '''<code>p-adr h-adr</code>''' including compat root class <code>adr</code> | + | * ''adr'' - 解析作 ''p-adr h-adr'' 包括compat要类''adr'' |
- | * <code>extended-address</code> | + | * ''extended-address'' |
- | * <code>street-address</code> | + | * ''street-address'' |
- | * <code>locality</code> | + | * ''locality'' |
- | * <code>region</code> | + | * ''region'' |
- | * <code>postal-code</code> | + | * ''postal-code'' |
- | * <code>country-name</code> | + | * ''country-name'' |
- | * <code>label</code> | + | * ''label'' |
- | * <code>geo</code> - parse as '''<code>p-geo h-geo</code>''' including compat root class <code>geo</code> | + | * ''geo'' - 解析作 ''p-geo h-geo'' 包括compat根类 ''geo'' |
- | * <code>latitude</code> | + | * ''latitude'' |
- | * <code>longitude</code> | + | * ''longitude'' |
- | * <code>tel</code> | + | * ''tel'' |
- | * <code>note</code> | + | * ''note'' |
- | * <code>bday</code> - parse as '''dt-''' | + | * ''bday'' - 解析作 '''dt-''' |
- | * <code>key</code> - parse as '''u-''' | + | * ''key'' - 解析作 '''u-''' |
- | * <code>org</code> | + | * ''org'' |
- | * <code>organization-name</code> | + | * ''organization-name'' |
- | * <code>organization-unit</code> | + | * ''organization-unit'' |
- | * <code>title</code> - parse as '''p-job-title''' | + | * ''title'' - 解析作 '''p-job-title''' |
- | * <code>role</code> | + | * ''role'' |
- | Reserved: (backward compat properties that parsers {{may}} implement, if they do, they {{must}} implement in this way: | + | 保留:(解析器//可能//实现向后兼容属性,如果它们这样做,它们//必须//以这种方式实现: |
- | * <code>tz</code> | + | * ''tz'' |
- | * <code>rev</code> - parse as '''dt-''' | + | * ''rev'' - 解析为 '''dt-''' |
- | == Background == | + | ==== 背景 ==== |
This work is based on the existing [[hCard]] and [[vcard]] specifications. | This work is based on the existing [[hCard]] and [[vcard]] specifications. | ||
- | == Design Principles == | + | ==== 设计原则 ==== |
- | (stub, expand) | + | (留白,扩展) |
- | == Additions == | + | ==== 补充 ==== |
- | We've tried very hard with h-card to stay compatible with the vCard4 vocabulary, and thus additions should be proposed on the vCard4 mailing list. | + | 我们已经非常努力地使h-card同vCard4词汇表保持兼容,因此需要补充的话可以在vCard4邮件列表中提出。 |
- | However, you may still use this wiki to capture additions for h-card here: | + | 不过,您仍然可以使用这个wiki来抓取h-card的附加内容: |
* [[h-card-brainstorming]] | * [[h-card-brainstorming]] | ||
+ | * [[h-card-brainstorming]] | ||
+ | |||
+ | ==== 参见 ==== | ||
+ | * [[microformats2]] | ||
+ | * [[microformats2-parsing]] | ||
+ | * [[h-adr]] | ||
+ | * [[h-geo]] | ||
+ | * [[hCard]] | ||
- | == See Also == | ||
- | * [[microformats2]] | ||
- | * [[microformats2-parsing]] | ||
- | * [[h-adr]] | ||
- | * [[h-geo]] | ||
- | * [[hCard]] | ||
- | [[Category:Draft Specifications]] |