Skip to content

Commit

Permalink
small fixes
Browse files Browse the repository at this point in the history
  • Loading branch information
@BOberreither
BOberreither committed Nov 15, 2024
1 parent a061e65 commit 52797d4
Show file tree
Hide file tree
Showing 2 changed files with 38 additions and 31 deletions.
31 changes: 17 additions & 14 deletions INTRO_beta202408.owl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -504,7 +504,7 @@
</owl:unionOf>
</owl:Class>
</rdfs:range>
<rdfs:comment xml:lang="en">Links an INT Interpretation to the INT3 Interrelation or the INT2 Actualization of Feature it identifies.</rdfs:comment>
<rdfs:comment xml:lang="en">Links an INT Identification or INT Interpretation to the INT3 Interrelation or the INT2 Actualization of Feature it identifies.</rdfs:comment>
<rdfs:label xml:lang="en">R21 identifies</rdfs:label>
</owl:ObjectProperty>

Expand Down Expand Up @@ -627,7 +627,7 @@
</owl:unionOf>
</owl:Class>
</rdfs:range>
<rdfs:comment xml:lang="en">Links any INT3 Interrelation to a text or image (on any ontological level) or INT2 Actualization of Feature that is part of the INT3 Interrelation. The skos:boradMatch states that this property is a more specific version of oa:hasTarget in the sense that the INT3 Interrelation can be seen as an annotation, the texts/images linked by this relationship as their targets.</rdfs:comment>
<rdfs:comment xml:lang="en">Links any INT3 Interrelation to a text or image (on any ontological level) or INT2 Actualization of Feature that is part of the INT3 Interrelation. The skos:broadMatch states that this property is a more specific version of oa:hasTarget in the sense that the INT3 Interrelation can be seen as an annotation, the texts/images linked by this relationship as their targets.</rdfs:comment>
<rdfs:label xml:lang="en">R24 has related entity</rdfs:label>
<skos:broadMatch rdf:resource="http://www.w3.org/ns/oa#hasTarget"/>
</owl:ObjectProperty>
Expand Down Expand Up @@ -696,7 +696,7 @@
<owl:inverseOf rdf:resource="https://w3id.org/lso/intro/beta202408#R3_constellates"/>
<rdfs:domain rdf:resource="https://w3id.org/lso/intro/beta202408#INT2_ActualizationOfFeature"/>
<rdfs:range rdf:resource="https://w3id.org/lso/intro/beta202408#INT_Constellation"/>
<rdfs:label xml:lang="en">R3i ist constellated by</rdfs:label>
<rdfs:label xml:lang="en">R3i is constellated by</rdfs:label>
</owl:ObjectProperty>


Expand Down Expand Up @@ -937,7 +937,7 @@
<rdfs:domain rdf:resource="https://w3id.org/lso/intro/beta202408#INT4_Feature"/>
<rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#string"/>
<rdfs:comment xml:lang="en">Links a feature to a data string defining or describing it more closely.</rdfs:comment>
<rdfs:label xml:lang="en">R42 has specification</rdfs:label>
<rdfs:label xml:lang="en">R43 has specification</rdfs:label>
</owl:DatatypeProperty>


Expand Down Expand Up @@ -1041,7 +1041,7 @@
<rdfs:comment xml:lang="en">The INT1 Passage is a means of modelling an identifiable part of an E73 Information Object or its subclasses – without that part being removed from its source Information Object.
For examples, see subclass comments.
The skos:broadMatch states that the INT1 Passage can be regarded as an oa:SpecificResource in the sense that it is a section of a resource.
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R42 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT1 Passage&apos;s location.</rdfs:comment>
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R41 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT1 Passage&apos;s location.</rdfs:comment>
<rdfs:label xml:lang="en">INT1 Passage</rdfs:label>
<skos:broadMatch rdf:resource="http://www.w3.org/ns/oa#SpecificResource"/>
</owl:Class>
Expand Down Expand Up @@ -1080,7 +1080,8 @@

<owl:Class rdf:about="https://w3id.org/lso/intro/beta202408#INT4_Feature">
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E28_Conceptual_Object"/>
<rdfs:comment xml:lang="en">This class comprises features that &apos;are in&apos; or &apos;can be found in&apos; or &apos;can be read out of&apos; a text or an image. INT2 Actualizations of these features are the results of a receptive process that identifies the specific form the INT4 Feature – a distinct abstract concept, itself separate from the text or image – takes in the text or image. This class therefore has a wide scope. Its domain could be divided into subclasses following any number of different ratios; to avoid the resulting restrictions and/or complex hierarchies, the actual subclasses of the INT4 Receptional Entity represent diverse approaches to its subject matter, covering medial aspects as well as aspect of form and semantics. They can be populated resp. extended with custom subclasses based e.g. on relevant reference works: The class INT8 Rhetorical Feature could contain concepts based on classical rhetoric like allegory or personification, but would of course also include the pictorial pendants of these tropes. Lemmata from handbooks of poetic terms as well as concepts of pictorial composition could populate the INT10 Formal Feature resp. its (sub-)subclasses. Subclasses of INT9 Semantic Feature could be extended using art thesauri as well as handbooks on literary motives.</rdfs:comment>
<rdfs:comment xml:lang="en">This class comprises features that &apos;are in&apos; or &apos;can be found in&apos; or &apos;can be read out of&apos; a text or an image. INT2 Actualizations of these features are the results of a receptive process that identifies the specific form the INT4 Feature – a distinct abstract concept, itself separate from the text or image – takes in the text or image. This class therefore has a wide scope. Its domain could be divided into subclasses following any number of different ratios; to avoid the resulting restrictions and/or complex hierarchies, the actual subclasses of the INT4 Feature represent diverse approaches to its subject matter, covering medial aspects as well as aspect of form and semantics. They can be populated resp. extended with custom subclasses based e.g. on relevant reference works: The class INT8 Rhetorical Feature could contain concepts based on classical rhetoric like allegory or personification, but would of course also include the pictorial pendants of these tropes. Lemmata from handbooks of poetic terms as well as concepts of pictorial composition could populate the INT10 Formal Feature resp. its (sub-)subclasses. Subclasses of INT9 Semantic Feature could be extended using art thesauri as well as handbooks on literary motives.
For external thesauri and vocabularies see, e. g., ICONCLASS, the Getty Art and Architecture Thesaurus, the Getty Cultural Objects Name Authority, the Getty Union List of Artist Names, the Literary Theme Ontology (LTO), the Document Components Ontology, the OntoPoetry Ontology, the Taxonomy of Themes and Motifs (TTM2) ...</rdfs:comment>
<rdfs:label xml:lang="en">INT4 Feature</rdfs:label>
</owl:Class>

