W3C home > Mailing lists > Public > public-esw-thes@w3.org > August 2005

RE: SKOS Core second review

From: Stella Dextre Clarke <sdclarke@lukehouse.demon.co.uk>
Date: Wed, 3 Aug 2005 12:13:03 +0100
To: "'Mark van Assem'" <mark@cs.vu.nl>, <public-esw-thes@w3.org>
Message-ID: <002701c5981c$5130dc30$0300a8c0@DELL>

Quoting from the draft of BS8723, 
' Editorial note is useful for entries such as "Review this term after
the company merger complete" or "This term is mentioned in the scope
note of Term X" (See or "Check spelling with expert A". '
These are reminders of editorial work still to be done, or warnings in
the event that future editorial changes might be made. A housekeeping
aid, not a search aid.

Stella Dextre Clarke
Information Consultant
Luke House, West Hendred, Wantage, Oxon, OX12 8RR, UK
Tel: 01235-833-298
Fax: 01235-863-298

-----Original Message-----
From: public-esw-thes-request@w3.org
[mailto:public-esw-thes-request@w3.org] On Behalf Of Mark van Assem
Sent: 03 August 2005 11:27
To: public-esw-thes@w3.org
Subject: Re: SKOS Core second review

Hi Stella,

> History Notes or Change Notes. History Notes are intended to help 
> users choose the right formulation of search terms, so they need to 
> see them; Editorial Notes need to be kept out of sight in normal 
> usage, to avoid confusion.

Specifying the audience would do just that: act as a filter. But of 
course it requires that the user/system specifies itself as the 
appropriate audience. But your point is that editorialNote has a 
seperate function (maintenance, so notes about e.g. the "future" of 
the concept?). Could you give some examples to win me over completely 
:-) Also nice to have in the Guide.


  Mark F.J. van Assem - Vrije Universiteit Amsterdam
        mark@cs.vu.nl - http://www.cs.vu.nl/~mark
Received on Wednesday, 3 August 2005 11:13:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:45:22 UTC