[crm-sig] Scope notes

Nicholas Crofts nickcrofts at yahoo.com
Thu Nov 8 10:02:20 EET 2001


Dear all, Tony in particular,
Apparently the Word file I sent containing scope notes for P51 - P 70 seems to have got scrambled in transit. Below are the same scope notes as an HTML table. I've also attached an RTF file containing the same text. I hope at least one of these is readable.
best wishes
Nick Crofts
P.S. Tony - can't read the photos you posted, 404 errors.
 
 

P51

Physical Object

E19

has former or current owner (is former or current owner of)

Actor

E39

This is a 'shortcut' property link which allows an E39 Actor to be associated directly as owner with an E19 Physical Object. The property does not allow any indication of the time span during which the Actor was the owner, nor if the Actor still is the owner. A more detailed representation can be made using the fully developed (i.e. indirect) path through E8 Acquisition.

P52

Physical Object

E19

has current owner (is current owner of)

Actor

E39

This 'shortcut' property is similar in intention to P51has former or current owner... However, it indicates that the Actor associated with the physical object is currently the owner of the object. This information would need to be updated when a change of ownership takes place. The property does not allow any indication of the moment at which the Actor came into possession of the objet. A more detailed representation can make use of the fully developed (i.e. indirect) path through E8 Acquisition.

P53

Physical Object

E19

has former or current location (is former or current location of) 

Place

E53

This is a 'shortcut' property link which allows an E53 Place to be associated directly, as location, with a physical object. The property does not allow any indication of the time span during which the Object was located at this Place, nor if this is the current location. A more detailed representation can make use of the fully developed (i.e. indirect) path through E9 Move.

P54

Physical Object

E19

has current permanent location (is current permanent location of)

Place

E53

This 'shortcut' property is similar in intention to P55 has current location... However, it indicates in addition that the Place associated with the physical object is the current permanent location of the object. The degree to which a location is in fact permanent is a matter of judgement. Some institutions may choose to use this property link to indicate the location reserved for storage, as opposed to exhibition i.e. the default location. This would entail that, during an exhibition, an object may not in fact be found at its permanent location. This information would need to be updated if, contrary to expectations, a change of permanent location did in fact take place. The property does not allow any indication of how long the Object has been at the current permanent location, nor indeed if the object is actually at this location. A more detailed representation can make use of the fully developed (i.e. indirect) path through E9 Move.

P55

Physical Object

E19

has current location (currently holds) 

Place

E53

This 'shortcut' property is similar in intention to P53 has former or current location... However, it indicates that the Place associated with the physical object is the current location of the object. This information would need to be updated when a change of location takes place. The property does not allow any indication of how long the Object has been at the current location. A more detailed representation can make use of the fully developed (i.e. indirect) path through E9 Move.

P56

Physical Object

E19

bears feature (is found on)

Physical Feature

E26

This property link allows an E26 Physical Feature, to be associated with the E19 Physical Object on which it is found. Physical Features need to be documented explicitly when they are of special significance and require detailed description independently of the object. Features such as the colour or weight of an object would not normally merit this treatment whereas a hole, a mark or an inscription might well do.

P57

Physical Object

E19

has number of parts

Number

E60

This property provides a simple way of documenting the number of components of which an object is composed. What constitutes a part or component depends on the context and requirements of the documentation. Normally, the parts documented in this way would not be considered as worthy of individual attention. For a more complete description, objects may be decomposed into their components and constituents using P46 is composed of ... and P45 consists of This allows each element to be described individually.

This property link is currently lacking a reverse direction label. 'is the number of parts of' might be suitable. 

P58

Physical Object

E19

has section definition (defines section)

Section Definition

E46

Physical objects may be decomposed into sections. This property link allows section definitions (i.e. names of sections) to be associated directly with the Physical Object of which they form a part. This property link is in effect a 'shortcut' of the fully developed path from object to E53 Place and hence to place appellation through P59 has section. 

Section definitions need not be discrete and separable components or parts of an object (cf scope note for E46 Section Definition). 

