On Mon, 1 Dec 1997, Weibel,Stu wrote:
> Commas strike me as dangerous... occur too much in phrases that might
> properly be atomic?
>
> In fact, I was sort of expecting someone to make the same assertion
> about semicolons.
Yes. It would - from a machine-processability point of view - be nice to
know for sure how to split up a DC Keywords field. Or any other
multi-value field for that matter...
Is there perhaps a case for creating some simple 'utility' DC schemes
here, so we could be explicit about the separator character?
For eg:
<META NAME="Keywords"
CONTENT="1996 Political Contributions;Fraud;Blackmail"
SCHEME="DublinCore.SemiColonSeparatedList">
<META NAME="Keywords"
CONTENT="Baseball cards from 1996, Politicial Jokes, Readers' Contributions"
SCHEME="DublinCore.CommaSeparatedList">
(This takes us back to the 'what exactly are schemes and how are they
formally named' question)
Could someone clarify whether keywords are a special case here. Or
are there other circumstances in which a single DC entry can, as a
convenience, contain multiple values?
Muliple subject classification come to mind (eg. a comma-separated
list of DDC classifications). If this is the case, then my suggestion
above may be useless - we couldn't SCHEME an entry a both
'CommaSeparated' and 'DDC' simultaneously...
Dan
|