Definition of Object-Oriented frbr
Yüklə 1,5 Mb.
|
- Bu səhifədəki naviqasiya:
- E13 Attribute Assignment
- E15 Identifier Assignment
- E24 Physical Man-Made Thing
- E29 Design or Procedure
- E47 Spatial Coordinates
- E63 Beginning of Existence
- E84 Information Carrier
- E89 Propositional Object
E5 EventSubclass of: E4 Period Superclass of: E7 Activity E63 Beginning of Existence E64 End of Existence Scope note: This class comprises changes of states in cultural, social or physical systems, regardless of scale, brought about by a series or group of coherent physical, cultural, technological or legal phenomena. Such changes of state will affect instances of E77 Persistent Item or its subclasses. The distinction between an E5 Event and an E4 Period is partly a question of the scale of observation. Viewed at a coarse level of detail, an E5 Event is an ‘instantaneous’ change of state. At a fine level, the E5 Event can be analysed into its component phenomena within a space and time frame, and as such can be seen as an E4 Period. The reverse is not necessarily the case: not all instances of E4 Period give rise to a noteworthy change of state. Examples:
Properties: P11 had participant (participated in): E39 Actor P12 occurred in the presence of (was present at): E77 Persistent Item E7 ActivitySubclass of: E5 Event Superclass of: E8 Acquisition E9 Move E10 Transfer of Custody E11 Modification E13 Attribute Assignment E65 Creation E66 Formation E85 Joining E86 Leaving E87 Curation Activity Scope note: This class comprises actions intentionally carried out by instances of E39 Actor that result in changes of state in the cultural, social, or physical systems documented. This notion includes complex, composite and long-lasting actions such as the building of a settlement or a war, as well as simple, short-lived actions such as the opening of a door. Examples:
Properties: P14 carried out by (performed): E39 Actor (P14.1 in the role of: E55 Type) P15 was influenced by (influenced): E1 CRM Entity P16 used specific object (was used for): E70 Thing (P16.1 mode of use: E55 Type) P17 was motivated by (motivated): E1 CRM Entity P19 was intended use of (was made for): E71 Man-Made Thing (P19.1 mode of use: E55 Type) P20 had specific purpose (was purpose of): E5 Event P21 had general purpose (was purpose of): E55 Type P32 used general technique (was technique of): E55 Type
P134 continued (was continued by): E7 Activity E11 ModificationSubclass of: E7 Activity Superclass of: E12 Production E79 Part Addition E80 Part Removal Scope note: This class comprises all instances of E7 Activity that create, alter or change E24 Physical Man-Made Thing. This class includes the production of an item from raw materials, and other so far undocumented objects, and the preventive treatment or restoration of an object for conservation. Since the distinction between modification and production is not always clear, modification is regarded as the more generally applicable concept. This implies that some items may be consumed or destroyed in a Modification, and that others may be produced as a result of it. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities. If the instance of the E29 Design or Procedure utilized for the modification prescribes the use of specific materials, they should be documented using property P68 foresees use of (use foreseen by): E57 Material of E29 Design or Procedure, rather than via P126 employed (was employed in): E57 Material. Examples:
Properties: P31 has modified (was modified by): E24 Physical Man-Made Thing P126 employed (was employed in): E57 Material E12 ProductionSubclass of: E11 Modification E63 Beginning of Existence Scope note: This class comprises activities that are designed to, and succeed in, creating one or more new items. It specializes the notion of modification into production. The decision as to whether or not an object is regarded as new is context sensitive. Normally, items are considered “new” if there is no obvious overall similarity between them and the consumed items and material used in their production. In other cases, an item is considered “new” because it becomes relevant to documentation by a modification. For example, the scribbling of a name on a potsherd may make it a voting token. The original potsherd may not be worth documenting, in contrast to the inscribed one. This entity can be collective: the printing of a thousand books, for example, would normally be considered a single event. An event should also be documented using E81 Transformation if it results in the destruction of one or more objects and the simultaneous production of others using parts or material from the originals. In this case, the new items have separate identities and matter is preserved, but identity is not. Examples:
Properties: P108 has produced (was produced by): E24 Physical Man-Made Thing E13 Attribute AssignmentSubclass of: E7 Activity Superclass of: E14 Condition Assessment E15 Identifier Assignment E16 Measurement E17 Type Assignment Scope note: This class comprises the actions of making assertions about properties of an object or any relation between two items or concepts. This class allows the documentation of how the respective assignment came about, and whose opinion it was. All the attributes or properties assigned in such an action can also be seen as directly attached to the respective item or concept, possibly as a collection of contradictory values. All cases of properties in this model that are also described indirectly through an action are characterised as “short cuts” of this action. This redundant modelling of two alternative views is preferred because many implementations may have good reasons to model either the action or the short cut, and the relation between both alternatives can be captured by simple rules. In particular, the class describes the actions of people making propositions and statements during certain museum procedures, e.g. the person and date when a condition statement was made, an identifier was assigned, the museum object was measured, etc. Which kinds of such assignments and statements need to be documented explicitly in structures of a schema rather than free text, depends on if this information should be accessible by structured queries. Examples:
Properties: P140 assigned attribute to (was attributed by): E1 CRM Entity P141 assigned (was assigned by): E1 CRM Entity
The fact that an identifier is a preferred one for an organisation can be expressed by using the property E1 CRM Entity. P48 has preferred identifier (is preferred identifier of): E42 Identifier. It can better be expressed in a context independent form by assigning a suitable E55 Type, such as “preferred identifier assignment”, to the respective instance of E15 Identifier Assignment via the P2 has type property. Examples:
Properties: P37 assigned (was assigned by): E42 Identifier P38 deassigned (was deassigned by): E42 Identifier P142 used constituent (was used in): E90 Symbolic Object E18 Physical ThingSubclass of: E72 Legal Object Superclass of: E19 Physical Object E24 Physical Man-Made Thing E26 Physical Feature Scope Note: This class comprises all persistent physical items with a relatively stable form, man-made or natural. Depending on the existence of natural boundaries of such things, the CRM distinguishes the instances of E19 Physical Object from instances of E26 Physical Feature, such as holes, rivers, pieces of land etc. Most instances of E19 Physical Object can be moved (if not too heavy), whereas features are integral to the surrounding matter. The CRM is generally not concerned with amounts of matter in fluid or gaseous states. Examples:
Properties: P44 has condition (condition of): E3 Condition State P45 consists of (is incorporated in): E57 Material P46 is composed of (forms part of): E18 Physical Thing P49 has former or current keeper (is former or current keeper of): E39 Actor P50 has current keeper (is current keeper of): E39 Actor P51 has former or current owner (is former or current owner of): E39 Actor P52 has current owner (is current owner of): E39 Actor P53 has former or current location (is former or current location of): E53 Place P58 has section definition (defines section): E46 Section Definition P59 has section (is located on or within): E53 Place E19 Physical ObjectSubclass of: E18 Physical Thing Superclass of: E20 Biological Object E22 Man-Made Object
Examples:
Properties: P54 has current permanent location (is current permanent location of): E53 Place P55 has current location (currently holds): E53 Place P56 bears feature (is found on): E26 Physical Feature P57 has number of parts: E60 Number E21 PersonSubclass of: E20 Biological Object E39 Actor Scope note: This class comprises real persons who live or are assumed to have lived. Legendary figures that may have existed, such as Ulysses and King Arthur, fall into this class if the documentation refers to them as historical figures. In cases where doubt exists as to whether several persons are in fact identical, multiple instances can be created and linked to indicate their relationship. The CRM does not propose a specific form to support reasoning about possible identity. Examples:
E22 Man-Made ObjectSubclass of: E19 Physical Object E24 Physical Man-Made Thing Superclass of: E84 Information Carrier
Examples:
E24 Physical Man-Made ThingSubclass of: E18 Physical Thing E71 Man-Made Thing Superclass of: E22 Man-Made Object E25 Man-Made Feature E78 Collection Scope Note: This class comprises all persistent physical items that are purposely created by human activity. This class comprises man-made objects, such as a swords, and man-made features, such as rock art. No assumptions are made as to the extent of modification required to justify regarding an object as man-made. For example, a “cup and ring” carving on bedrock is regarded as instance of E24 Physical Man-Made Thing. Examples:
Properties: P62 depicts (is depicted by): E1 CRM Entity (P62.1 mode of depiction: E55 Type)
E25 Man-Made FeatureSubclass of: E24 Physical Man-Made Thing E26 Physical Feature Scope Note: This class comprises physical features that are purposely created by human activity, such as scratches, artificial caves, artificial water channels, etc. No assumptions are made as to the extent of modification required to justify regarding a feature as man-made. For example, rock art or even “cup and ring” carvings on bedrock a regarded as types of E25 Man-Made Feature. Examples:
E26 Physical FeatureSubclass of: E18 Physical Thing Superclass of: E25 Man-Made Feature E27 Site
Examples:
E27 SiteSubclass of: E26 Physical Feature Scope Note: This class comprises pieces of land or sea floor. In contrast to the purely geometric notion of E53 Place, this class describes constellations of matter on the surface of the Earth or other celestial body, which can be represented by photographs, paintings and maps. Instances of E27 Site are composed of relatively immobile material items and features in a particular configuration at a particular location. Examples:
E28 Conceptual ObjectSubclass of: E71 Man-Made Thing Superclass of: E55 Type E89 Propositional Object E90 Symbolic Object Scope note: This class comprises non-material products of our minds and other human produced data that have become objects of a discourse about their identity, circumstances of creation or historical implication. The production of such information may have been supported by the use of technical devices such as cameras or computers. Characteristically, instances of this class are created, invented or thought by someone, and then may be documented or communicated between persons. Instances of E28 Conceptual Object have the ability to exist on more than one particular carrier at the same time, such as paper, electronic signals, marks, audio media, paintings, photos, human memories, etc. They cannot be destroyed. They exist as long as they can be found on at least one carrier or in at least one human memory. Their existence ends when the last carrier and the last memory are lost. Examples:
Properties: P149 is identified by (identifies): E75 Conceptual Object Appellation E29 Design or ProcedureSubclass of: E73 Information Object Scope note: This class comprises documented plans for the execution of actions in order to achieve a result of a specific quality, form or contents. In particular it comprises plans for deliberate human activities that may result in the modification or production of instances of E24 Physical Thing. Instances of E29 Design or Procedure can be structured in parts and sequences or depend on others. This is modelled using P69 is associated with. Designs or procedures can be seen as one of the following:
Because designs or procedures may never be applied or only partially executed, the CRM models a loose relationship between the plan and the respective product. Examples:
Properties: P68 foresees use of (use foreseen by): E57 Material P69 has association with (is associated with): E29 Design or Procedure (P69.1 has type: E55 Type) E30 RightSubclass of: E89 Propositional Object Scope Note: This class comprises legal privileges concerning material and immaterial things or their derivatives. These include reproduction and property rights. Examples:
E31 DocumentSubclass of: E73 Information Object Superclass of: E32 Authority Document Scope note: This class comprises identifiable immaterial items that make propositions about reality. These propositions may be expressed in text, graphics, images, audiograms, videograms or by other similar means. Documentation databases are regarded as a special case of E31 Document. This class should not be confused with the term “document” in Information Technology, which is compatible with E73 Information Object. Examples:
Properties: P70 documents (is documented in): E1 CRM Entity E32 Authority DocumentSubclass of: E31 Document Scope note: This class comprises encyclopaedia, thesauri, authority lists and other documents that define terminology or conceptual systems for consistent use. Examples:
Properties: P71 lists (is listed in): E1 CRM Entity E33 Linguistic ObjectSubclass of: E73 Information Object Superclass of: E34 Inscription E35 Title Scope note: This class comprises identifiable expressions in natural language or languages. Instances of E33 Linguistic Object can be expressed in many ways: e.g. as written texts, recorded speech or sign language. However, the CRM treats instances of E33 Linguistic Object independently from the medium or method by which they are expressed. Expressions in formal languages, such as computer code or mathematical formulae, are not treated as instances of E33 Linguistic Object by the CRM. These should be modelled as instances of E73 Information Object. The text of an instance of E33 Linguistic Object can be documented in a note by P3 has note: E62 String Examples:
Properties: P72 has language (is language of): E56 Language P73 has translation (is translation of): E33 Linguistic Object E35 TitleSubclass of: E33 Linguistic Object E41 Appellation Scope note: This class comprises the names assigned to works, such as texts, artworks or pieces of music. Titles are proper noun phrases or verbal phrases, and should not be confused with generic object names such as “chair”, “painting” or “book” (the latter are common nouns that stand for instances of E55 Type). Titles may be assigned by the creator of the work itself, or by a social group. This class also comprises the translations of titles that are used as surrogates for the original titles in different social contexts. Examples:
E36 Visual ItemSubclass of: E73 Information Object Superclass of: E37 Mark E38 Image
Properties: P138 represents (has representation): E1 CRM Entity (P138.1 mode of representation: E55 Type) E37 MarkSubclass of: E36 Visual Item Superclass of: E34 Inscription Scope note: This class comprises symbols, signs, signatures or short texts applied to instances of E24 Physical Man-Made Thing by arbitrary techniques in order to indicate the creator, owner, dedications, purpose, etc. This class specifically excludes features that have no semantic significance, such as scratches or tool marks. These should be documented as instances of E25 Man-Made Feature. Examples:
E39 ActorSubclass of: E77 Persistent Item Superclass of: E21 Person E74 Group Scope note: This class comprises people, either individually or in groups, who have the potential to perform intentional actions for which they can be held responsible. The CRM does not attempt to model the inadvertent actions of such actors. Individual people should be documented as instances of E21 Person, whereas groups should be documented as instances of either E74 Group or its subclass E40 Legal Body. Examples:
Properties: P74 has current or former residence (is current or former residence of): E53 Place P75 possesses (is possessed by): E30 Right P76 has contact point (provides access to): E51 Contact Point P131 is identified by (identifies): E82 Actor Appellation E40 Legal BodySubclass of: E74 Group Scope Note: This class comprises institutions or groups of people that have obtained a legal recognition as a group and can act collectively as agents. This means that they can perform actions, own property, create or destroy things and can be held collectively responsible for their actions like individual people. The term ‘personne morale’ is often used for this in French. Examples:
E41 AppellationSubclass of: E90 Symbolic Object Superclass of: E35 Title E42 Identifier E44 Place Appellation E49 Time Appellation E51 Contact Point E75 Conceptual Object Appellation E82 Actor Appellation Scope note: This class comprises signs, either meaningful or not, or arrangements of signs following a specific syntax, that are used or can be used to refer to and identify a specific instance of some class within a certain context. Instances of E41 Appellation do not identify things by their meaning, even if they happen to have one, but by convention, tradition, or agreement. Instances of E41 Appellation are cultural constructs; as such, they have a context, a history, and a use in time and space by some group of users. A given instance of E41 Appellation can have alternative forms, i.e., other instances of E41 Appellation that are always regarded as equivalent independent from the thing it denotes. Specific subclasses of E41 Appellation should be used when instances of E41 Appellation of a characteristic form are used for particular objects. Instances of E49 Time Appellation, for example, which take the form of instances of E50 Date, can be easily recognised. E41 Appellation should not be confused with the act of naming something. Cf. E15 Identifier Assignment Examples:
Properties: P139 has alternative form: E41 Appellation P139.1 has type: E55 Type
E42 IdentifierSubclass of: E41 Appellation Scope note: This class comprises strings or codes assigned to instances of E1 CRM Entity in order to identify them uniquely and permanently within the context of one or more organisations. Such codes are often known as inventory numbers, registration codes, etc. and are typically composed of alphanumeric sequences. The class E42 Identifier is not normally used for machine-generated identifiers used for automated processing unless these are also used by human agents. Examples:
E44 Place AppellationSubclass of: E41 Appellation Superclass of E45 Address E46 Section Definition E47 Spatial Coordinates E48 Place Name Scope Note: This class comprises any sort of identifier characteristically used to refer to an E53 Place. Instances of E44 Place Appellation may vary in their degree of precision and their meaning may vary over time – the same instance of E44 Place Appellation may be used to refer to several places, either because of cultural shifts, or because objects used as reference points have moved around. Instances of E44 Place Appellation can be extremely varied in form: postal addresses, instances of E47 Spatial Coordinate, and parts of buildings can all be considered as instances of E44 Place Appellation. Examples:
E47 Spatial CoordinatesSubclass of: E44 Place Appellation Scope Note: This class comprises the textual or numeric information required to locate specific instances of E53 Place within schemes of spatial identification. Coordinates are a specific form of E44 Place Appellation, that is, a means of referring to a particular E53 Place. Coordinates are not restricted to longitude, latitude and altitude. Any regular system of reference that maps onto an E19 Physical Object can be used to generate coordinates. Examples:
E49 Time AppellationSubclass of: E41 Appellation Superclass of E50 Date Scope Note: This class comprises all forms of names or codes, such as historical periods, and dates, which are characteristically used to refer to a specific E52 Time-Span. The instances of E49 Time Appellation may vary in their degree of precision, and they may be relative to other time frames, “Before Christ” for example. Instances of E52 Time-Span are often defined by reference to a cultural period or an event e.g. ‘the duration of the Ming Dynasty’. Examples:
E50 DateSubclass of: E49 Time Appellation Scope Note: This class comprises specific forms of E49 Time Appellation. Dates may vary in their degree of precision. Examples:
E52 Time-SpanSubclass of: E1 CRM Entity Scope note: This class comprises abstract temporal extents, in the sense of Galilean physics, having a beginning, an end and a duration. Time Span has no other semantic connotations. Time-Spans are used to define the temporal extent of instances of E4 Period, E5 Event and any other phenomena valid for a certain time. An E52 Time-Span may be identified by one or more instances of E49 Time Appellation. Since our knowledge of history is imperfect, instances of E52 Time-Span can best be considered as approximations of the actual Time-Spans of temporal entities. The properties of E52 Time-Span are intended to allow these approximations to be expressed precisely. An extreme case of approximation, might, for example, define an E52 Time-Span having unknown beginning, end and duration. Used as a common E52 Time-Span for two events, it would nevertheless define them as being simultaneous, even if nothing else was known. Automatic processing and querying of instances of E52 Time-Span is facilitated if data can be parsed into an E61 Time Primitive. Examples:
Properties: P78 is identified by (identifies): E49 Time Appellation P79 beginning is qualified by: E62 String P80 end is qualified by: E62 String P81 ongoing throughout: E61 Time Primitive P82 at some time within: E61 Time Primitive P83 had at least duration (was minimum duration of): E54 Dimension P84 had at most duration (was maximum duration of): E54 Dimension P86 falls within (contains): E52 Time-Span E53 PlaceSubclass of: E1 CRM Entity Scope note: This class comprises extents in space, in particular on the surface of the earth, in the pure sense of physics: independent from temporal phenomena and matter. The instances of E53 Place are usually determined by reference to the position of “immobile” objects such as buildings, cities, mountains, rivers, or dedicated geodetic marks. A Place can be determined by combining a frame of reference and a location with respect to this frame. It may be identified by one or more instances of E44 Place Appellation. It is sometimes argued that instances of E53 Place are best identified by global coordinates or absolute reference systems. However, relative references are often more relevant in the context of cultural documentation and tend to be more precise. In particular, we are often interested in position in relation to large, mobile objects, such as ships. For example, the Place at which Nelson died is known with reference to a large mobile object – H.M.S Victory. A resolution of this Place in terms of absolute coordinates would require knowledge of the movements of the vessel and the precise time of death, either of which may be revised, and the result would lack historical and cultural relevance. Any object can serve as a frame of reference for E53 Place determination. The model foresees the notion of a “section” of an E19 Physical Object as a valid E53 Place determination. Examples:
Properties: P87 is identified by (identifies): E44 Place Appellation P89 falls within (contains): E53 Place P121 overlaps with: E53 Place P122 borders with: E53 Place E54 DimensionSubclass of: E1 CRM Entity Scope note: This class comprises quantifiable properties that can be measured by some calibrated means and can be approximated by values, i.e. points or regions in a mathematical or conceptual space, such as natural or real numbers, RGB values etc. An instance of E54 Dimension represents the true quantity, independent from its numerical approximation, e.g. in inches or in cm. The properties of the class E54 Dimension allow for expressing the numerical approximation of the values of an instance of E54 Dimension. If the true values belong to a non-discrete space, such as spatial distances, it is recommended to record them as approximations by intervals or regions of indeterminacy enclosing the assumed true values. For instance, a length of 5 cm may be recorded as 4.5-5.5 cm, according to the precision of the respective observation. Note, that interoperability of values described in different units depends critically on the representation as value regions. Numerical approximations in archaic instances of E58 Measurement Unit used in historical records should be preserved. Equivalents corresponding to current knowledge should be recorded as additional instances of E54 Dimension as appropriate. Examples:
Properties: P90 has value: E60 Number P91 has unit (is unit of): E58 Measurement Unit
E55 TypeSubclass of: E28 Conceptual Object Superclass of: E56 Language E57 Material E58 Measurement Unit Scope note: This class comprises concepts denoted by terms from thesauri and controlled vocabularies used to characterize and classify instances of CRM classes. Instances of E55 Type represent concepts in contrast to instances of E41 Appellation which are used to name instances of CRM classes. E55 Type is the CRM’s interface to domain specific ontologies and thesauri. These can be represented in the CRM as subclasses of E55 Type, forming hierarchies of terms, i.e. instances of E55 Type linked via P127 has broader term (has narrower term). Such hierarchies may be extended with additional properties. Examples:
Properties: P127 has broader term (has narrower term): E55 Type P150 defines typical parts of (define typical wholes for): E55 Type E56 LanguageSubclass of: E55 Type Scope note: This class is a specialization of E55 Type and comprises the natural languages in the sense of concepts. This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E56 Language, e.g.: “instances of Mandarin Chinese”. It is recommended that internationally or nationally agreed codes and terminology are used to denote instances of E56 Language, such as those defined in ISO 639:1988. Examples:
E57 MaterialSubclass of: E55 Type Scope note: This class is a specialization of E55 Type and comprises the concepts of materials. Instances of E57 Material may denote properties of matter before its use, during its use, and as incorporated in an object, such as ultramarine powder, tempera paste, reinforced concrete. Discrete pieces of raw-materials kept in museums, such as bricks, sheets of fabric, pieces of metal, should be modelled individually in the same way as other objects. Discrete used or processed pieces, such as the stones from Nefer Titi’s temple, should be modelled as parts (cf. P46 is composed of). This type is used categorically in the model without reference to instances of it, i.e. the Model does not foresee the description of instances of instances of E57 Material, e.g.: “instances of gold”. It is recommended that internationally or nationally agreed codes and terminology are used. Examples:
E59 Primitive ValueSuperclass of: E60 Number E61 Time Primitive E62 String
Examples:
E60 NumberSubclass of: E59 Primitive Value Scope Note: This class comprises any encoding of computable (algebraic) values such as integers, real numbers, complex numbers, vectors, tensors etc., including intervals of these values to express limited precision. Numbers are fundamentally distinct from identifiers in continua, such as instances of E50 Date and E47 Spatial Coordinate, even though their encoding may be similar. Instances of E60 Number can be combined with each other in algebraic operations to yield other instances of E60 Number, e.g., 1+1=2. Identifiers in continua may be combined with numbers expressing distances to yield new identifiers, e.g., 1924-01-31 + 2 days = 1924-02-02. Cf. E54 Dimension. Examples:
E61 Time PrimitiveSubclass of: E59 Primitive Value Scope Note: This class comprises instances of E59 Primitive Value for time that should be implemented with appropriate validation, precision and interval logic to express date ranges relevant to cultural documentation. E61 Time Primitive is not further elaborated upon within the model. Examples:
E62 StringSubclass of: E59 Primitive Value Scope Note: This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc. E62 String is not further elaborated upon within the model. Examples:
E63 Beginning of ExistenceSubclass of: E5 Event Superclass of: E12 Production E65 Creation E66 Formation E67 Birth E81 Transformation Scope note: This class comprises events that bring into existence any E77 Persistent Item. It may be used for temporal reasoning about things (intellectual products, physical items, groups of people, living beings) beginning to exist; it serves as a hook for determination of a terminus post quem and ante quem. Examples:
Properties: P92 brought into existence (was brought into existence by): E77 Persistent Item E64 End of ExistenceSubclass of: E5 Event Superclass of: E6 Destruction E68 Dissolution E69 Death E81 Transformation
Examples:
Properties: P93 took out of existence (was taken out of existence by): E77 Persistent Item E65 CreationSubclass of: E7 Activity E63 Beginning of Existence Superclass of: E83 Type Creation Scope note: This class comprises events that result in the creation of conceptual items or immaterial products, such as legends, poems, texts, music, images, movies, laws, types etc. Examples:
Properties: P94 has created (was created by): E28 Conceptual Object E66 FormationSubclass of: E7 Activity E63 Beginning of Existence Scope note: This class comprises events that result in the formation of a formal or informal E74 Group of people, such as a club, society, association, corporation or nation. E66 Formation does not include the arbitrary aggregation of people who do not act as a collective. The formation of an instance of E74 Group does not mean that the group is populated with members at the time of formation. In order to express the joining of members at the time of formation, the respective activity should be simultaneously an instance of both E66 Formation and E85 Joining. Examples:
Properties: P95 has formed (was formed by): E74 Group P151 was formed from (participated in): E74 Group E67 BirthSubclass of: E63 Beginning of Existence Scope note: This class comprises the births of human beings. E67 Birth is a biological event focussing on the context of people coming into life. (E63 Beginning of Existence comprises the coming into life of any living beings). Twins, triplets etc. are brought into life by the same E67 Birth event. The introduction of the E67 Birth event as a documentation element allows the description of a range of family relationships in a simple model. Suitable extensions may describe more details and the complexity of motherhood with the intervention of modern medicine. In this model, the biological father is not seen as a necessary participant in the E67 Birth event. Examples:
Properties: P96 by mother (gave birth): E21 Person P97 from father (was father for): E21 Person P98 brought into life (was born): E21 Person E69 DeathSubclass of: E64 End of Existence Scope note: This class comprises the deaths of human beings. If a person is killed, their death should be instantiated as E69 Death and as E7 Activity. The death or perishing of other living beings should be documented using E64 End of Existence. Examples:
Properties: P100 was death of (died in): E21 Person E70 ThingSubclass of: E77 Persistent Item Superclass of: E71 Man-Made Thing E72 Legal Object Scope note: This general class comprises usable discrete, identifiable, instances of E77 Persistent Item that are documented as single units. They can be either intellectual products or physical things, and are characterized by relative stability. They may for instance either have a solid physical form, an electronic encoding, or they may be logical concept or structure. Examples:
Properties: P43 has dimension (is dimension of): E54 Dimension P101 had as general use (was use of): E55 Type P130 shows features of (features are also found on): E70 Thing (P130.1 kind of similarity: E55 Type) E71 Man-Made ThingSubclass of: E70 Thing Superclass of: E24 Physical Man-Made Thing E28 Conceptual Object
Examples:
Properties: P102 has title (is title of): E35 Title (P102.1 has type: E55 Type) P103 was intended for (was intention of): E55 Type E72 Legal ObjectSubclass of: E70 Thing Superclass of: E18 Physical Thing E90 Symbolic Object Scope note: This class comprises those material or immaterial items to which instances of E30 Right, such as the right of ownership or use, can be applied. This is true for all E18 Physical Thing. In the case of instances of E28 Conceptual Object, however, the identity of the E28 Conceptual Object or the method of its use may be too ambiguous to reliably establish instances of E30 Right, as in the case of taxa and inspirations. Ownership of corporations is currently regarded as out of scope of the CRM. Examples:
Properties: P104 is subject to (applies to): E30 Right P105 right held by (has right on): E39 Actor E73 Information ObjectSubclass of: E89 Propositional Object E90 Symbolic Object Superclass of: E29 Design or Procedure E31 Document E33 Linguistic Object E36 Visual Item Scope note: This class comprises identifiable immaterial items, such as a poems, jokes, data sets, images, texts, multimedia objects, procedural prescriptions, computer program code, algorithm or mathematical formulae, that have an objectively recognizable structure and are documented as single units. An E73 Information Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. Instances of E73 Information Object of a linguistic nature should be declared as instances of the E33 Linguistic Object subclass. Instances of E73 Information Object of a documentary nature should be declared as instances of the E31 Document subclass. Conceptual items such as types and classes are not instances of E73 Information Object, nor are ideas without a reproducible expression. Examples:
Properties: E74 GroupSubclass of: E39 Actor Superclass of: E40 Legal Body Scope note: This class comprises any gatherings or organizations of two or more people that act collectively or in a similar way due to any form of unifying relationship. In the wider sense this class also comprises official positions which used to be regarded in certain contexts as one actor, independent of the current holder of the office, such as the president of a country. A gathering of people becomes an E74 Group when it exhibits organizational characteristics usually typified by a set of ideas or beliefs held in common, or actions performed together. These might be communication, creating some common ulgate, a common purpose such as study, worship, business, sports, etc. Nationality can be ulgate as membership in an E74 Group (cf. HumanML markup). Married couples and other concepts of family are regarded as particular examples of E74 Group. Examples:
Properties: P107 has current or former member (is current or former member of): E39 Actor (P107.1 kind of member: E55 Type) E77 Persistent ItemSubclass of: E1 CRM Entity Superclass of: E39 Actor E70 Thing
The main classes of objects that fall outside the scope the E77 Persistent Item class are temporal objects such as periods, events and acts, and descriptive properties. Examples:
E82 Actor AppellationSubclass of: E41 Appellation Scope note: This class comprises any sort of name, number, code or symbol characteristically used to identify an E39 Actor. An E39 Actor will typically have more than one E82 Actor Appellation, and instances of E82 Actor Appellation in turn may have alternative representations. The distinction between corporate and personal names, which is particularly important in library applications, should be made by explicitly linking the E82 Actor Appellation to an instance of either E21 Person or E74 Group/E40 Legal Body. If this is not possible, the distinction can be made through the use of the P2 has type mechanism. Examples:
E84 Information CarrierSubclass of: E22 Man-Made Object Scope note: This class comprises all instances of E22 Man-Made Object that are explicitly designed to act as persistent physical carriers for instances of E73 Information Object. This allows a relationship to be asserted between an E19 Physical Object and its immaterial information contents. An E84 Information Carrier may or may not contain information, e.g., a diskette. Note that any E18 Physical Thing may carry information, such as an E34 Inscription. However, unless it was specifically designed for this purpose, it is not an Information Carrier. Therefore the property P128 carries (is carried by) applies to E18 Physical Thing in general. Examples:
Properties: E89 Propositional ObjectSubclass of: E28 Conceptual Object Superclass of: E73 Information Object E30 Right Scope note: This class comprises immaterial items, including but not limited to stories, plots, procedural prescriptions, algorithms, laws of physics or images that are, or represent in some sense, sets of propositions about real or mental things and that are documented as single units or serve as topic of discourse. This class also comprises items that are “about” something in the sense of a subject. In the wider sense, this class includes expressions of psychological value such as non-figural art and musical themes. However, conceptual items such as types and classes are not instances of E89 Propositional Object. This should not be confused with the definition of a type, which is indeed an instance of E89 Propositional Object. Examples:
Properties: P67 refers to (is referred to by): E1 CRM Entity (P67.1 has type: E55 Type) P129 is about (is subject of): E1 CRM Entity P148 has component (is component of): E89 Propositional Object E90 Symbolic ObjectSubclass of: E28 Conceptual Object E72 Legal Object Superclass of: E73 Information Object E41 Appellation Scope note: This class comprises identifiable symbols and any aggregation of symbols, such as characters, identifiers, traffic signs, emblems, texts, data sets, images, musical scores, multimedia objects, computer program code or mathematical formulae that have an objectively recognizable structure and that are documented as single units. It includes sets of signs of any nature, which may serve to designate something, or to communicate some propositional content. An instance of E90 Symbolic Object does not depend on a specific physical carrier, which can include human memory, and it can exist on one or more carriers simultaneously. An instance of E90 Symbolic Object may or may not have a specific meaning, for example an arbitrary character string. In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized content model, such.. as the property P3 has note allows for describing this content model…P3.1 has type: E55 Type to specify the encoding.. Examples:
Properties: P106 is composed of (forms part of): E90 Symbolic Object Yüklə 1,5 Mb. Dostları ilə paylaş:
|