There are 1 input files: /usr/local/archivo-data/ontologydesignpatterns.org/ont--dul--DUL--owl/2025.10.17-074842/ont--dul--DUL--owl_type=parsed.ttl Start loading Finished loading in 00:00:01.419 Input size: Classes = 80, Properties = 132, Individuals = 0 Expressivity: SRIQ(D) Start consistency check Finished consistency check in 00:00:00.021 Timer summary:
<http://purl.org/dc/elements/1.1/creator> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://purl.org/dc/elements/1.1/date> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#comment> "Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#comment> "An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#subClassOf> _:genid42 . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#subClassOf> _:genid43 . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent> <http://www.w3.org/2000/01/rdf-schema#comment> "Additional comment: a computational agent can be considered as a PhysicalAgent that realizes a certain class of algorithms (that can be considered as instances of InformationObject) that allow to obtain some behaviors that are considered typical of agents in general. For an ontology of computational objects based on DOLCE see e.g. http://www.loa-cnr.it/COS/COS.owl, and http://www.loa-cnr.it/KCO/KCO.owl." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent> <http://www.w3.org/2000/01/rdf-schema#comment> "Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community)." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Amount> <http://www.w3.org/2000/01/rdf-schema#comment> "A quantity, independently from how it is measured, computed, etc." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Classification> <http://www.w3.org/2000/01/rdf-schema#comment> "A special kind of Situation that allows to include time indexing for the classifies relation in situations. For example, if a Situation s 'my old cradle is used in these days as a flower pot' isSettingFor the entity 'my old cradle' and the TimeIntervals '8June2007' and '10June2007', and we know that s satisfies a functional Description for aesthetic objects, which defines the Concepts 'flower pot' and 'flower', then we also need to know what concept classifies 'my old cradle' at what time.\nIn order to solve this issue, we need to create a sub-situation s' for the classification time: 'my old cradle is a flower pot in 8June2007'. Such sub-situation s' isPartOf s." .
@prefix sh: <http://www.w3.org/ns/shacl#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . [] a sh:ValidationReport ; sh:conforms false ; sh:result [ a sh:ValidationResult ; sh:focusNode <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> ; sh:resultMessage "Archivo requires either dct:abstract, dct:description or dc:description for a short comment about the ontology."@en ; sh:resultSeverity sh:Violation ; sh:sourceConstraintComponent sh:OrConstraintComponent ;
<?xml version="1.0" encoding="utf-8"?> <rdf:RDF xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns="http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#"> <rdf:Description rdf:about="http://www.ontologydesignpatterns.org/ont/dul/DUL.owl"> <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Ontology"/> </rdf:Description> <rdf:Description rdf:about="http://www.ontologydesignpatterns.org/ont/dul/DUL.owl"> <rdfs:comment>The DOLCE+DnS Ultralite ontology. It is a simplification of some parts of the DOLCE Lite-Plus library (cf. http://www.ontologydesignpatterns.org/ont/dul/DLP397.owl). Main aspects in which DOLCE+DnS Ultralite departs from DOLCE Lite-Plus are the following:
@prefix dct: <http://purl.org/dc/terms/> . @prefix sh: <http://www.w3.org/ns/shacl#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . [] a sh:ValidationReport ; sh:conforms false ; sh:result [ a sh:ValidationResult ; sh:focusNode <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> ; sh:resultMessage "No dct:license statement found"@en ; sh:resultPath dct:license ;
@prefix : <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix xml: <http://www.w3.org/XML/1998/namespace> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @base <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> rdf:type owl:Ontology ; rdfs:comment """The DOLCE+DnS Ultralite ontology.
<?xml version="1.0" encoding="UTF-8"?> DOLCE+DnS Ultralite DOLCE+DnS Ultralite $(document).ready( function () { jQuery(".markdown").each(function(el){ jQuery(this).after(marked(jQuery(this).text())).remove()}); var list = $('a[name=" http://www.ontologydesignpatterns.org/ont/dul/DUL.owl "]'); if (list.size() != 0) {
<http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Ontology> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/2000/01/rdf-schema#comment> "The DOLCE+DnS Ultralite ontology.\nIt is a simplification of some parts of the DOLCE Lite-Plus library (cf. http://www.ontologydesignpatterns.org/ont/dul/DLP397.owl). \nMain aspects in which DOLCE+DnS Ultralite departs from DOLCE Lite-Plus are the following:\n\n- The names of classes and relations have been made more intuitive\n- The DnS-related part is closer to the newer 'constructive DnS' ontology (http://www.ontologydesignpatterns.org/ont/dul/cDnS.owl).\n- Temporal and spatial relations are simplified\n- Qualities and regions are more relaxed than in DOLCE-Full: they can be used as attributes of any entity; an axiom states that each quality has a region\n- Axiomatization makes use of simpler constructs than DOLCE Lite-Plus\n- The architecture of the ontology is pattern-based, which means that DOLCE+DnS Ultralite is also available in modules, called 'content ontology design patterns', which can be applied independently in the design of domain ontologies (cf. http://www.ontologydesignpatterns.org). If many modules are needed in a same ontology project, it is anyway useful to use this integrated version.\n\nThe final result is a lightweight, easy-to-apply foundational ontology for modeling either physical or social contexts.\nSeveral extensions of DOLCE+DnS Ultralite have been designed: \n- Information objects: http://www.ontologydesignpatterns.org/ont/dul/IOLite.owl \n- Systems: http://www.ontologydesignpatterns.org/ont/dul/SystemsLite.owl \n- Plans: http://www.ontologydesignpatterns.org/ont/dul/PlansLite.owl\n- Legal domain: http://www.ontologydesignpatterns.org/ont/dul/CLO/CoreLegal.owl\n- Lexical and semiotic domains: http://www.ontologydesignpatterns.org/ont/lmm/LMM_L2.owl\n- DOLCE-Zero: http://www.ontologydesignpatterns.org/ont/d0.owl is a commonsense-oriented generalisation of some top-level classes, which allows to use DOLCE with tolerance against ambiguities like abstract vs. concrete information, locations vs. physical artifacts, event occurrences vs. event types, events vs. situations, qualities vs. regions, etc.; etc." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/2000/01/rdf-schema#label> "DOLCE+DnS Ultralite" . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/2002/07/owl#versionInfo> "4.2"^^<http://www.w3.org/2001/XMLSchema#decimal> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/2002/07/owl#versionInfo> "Created by Aldo Gangemi as both a simplification and extension of DOLCE and Descriptions and Situations ontologies." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> <http://www.w3.org/2002/07/owl#versionInfo> "In 3.2, the links between instances of Region or Parameter, and datatypes have been revised and made more powerful, in order to support efficient design patterns for data value modelling in OWL1.0.\nAlso, the names of the related properties have been changed in order to make them more intuitive.\nFurthermore, a large comment field has been added to the 'expresses' object property, in order to clarify some issues about the many interpretations.\nIn 3.3, the relation between regions, parameters, and datatypes has been still improved.\nIn 3.5, the person-related classes have been refactored: Person in 3.4 is now SocialPerson, to avoid confusion with commonsense intuition; Person is now the union of social persons and humans, therefore being a subclass of Agent.\nIn 3.6, other fixes on universal restriction involving expresses. Also added the property 'isConstraintFor' between parameters and entities. Moved the properties: 'assumes' and 'adopts' to the new module: http://www.ontologydesignpatterns.org/ont/dul/Conceptualization.owl.\nIn 3.7, some fixes on the names of classes and properties related to FormalEntity; created a new separate module for general universal restrictions (DULGCI.owl).\nIn 3.8, more fixes on the interface to formal entities and links to IOLite.owl.\nIn 3.9, some naming and comment fixes.\nIn 3.10, removed cardinality restriction from hasPart and isPartOf restrictions (changed to hasComponent and isComponentOf), for OWL(DL) compatibility. Also enlarged the range of includesAgent to contain both social and physical agents, and of conceptualizes universal restriction on agents, to include all social objects.\nIn 3.11, some more subproperty axioms have been introduced, and all elements have got English labels.\nIn 3.12, added some classes to map some old DolceLitePlus classes that were used to align OntoWordNet.\nIn 3.13, added the LocalConcept class to express a Concept that cannot be used in a Description different from the one that defines it. Also updated some comments.\nIn 3.14, added some comments.\nIn 3.15, removed some owl:disjointWith axioms relating Collection to InformationObject, Description, Situation, and SocialAgent. The rationale for doing that is to allow less strict constraints on domain relations involving collections that can be also conceived as descriptions, situations, social agents, or information objects; for example: a collection of sentences from a text (an information object) that are ranked with a relevance criterion can be still considered a text.\nIn 3.16, name of isActedBy changed to actsThrough, which is clearer. Also added SpatioTemporalRegion as constituted by a SpaceRegion and a TimeInterval.\nIn 3.17, removed redundant universal axioms from Entity and other top classes. Fixed restrictions on FunctionalSubstance class, and comments in Design and Substance classes.\nIn 3.18, removed subClassOf axiom from FunctionalSubstance to DesignedArtifact, created a new subclass of FunctionalSubstance, called DesignedSubstance, and created a subClassOf axiom from DesignedSubstance to DesignedArtifact.\nIn 3.19, removed disjointness axiom between Concept and Collection (the same rationale applies as in 3.15 version.\nIn 3.20, revised the comment for Quality, added InformationEntity as the superclass for InformationObject and InformationRealization (represented as the union of those classes). This is needed in many domain ontologies that do not need to distinguish between abstract and concrete aspects of information entities. One possible revision (not implemented here) would be to introduce the relations: expresses and isAbout with a broader domain:InformationEntity, and two more specific properties: abstractlyExpresses and isAbstractlyAbout. This last revision has not been implemented yet, since a large revision procedure should be carried out in order to check the impact of the revision on the existing DOLCE-DnS-Ultralite plugins.\nIn 3.21, added comment to InformationEntity, and optimized representation of equivalence for InformationRealization.\nIn 3.22, added comment to Personification.\nIn 3.23, added associatedWith object property, and put all object properties as subproperties of it.\nIn 3.24, removed hasProxy datatype property.\nIn 3.25, generalized domain and range of hasComponent and isComponentOf.\nIn 3.26, updated some comments in order to clarify or exemplify the concepts.\nIn 3.27, added rdfs:isDefinedBy annotations for Linked Data browsers.\nIn 3.28, broadened the universe of pre-/post-conditions to give room to events and states.\nIn 3.29, added some properties to support DBpedia alignment: sameSettingAs (situational analogous to coparticipation), including relations originating e.g. from sharing kinship, ownership, or roleplaying situations.\nIn 3.30, completed some domains and ranges (formerly owl:Thing, now dul:Entity), and added axiom: Organism subClassOf PhysicalAgent.\nIn 3.31, added a restriction to Quality and one to Region in order to ensure the original DOLCE constraint of qualities being always associated with a region, and vice versa. These axioms do not however exclude a direct applicability of qualities or regions to any other entity.\nIn 3.32, removed redundant union axioms and some restrictions, which spot a negative trade-off between expressivity and complexity.\nIn 3.33, added the ObjectAggregate class, added two property chains for coparticipation and same situation setting, updated some comments, added an axiom to Transition.\nIn 3.34, extended mereological support for parthood, introducing hasPropertPart (transitive) as a middle property between hasPart (transitive and reflexive) and hasComponent (asymmetric). This solution uses then \"reflexive reduction\" and \"transitive reduction\" design patterns (they allow to grant property characteristics through the superproperties, but not in the subproperties). Technically, mereology axioms would require that also hasProperPart be asymmetric, however a direct subproperty of an OWL non-simple property (hasPart) cannot be also asymmetric, hence the approximation. \nAdded a n-ary parthood class in order to suggest an alternative pattern for time- (and space-)indexed part relations. In order to ensure that property characteristics hold also with parthood n-ary, a property chain is introduced which infers a direct dul:partOf property for each parthood individual.\nAdded a dul:realizesSelfInformation propery in order to enable local reflexivity ('Self') axioms for all information realizations.\n\nIn 4.0, some foundational changes are introduced. \n- Firstly, the temporally indexed versions of some properties are introduced as subclasses of Situation (following the n-ary relation pattern), so covering relations from DOLCE that were skipped because of their larger arity. - \n- Secondly, D&S's Situation class is extracted from DOLCE top-level distinctions (it used to be a subclass of SocialObject), put as a primitive class under Entity, and not disjoint from any other class. Since we are relaxing the semantics of Situation, this change is fully compatible with previous versions of DUL.\nThe reason for the change is that it may sound counterintuitive (as many have noticed) to assume a descriptive commitment for situations, but not for events or states. \nIn fact, D&S provides an epistemological commitment to an ontology, independently from its foundational distinctions. A situation operationalizes that epistemology, and it is better not to put it under any foundational distinction (event, object, fluent, etc.), leaving to the designer whether to use descriptions as epistemological lenses, and so generating a situation, or not. \nA consequence is that any entity, when 'framed' by (satisfying) a description, becomes a situation. We can still model entities as being in a situation's setting, and classified by a concept defined in a description.\n\nIn 4.1, also the disjointness between Description and Concept has been dropped, in order to unify the projections of an intensional relation with its mereological dependencies. Until now, when a description d1 is part of another description d, we cannot model d1 as a concept defined or used by d, even though it is totally reasonable to consider it as such, i.e., playing a role in d. The impediment is due to the disjointness between being Description and Concept. By dropping that axiom, we can operate on descriptions and concepts more flexibly.\nA compositional property, hasInScope, is introduced to link situations that are 'diagonally' modelled through a description, e.g., when a situation s1 involves a description d1 (diagonal meta-level), which is satisfied by a situation s2, s1 hasInScope s2. \nLegal reasoning is a relevant example: a case in point (s2) may satisfy two legal norms (d1 and d2) that are conflicting according to a meta-norm d; d3 can be satisfied by a situation s that 'interprets' (involves) both d1 and d2 against s2. hence, s hasInScope s2. This may also happen wehen the two conflicting descriptions are satisfied by alternative situations sharing important elements, as in perspectival reasoning: the meta-description in this case has in scope both alternative situations.\n\nIn 4.2, the disjointness between Information Object and either Description or Concept has been dropped because of the full dependence of non-agentive social objects from information artifacts." . <http://purl.org/dc/elements/1.1/creator> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://purl.org/dc/elements/1.1/date> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://www.w3.org/2000/01/rdf-schema#comment> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://www.w3.org/2000/01/rdf-schema#label> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> .
There are 1 input files: /usr/local/archivo-data/ontologydesignpatterns.org/ont--dul--DUL--owl/2025.10.17-074842/ont--dul--DUL--owl_type=parsed.ttl Start loading Finished loading in 00:00:01.424 Input size: Classes = 80, Properties = 132, Individuals = 0 Expressivity: SRIQ(D) Start consistency check Finished consistency check in 00:00:00.021 Timer summary:
<http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#comment> "Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#comment> "An Event with at least one Agent that isParticipantIn it, and that executes a Task that typically isDefinedIn a Plan, Workflow, Project, etc."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#subClassOf> _:genid25 . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Action> <http://www.w3.org/2000/01/rdf-schema#subClassOf> _:genid26 . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent> <http://www.w3.org/2000/01/rdf-schema#comment> "Additional comment: a computational agent can be considered as a PhysicalAgent that realizes a certain class of algorithms (that can be considered as instances of InformationObject) that allow to obtain some behaviors that are considered typical of agents in general. For an ontology of computational objects based on DOLCE see e.g. http://www.loa-cnr.it/COS/COS.owl, and http://www.loa-cnr.it/KCO/KCO.owl."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent> <http://www.w3.org/2000/01/rdf-schema#comment> "Any agentive Object , either physical (e.g. a whale, a robot, an oak), or social (e.g. a corporation, an institution, a community)."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Agent> <http://www.w3.org/2002/07/owl#equivalentClass> _:genid27 . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Amount> <http://www.w3.org/2000/01/rdf-schema#comment> "A quantity, independently from how it is measured, computed, etc."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Classification> <http://www.w3.org/2000/01/rdf-schema#comment> "A special kind of Situation that allows to include time indexing for the classifies relation in situations. For example, if a Situation s 'my old cradle is used in these days as a flower pot' isSettingFor the entity 'my old cradle' and the TimeIntervals '8June2007' and '10June2007', and we know that s satisfies a functional Description for aesthetic objects, which defines the Concepts 'flower pot' and 'flower', then we also need to know what concept classifies 'my old cradle' at what time.\nIn order to solve this issue, we need to create a sub-situation s' for the classification time: 'my old cradle is a flower pot in 8June2007'. Such sub-situation s' isPartOf s."^^<http://www.w3.org/2001/XMLSchema#string> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Classification> <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Situation> .
Project ⊑ ∃ defines.Task isDescribedBy ≡ describes⁻ Group ⊑ ∀ actsThrough.(∃ conceptualizes.SocialRelation) isPartOf ≡ hasPart⁻ ⊤ ⊑ ∀ hasEventDate.date isQualityOf ≡ hasQuality⁻ Description ⊑ ¬ Situation InformationObject ⊑ ¬ Situation Transition ⊑ ≥ 2 includesEvent.⊤ ⊤ ⊑ ∀ hasIntervalDate.date
Parthood ⊑ ∃ includesWhole.Entity WorkflowExecution ⊑ Situation ⊤ ⊑ ∃ isPartOf .self hasComponent ⊑ hasProperPart hasSetting ∘ isSettingFor ⊑ sameSettingAs usesConcept ∘ classifies ⊑ describes Workflow ⊑ ∃ definesRole.Role isPropertPartOf ⊑ isPartOf PhysicalAttribute ⊑ ∀ isRegionFor.PhysicalObject TimeIndexedRelation ⊑ Situation
WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$2 (file:/usr/lib/pellet/cli/target/pelletcli/lib/guice-4.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$2 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release [main] WARN org.semanticweb.owlapi.util.SAXParsers - http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl [main] WARN org.semanticweb.owlapi.util.SAXParsers - entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl [main] WARN org.semanticweb.owlapi.util.SAXParsers - http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl [main] WARN org.semanticweb.owlapi.util.SAXParsers - entityExpansionLimit not supported by parser type org.apache.xerces.jaxp.SAXParserImpl [main] INFO org.semanticweb.owlapi.rdf.rdfxml.parser.OWLRDFConsumer - dumping remaining triples
@prefix sh: <http://www.w3.org/ns/shacl#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . [] a sh:ValidationReport ; sh:conforms false ; sh:result [ a sh:ValidationResult ; sh:focusNode <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> ; sh:resultMessage "No license found at all (neither dct:license, xhv:license nor cc:license)"@en ; sh:resultSeverity sh:Violation ; sh:sourceConstraintComponent sh:OrConstraintComponent ;
WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/usr/local/src/webapp/archivo/archivo/helpingBinaries/profilechecker-1.1.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release OWL2_DL: OK OWL2_QL: 68 violations OWL2_EL: 119 violations OWL2_RL: 56 violations
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix : <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix xml: <http://www.w3.org/XML/1998/namespace> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . <http://purl.org/dc/elements/1.1/creator> a owl:AnnotationProperty .
Metadata created by the DBpedia Databus Maven Plugin: https://github.com/dbpedia/databus-maven-plugin (Version 1.3-SNAPSHOT) The DataID ontology is a metadata omnibus, which can be extended to be interoperable with all metadata formats Note that the metadata (the dataid.ttl file) is always CC-0, the files are licensed individually Metadata created by https://yum-yab.github.io/webid.ttl#onto
DataID metadata for ontologydesignpatterns.org/ont--dul--DUL--owl
@prefix dc: <http://purl.org/dc/elements/1.1/> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix sh: <http://www.w3.org/ns/shacl#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . [] a sh:ValidationReport ; sh:conforms false ; sh:result [ a sh:ValidationResult ; sh:focusNode <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#DesignedSubstance> ;
<http://purl.org/dc/elements/1.1/creator> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://purl.org/dc/elements/1.1/date> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#AnnotationProperty> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Class> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#comment> "Any Entity that cannot be located in space-time. E.g. mathematical entities: formal semantics elements, regions within dimensional spaces, etc." . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#label> "Abstract"@en . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#label> "Astratto"@it . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Entity> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2002/07/owl#disjointWith> <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Event> . <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Abstract> <http://www.w3.org/2002/07/owl#disjointWith> <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#Object> .
Archivo Ontology Snapshot for http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
DOLCE+DnS Ultralite
## All DBpedia Archivo ontologies from ontologydesignpatterns.org domain Each artifact in this group deals as the archive for snapshots of one ontology of the [DBpedia Archivo](https://databus.dbpedia.org/ontologies) - A Web-Scale Interface for Ontology Archiving under Consumer-oriented Aspects. Find out more at [http://archivo.dbpedia.org](http://archivo.dbpedia.org). The description for the individual files in the artifact can be found [here](http://dev.dbpedia.org/DBpedia_Archvio#files).
## DBpedia Archivo Ontology Snapshot | Attribute | Value | | - | - | | Ontology URI | <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> | Archivo Ontology Factsheet| [Link](http://archivo.dbpedia.org/info?o=http://www.ontologydesignpatterns.org/ont/dul/DUL.owl) | Snapshot File URL | <http://www.ontologydesignpatterns.org/ont/dul/DUL.owl> | Snapshot OWL Version IRI | <None> | Snapshot Time | 2025-10-17 07:48:42 The [DBpedia Archivo Databus agent](https://databus.dbpedia.org/ontologies) generates only basic, static documentation for the archived snapshots of the ontologies. ## Ontology Metadata DBpedia Archivo extracts metadata from the ontology for well known properties (e.g. dct:description). This subsection shows the content of every property individually using a separate heading. ### rdfs:comment The DOLCE+DnS Ultralite ontology. It is a simplification of some parts of the DOLCE Lite-Plus library (cf. http://www.ontologydesignpatterns.org/ont/dul/DLP397.owl). Main aspects in which DOLCE+DnS Ultralite departs from DOLCE Lite-Plus are the following: - The names of classes and relations have been made more intuitive - The DnS-related part is closer to the newer 'constructive DnS' ontology (http://www.ontologydesignpatterns.org/ont/dul/cDnS.owl). - Temporal and spatial relations are simplified - Qualities and regions are more relaxed than in DOLCE-Full: they can be used as attributes of any entity; an axiom states that each quality has a region - Axiomatization makes use of simpler constructs than DOLCE Lite-Plus - The architecture of the ontology is pattern-based, which means that DOLCE+DnS Ultralite is also available in modules, called 'content ontology design patterns', which can be applied independently in the design of domain ontologies (cf. http://www.ontologydesignpatterns.org). If many modules are needed in a same ontology project, it is anyway useful to use this integrated version. The final result is a lightweight, easy-to-apply foundational ontology for modeling either physical or social contexts. Several extensions of DOLCE+DnS Ultralite have been designed: - Information objects: http://www.ontologydesignpatterns.org/ont/dul/IOLite.owl - Systems: http://www.ontologydesignpatterns.org/ont/dul/SystemsLite.owl - Plans: http://www.ontologydesignpatterns.org/ont/dul/PlansLite.owl - Legal domain: http://www.ontologydesignpatterns.org/ont/dul/CLO/CoreLegal.owl - Lexical and semiotic domains: http://www.ontologydesignpatterns.org/ont/lmm/LMM_L2.owl - DOLCE-Zero: http://www.ontologydesignpatterns.org/ont/d0.owl is a commonsense-oriented generalisation of some top-level classes, which allows to use DOLCE with tolerance against ambiguities like abstract vs. concrete information, locations vs. physical artifacts, event occurrences vs. event types, events vs. situations, qualities vs. regions, etc.; etc.