- From: Paul Watson <lazarus@lazaruscorporation.co.uk>
- Date: Sun, 09 Aug 2015 21:23:57 +0100
- To: Jarno van Driel <jarnovandriel@gmail.com>
- CC: "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <55C7B6DD.30408@lazaruscorporation.co.uk>
Hi Jarno,
No, I can see the logic in that - especially since HTML5 provides
semantic elements for marking up similar web page "elements" (in the
form of nav, main, header, footer, etc.) and even if people aren't using
HTML5 then these semantic web page elements can be indicated using
WAI-ARIA roles. As such, the varios subtypes of WebPageElement can not
only be seen as not describing real world entities but also a
duplication of effort.
But - and this is a big obstacle - I think we'd find it difficult to
deprecate the BreadcrumbList type (which is the expected type of the
breadcrumb property of WebPage) because of its very popular use in
enriching how search engine results are displayed in Google ("rich
snippets") and other search engines, regardless of the fact that
BreadcrumbList doesn't describe a "real world entity".
Paul
On 09/08/15 20:37, Jarno van Driel wrote:
> May this year I suggested we deprecate WebPageElement and it's
> subtypes:
> https://lists.w3.org/Archives/Public/public-schemaorg/2015May/0014.html
>
> Personally I don't see the value of keeping these types anymore as
> they describe parts of web pages as opposed to real world entities. Do
> you any reasons why we shouldn't deprecate them Paul? (not a
> rhetorical question, being serious here)
>
> 2015-08-09 10:06 GMT+02:00 Paul Watson
> <lazarus@lazaruscorporation.co.uk
> <mailto:lazarus@lazaruscorporation.co.uk>>:
>
> Hi
>
> I have been looking at schema.org/WebPage
> <http://schema.org/WebPage> and have a couple of proposals I
> wanted to raise on this list before creating issues on Github:
>
> 1. Proposal: mainContentOfPage property should have expected type
> of schema.org/Thing <http://schema.org/Thing>
>
> At the moment the mainContentOfPage property has an expected type
> of WebPageElement. If we broadened this to Thing then an Article,
> NewsItem, Product etc. could be easily marked as the main subject
> of the page. Perhaps this needs to be considered alongside the
> recent work on mainEntityOfPage?
>
> 2. Proposal: method to explicitly attach schema.org/WebPageElement
> <http://schema.org/WebPageElement> types to schema.org/WebPage
> <http://schema.org/WebPage>
>
> There are a number of more specific "WebPageElement" types -
> SiteNavigationElement, Table, WPAdBlock, WPFooter, WPHeader,
> WPSideBar - but not way to explicitly attach them to a WebPage
> (apart from the ability to attach one of them as the
> mainContentOfPage, see above).
>
> Within schema.org/WebPage <http://schema.org/WebPage> we also have
> a breadcrumb property that takes a type of BreadcrumbList.
>
> I think it would be good if there was a way to explicitly attach
> multiple WebPageElements (or child Types) to a WebPage - perhaps
> in the form of a pageElement property on WebPage. That way it
> would be easy to do something as follows:
>
> <body vocab="http://schema.org/" typeof="WebPage">
>
> <header property="pageElement" typeof="WPHeader">
> <!-- header goes here -->
> </header>
>
> <nav property="pageElement" typeof="SiteNavigationElement">
> <!-- navigation goes here -->
> </nav>
>
> <!-- main content of page goes here -->
>
> <footer property="pageElement" typeof="WPFooter">
> <!-- footer goes here -->
> </footer>
>
> </body>
>
>
> Arguably BreadcrumbList should be relocated in the hierarchy to
> become a child type of WebPageElement, but that might
> overly-complicate this proposal.
>
> Regards,
>
> Paul
> --
>
>
Received on Sunday, 9 August 2015 20:24:30 UTC