Note that E19 has section definition says nothing about what sections are typical of certain types of physical objects, merely that one particular instance of an object has a particular section.

P59

Physical Object

E19

has section (is located on or within)

Place

E53

Physical objects may be decomposed into sections. The CRM handles sections as as locations within or on an object (instances of E53 Place). This property link allows sections to be associated with the Physical Object of which they form a part. Sections need not be discrete and separable components or parts of an object (cf scope note for E46 Section Definition).

Note that E19 has section says nothing about what sections are typical of a certain types of physical objects, merely that one particular instance of an object has a particular section. 

P58 has section definition... offers a direct shortcut from E19 Physical Object to E46 Section Definition, which is a sub-entity of E44 Place Appellation.

P60

Person

E21

is member of (has members)

Legal Body

E40

Instances of E21 Person, may be members of groups. Some groups are legal entities such as companies, institutions and nations. P60 is member of... allows this relationship to be documented. Joining and belonging to a group may not require explicit actions on the part of the Person concerned, (membership may result from circumstances or from an a posteriori decision.) 

P60 is member of ... says nothing about the date at which a person became a member of E40 Legal Body, however, it does imply that the person is currently a member of the body. It should therefore be updated if the person in question ceases to be a member.

P60 can be considered as an approximate specialisation of P107 had member... although the temporal constraints are different.

Both P107 and P60 can be thought of as shortcuts of a more fully developed path via a specialisation of Event such as 'became member', though no such entity currently exists in the CRM.

The scope of P107 and P60 may need to be revised at some stage for greater consistency.

P61

Person

E21

has gender (is gender of)

Gender

E76

This property link allows the gender of a person (male or female) to be specified. The CRM does not currently cater for changes of gender. 

The most appropriate treatment for this property, and its extension to other biological objects such as animals and plants, are issues currently under discussion.

P62

Physical Man-Made Stuff

E24

depicts object (is depicted by) 

(mode of depiction : Type)

Physical Stuff

E18

P62, P63, and P64 are related property links. 

Any item of E24 Physical Man-Made Stuff may depict or represent other objects, events, concepts, etc. These three 'depicts' properties allow this relationship to be documented.

The CRM 'world view' treats all forms of depiction as essentially visual, so a book, for example, does not 'depict' its subject matter, though at a very general level, P70 documents is clearly related.

Unlike the P70 link used for documents, P62, P63 and P64 all have a mode of depiction link to the Type hierarchy. This is intended to allow a fine-level description of the mode of representation such as 'realistic', 'abstract', 'naive', etc. (This may give rise to overlap with stylistic classification.) The mode of depiction property, being a property of a property, has not been assigned a P number in the property hierarchy.

It could be argued that since anything at all may be depicted, the three existing 'depicts' links could be replaced with a single, high level property link to E1, analogous to that for P70.

P63

Physical Man-Made Stuff

E24

depicts event (is depicted by)

(mode of depiction : Type)

Event

E5

cf note for P62

P64

Physical Man-Made Stuff

E24

depicts concept (is depicted by)

(mode of depiction : Type)

Type

E55

cf note for P62

P65

Physical Man-Made Stuff

E24

shows visual item (is shown by)

Visual Item

E36

This link is similar to P62, P63 and P64 in that is associates an item of Physical Man-Made Stuff with a visual representation. However, P65 shows visual item differs from the 'depicts' property links in that it makes no claims about the what the visual item is deemed to represent. E36 Visual item identifies a recognisable image or visual symbol, regardless of what this image may or may not represent. For example, all recent British coins bear a portrait of Queen Elizabeth II, a fact which is correctly documented using P62 depicts object... Different portraits have been used at different periods, however. P65 shows visual item can be used to refer to a particular portrait.

P65 show visual item may also be used for visual items such as signs, marks and symbols, such as the 'Maltese Cross' or the 'copyright symbol' which have no particular representational content.

P66

Conceptual Object

E28

refers to concept (is referred to by)

Type

E55

