Data Portal @ linkeddatafragments.org

Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }

• BT36_Language comment "This class comprises the natural languages in the sense of concepts, i.e. the Model does not foresee the description of instances of BT36 Language, e.g.: “instances of French”.\n\nIt is recommended that internationally or nationally agreed codes and terminology are used to denote instances of BT36 Language, such as those defined in ISO 639:1988. [CIDOC CRM].".
• BT3_Physical_Thing_Type comment "This class comprises types of constellations of matter with a relative stability of any form sufficient to associate them with a persistent identity, such as being confined to certain extent, having a relative stability of form or structure, or containing a fixed amount of matter. In particular, it comprises physical things in the narrower sense and fluid bodies. It is an abstraction of physical substance for solid and non-solid things of matter.".
• BT4_Conceptual_Object_Type comment "This metaclass comprises types of identifiable immaterial items, such as, types of 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.".
• BT5_Legislative_Zone_Type comment "This class comprises types of extents in space where real world phenomenon can be observed or measured.".
• BT6_Human_Event_Type comment "This class comprises types of actions intentionally carried out by humans that result in changes of state in the scientific, social, or physical systems documented.".
• BT7_Ecosystem_Type comment "This metaclass comprises types of coherent ecological phenomena bounded in time and space. The coherence of these phenomena is given by the type of interaction characteristic for biological systems. This coherence identifies the ecosystem and not the associated spatio-temporal bounds. These bounds are a mere approximation of the actual process of growth, spread and retreat. Consequently, different ecosystems can overlap and coexist in time and space.".
• BT8_Abiotic_Element_Type comment "This metaclass comprises types of abiotic components of a type of Ecosystem.".
• BT9_Actor_Type comment "This class comprises types of human agents either individually or in groups, who have the potential to perform intentional actions for which they can be held responsible.".
• LC10_belongs_to comment "This property associates a physical thing like biotic or abiotic element with the biotic element or abiotic which is part of or member.".
• LC11_had_participant comment "This property describes the active or passive participation of instances of E39 Actors in an E5 Event. \n\nIt connects the life-line of the related E39 Actor with the E53 Place and E50 Date of the event. The property implies that the Actor was involved in the event but does not imply any causal relationship. The subject of a portrait can be said to have participated in the creation of the portrait.\n[Scope Note for P11 had participant (participated in) CIDOC CRM version 5.1.2]".
• LC12_assigned_attribute_to comment "This property indicates the item to which an attribute or relation is assigned.".
• LC13_is_carried_out_by comment "This property describes the active participation of a BC8 Actor in an BC43 Activity.".
• LC15_took_place_at comment "This property describes the spatial location of an instance of a BC4 Temporal Phenomenon. \n\nThe related BC3 Place should be seen as an approximation of the geographical area within which the phenomena that characterize the period in question occurred.".
• LC16_is_composed_of comment "This property allows instances of E18 Physical Thing to be analysed into component elements.\n\nComponent elements, since they are themselves instances of E18 Physical Thing, may be further analysed into sub-components, thereby creating a hierarchy of part decomposition. An instance of E18 Physical Thing may be shared between multiple wholes, for example two buildings may share a common wall.\n\nThis property is intended to describe specific components that are individually documented, rather than general aspects. Overall descriptions of the structure of an instance of E18 Physical Thing are captured by the P3 has note property.\n\nThe instances of E57 Materials of which an item of E18 Physical Thing is composed should be documented using P45 consists of (is incorporated in).\n\n[Scope Note for P46 is composed of (forms part of)CIDOC CRM version 5.1.2]".
• LC17_observed comment "This property identifies a thing, a feature, a phenomenon or its reaction that is observed by an activity of Observation.".
• LC19_has_dimension comment "This property records a E54 Dimension of some E70 Thing.\nIt is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.\n\nAn instance of E54 Dimension is specific to an instance of E70 Thing.\n[Scope Note for P43 has dimension (is dimension of)CIDOC CRM version 5.1.2]\nThis property records a E54 Dimension of some E70 Thing.\nIt is a shortcut of the more fully developed path from E70 Thing through P39 measured (was measured by), E16 Measurement P40 observed dimension (was observed in) to E54 Dimension. It offers no information about how and when an E54 Dimension was established, nor by whom.\n\nAn instance of E54 Dimension is specific to an instance of E70 Thing.\n[Scope Note for P43 has dimension (is dimension of)CIDOC CRM version 5.1.2]".
• LC1_is_identified_by comment "This property describes the naming or identification of any real world item by a name or any other identifier. \n\nThis property is intended for identifiers in general use, which form part of the world the model intends to describe, and not merely for internal database identifiers which are specific to a technical system, unless these latter also have a more general use outside the technical context. This property includes in particular identification by mathematical expressions such as coordinate systems used for the identification of instances of E53 Place. The property does not reveal anything about when, where and by whom this identifier was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through E15 Identifier Assignment.\n[Scope Note for P1 is identified by (identifies). CIDOC CRM version 5.1.2].".
• LC20_has_value comment "This property allows a BC5 Dimension to be approximated by Number primitive.".
• LC21_has_unit comment "This property shows the type of unit a BC5 Dimension was expressed in.".
• LC22_approximates comment "This property approximates an BC3 Place which is defined in the same reference space. The property does not state the quality or accuracy of the approximation, but states the intention to approximate the place.".
• LC23_is_expressed_in_terms_of comment "This property defines the coordinate reference system in terms of which a geometric place expression is formulated.".
• LC24_defines_place comment "This property associates an instance of BC34 Geometric Place Expression with the instance of BC20 Declarative Place it defines. Syntactic variants or use of different scripts may result in multiple instances of BC34 Geometric Place Expression defining exactly the same place. Transformations between different reference systems in general result in new definitions of places approximating each other.".
• LC27_has_section comment "This property links an area to the instance of E18 Physical Thing upon which it is found.\n\n[Scope Note for P59 has section (is located on or within)CIDOC CRM version 5.1.2]".
• LC28_has_dimension comment "This property records a BC5 Dimension of a BC9 Observable Entity.\nIt is a shortcut of the more fully developed path from a BC9 Observable Entity through LC37 measured (was measured by), BC54 Measurement LC34 observed dimension (was observed in) to BC5 Dimension. It offers no information about how and when an E54 Dimension was established.".
• LC29_had_output comment "This property associates an instance of BC56 Digital Measurement Event with an instance of BC23 Digital Object which is the output of the activity.".
• LC2_refers_to comment "This property documents that a BC18 Proposition makes a statement about an instance of BC1 TLO Entity.".
• LC30_had_input comment "This property associates an instance of BC56 Digital Measurement Event with an instance of BC23 Digital Object which is the input used to specify the machine action.".
• LC31_used_software comment "This property associates an instance of BC56 Digital Measurement Event with the instance of BC59 Software.".
• LC32_happened_on_device comment "This property associates an instance of BC56 Digital Measurement Event with the instance of BC58 Digital Device that had used.".
• LC33_captures comment "This property associates an instance of BC61 Capture Activity with the instance of BC57 Capture.".
• LC34_observed_dimension comment "This property records the dimension that was observed in an E16 Measurement Event.\nE54 Dimension can be any quantifiable aspect of E70 Thing. Weight, image colour depth and monetary value are dimensions in this sense. One measurement activity may determine more than one dimension of one object.\nDimensions may be determined either by direct observation or using recorded evidence. In the latter case the measured Thing does not need to be present or extant. [Scope Note for P40 observed dimension (was observed in)CIDOC CRM version 5.1.2].".
• LC35_describes comment "This property associates an instance of SP4 Spatial Coordinate Reference System with the instance of SP3 Reference Space for which it can be used to describe locations. [Scope Note for Q7 Describes CRMgeo].".
• LC36_is_fixed_on comment "This property defines the physical reference features that ground a spatial coordinate reference system in the real world. [Scope Note for Q8 is fixed on CRMgeo].".
• LC37_measured comment "This property associates an instance of E16 Measurement with the instance of E1 CRM Entity to which it applied. An instance of E1 CRM Entity may be measured more than once. Material and immaterial things and processes may be measured, e.g. the number of words in a text, or the duration of an event. \n[Scope Note for P39 measured (was measured by)CIDOC CRM version 5.1.2].".
• LC38_folls_within_or_overlaps comment "This property identifies the instances of Places that overlaps or fall within the area covered by another Place.".
• LC43_occupied comment "This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime.\n\n [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].".
• LC44_has_temporal_projection comment "This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime.\n\n [Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].".
• LC45_has_spatial_projection comment "This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime.\n\n[Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM].".
• LC46_observed_value comment "This property associates an instance of E4 Period with the real (phenomenal) 4 dimensional point set (volume) in spacetime that it has occupied. The associated instance of E92 Spacetime Volume includes the trajectories of the participating physical things during their participation in the instance of E4 Period, the open spaces via which they have interacted and the spaces by which they had the potential to interact during that period or event in the way defined by the type of the respective period or event, such as the air in a meeting room transferring the voices. Another example are the areas controlled by some military power. In general, instances of E4 Period have fuzzy boundaries in spacetime.\n[Scope Note P74 has current or former residence (is current or former residence of) CIDOC CRM]".
• LC47_took_place_at comment "This property associates an instance of BC61 Capture Activity with an instance of BC3 Place at which the capture activity found or captured things. It identifies the narrower spatial location in which a thing was found at. This maybe known or given in absolute terms or relative to the thing found. It describes a position within the area in which the instance of the encounter event occurred and found something.".
• LC48_assigned_dimension comment "This property associates an instance of BC61 Capture Activity with an instance of BC3 Place at which the capture activity found or captured things. It identifies the narrower spatial location in which a thing was found at. This maybe known or given in absolute terms or relative to the thing found. It describes a position within the area in which the instance of the encounter event occurred and found something.".
• LC4_has_appellation comment "This property associates an instance of BC1 TLO Entity with an instance of BC30 Appellation. This property is intended for names in general use. The property does not reveal anything about when, where and by whom this name was used. A more detailed representation can be made using the fully developed (i.e. indirect) path through BC46 Identifier Assignment.".
• LC5_has_time_span comment "This property describes the temporal bounds of an instance of an E2 Temporal Phenomenon.".
• LC6_has_alternative_form comment "This property establishes a relationship of equivalence between two instances of E41 Appellation independent from any item identified by them. It is a dynamic asymmetric relationship, where the range expresses the derivative, if such a direction can be established. Otherwise, the relationship is symmetric. The relationship is not transitive.\n\nThe equivalence applies to all cases of use of an instance of E41 Appellation. Multiple names assigned to an object, which are not equivalent for all things identified with a specific instance of E41 Appellation, should be modelled as repeated values of P1 is identified by (identifies). \n\n[Scope Note for P139 has alternative form CIDOC CRM version 5.1.2]".
• LC7_is_about comment "This property documents that an E89 Propositional Object has as subject an instance of E1 CRM Entity. \n\nThis differs from P67 refers to (is referred to by), which refers to an E1 CRM Entity, in that it describes the primary subject or subjects of an E89 Propositional Object.\n[Scope Note for P129 is about (is subject of) CIDOC CRM version 5.1.2]".
• LC8_occured_in_the_presence_of comment "This property describes the active or passive presence of an E77 Persistent Item in an E5 Event without implying any specific role. \n\nIt connects the history of a thing with the E53 Place and E50 Date of an event. For example, an object may be the desk, now in a museum on which a treaty was signed. The presence of an immaterial thing implies the presence of at least one of its carriers.\n\n[Scope Note for P12 occurred in the presence of (was present at) CIDOC CRM version 5.1.2]".
• LC9_assigned comment "This property indicates the attribute that was assigned or the item that was related to the item denoted by a property P140 assigned attribute to in an Attribute assignment action.\n[Scope Note for P141 assigned (was assigned by) CIDOC CRM version 5.1.2]".
• LT1_usually_is_identified_by comment "This property describes the type of appellation of a TLO entity type.".
• LT2_usually_consists_of comment "This property describes the types of components of an Temporal Phenomenon Type.".
• LT3_usaually_is_component_of comment "This property connects the type of a biotic element with the type of the Ecosystem where it lives.".
• LT4_usually_use_to_appear comment "This property connects the type of a biotic element with the type of a biotic element where it appears.".
• LT5_usually_is_predator_of comment "This property connects the types of predators with their prey type.".
• LT6_usually_is_about comment "This property associates a type of a conceptual object such as propositions or appellations with an entity type.".
• LT7_usually_is_carried_out_by comment "This property associates a type of activity with a type of actor.".
• LT8_usually_belongs_to comment "This property associates a type of biotic element with the type of biotic element which is part of or member.".
• LX1_is_identified_by comment "This property describes the types of identifiers, names or labels of any marineTLO item type.".
• LX2_is_about_type comment "This property documents that an instance of BC17 Conceptual Object is a subject of an instance of BT1 TLO Entity Type.".
• LX3_has_type comment "This property allows sub typing of MarineTLO entities - a form of specialisation – through the use of a terminological hierarchy, or thesaurus.".
• LX4_has_appellation comment "This property associates an instance of BT1 TLO Entity Type with an instance of BC7 Appellation.".
• LX6_assigned_attribute_to_type comment "This property indicates the type of item to which an attribute or relation is assigned.".
• LX7_observed_propery comment "This property identifies the type of Property that is observed by an activity of BC45 Observation. It describes assertions about types of properties of things.".
• LX8_has_language comment "This property declares the Language of a BC18 Proposition.".
• O3_has_note comment "This property associates an entity to MarineTLO Environment with abstraction levels where it is defined.".
• Configuration comment "Based on the fact that a measurement is carried out by an agent using a specific metric according to one (or more) configurations over one (or more) datasets (atomic or composite) and produces a value (i.e. literal). The Configuration defines the polices with respect to a measurement is carried out. It defines polices about how to compare URIs and the configuration of an entity.".
• EntityConfiguration comment "The notion of Configuration concerns issues that explain how the measurement was done. At this point, and for the requirements at hand, we need two subclasses: the first concerns the way URI equivalence is defined (see URIEquivalence class), while the second (the EntityConfiguration class) concerns how the entities of interest are defined. Regarding the latter the current modeling allows someone to specify the desired set of entities by providing a SPARQL query that returns them.".
• Measurement comment "The notion of Measurement is actually a specialization of dc:Event and therefore inherits the property date. A measurement is carried out by an agent using a specific metric according to one (or more) configurations over one (or more) datasets (atomic or composite) and produces a value (i.e. literal).".
• Metrics comment "A metric is an individual with a URI and is defined by a resource (e.g. the DOI of the scientific paper that defined that metric).".
• URIEquivalence comment "The notion of Configuration concerns issues that explain how the measurement was done. At this point, and for the requirements at hand, we need two subclasses: the first concerns the way URI equivalence is defined (see URIEquivalence class), while the second (the EntityConfiguration class) concerns how the entities of interest are defined. Regarding the latter the current modeling allows someone to specify the desired set of entities by providing a SPARQL query that returns them.".
• over comment "A measurement is carried out by an agent using a specific metric according to one (or more) configurations over one (or more) datasets (atomic or composite) and produces a value (i.e. literal). Therefore, this property links instances of Measurement class with instances of dataset class.".
• producesValue comment "A measurement is carried out by an agent using a specific metric according to one (or more) configurations over one (or more) datasets. Therefore, this property indicates the value produced by the measurement.".
• Business comment "A business is a legal entity which is permitted to enter into a contract with another entity.".
• Business comment "Un business est une entité morale comme une organisation, une entreprise, une association ou une agence...".
• BusinessInformation comment "Identité associée uniquement à une personne morale.".
• CellPhoneData comment "Les données correspondant à l'appareil mobile.".
• Certificate comment "Il s'agit de l'élèment de l'identité qui permettera l'authentification de l'utilisateur, du fournisseur de service ainsi que l'émetteur de l'identité.".
• Certificate comment "This structure is used to specify identity certificates.".
• ContactInformation comment "Les informations nécessaires pour contacter un agent.".
• ContactInformation comment "Required information to contact an agent.".
• Date comment "The date structure specifies a date. Date information can be used in different ways, depending on the context.".
• Group comment "A group of persons that figure in the contact list of an individual.".
• Group comment "Un groupe des personnes qui constituent la liste des contacts d'un individu.".
• IdentityInformation comment "Identity information of a legal or natural entity.".
• IdentityInformation comment "Les informations relatives à une identité numérique d'une personne physique ou morale.".
• Individual comment "Indivuals or natural entities.".
• Individual comment "L'ensemble des personnes physiques.".
• IndividualInformation comment "Identité associée uniquement à une personne physique.".
• Issuer comment "L'émetteur d'une identité numérique (opérateur téléphonique par exemple).".
• Issuer comment "This legal entity is the issuer of an individual digital identity.".
• LocationData comment "Les données de locations permettant de localiser le porteur de l'identité.".
• Login comment "IDs ans Passwords for web services which require authentification.".
• MiscData comment "Photos, videos, sms, documents, notes, call logs, cookies...".
• Name comment "The person name specifies information about the naming of a person.".
• Online comment "Les adresses électroniques pour contacter un agent.".
• Online comment "Online information about an agent.".
• OnlineAccount comment "Les comptes en ligne de l'utilisateur.".
• Person comment "A person is an individual who has a social identity and a technical one.".
• Person comment "Une personne est un individu qui possède une identité numérique et qui cherche à protéger sa vie privée.".
• Postal comment "Postal mailing address.".
• Telecommunication comment "Telecommunication information about an agnet.".
• TelephoneNumber comment "The characteristics of a telephone number.".

• first
• previous
• next