Re: Am I right that WebPage lacks a generic property for linking to WebPageElement?

So far I have been using http://schema.org/mentions to link (secondary)
webpageelements to a WebPage, while using http://schema.org/text to enclose
the primary content, and personally I'm quite happy marking it up as such.

I always figured that webpage elements like WPHeader/WPSideBar/etc mirror
their HTML equivalents like <header>/<aside>/etc, which in their turn exist
to markup related/secondary content. For me the meaning of
http://schema.org/mentions reflects this perfectly while
http://schema.org/pageElement seems a bit too generic and could lead to
confusion weither it implies primary or secondary webpage elements.

Now I'm aware the description of http://schema.org/mentions doesn't reflect
this and on top of that there are no clear examples on schema.org which
show how to properly use webpage elements but maybe adding some good
examples would be enough to clarify things. Adding a new property for this
seems a bit overkill IMHO.


On Sun, Jan 19, 2014 at 9:42 AM, Martin Hepp <
martin.hepp@ebusiness-unibw.org> wrote:

> Dear all:
>
> As far as I understand,
>
>     http://schema.org/WebPageElement
>
> would provide a nice way of exposing the meaning of, and meta-data for,
> page elements, which could be used by search engines e.g. for guessing the
> best contextual links (as opposed to breadcrumbs, which imply some kind of
> hierarchy). In particular, one could nicely use
>
>     http://schema.org/SiteNavigationElement
>
> to mark-up important links inside the page, which would often make good
> contextual links.
>
> Unfortunately,
>
>     http://schema.org/WebPage
>
> does not define a generic property for linking from the WebPage to multiple
>
>     http://schema.org/WebPageElement
>
> entities in the same page.
>
> Formally,
>
>     http://schema.org/mentions
>
> would work, but I am unsure whether this is intended.
>
>     http://schema.org/isPartOf
>
> would work from the perspective of the
>
>     http://schema.org/SiteNavigationElement,
>
> but could lead to circular processing of the data.
>
>     http://schema.org/mainContentOfPage
>
> works only for the most important WegPageElement.
>
> I think the best solution would be to add a property
>
>     http://schema.org/pageElement
>
> Indicates that the web page element is a relevant part of the Web page
> (e.g. for linking from a web page to its site navigation elements).
>
> What do others think? Did I miss anything?
>
> Martin
>
> --------------------------------------------------------
> martin hepp
> e-business & web science research group
> universitaet der bundeswehr muenchen
>
> e-mail:  hepp@ebusiness-unibw.org
> phone:   +49-(0)89-6004-4217
> fax:     +49-(0)89-6004-4620
> www:     http://www.unibw.de/ebusiness/ (group)
>          http://www.heppnetz.de/ (personal)
> skype:   mfhepp
> twitter: mfhepp
>
> Check out GoodRelations for E-Commerce on the Web of Linked Data!
> =================================================================
> * Project Main Page: http://purl.org/goodrelations/
>
>
>
>
>