Cross Reference: /hets/CASL_DL/doc/CASL

Lines Matching defs:is
21 \subsection{Each OWL DL-File is one Named Spec}
24 the named spec is put into a file/CASL library that contains
35   two nodes: food and wine where wine is an extension of
37     abstract syntax like this is not possible. There can be
53   But is every named theory (spec) an OWL DL-file?  [Yes, unless we
56   for parametrised specifications? [Yes. Till] [This is not very
57   useful. As there is no notion of parametrisation in OWL DL these
60   [The reulting theory is just a loose theory, which may be useful
65   abbrev for the disambiguation when an imported ontology is extended)
73   only once. This even applies if an OWL DL file is not loaded form
74   the document inherent base URI which is seen as the URI of the
82   keeping track of parametrised specifications is not easy. 
91   structuring is lost. (or we have to add many Annotations to the
102     Cardinality Restrictions. No tracing is needed. Only the the
103     embedding into \CASL is a little bit harder, as the instantiation
107 [don't know which one is better. Till] [Extendenting FORMULA seems
120   \item with annos this is not easy. Here it must be possible to
122   \item with annos this is not easy. Here it must be possible to
129   unification is done by the parser we currently consider, but all
138   that declares this name. But a redeclaration is allways allowed. Or
141   \CASLDL and translated to OWL DL the declaration of symbols is
148     if this is an predicate Identifier obtained from an
152     identifiers into Namespaces (different OWL DL files) is written
168 used. One of them is used for \CASLDL sort marking. But what to do
209 an URI and file path. The URI is used as the base URI of the xml (owl)
229 CID is a \CASL Id that must be declared in the current specification (library).
231 DATA-LITERAL is a literal allowed for a subsort of \Id{Data}.
233 INDIVIDULA-ID is the Id of a declared constant operation.