Re: schema.org properties with multiple value types

To my understanding, the range and domain information is correct. While the typical case will be that the element that supersedes another element is of the same top-level type (Class, Property, or Enumeration), it is simply not ruled out that a deprecated element is superseded by another element of a different top-level type. So schema.org does not rule out superseding e.g. a class by a property.

I do not see a problem with that, since supersededBy simply points to another schema.org element that should be considered in lieu of the first element. supersededBy does not guarantee equivalence and thus also does not constrain us to pure renaming of elements, but also change the underlying patterns or definitions.

Best

Martin
-----------------------------------
martin hepp  http://www.heppnetz.de
mhepp@computer.org          @mfhepp







> On 13 Jul 2015, at 17:04, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote:
> 
> There are some schema.org properties with multiple expected value types.  For
> example, supersededBy has expected value types Class, Enumeration, and
> Property.  It seems that the expected type Class comes from supercededBy being
> used on Class, and similarly for the other two expected types.
> 
> Is there machine-readable information that would confirm this?
> 
> peter
>

Received on Monday, 13 July 2015 15:22:13 UTC