xml:base
attribute is not always specified in
input file, or you could
want to change it and specify another base URI for your imports. Enter
the URI in the import dialog.The
xml:base attribute specified by user
will not force the base URI. It is
used only if the attribute is not defined in the data file. |
if you choose the first option, the file format will automatically be selected depending on the file extension. if file extension is not recognize, RDF/XML is the default. |
Note that existing references to the modified identifier are updated into the whole knowledge base. |
This mode is interesting to demonstrate some properties but in practice, it cannot be used with big graphs because the application of all rules on the sum graphs of imports plus rdf(s) axioms quickly increases the graph size. |
When support completion is allowed two ways exist to
express rdfs:range
and rdfs:domain semantic. The default is to
define relation type signatures but it can be expressed by range rules
and domain rules, depending on the purpose. Do the user want to correct
future factual imports or to have a way to verify imports with
signature. |
signature |
domain rule |
range rule
|
Note that the generated rules can be considered as positive constraints which is very similar to signature checking. Just drag rules from rule set to the constraint set on the project tree. |
owl:disjointWith
property is used to
defined banned type in the
concept type hierarchy.
owl:SymmetricProperty |
owl:inverseOf |
owl:TransitiveProperty |
owl:allValuesFrom |