Re: sub/super (Event, Organization, Place, CreativeWork etc.)

On 29 March 2015 at 11:45, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote:
> Hello,
>
> Currently schema.org has many properties for sub/super relationships

What exactly do you mean by 'sub/super'? For example, you have
included 'member' / 'memberOf', but not for example
http://schema.org/alumni and http://schema.org/alumniOf, can you
articulate the intuition that includes the one pair but not the other?

> # Event
> * https://schema.org/subEvent
> * https://schema.org/superEvent
> ✗ defined as inverseOf
>
> # Organization
> * https://schema.org/subOrganization
> * no superOrganization!
>
> also
> * https://schema.org/member
> * https://schema.org/memberOf
> ✓ defined as inverseOf
>
> # Place
> * https://schema.org/containedIn
> * no contains!
>
> # CreativeWork
> * https://schema.org/hasPart
> * https://schema.org/isPartOf
> ✓ defined as inverseOf
>
> If one day schema.org will have types like Device or Project, they all
> may also need some kind of sub/super relation. Some ideas I would like
> to get some feedback on, even just +/-1
>
> 1) define generic sub / super properties (Thing)
> 2) define them as schema:inverseOf
> 3) define all subX / superX as rdfs:subPropertyOf sub / super
> 4) define pairs of sub properties as schema:inverseOf (where missing)

The trouble with trying for a general theory of parts (c.f.
http://plato.stanford.edu/entries/mereology/ ) is that it's a maze
that you can innocently wander into, but never leave. But you're right
that there is potential for a bit more common or documented structure
here. Some of these above might be transititve, for example. If x is
containedIn y, and y containedIn z, x is containedIn z. Same for
isPartOf, and superEvent I'd argue, but not for memberOf. Most, but
not all (memberOf) of the properties you have listed (isPartOf,
containedIn, subOrganization, subEvent) are more or less homogenous in
that they link things of the same type (creative works, places,
organizations, events). Is this essential to your sense for which
properties are sub/super? Is it essential that they don't allow loops?
(again memberOf seems an outlier...)

Dan

> Cheers!
>

Received on Sunday, 29 March 2015 20:17:22 UTC