|
Hi Bill,
When you speak about "book" there are two
possibilities:
1- you speak about a class of representation that is an
aggregate of other classes of representation (strings, reals,
binaries)
2- you speak about members of that class, being
ink-on-paper or pixels-on-screen, i.e. physical objects that are copies of that
book
Normally you use 1- and use a URI for that. You use 2- only
in case you want to manage individual copies, such as of a
contract.
Both can be related to as many identifiers as you need by
relating it to one or more strings. In the 2- case such an identifier
could be the copy number. For that (and other) reason(s) we represent
strings etc as classes with a datatype property. That string class has its own
URI. It can be typed as "English" (or, denormalized for FOL fans, it can be made
a subclass of something like "English text").
Regards,
Hans
Hey Ken et al..
Ken Laskey
wrote:
Thus, anything that can be identified is a resource (i.e., you can use
everything for something) and URIs are one means (and one that has been found
very useful) for providing that identity.
I think there's a slight confusion here. It is decidedly *not* a name
(which URIs are) that provides the identity. Granted, URIs are meant to be
*identifiers* which suggests that at any given time they name one and only one
thing. Rather, it is the primitive fact that books are individuable at
all, for example, that allows them to be so named. There's the
identity.
.bill
--
No virus found in this incoming message.
Checked by AVG
Free Edition.
Version: 7.5.446 / Virus Database: 269.4.0/760 - Release Date:
13-Apr-07 20:04
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 269.4.0/760 - Release Date: 13-Apr-07 20:04
|