owlvocabularyexplanationdeposit.java

来自「Semantic Web Ontology Editor」· Java 代码 · 共 722 行 · 第 1/5 页

			+	TAB+"&lt;rdfs:domain rdf:resource=\"#VintageYear\" /&gt;<br>"
			+	TAB+"&lt;rdfs:range  rdf:resource=\"&amp;xsd;positiveInteger\"/&gt;<br>"
			+	"&lt;/owl:DatatypeProperty&gt;<br>",
				sources_DT, OWL_REF, null) 
			);		
		
			name = OWLVocabularyAdapter.OWL + "DeprecatedClass";
			URI [] sources_DeprecatedClass = { new URI("http://www.w3.org/TR/owl-ref/#DeprecatedClass-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
				"<p >Deprecation is a feature commonly used in versioning software (for example, see the Java programming language) to indicate that a particular feature is preserved for backward-compatibility purposes, but may be phased out in the future. Here, a specific identifier is said to be of type http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_DeprecatedClass -- owl:DeprecatedClass"
			+	"or http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_DeprecatedProperty -- owl:DeprecatedProperty where <code>owl:DeprecatedClass</code> is a subclass  <code>rdfs:Class</code> and <code>owl:DeprecatedProperty</code> is a subclass of <code>rdf:Property</code>.  By deprecating a term, it means that the term should not be used in new documents that commit to the ontology.  This allows an ontology to maintain"
			+ 	"backward-compatibility while phasing out an old vocabulary (thus, it only makes sense to use deprecation in combination with backward compatibility).  As a result, it it easier for old data and applications to migrate to a new version, and thus can increase the level of adoption of the new version.  This has no meaning in the model theoretic semantics other than that given by the RDF(S) model theory.  However, authoring tools may use it to warn users when checking OWL markup.</p>"
			+ 	"<p>An example of deprecation is:</p>" 
			+ 	"<p>&lt;owl:Ontology rdf:about=\"\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;Vehicle Ontology, v. 1.1&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:backwardCompatibleWith" + NL
			+	TAB+"TAB+rdf:resource=\"http://www.example.org/vehicle-1.0\"/&gt;" + NL
			+	TAB+"&lt;owl:priorVersion rdf:resource=\"http://www.example.org/vehicle-1.0\"/&gt;" + NL
			+	"&lt;/owl:Ontology&gt;" + NL
			+	"&lt;owl:DeprecatedClass rdf:ID=\"Car\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;Automobile is now preferred&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:equivalentClass rdf:resource=\"#Automobile\"/&gt;" + NL
			+	TAB+"&lt;!-- note that equivalentClass only means that the classes have the same extension, so this DOES NOT lead to the entailment that  Automobile is of type DeprecatedClass too --&gt;" + NL
			+	"&lt;/owl:DeprecatedClass&gt;" + NL
			+	"&lt;owl:Class rdf:ID=\"Automobile\" /&gt;" + NL
			+	"&lt;owl:DeprecatedProperty rdf:ID=\"hasDriver\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;inverse property drives is now preferred&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:inverseOf rdf:resource=\"#drives\" /&gt;" + NL
			+	"&lt;/owl:DeprecatedProperty&gt;" + NL
			+	"&lt;owl:ObjectProperty rdf:ID=\"drives\" /&gt;</p>",
				sources_DeprecatedClass, OWL_REF, null) 
			);		
			
			name = OWLVocabularyAdapter.OWL + "DeprecatedProperty";
			URI [] sources_DeprecatedProperty = { new URI("http://www.w3.org/TR/owl-ref/#DeprecatedProperty-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
				"<p >Deprecation is a feature commonly used in versioning software (for example, see the Java programming language) to indicate that a particular feature is preserved for backward-compatibility purposes, but may be phased out in the future. Here, a specific identifier is said to be of type http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_DeprecatedClass -- owl:DeprecatedClass"
			+	"or http://www.w3.org/TR/2004/REC-owl-semantics-20040210/#owl_DeprecatedProperty -- owl:DeprecatedProperty where <code>owl:DeprecatedClass</code> is a subclass  <code>rdfs:Class</code> and <code>owl:DeprecatedProperty</code> is a subclass of <code>rdf:Property</code>.  By deprecating a term, it means that the term should not be used in new documents that commit to the ontology.  This allows an ontology to maintain"
			+ 	"backward-compatibility while phasing out an old vocabulary (thus, it only makes sense to use deprecation in combination with backward compatibility).  As a result, it it easier for old data and applications to migrate to a new version, and thus can increase the level of adoption of the new version.  This has no meaning in the model theoretic semantics other than that given by the RDF(S) model theory.  However, authoring tools may use it to warn users when checking OWL markup.</p>"
			+ 	"<p>An example of deprecation is:</p>" 
			+ 	"<p>&lt;owl:Ontology rdf:about=\"\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;Vehicle Ontology, v. 1.1&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:backwardCompatibleWith" + NL
			+	TAB+"TAB+rdf:resource=\"http://www.example.org/vehicle-1.0\"/&gt;" + NL
			+	TAB+"&lt;owl:priorVersion rdf:resource=\"http://www.example.org/vehicle-1.0\"/&gt;" + NL
			+	"&lt;/owl:Ontology&gt;" + NL
			+	"<br>" + NL
			+	"&lt;owl:DeprecatedClass rdf:ID=\"Car\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;Automobile is now preferred&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:equivalentClass rdf:resource=\"#Automobile\"/&gt;" + NL
			+	TAB+"&lt;!-- note that equivalentClass only means that the classes have the same extension, so this DOES NOT lead to the entailment that  Automobile is of type DeprecatedClass too --&gt;" + NL
			+	"&lt;/owl:DeprecatedClass&gt;" + NL
			+	"<br>" + NL
			+	"&lt;owl:Class rdf:ID=\"Automobile\" /&gt;" + NL
			+	"&lt;owl:DeprecatedProperty rdf:ID=\"hasDriver\"&gt;" + NL
			+	TAB+"&lt;rdfs:comment&gt;inverse property drives is now preferred&lt;/rdfs:comment&gt;" + NL
			+	TAB+"&lt;owl:inverseOf rdf:resource=\"#drives\" /&gt;" + NL
			+	"&lt;/owl:DeprecatedProperty&gt;" + NL
			+	"<br>" + NL
			+	"&lt;owl:ObjectProperty rdf:ID=\"drives\" /&gt; </p>",
				sources_DeprecatedProperty, OWL_REF, null) 
			);
			
			name = OWLVocabularyAdapter.OWL + "FunctionalProperty";
			URI [] sources_FP = { new URI("http://www.w3.org/TR/owl-ref/#FunctionalProperty-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
				"<p>A functional property is a property that can have only one (unique) value y for each instance x, i.e. there cannot be two distinct values y1 and y2 such that the pairs (x,y1) and (x,y2) are both instances of this property. Both object properties and datatype properties can be declared as \"functional\". For this purpose, OWL defines the built-in class owl:FunctionalProperty as a special subclass of the RDF class rdf:Property."
			+	"The following axiom states that the husband property is functional, i.e., a woman can have at most one husband (a good example of culture dependence of ontologies): </p> <br>"
			+	"&lt;owl:ObjectProperty rdf:ID=\"husband\"&gt;"+ NL
			+	TAB+"&lt;rdf:type    rdf:resource=\"&amp;owl;FunctionalProperty\" /&gt;"+ NL
			+	TAB+"&lt;rdfs:domain rdf:resource=\"#Woman\" /&gt;"+ NL
			+	"&lt;rdfs:range  rdf:resource=\"#Man\" /&gt;"+ NL
			+	"&lt;/owl:ObjectProperty&gt;" + NL
			+	"<p>As always, there are syntactic variations. The example above is semantically equivalent to the one below:</p>" + NL 
			+ "&lt;owl:ObjectProperty rdf:ID=\"husband\"&gt;" + NL
			+ TAB + " &lt;rdfs:domain rdf:resource=\"#Woman\" /&gt;" + NL 
			+ TAB + "  &lt;rdfs:range  rdf:resource=\"#Man\" /&gt;" + NL 
			+ "&lt;/owl:ObjectProperty&gt;" + NL
			+ "&lt;owl:FunctionalProperty rdf:about=\"#husband\" /&gt;",
				sources_FP, OWL_REF, null) 
			);
			
			name = OWLVocabularyAdapter.OWL + "InverseFunctionalProperty";
			URI [] sources_IFP = { new URI("http://www.w3.org/TR/owl-ref/#InverseFunctionalProperty-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
				"<p>If a property is declared to be inverse-functional, then the object of a property statement uniquely determines the subject (some individual). More formally, if we state that P is an owl:InverseFunctionalProperty, then this asserts that a value y can only be the value of P for a single instance x, i.e. there cannot be two distinct instances x1 and x2 such that both pairs (x1,y) and (x2,y) are instances of P.</p>"
			+	"<p>Syntactically, an inverse-functional property axiom is specified by declaring the property to be an instance of the built-in OWL class owl:InverseFunctionalProperty, which is a subclass of the OWL class owl:ObjectProperty.</p>"
			+	"<p>NOTE: Because in OWL Full datatype properties are a subclass of object properties, an inverse-functional property can be defined for datatype properties. In OWL DL object properties and datatype properties are disjoint, so an inverse-functional property cannot be defined for datatype properties.</p>"
			+   "<p>A typical example of an inverse-functional property:</p><br>"
			+	"&lt;owl:InverseFunctionalProperty rdf:ID=\"biologicalMotherOf\"&gt;" + NL
			+	TAB+"&lt;rdfs:domain rdf:resource=\"#Woman\"/&gt;" + NL
			+	TAB+"&lt;rdfs:range rdf:resource=\"#Human\"/&gt;"  + NL
			+	"&lt;/owl:InverseFunctionalProperty&gt;" +NL			
			+	"<p>This example states that for each object of biologicalMotherOf statements (some human) one should be able to uniquely identify a subject (some woman). Inverse-functional properties resemble the notion of a key in databases.</P>" 
			+	"<p>One difference with functional properties is that for inverse-functional properties no additional object-property or datatype-property axiom is required: inverse-functional properties are by definition object properties.</p>"    
			+	"<p>Notice that owl:FunctionalProperty and owl:InverseFunctionalProperty specify global cardinality constraints. That is, no matter which class the property is applied to, the cardinality constraints must hold. This is different from the cardinality constraints contained in property restrictions. The latter are class descriptions and are only enforced on the property when applied to that class.</p>",
				sources_IFP, OWL_REF, null) 
			);
			
			name = OWLVocabularyAdapter.OWL + "Nothing";
			URI [] sources_nothing = { new URI("http://www.w3.org/TR/owl-ref/#Nothing-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
					"<p>Two OWL class identifiers are predefined, namely the classes  owl:Thing and  owl:Nothing. The class extension of owl:Thing is the set of all individuals. The class extension of owl:Nothing is the empty set. Consequently, every OWL class is a subclass of owl:Thing and owl:Nothing is a subclass of every class (for the meaning of the subclass relation, see rdfs:subClassOf).</p>",
					sources_nothing, OWL_REF, null) 
			);	
			
			name = OWLVocabularyAdapter.OWL + "ObjectProperty";
			URI [] sources_OP = { new URI("http://www.w3.org/TR/2004/REC-owl-guide-20040210/#owl_ObjectProperty")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
					"<p>Object properties, relations between instances of two classes. Note that the name object property is not intended to reflect a connection with the RDF term rdf:object</p>",
					sources_OP, OWL_REF, null) 
			);		
			
			
			name = OWLVocabularyAdapter.OWL + "Ontology";
			URI [] sources_Ont = { new URI("http://www.w3.org/TR/owl-ref/#Ontology-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
					"<p>A document describing an ontology typically contains information about the ontology itself. An ontology is a resource, so it may be described using properties from the OWL and other namespaces, e.g.:</p><br>"
				+	"&lt;owl:Ontology rdf:about=\"\"&gt;" +NL
				+	TAB+"&lt;owl:versionInfo&gt; ... &lt;/owl:versionInfo&gt;" + NL
				+	TAB+"&lt;rdfs:comment&gt;...&lt;/rdfs:comment&gt;"+ NL
				+	TAB+"&lt;owl:imports rdf:resource=\"...\"/&gt;" + NL
				+	"&lt;/owl:Ontology&gt;"
				+	"<p>This is commonly called the ontology header and is typically found near the beginning of the RDF/XML document. The line</p><br>"
				+ 	"&lt;owl:Ontology rdf:about=\"\"&gt;"
				+	"<P>states that this block describes the current ontology. More precisely, it states the current base URI identifies an instance of the class owl:Ontology. It is recommended that the base URI be defined using an xml:base attribute in the &lt;rdf:RDF&gt; element at the beginning of the document.</P>"
				+	"&lt;owl:Ontology rdf:about=\"\"&gt;" + NL
				+	TAB+"&lt;owl:versionInfo&gt;v 1.17 2003/02/26 12:56:51 mdean&lt;/owl:versionInfo&gt;" + NL
				+	TAB+"&lt;rdfs:comment&gt;An example ontology&lt;/rdfs:comment&gt;" + NL
				+	TAB+"&lt;owl:imports rdf:resource=\"http://www.example.org/foo\"/&gt;" + NL
				+	"&lt;/owl:Ontology&gt;" + NL,
					sources_Ont, OWL_REF, null)
			);		

			name = OWLVocabularyAdapter.OWL + "OntologyProperty";
			URI [] sources_OntP = { new URI("http://www.w3.org/TR/owl-ref/#OntologyProperty-def")  };
			add( new OWLVocabularyExplanation( new URI(name), name,
			  "The ontology-import construct owl:imports and the ontology-versioning constructs owl:priorVersion, owl:backwardCompatibleWith and owl:incompatibleWith are defined in the OWL vocabulary as instances of the OWL built-in class owl:OntologyProperty. Instances of owl:OntologyProperty must have the class owl:Ontology as their domain and range. It is permitted to define other instances of owl:OntologyProperty. In OWL DL for ontology properties the same constraints hold as those specified for annotation properties in Sec. 7.1.",
			  sources_OntP, OWL_REF, null)
			);	
			
			name = OWLVocabularyAdapter.OWL + "Restriction";
			URI [] sources_Restriction = { new URI("http://www.w3.org/TR/owl-ref/#Restriction-def"),  new URI("http://www.w3.org/TR/2004/REC-owl-guide-20040210/#owl_Restriction") };
			add( new OWLVocabularyExplanation( new URI(name), name,
			"<p>In addition to designating property characteristics, it is possible to further constrain the range of a property in specific contexts in a variety of ways. We do this with property restrictions. The various forms described below can only be used within the context of an owl:Restriction. The owl:onProperty element indicates the restricted property.</p>"