Re: Two proposals for schema.org/WebPage

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>:

> Hi
>
> I have been looking at 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
>
> 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 types
> to 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 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 19:38:24 UTC