[doap-interest] Changelog with DOAP
olivier.dameron at univ-rennes1.fr
Wed Sep 13 10:14:10 UTC 2006
On Tue, 12 Sep 2006 11:47:04 +0200, "Alexandre Passant"
<alex at passant.org> wrote:
> The interest I see in using DOAP to maintain it is that you've got
> only one file to maintain (well, even if there's tools to create it
> from cvs),
> but then it will be in RDF using a well-known vocabulary
> so that you can SPARQL it, eg to get all changes from a maintainer
> for a given timeline. Finally, the RDF file could be rendered to a
> text changelog (with different formats) as I mention in my blog post.
All the changelog stuff is still stored as plain text in one element,
so from my point of view, even though you are using semantic web tools,
you hardly exploit the "semantic" part. Still, it is a good idea to
store everything in a single place.
Also, what about using a rdfs:list to store the list of changes? One of
the benefits is that you increase the granularity of you description so
that each item of the list can be refered to by something else.
Eventually, each item of the list could be either plain text or a mix
of plain text and rdf ti increase the granularity of your description.
This would allow you to retrieve all the changes relative to one
subject. A first approximation of this retrieval could simply consist
in getting all the list items refering to a particular subject. A
semantically-enabled extension would require to have a model specifying
if some subject is a sub-subject of another one, or is somehows related
to it. Then, your semantic query would start from a subject, compute
all the more specific ones and the related ones, and then retrieve all
the relevant changes that were made. Is this what you had in mind?
More information about the doap-interest