W3C home > Mailing lists > Public > public-vocabs@w3.org > March 2014

Re: How to avoid that collections "break" relationships

From: Niklas Lindström <lindstream@gmail.com>
Date: Tue, 25 Mar 2014 17:20:30 +0100
Message-ID: <CADjV5jciQ9c+KiNKoA_Qs4-Bem0+Ot13gJ-ekw_bCktwvJdcYA@mail.gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: "public-vocabs@w3.org" <public-vocabs@w3.org>, public-hydra@w3.org, Linked Data community <public-lod@w3.org>, Michael Haschke <mhaschke@brox.de>
Hi,

Just thinking out loud here,

On Tue, Mar 25, 2014 at 4:57 PM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> +cc public-lod and public-hydra which you've removed Michael
>
>
> On Monday, March 24, 2014 5:54 PM, Michael Haschke wrote:
> > >> Would it be correct to summarize your question as, how do we enable
> > >> "mechanical" features like addressability and pagination to a value
> > >> collection in a way that doesn't interfere with its semantics (i.e.,
> > >> change the range)?
> > >
> > > Yup, this sums it up quite well. Thanks.
> >
> > I think we have the "pagination" feature already because we could
> > spread resource statements over various documents, e.g.
> >
> > on /markus/friends/page/1 describe
> >
> > </markus> schema:knows </alice>.
> >
> > and on /markus/friends/page/2 add
> >
> > </markus> schema:knows </zorro>.
>
> Yeah, but that's not the problem. The problem is how to link from /markus
> to /markus/friends[/page/{page}]
>
>
> > Maybe we would need a property in schema.org that let us relate
> > documents which contain statements about the resource, something very
> > similar to rdfs:seeAlso:
> >
> > </markus> a schema:Person ;
> >       rdfs:seeAlso </markus/friends/page/1> ;
> >       rdfs:seeAlso </markus/friends/page/2> .
>
> The mechanism also needs to tell in which relationship the resources stand
> to each other, in other words, by which property they are "connected"
> (schema:knows).
>

I was thinking the same as Michael (using a mechanism akin to the common
use of rdfs:seeAlso), and then describe the nature of the page linked to.
Perhaps seeing it as a variant of a Linkset, to use VoID terminology [1].
Giving us something like:

    </markus> a schema:Person ;
        rdfs:seeAlso </markus/friends/page/1> .    # or something like
:describedBy (as an inverse of :about)

    </markus/friends/page/1> a void:Linkset;    # or e.g. :LinkPage
        void:linkPredicate :knows .    #  ...

(The difference to VoID is that this is reasonably occurring within the
same dataset, just partitioned across various documents
(pages/records/named graphs/information resources/...).)

Cheers,
Niklas

[1]: http://www.w3.org/TR/void/#describing-linksets



> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
> > regards,
> > Haschek
> >
> > PS: as this is my first post to this group, I add a short info about me
> > (don't know if it is necessary here):
> >
> > Michael Haschke, born in Leipzig, studied & worked in the AKSW at Uni
> > Leipzig on the OntoWiki GUI and Erfurt plugin dispatcher. Now I'm
> > working at eccenca as Front End Developer. In my spare time I wrote
> > SIOC
> > plugins for DokuWiki and small Linked Data apps like foafpress.org
> > My URI is http://michael.haschke.biz/
> >
> > --
> > Michael Haschke
> > eccenca GmbH
> > Neumarkt 20 | 04109  Leipzig | Germany
> > http://eccenca.com/
>
>
>
Received on Tuesday, 25 March 2014 16:21:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:38 UTC