a RuleML Rule encoding a Constitutive Statement.
logical conjunction within a Constitutive Statement.
logical disjunction within a Constitutive Statement.
logical implication within a Constitutive Statement.
logical equivalence within a Constitutive Statement.
universal quantification within a Constitutive Statement.
existential quantification within a Constitutive
Statement.
logical negation within a Constitutive Statement.
a RuleML Rule encoding a Prescriptive Statement.
a role of the deontic operator and its filler.
These edges could be made skippable, since if-then order is
required.
the premise (antecedent) of a Rule.
the conclusion (consequent) of a Rule.
the premise (antecedent) of a constitutive statement.
the conclusion (consequent) of a constitutive
statement.
the premise (antecedent) of a prescriptive statement.
the conclusion (consequent) of a prescriptive
statement.
a neutral temporal entity.
a temporal data value.
atomic formulas are a kind of simple formula
<Atom>: a predicate applied to arguments. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Atom
Atomic formulas may have an optional closure attribute.
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
The operator role in the context of an atomic formula is filled by a
predicate.
<Rel>: a category of name used as the predicate of an atomic formula. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Rel
Relations accept the optional attribute pattern of
resources.
The content model for relations is the XSD datatype
token.
A polyadic conjunctive expression, Within anything other than
Query...
<And>: polyadic conjunction where <And/> is true. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-And
The main section of the conjunction content model contains zero or more
formulas.
Formulas within conjunctions consist of a single formula
an extension point for specializations of the disjunction tag name.
A polyadic disjunctive expression,
<Or>: polyadic disjunction where <Or/> is false. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Or
The main section of the disjunction content model contains zero or more
formulas.
Formulas within disjunctions consist of a single formula
an extension point to allow alternate names and internationalization of
universal quantifiers
Explicit universal quantifier. It consists of a sequence of one or more
variables (<Var>), each optionally surrounded by a <declare> role, and a logical formula
(optionally surrounded by a <formula> role). See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Forall
Universally qualified formulas contain a sequence of bound variables and one
formula.
an extension point to allow alternate names and internationalization for
existential quantifiers
Explicit existential quantifier. It consists of one or more variables
(<Var>), each optionally surrounded by a <declare> role, followed by a logical formula
(optionally surrounded by a <formula> role). See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Exists
Existentially qualified formulas contain a sequence of bound variables and
one formula.
a declaration element contains a single quantifiable term
The formula role of universal quantifications contains a single formula.
The formula role of existential quantifications contains a single
formula.
an extension point for specializations of the expression tag name.
<Expr>: a functional expression. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Expr
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
The operator role of an expression is filled by a
functor.
an extension point for specializations of the function operator tag name.
<Fun>: a type of name for functional operators. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Fun
functors accept the resource attribute list
A functor contains the XSD datatype token.
an extension point for specializations of the strong negation tag name.
A classical negation of a logical atom (<Atom>) (i.e. classical or
"strong" negation). The negated atom may be optionally surrounded by a <strong> role.
See http://deliberation.ruleml.org/1.02/glossary/#gloss-Neg
Negation formulas contain a single role.
The negation role contains a single formula.
an extension point for specializations of the weak negation tag name.
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
Negation As Failure formulas accept the header patter common to truth-valued
connectives.
Negation As Failure formulas contain a single role.
The negation role contains a single formula.
formulas allowed to belong to weak negation formulas include atomic
forumulas.
an extension point for specializations of the equivalence tag name.
An equivalence expression, which is "syntactic sugar" for a pair of
conjoined converse implication rules (<Implies>). It consists of a pair of (optionally
skipped) <torso> roles. For example, "A person owning an object is equivalent to an object
belonging to a person": See http://deliberation.ruleml.org/1.02/glossary/#gloss-Equivalent
<Equivalent>: Syntactic sugar for two implications. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Equivalent
the main content model of equivalances consists of two "torso"
formulas
An equivalance is syntactic sugar for two implications. In all RuleML
languages, formulas allowed as premises are the same or more general than those allowed as
conclusions, because this is a requirement for the statement "P implies P" to be
syntactically valid whenever P is a valid conclusion. Therefore, formulas allowed in
equivalences are the same as those allowed in conclusions.
an extension point for specializations of the equation tag name.
<Equal>: an equation between two terms. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Equal
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
Equations accept the header of truth-valued connectives
The left-hand side role in an equation is filled by a
term.
The right-hand side role in an equation is filled by a
term.
terms allowed in the left-hand side of an equation
terms allowed in the right-hand side of an equation
A required attribute for specifying the position of a positional argument
(<arg>) within a logical atom (<Atom>). See
http://deliberation.ruleml.org/1.02/glossary/#gloss-index
A required attribute for specifying the position of a positional argument
(<arg>) within a logical atom (<Atom>). See
http://deliberation.ruleml.org/1.02/glossary/#gloss-index
The content model of positional arguments for atomic formulas consists of
any single term.
Skolem constants are simple constant terms, but are not used in keys.
Individuals and literals (data) are simple, constant terms, and may be used
in slot keys.
Data terms are literals, and may have simple or complex
datatypes.
an extension point for specializations of the individual tag name.
<Ind>: an individual constant. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Ind
Individuals optionally accept the attribute patterns of resources, and
objects with user-defined types.
The content model for individuals is the XSD datatype
token.
<Interval>: generic Interval element. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Interval
<Negation>: a generic polymorphic negation, which is interpreted by the
intended semantics (i.e. semantic profile). See
http://consumer.ruleml.org/1.02/glossary/#gloss-Negation
an extension point for the generic operation category.
<Operation>: a generic polymorphic Operation, which is interpreted by the
intended semantics (i.e. semantic profile). See
http://consumer.ruleml.org/1.02/glossary/#gloss-Operation
the Operation attribute list follows the generic pattern
Formulas within generic operations consist of a single
formula
formulas allowed to participate in generic operations include all formulas
allowed in conjunctions. Typically, this will be all logical formulas.
<Spatial>: generic Spatial element. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Spatial
An internal group for the spatial primitives for interpretation as
spatial
<Time>: generic Time element. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Time
An internal group for the time primitives for interpretation as
time
a convenience pattern that unifies implications and equivalences because
equivalence is allowed wherever implication is allowed.
an extension point to allow alternate names and internationalization of
uni-directional implication tag name.
An implication rule. It consists of a conclusion role (<then>) followed by a
Premise role (<if>), or, equivalently (since roles constitute unordered elements), a Premise
role followed by a conclusion role. Alternatively, the roles may be skipped, in which case
the Premise comes first followed by the conclusion as suggested by the element name
'Implies'. The children of the implication element are divided into two sections, a header
section for modifiers, and a main section for the premises and conclusion.
<Implies>: an implication between two formulas, a premise and a
conclusion. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Implies
an extension point for stripe skipping as well as specializations of the if
tag name in implications.
The if of an implication rule (<Implies>) containing the Premise(s), also
known as the "antecedent" part of the rule. Also used as the "antecedent" part of an
entailment (<Entails>). Within Implies...
<if>: contains the premise of the implication. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-if
The premise of an implication consists of a single
formula
an extension point for stripe skipping as well as specializations of the
then tag name in implications.
The then of an implication rule (<Implies>) containing the conclusion, also
known as the "consequent" or "then" part of the rule. Also used as the "consequent" part of
an entailment (<Entails>). Within Implies...
<then>: contains the conclusion of the implication. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-then
The conclusion of an implication consists of a single
formula.
backbone patterns
implications have inference direction and material implication as an
attribute with default values. implications have scoped attributes that are activated at
full first-order logic
Slotted arguments follow positional arguments in atomic formulas in the
normal-form serialization.
Positional rest arguments follow the ordinary positional arguments in atomic
formulas in the normal-form serialization.
Slotted rest arguments follow the ordinary slots in atomic formulas in the
normal-form serialization.
Pre-fix operator notation for expressions is required in the normal-form
serialization.
Slotted arguments follow positional arguments in expressions in the
normal-form serialization.
Positional rest arguments follow the ordinary positional arguments in
expressions in the normal-form serialization.
Slotted rest arguments follow the ordinary slots in expressions in the
normal-form serialization.
In the normal-form serialization, the if and then of an implication must
occur in canonical order.
In the normal-form serialization, the order of header elements is: an
optional header element sequence as defined in Node.header, followed by optional object
identifier and degree
attribute list for resources includes and optional iri
attribute.
An attribute for referring to a IRI. See
http://deliberation.ruleml.org/1.02/glossary/.40iri
an extension point for specializations of the oriented equation attribute
name.
An attribute for referring to a IRI. See
http://deliberation.ruleml.org/1.02/glossary/.40iri
An optional uncertainty value (between 0.0 and 1.0) that may be assigned to
simple formulas. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-degree
The degree edge element contains a single data term.
an extension point for specializations of the material implication attribute
name.
An attribute indicating the kind of an implication rule (<Implies>).
Allowed values are "yes" (the default) and "no". See
http://deliberation.ruleml.org/1.02/glossary/.40material
An attribute indicating the kind of an implication rule (<Implies>).
Allowed values are "yes" (the default) and "no". See
http://deliberation.ruleml.org/1.02/glossary/.40material
an extension point for stripe skipping as well as specializations of the
object identifier tag name.
<oid>: a label for Node elements. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-oid
The object descriptor content model consists of any single term. Note: this
corrects an error in the oid content model of RuleML 1.0, where Var is allowed in oid in
bindatagroundlog and bindatagroundfact.
In atomic formulas, zero or more slots are allowed.
In expressions, zero or more slots are allowed.
an extension point for specializations of the slot tag name.
A user-defined slot (property). See
http://deliberation.ruleml.org/1.02/glossary/#gloss-slot
The slot content model consists of a key (first position) and a filler
(second position).
The key (first position) in a slot contains an interpreted term or data,
which may be simple or compound.
The filler (second position) in a slot contains any single
term.
an extension point for specializations of the cardinality attribute name.
the cardinality of a slot.
An attribute optionally specifying a <slot>'s cardinality. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-card
the cardinality of a slot.
attribute list for objects that can have user-defined types, includes an
optional type attribute.
an extension point for specializations of the oriented equation attribute
name.
A role for optionally specifying a term's (user-defined) type. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-type
A role for optionally specifying a term's (user-defined) type. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-type
Data terms may have mixed content from any namespace.
an extension point for specializations of the data tag name.
A fixed argument like RDF literals. Data may have mixed content with any
elements interleaved with text. Explicit datatyping of xs:anyType is implemented in the
explicit datatyping module.
an extension point to allow alternate names and internationalization for
Skolem constants
A Skolem individual constant, like RDF's blank nodes. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Skolem
Skolems optionally accept the attribute pattern of objects with user-defined
types.
The content model for skolems is the XSD datatype token.
terms that can be bound by a quantifier include
variables.
an extension point for specializations of the variable tag name.
A logical variable, as in logic programming. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-Var
Variables optionally accept the attribute pattern of objects with
user-defined types.
The content model for variables is the XSD datatype
token.
an extension point for specializations of the implicit closure attribute
name.
An attribute indicating how the contained free variables are quantified.
Allowed values are "universal" and "existential". See
http://deliberation.ruleml.org/1.02/glossary/.40closure
An attribute indicating how the contained free variables are quantified.
Allowed values are "universal" and "existential". See
http://deliberation.ruleml.org/1.02/glossary/.40closure
an extension point for specializations of the slotted rest tag name.
Stripe-skipping is not allowed for slotted rest variables.
A slotted rest variable used in <Atom>s, <Expr>s and <Plex>s. Note that <Plex>s are
generated, so <resl>s are only available above the Datalog sublanguage. See
http://deliberation.ruleml.org/1.02/glossary/#gloss-resl
The content model of a slotted rest variable is a single
term.
terms allowed in slotted rest variables.
Sequence markers are represented as ordinary variables.
an extension point for specializations of the positional rest tag name.
Stripe-skipping is not allowed for positional rest variables.
A positional rest variable used in <Atom>s, <Expr>s and <Plex>s. Note that <Plex>s
are generated, so <repo>s are only available above the Datalog sublanguage. See
http://www.ruleml.org/0.9/glossary/#gloss-repo
The content model of a positional rest variable is a single
term.
terms allowed in positional rest variables include sequence markers.
Sequence markers are represented as ordinary variables.
an extension point for specializations of the generalized list tag name.
A collection of (ordered) arguments (optionally enclosed by <arg>) and/or
(unordered) user-defined slots (<slot>), identical to an uninterpreted expression (<Expr
in="no">) except not having a user-specified function name (equivalent to having a
system-specified constructor 'Plex'). Rest variables (<repo> and <resl>) are also permitted.
See http://deliberation.ruleml.org/1.02/glossary/#gloss-Plex within
Atom
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
Generalized lists accept the header pattern common to
Nodes.
A generalized list contains a generalized term sequence, which may be
empty.
an extension point for specializations of the generalized list tag name.
A collection of (ordered) arguments (optionally enclosed by <arg>) and/or
(unordered) user-defined slots (<slot>), identical to an uninterpreted expression (<Expr
in="no">) except not having a user-specified function name (equivalent to having a
system-specified constructor 'Plex'). Rest variables (<repo> and <resl>) are also permitted.
See http://deliberation.ruleml.org/1.02/glossary/#gloss-Plex within
repo
A generalized list within a positional rest variable contains a positional
argument sequence
an extension point for specializations of the generalized list tag name.
A collection of (ordered) arguments (optionally enclosed by <arg>) and/or
(unordered) user-defined slots (<slot>), identical to an uninterpreted expression (<Expr
in="no">) except not having a user-specified function name (equivalent to having a
system-specified constructor 'Plex'). Rest variables (<repo> and <resl>) are also permitted.
See http://deliberation.ruleml.org/1.02/glossary/#gloss-Plex within
resl
A generalized list within a slotted rest variable contains a slotted
argument sequence
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
@style: defines a reference to a semantic profile. See
http://consumer.ruleml.org/1.02/glossary/#.40style
@key: defines a unique key attribute which can be used for distributed
referencing from a keyref attribute. See
http://consumer.ruleml.org/1.02/glossary/#.40key
@keyref: defines a reference to a corresponding unique key. See
http://consumer.ruleml.org/1.02/glossary/#.40keyref
<Rule>: defines a rule in Consumer RuleML. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Rule
<if>: contains the premises of the rule. See
http://consumer.ruleml.org/1.02/glossary/#gloss-if
<then>: contains the conclusion of the rule. See
http://consumer.ruleml.org/1.02/glossary/#gloss-then
an extension point for the before constructor category.
<Before>: an interval constructor "d before (t)". See
http://consumer.ruleml.org/1.02/glossary/#gloss-Before
an extension point for the after constructor category.
<After>: an interval constructor "d after (t)". See
http://consumer.ruleml.org/1.02/glossary/#gloss-After
an extension point for the every constructor category.
<Every>: an interval constructor "every d". See
http://consumer.ruleml.org/1.02/glossary/#gloss-Every
an extension point for the every constructor category.
<Any>: an interval constructor "any t1, .., tn". See
http://consumer.ruleml.org/1.02/glossary/#gloss-Any
an extension point for the every constructor category.
<Timer>: an interval constructor "After t Every d". See
http://consumer.ruleml.org/1.02/glossary/#gloss-Timer
an extension point for the during operator category.
<During>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-During
an extension point for the overlaps operator category.
<Overlaps>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Overlaps
an extension point for the starts operator category.
<Starts>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Starts
an extension point for the preceds operator category.
<Precedes>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Precedes
an extension point for the succeeds operator category.
<Succeeds>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Succeeds
an extension point for the meets operator category.
<Meets>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Meets
an extension point for the finishes operator category.
<Finishes>: an interval operator. See
http://consumer.ruleml.org/1.02/glossary/#gloss-Finishes
Common Patterns for Interval Algebra