All geek questions in one place

HTML5 and Schema.org, why use both?

Does Schema.org microdata already describe any element better than HTML5 seems redundant? For example:

<nav itemscope itemtype="http://schema.org/SiteNavigationElement">
    <!-- might as well just be... -->
<div itemscope itemtype="http://schema.org/SiteNavigationElement">

and

<article itemscope itemtype="http://schema.org/NewsArticle">
    <!-- might as well just be... -->
<div itemscope itemtype="http://schema.org/NewsArticle">

Some elements create an outline for a web page, but beyond that, what is the point? Why not just use divand forget about semantic tags, but just use Microdata and Schema.org?

+4
source share
2 answers

The schema.org definitions are specifically for applications such as search engines (From What is schema.org? ):

, .. html, - , . , Bing, Google, Yahoo! , , -.

, ( schema.org ):

HTML , . , < h1 > </h1 > "" 1. HTML- , "" 3D-, , .

, ( , schema.org), , , , , .

HTML, , . nav article - , , .

, . schema.org , , .

, , . , (LinkedIn, github ) , , google , .

+3

, schema.org, HTML, , , , ..

, , http://schema.org/WebPageElement. , , , , , HTML-.

0

Source: https://habr.com/ru/post/1526260/

More articles:


All Articles