W3C home > Mailing lists > Public > public-swbp-wg@w3.org > May 2004

Re: [OEP and PORT] "Classes as values": comments on usage of dc:s ubject

From: Guus Schreiber <schreiber@cs.vu.nl>
Date: Thu, 06 May 2004 23:25:54 +0200
Message-ID: <409AAD62.5080209@cs.vu.nl>
To: Natasha Noy <noy@SMI.Stanford.EDU>
Cc: "Miles, AJ (Alistair) " <A.J.Miles@rl.ac.uk>, public-swbp-wg@w3.org

Natasha Noy wrote:

> 
> Hi Alistair,
> 
>> I think if approach 3 is going to stay in this note, then using the SKOS
>> vocab is a good idea, mainly because if everyone uses the same set of
>> properties to organise their subject hierarchies (rather than everyone
>> inventing their own), it makes sharing them even easier.  Also if 
>> there is a
>> clear spec on how they should be used, this helps to promote 
>> consistent use
>> and application.
> 
> 
> agreed -- will change that.
> 
>> My current personal view on using dc:subject is that it should only be
>> applied as in approach 3.  For other approaches, other properties 
>> should be
>> used (e.g. foaf:topic and foaf:primaryTopic).  This could lead to a clear
>> recommendation on which approach should be used with which property.  
>> Then,
>> when you come across a dc:subject property or a foaf:topic property, you
>> would know exactly what to expect.
> 
> 
> This is where I would come back to the point of having only the bare 
> essentials.. This note is not about proper usage of dc:subject. The only 
> reason it's there is because subjects are a natural place where the need 
> of using classes as values arise. There are many other use cases. 
> Thinking about it more, perhaps using something other than dc:subject 
> (just a local property subject?) could be a better idea to avoid 
> touching on this issue. On the other hand, most people looking at a 
> newly introduced subject property will immediately wonder why we are not 
> using dc:subject. Will using some other property, say "topic" create 
> less confusion? Any other suggestions?
> 
> If we do want to address the proper use (and best practice) of 
> dc:subject, it can probably be in a different note that cross-references 
> this one. So, understanding the use of dc;subject perhaps requires 
> understanding this note but not the other way around.

I strongly agree with Natasha's view. We leave it to the developers to 
take their pick from the choices we outline.

Guus

> 
> Thoughts?
> 
> Natasha
> 

-- 
Free University Amsterdam, Computer Science
De Boelelaan 1081a, 1081 HV Amsterdam, The Netherlands
Tel: +31 20 444 7739/7718
E-mail: schreiber@cs.vu.nl
Home page: http://www.cs.vu.nl/~guus/
Received on Thursday, 6 May 2004 17:35:58 UTC

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