RDFa / 微格式 - 配方标记标准

发布于 2024-08-30 00:55:00 字数 368 浏览 4 评论 0原文

我想知道是否有人可以帮忙?

Google 宣布之后请注意在线食谱的 RDFa / 微格式,我一直在为我运行的几个基于食谱的网站研究这一点。然而,我们根本没有满足任何标准所需的所有数据。

这有关系吗?搜索引擎爬虫是否仍然会充分利用他们找到的内容,或者如果缺少一些元素(例如评论或食谱评级),我会浪费时间来实现这一点吗?

另外,如果出于格式原因,我必须在信息周围添加额外的 div,这是否会使所有内容都无效?

干杯, H

I wonder if anyone can help?

After Google announced that it will take note of RDFa / Microformats for online recipes, I've been looking into this for a couple of recipe based sites I run. However we simply don't have all the required data to fulfill any of the standards.

Does this matter? Will search engine crawlers still make the most of what they do find, or by missing a few elements (like a review or recipe rating) will I be wasting my time implementing this?

Also, if, for formatting reasons, I have to add extra divs around the information, does that invalidate it all?

Cheers,
H

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

难忘№最初的完美 2024-09-06 00:55:00

查看 hRecipe 规范草案。

hRecipe 架构由以下属性组成:

* hrecipe
      o fn. required. text. the name of the recipe.
      o ingredient. required. 1 or more. text with optional valid (x)HTML markup.
            + value and type. optional. [experimental] 
      o yield. optional. text.
      o instructions. optional. text with optional valid (x)HTML markup.
      o duration. optional. 1 or more. text.
      o photo. optional. 1 or more. using any element containing a URL, such as IMG. [experimental]
      o summary. optional. text. [experimental]
      o author. optional. 1 or more. [experimental]
      o published. optional. [experimental]
      o nutrition. optional. 1 or more. [experimental]
            + value and type. optional. [experimental] 
      o tag. optional. 1 or more. [experimental] 

如果您查看必填字段,fningredient 是必填字段,其他字段是可选字段。
以下示例是有效的 hRecipe 配方:

  <div class="mydivclass1">
   <h1 class="fn">Spaghetti al ragù</h1>
     <div class="myfancydiv2>Ingredients:</div>
   <span class="ingredient">
      spaghetti
   </span>
   <span class="ingredient">
      ragù
   </span>
 </div>

要检查您的微格式,您可以使用很酷的 Optimus 验证器

Have a look to hRecipe draft specification.

The hRecipe schema consists of the following properties:

* hrecipe
      o fn. required. text. the name of the recipe.
      o ingredient. required. 1 or more. text with optional valid (x)HTML markup.
            + value and type. optional. [experimental] 
      o yield. optional. text.
      o instructions. optional. text with optional valid (x)HTML markup.
      o duration. optional. 1 or more. text.
      o photo. optional. 1 or more. using any element containing a URL, such as IMG. [experimental]
      o summary. optional. text. [experimental]
      o author. optional. 1 or more. [experimental]
      o published. optional. [experimental]
      o nutrition. optional. 1 or more. [experimental]
            + value and type. optional. [experimental] 
      o tag. optional. 1 or more. [experimental] 

If you look at required fields fn and ingredient are mandatory, the others fields are optional.
The following example is a valid hRecipe recipe:

  <div class="mydivclass1">
   <h1 class="fn">Spaghetti al ragù</h1>
     <div class="myfancydiv2>Ingredients:</div>
   <span class="ingredient">
      spaghetti
   </span>
   <span class="ingredient">
      ragù
   </span>
 </div>

To check your microformats, you could use the cool Optimus validator.

面如桃花 2024-09-06 00:55:00

唯一的“必须有”标签是配方的名称,如果您使用微格式,则为 fn 类。但是,它必须是具有 hrecipe 类名的父级的子级,以帮助索引器区分特殊数据和标准文本。

但!对此的支持刚刚发布,我无法告诉您仅包含食谱名称是否会对您有任何帮助;由于这只是一些更改的问题,您可能想在一个网站上对其进行测试,等待几周,如果有效,则将其应用于其他网站。

关于额外的 DIV,它应该没有任何区别。

The only "must have" tag is the name of the recipe, the fn class if you go with microformats. This however must be the child of a parent which has the hrecipe class name to help the indexers distinguish between the special data and standard text.

BUT! The support for this was just released and I can't tell you if including only the recipe name will help you in any way; since it's a matter of a few changes, you probably want to test it on a site, wait a few weeks and apply to the rest of the sites if it works.

Regarding the extra DIVs, it shouldn't make any difference.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文