W3C home > Mailing lists > Public > semantic-web@w3.org > August 2015

Re: Link relations between revisions of documents

From: Umutcan Şimşek <s.umutcan@gmail.com>
Date: Sun, 30 Aug 2015 03:41:21 +0200
Message-ID: <CAK1bobeSu6oNf8LD02b646cxgmS8kMKU+LqEoRCU8QOS+ZAQ=g@mail.gmail.com>
To: Austin William Wright <aaa@bzfx.net>
Cc: Semantic Web <semantic-web@w3.org>
Hi Austin,

If I have been working for long hours today so forgive me if I
misunderstood your question, but I think PROV [1] ontology can help to
solve your problem. You can utilize the "invalidated" property for outdated
documents I believe, to make a distinction.

[1] http://www.w3.org/TR/prov-o/


2015-08-30 0:37 GMT+02:00 Austin William Wright <aaa@bzfx.net>:

> I've come across a problem trying to make it easy to revision documents
> that have link relations to each other. I keep document which embed fairly
> standard link relations like "up", "tag" and "collection". These documents
> are stored in a database alongside metadata, revisioning link relations
> like "predecessor-version".
> So the links from one document might look something like this: { ex:foo3
> iana:predecessor-version ex:foo2 ; iana:up ex:top . }
> But what about the resource containing the previous, now-outdated
> document? { ex:foo2 predecessor-version ex:foo1 ; up ex:top . }
> Both these documents are saying that "up" is pointing to the same
> document, which might be correct. Suppose I use these link relations to
> build a directory listing, then my listing will contain old versions of
> documents that I don't want to include. How do I avoid this?
> How do you revision documents in practice?
> Austin Wright.

Received on Sunday, 30 August 2015 01:41:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:43:02 UTC