Re: Schema.org: what schema is best suited for covering pages of word definitions?

Hi Bart,

You are correct that there is currently no ideal Types/Properties to fit
your use case.

However there is a proposal (for the next release) that can be seen in the
webschemas.org development version for EnumerationValue
<http://pending.webschemas.org/EnumerationValue>, which has an example for
terms in a legal dictionary
<http://pending.webschemas.org/EnumerationValue#enumval-3> that comes close
to what you describe.

You could use this approach using disambiguatingDescription for the
definition paragraph and description for the description or you could use
description for both.  If the descriptions are more an article about the
word you could describe the entity as EnumerationValue and Article and
proceed as you describe.

This approach has the benefit of describing the Word’s URL as an identifier
in a set of word identifiers, as part of your website (not necessarily a
Book as in the example).

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 25 July 2016 at 10:44, Bart Kleijngeld <bartkleijngeld@ensie.nl> wrote:

> Hello!
>
> I am looking into Schema.org as a means of improving SEO for our product.
> It's pretty clear to me why it makes sense to use it, but I'm struggling to
> choose an appropriate schema which fits my needs.
>
> Our product can be described approximately as a kind of dictionary, where
> word has its own page, which is composed of a brief definition, followed by
> a more extensive elaboration on the meaning. Like so:
>
> WORD [title]
>
>
>
> definition paragraph
>
>
>> description paragraph
>
>
>
> - list of sources
>
>
>
>
> So my question would be: what schema is best suited for my needs, and if
> no of the existing options suffices, would you recommend me to create my
> own scheme? I can imagine using existing schemes benefits SEO better, but
> I'm a layman on the subject.
>
> So far the best option seems to be the Article scheme, which has an
> articleSection property which can be used to distinguish between definition
> as description, however not semantically, so I wonder if there's a better
> option I'm overlooking. Also, a decent property covering listed sources
> seems to be lacking, since I don't consider citations and mentions to quite
> respect the actual semantic meaning.
>
> Thanks!
>