- From: Mark van Assem <mark@cs.vu.nl>
- Date: Wed, 03 Aug 2005 14:06:07 +0200
- To: public-esw-thes@w3.org
Stella, Thanks for the clarification. EditorialNote should be kept. Although I could go on arguing that - this note will thus probably only have one valid value for the audience ("editor") which is a clear sign of mixing up function and audience; - you could also interpret changeNote as being to also document the possible *future* changes of a concept, and then you can use the audience value as a filter; - I think we already discussed it wouldn't be good practice to produce/maintain a thesaurus in SKOS itself, so what would be the point of having this maintenance info in the RDF version as a housekeeping aid? I won't do that because that would be for rhetoric enjoyment only :-) Mark. Stella Dextre Clarke wrote: > Mark, > 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 6.1.2.4) 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 > > ***************************************************** > Stella Dextre Clarke > Information Consultant > Luke House, West Hendred, Wantage, Oxon, OX12 8RR, UK > Tel: 01235-833-298 > Fax: 01235-863-298 > SDClarke@LukeHouse.demon.co.uk > ***************************************************** > > > > -----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. > -- Mark F.J. van Assem - Vrije Universiteit Amsterdam mark@cs.vu.nl - http://www.cs.vu.nl/~mark -- Mark F.J. van Assem - Vrije Universiteit Amsterdam mark@cs.vu.nl - http://www.cs.vu.nl/~mark
Received on Wednesday, 3 August 2005 12:06:14 UTC