Expand Down Expand Up @@ -1210,7 +1211,8 @@
<rdfs:subClassOf rdf:resource="http://www.cidoc-crm.org/cidoc-crm/E89_Propositional_Object"/>
<rdfs:subClassOf rdf:resource="https://w3id.org/lso/intro/beta202408#INT9_SemanticFeature"/>
<rdfs:subClassOf rdf:resource="https://w3id.org/lso/intro/beta202408#INT_PragmaticFeature"/>
<rdfs:comment xml:lang="en">This class comprises references to – usually: real – identifiable objects of any kind. It is not restricted to non-fictional texts resp. images depicting real life objects or events, but can be most easily identified there.</rdfs:comment>
<rdfs:comment xml:lang="en">This class comprises references to – usually: real – identifiable objects of any kind. It is not restricted to non-fictional texts resp. images depicting real life objects or events, but can be most easily applied there. The CIDOC CRM property P67 refers to is recommended to establish the link to the entity referred to. However, there are two options: P67 can link this INT18 Reference (or any other feature) to the external entity, but it can also link the corresponding actualization of said feature to the external entity. This depends on the respective theoretical framework and is not specified in the context of this ontology.
(The scope of this class also includes references to other images/texts, if one wants to model an interrelation this way.)</rdfs:comment>
<rdfs:label xml:lang="en">INT18 Reference</rdfs:label>
</owl:Class>

Expand All @@ -1225,7 +1227,7 @@
- The first four lines of Rilke&apos;s poem &quot;Archaischer Torso Apollos&quot;
- The last item on a shopping list.
The skos:broadMatch states that the INT21 TextPassage can be regarded as an oa:SpecificResource in the sense that it is a section of a resource.
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R42 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT21 TextPassage&apos;s location.</rdfs:comment>
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R41 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT21 TextPassage&apos;s location.</rdfs:comment>
<rdfs:label xml:lang="en">INT21 Text Passage</rdfs:label>
<skos:broadMatch rdf:resource="http://www.w3.org/ns/oa#SpecificResource"/>
</owl:Class>
Expand All @@ -1245,7 +1247,7 @@
- The part of Piranesi&apos;s The Drawbridge, 2nd version, showing a drawbridge.

The skos:broadMatch states that the INT22 ImageArea can be regarded as an oa:SpecificResource in the sense that it is a section of a resource.
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R42 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT22 ImageArea&apos;s location.</rdfs:comment>
The skos:broadMatch between R41 hasLocation and oa:hasSelector indicates that by replacing R41 hasLocation with oa:hasSelector, multiple selector options from the Web Annotation Ontology can be utilized to specify the INT22 ImageArea&apos;s location.</rdfs:comment>
<skos:broadMatch rdf:resource="http://www.w3.org/ns/oa#SpecificResource"/>
</owl:Class>

Expand Down Expand Up @@ -1484,8 +1486,6 @@
<rdfs:label xml:lang="en">INT Genre</rdfs:label>
</owl:Class>



<!-- https://w3id.org/lso/intro/beta202408#INT_GenreSpecifics -->

<owl:Class rdf:about="https://w3id.org/lso/intro/beta202408#INT_GenreSpecifics">
Expand Down Expand Up @@ -1714,7 +1714,12 @@
<rdfs:label xml:lang="en">INT Temporally Defined Architext</rdfs:label>
</owl:Class>


<!-- https://w3id.org/lso/intro/beta202408#INT_TextType -->

<owl:Class rdf:about="https://w3id.org/lso/intro/beta202408#INT_TextType">
<rdfs:subClassOf rdf:resource="https://w3id.org/lso/intro/beta202408#INT6_Architext"/>
<rdfs:label xml:lang="en">INT Text Type</rdfs:label>
</owl:Class>

<!-- https://w3id.org/lso/intro/beta202408#INT_Theme -->

Expand Down Expand Up @@ -1777,8 +1782,6 @@
<rdfs:label xml:lang="en">INT Type of Place</rdfs:label>
</owl:Class>



<!-- https://w3id.org/lso/intro/beta202408#INT_TypicalObject -->

<owl:Class rdf:about="https://w3id.org/lso/intro/beta202408#INT_TypicalObject">
Expand Down
Loading

0 comments on commit 52797d4

Please sign in to comment.