RE: [Proposal][SKOS-Core] public/private notes

This proposal opened:

http://www.w3.org/2004/02/skos/core/proposals#notes-2

How does that look?

Cheers,

Al.


---
Alistair Miles
Research Associate
CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Chilton
Didcot
Oxfordshire OX11 0QX
United Kingdom
Email:        a.j.miles@rl.ac.uk
Tel: +44 (0)1235 445440



> -----Original Message-----
> From: public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org]On Behalf Of Miles, AJ 
> (Alistair)
> Sent: 14 June 2005 14:59
> To: Houghton,Andrew
> Cc: public-esw-thes@w3.org
> Subject: RE: [Proposal][SKOS-Core] public/private notes
> 
> 
> 
> Hi Andy,
> 
> Yes, this is exactly what I had in mind :)
> 
> Al.
> 
> 
> > -----Original Message-----
> > From: Houghton,Andrew [mailto:houghtoa@oclc.org]
> > Sent: 13 June 2005 19:03
> > To: Miles, AJ (Alistair); public-esw-thes@w3.org
> > Subject: RE: [Proposal][SKOS-Core] public/private notes
> > 
> > 
> > > From: public-esw-thes-request@w3.org 
> > > [mailto:public-esw-thes-request@w3.org] On Behalf Of Miles, 
> > > AJ (Alistair)
> > > Sent: 13 June, 2005 12:32
> > > To: public-esw-thes@w3.org
> > > Subject: [Proposal][SKOS-Core] public/private notes
> > > 
> > > 
> > > Hi all,
> > > 
> > > > b) Re the discussion of public versus private notes, I 
> > > agree you can't 
> > > > lay this down from above. For example, definitions 
> could be made 
> > > > public for one audience, private for another.
> > > 
> > > I propose that the skos:publicNote and skos:privateNote 
> > > properties be deprecated, and replaced by a single property 
> > > e.g. 'skos:note'.
> > > 
> > > The audience of a note may then be specified by using the 
> > > dcterms:audience property.
> > > 
> > > Any objections to me opening this as a proposal on 
> > > http://www.w3.org/2004/02/skos/core/proposals
> > 
> > Currently in the 10 May 2005 draft these properties have a 
> hierarchy:
> > 
> > skos:publicNote
> >   skos:definition
> >   skos:scopeNote
> >   skos:example
> >   skos:historyNote
> > 
> > skos:privateNote
> >   skos:editorialNote
> >   skos:changeNote
> > 
> > So it sounds like your proposal is to change the hierarchy to:
> > 
> > skos:note
> >   skos:definition
> >   skos:scopeNote
> >   skos:example
> >   skos:historyNote
> >   skos:editorialNote
> >   skos:changeNote
> > 
> > I'm also assuming that skos:note will allow you to make 
> > additional note types, just like publicNote and privateNote 
> > did.  In addition, if you want to specify dcterms:audience, 
> > then you will have to use the second (documentation as a 
> > related resource description) method.
> > 
> > If I understand the proposal correctly, then I feel this 
> > would be a positive change.  In looking at SKOS in relation 
> > to the DDC, we have struggled with SKOS note types, since 
> > there are well over 100 different note types in DDC with 
> > varying degrees of "public-ness" or "private-ness" for 
> > licensees and translators.
> > 
> > 
> > Andy.
> > 
> 
>

Received on Wednesday, 15 June 2005 14:49:55 UTC