Any instance of E28 Conceptual Object may refer to general concepts contained in the type hierarchy. As with P67, "refers to" is used here as distinct from the subject matter of a conceptual object, which is correctly documented using P70 documents. The text of this scope note, for example, refers to the subject of 'astrology', but does not describe or document it in any way.

P66 refers to... is provided in addition to P67 refers to... since references may be made to general ideas or classes of objects for which no instance may exist in the entity hierarchy. 

P67

Conceptual Object

E28

refers to ( is referred to by)

(has type : Type)

CRM Entity

E1

Instances of E28 Conceptual Object may refer to instances of other entities. As with P66, "refers to" is used here as distinct from subject matter, which is correctly documented using P70 documents. The text of this scope note, for example, refers to "Dr Martin Doerr", who is an instance of E21 Person, without describing or documenting him in detail.

P67 refers to.. .is provided in addition to P66 refers to... since references may be made to specific instances of entities as well as to general ideas or classes of objects.

P68

Design or Procedure

E29

usually employs (is usually employed by)

Material

E57

Certain designs and procedures commonly employ particular materials. The fabrication of adobe bricks, for example, requires clay and water. P68 usually employs... allows this sort of information to be documented. 

P68 is not intended for the documentation of materials that were required on a particular occasion when a design or procedure was executed.

P69

Design or Procedure

E29

is associated with

Design or Procedure

E29

Any instance of E29 Design or Procedure may be associated with other designs or procedures. P69 is associated with allows this relationship to be made explicit. P69 says nothing about the precise nature of the association, such as whether one procedure is a sub process of another.

P69 currently lacks an explicit reverse direction label since it can be read in either direction. The property is assumed to be entirely reciprocal.

P70

Document

E31

documents (is documented in)

CRM Entity

E1

This property link can be thought of as representing the primary subject matter of a document. However, it is slightly broader in application than the notion of subject since it is intended to encompass cases where objects acquire a documentary function by virtue of their role as evidence. 

Documents may describe or inform us about any conceivable subject, hence the link to the highest level entity in the CRM hierarchy.

The CRM makes a distinction between the primary subject matter of a document - what it documents - and other entities which are merely referred to. These latter are represented through P66 refers to concept and P67 refers to. 

The CRM does not currently provide a property such as 'documents concept', analogous to P66, for the documentation (as primary subject) of concepts in the type hierarchy.
 
  Tony Gill <tony_gill at notes.rlg.org> wrote: Nick,

Your scope notes appear to be double-encoded -- the Word file I received 
contains this kind of stuff:

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAAB
AAAALQAAAAAAAAAAEAAALgAAAAEAAAD+////AAAAACwAAAD/////////////
//////////////////////////////////////////////////////////// etc...

Cheers,

T.
----------------------------------------------------------------------
Tony Gill <> tony.gill at notes.rlg.org
Research Libraries Group <> http://www.rlg.org/
1200 Villa Street, Mountain View, CA 94041 USA
Voice: +1 (650) 691-2304 <> Fax: +1 (650) 964-1461







Nicholas Crofts 
Sent by: owner-crm-sig at ics.forth.gr
26/10/2001 05:57 AM


To: CRM-SIG 
cc: 
Subject: [crm-sig] Scope notes




Dear SIG members,

Please find in the attached file my proposed scope notes for property 
links P51 - P70 in accordance with the work dished out in Paris.

Best wishes




Nicholas Crofts
DAEL / DSI
rue David-Dufour 5
Case postale 22
CH - 1211 Genève 8
tél +41 22 327 5271
fax +41 22 328 4382



Nokia Game is on again. 
Click here to join the new all media adventure before November 3rd. 





---------------------------------
Do You Yahoo!?
Get personalised at My Yahoo!.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ics.forth.gr/pipermail/crm-sig/attachments/20011108/57e0905a/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: P 51-70 scope notes.rtf
Type: application/rtf
Size: 26922 bytes
Desc: P 51-70 scope notes.rtf
Url : http://lists.ics.forth.gr/pipermail/crm-sig/attachments/20011108/57e0905a/attachment-0001.rtf 


More information about the Crm-sig mailing list