W3C home > Mailing lists > Public > public-esw-thes@w3.org > November 2010

Re: Maintenance Workflow for SKOS (or RDF statements)

From: Christophe Dupriez <christophe.dupriez@destin.be>
Date: Thu, 18 Nov 2010 13:13:24 +0100
Message-ID: <4CE51864.2090105@destin.be>
To: Simon.Cox@csiro.au, SKOS <public-esw-thes@w3.org>
Thank you very much Simon!

Did you implemented something around that model? Or do you know a 
project team working on it? In Java?

For me, there is one thing to also think about is the granularity of the 
     "Concept" seems obvious. But I think it will be often a specific 
     To make the system rather general, I was thinking of a system able 
to manage any RDF statement (or group of RDF statement with the same 

Have a nice day!


Le 17/11/2010 06:23, Simon.Cox@csiro.au a écrit :
> Here's the key figures from the ISO doc.
> Look at the one called 'Registry Roles' first.
> I would map the terminology as follows:
> Registry = Repository
> Register = Vocabulary, Concept Scheme, etc
> A Register is distinguished by
> (a) usually having a homogeneous type (all items are the same kind of thing)
> (b) more importantly, having uniform governance arrangements (only one control body is involved).
> The Control Body sets the governance rules, acceptance criteria.
> The register manager merely administers the rules.
> If the rules are sufficiently simple the register manage is a piece of software.
> The control body is delegated by the register owner.
> I find the separation of roles and components very helpful.
> Simon
> -----Original Message-----
> From: Cox, Simon (CESRE, Kensington)
> Sent: Wednesday, 17 November 2010 10:46 AM
> To: 'Christophe Dupriez'
> Cc: public-esw-thes@w3.org
> Subject: RE: Maintenance Workflow for SKOS (or RDF statements)
> Christophe -
> Do you have access to a copy of ISO 19135?
> The workflows are very thorough, and I suspect that it would be worth comparing your proposal with these to verify that they are complete.
> I do not mean that every step in the ISO workflows must be explicit - sometimes they can be merged, and roles too - but a comparison may help you to be confident that you haven't missed anything important.
> Simon
> -----Original Message-----
> From: Christophe Dupriez [mailto:christophe.dupriez@destin.be]
> Sent: Tuesday, 16 November 2010 7:44 PM
> To: Cox, Simon (CESRE, Kensington)
> Cc: public-esw-thes@w3.org
> Subject: Re: Maintenance Workflow for SKOS (or RDF statements)
> Hi Simon!
> Thank you for reminding the discussion we had last June on this list.
> I think the conclusion was that the skos:status of NDSL is simply a list
> of the possible combinations of ISO 19135 independent attributes.
> I am pursuing in that direction, now trying to create a "real" system to
> identify SKOS (or RDF) statements that people want to change and to
> record their decision.
> Votation is a simple a mechanism for building/measuring consensus.
> If anybody is doing something in that direction or interested to
> contribute to the development or the documentation:
> http://www.askosi.org/maintenance.pdf
> I would be very happy to learn about it! Students welcome!
> PI=3, why not? In many domain, better decisions would be taken if people
> were conscious that operational precision is rarely better than a
> significant digit!
> Have a nice day!
> Christophe
> Le 16/11/2010 02:39, Simon.Cox@csiro.au a écrit :
>> "- a workflow manager to record update proposals and have the maintainers
>> vote about them."
>> There are good acceptance criteria other than voting, and it doesn't always get the right result. In 1897 the Indiana reps voted to define pi=3 - fortunately the bill died in the state senate.
>> I suggest you should provide a more abstract acceptance point for proposals.
>> FWIW ISO 19135 has a very nice model of workflows for register-maintenance.
>> In this context, a vocabulary is a kind of register.
>> Simon Cox
>> -----Original Message-----
>> From: public-esw-thes-request@w3.org [mailto:public-esw-thes-request@w3.org] On Behalf Of Christophe Dupriez
>> Sent: Thursday, 21 October 2010 6:22 AM
>> To: SKOS; dspace-fr@services.cnrs.fr
>> Subject: Maintenance Workflow for SKOS (or RDF statements)
>>     Maintaining thesauri and their interrelations requires:
>> - a user interface for browsing/search/visualisation of concepts and
>> their relations,
>> - a workflow manager to record update proposals and have the maintainers
>> vote about them.
>> We would like to "make happen" such a "maintenance workflow manager for
>> RDF and SKOS" first to serve the needs of Belgium Poison Centre (*) and
>> then those of the SKOS Community in general.
>> Please click below for draft specifications:
>> http://www.askosi.org/maintenance.pdf
>> As a computer scientist, I can develop parts of this system (upon the
>> basis of ASKOSI.org current results) but this could be also an
>> opportunity for other good wills and talents to improve users needs
>> assessment, specifications, documentation, HTML/CSS/Javascript design,
>> Java coding of specific parts, user acceptance validation, etc. We would
>> be also very happy to collaborate with an existing project.
>> Please let me know your potential interest for your students, for your
>> project team or for yourself.
>> Wishing you a very nice day,
>> Christophe Dupriez
>> (*) The resulting thesauri are currently used to index and retrieve
>> within a DSpace Repository of 90 thousands scientific articles about
>> Acute Toxicology.
Received on Thursday, 18 November 2010 12:13:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 March 2016 13:32:14 UTC