On 4/10/12 11:26 PM, Pete Johnston wrote:
> For some other examples, see the W3C XML Schema Datatypes specification
>
> http://www.w3.org/TR/xmlschema-2/
>
> which uses the terminology of "lexical space" ("set of strings") and
> "value space" ("set of resources").
>
> I often think the Boolean example is a nice one to consider, because
Unfortunately, our use case isn't Boolean, so I am trying to understand
how we apply this to our use case, for example Gordon's case #1:
http://wiki.dublincore.org/index.php/DCAM_Revision_High_Level_Example_Publication_Statement
which is currently declared to be an SES in the Open Metadata Registry.
An example of a publication statement, as it appears today, is:
New York, Bowker, 1987
coded as:
place of publication: New York
publisher: Bowker
date: 1987
The order is fixed, and any of the parts can be repeated, although again
with a fixed order. In library data today, repeated elements \= repeated
coding:
place of publication: London, New York
publisher: Penguin, Bowker
date: 1987
but we don't know how that will be handled in the future.
kc
>
> (i) both the lexical space and the value space are "small", so one can
> easily "work through the whole set"
> (ii) the concepts of "true" and "false" are fairly easy to grasp as
> two distinct concepts
> (iii) the act that two different components in the lexical space
> ("true" and "1") both map to a single component in the value space
> (true-as-concept) (and similarly for the "false" case), (I think)
> quite neatly illustrates the lexical space/value space separation and
> the idea that a mapping is being made.
>
> Pete
--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
|