<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Fuzzy Semantics for Semantic Web Languages</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mauro Mazzieri</string-name>
          <email>mauro.mazzieri@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Aldo Franco Dragoni</string-name>
          <email>a.f.dragoni@univpm.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fuzzy RDF</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Universiat` Politecnica delle Marche Dipartimento di Elettronica</institution>
          ,
          <addr-line>Intelligenza Artificiale e Telecomunicazioni, DEIT</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>Although the model-theoretic semantics of the languages used in the Semantic Web are crisps, the need arise to extend them to represent fuzzy data, in the same way fuzzy logic extend first-orderlogic. We will define a fuzzy counterpart of the RDF Model Theory for RDF (section 2) and RDF Schema (section 3). Last, we show how to implement the extended semantics in inference rules (section 4).</p>
      </abstract>
      <kwd-group>
        <kwd>Fuzzy Logic</kwd>
        <kwd>Knowledge Representation</kwd>
        <kwd>Semantic Web</kwd>
        <kwd>RDF</kwd>
        <kwd>RDF Schema</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>RDF has its own model-theoretic semantics, similar to that of rfist-order logic.
To represent fuzzy data, we will denfie a syntactic and semantic extension of
RDF, similar to the extension from first-order logic to fuzzy logic.</p>
      <p>Even if fuzzy data can be simply seen as a juxtaposition of a triple and a
number, the model-theoretic approach has well-known theoretical advantages.</p>
      <p>
        We will try to be as plain as possible. Starting from RDF Syntax and RDF
Model Theory, we will make as few changes as possible. In the rest of the paper,
for the sake of brevity only the changes from RDF Semantics[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] are shown.
2.1
      </p>
    </sec>
    <sec id="sec-2">
      <title>Syntax</title>
      <p>
        The RDF syntax must be extended to add to the triple hsubject, predicate,
objecti a value. Such a value can be taken as a real number in the interval [
        <xref ref-type="bibr" rid="ref1">0,
1</xref>
        ], but every bounded real interval will do.
      </p>
      <p>This is not an extension from a 3-elements tuple to a 4-elements tuple as it
may seem at a rfist glance. The added element has a syntactic nature different
from the others: it is not an element of the domain of the discourse, but a
property related to the formalism used by the language to represent uncertainty
and vagueness.</p>
      <p>
        The simple concrete syntax we define is as an extension of the EBNF of
N-Triples as given in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Our extension is given in table 1.
      </p>
      <p>N-Triples is a line-based, plain text format for encoding an RDF Graph, used
for expressing RDF test cases. A statement has the form s p o., where s, p and
o are respectively the subject, the predicate and the object of the statement. Our
extended syntax add an optional prexfi n: to a statement in N-triple notation,
where n is a decimal number representing the fuzzy truth-value of the triple.
The use of decimal numbers instead of real numbers is only a limitation of the
syntax and does not undermine the discussion.</p>
      <p>The term triple, used in the EBNF for N-Triple, is replaced with the more
generic term statement. Triple and statement are often used in semantic web
literature as a synonym, but we prefer to use the latter to avoid confusion between a
plain RDF statement (made actually of three parts) and a fuzzy RDF statement
(that, although is still a triple semantically, is made up of four elements).</p>
      <p>The fuzzy value is defined as optional. This way, the syntax is
backwardcompatible; the intended semantics is that a statement with the form s p o. is
equivalent to the statement 1: s p o.. With such a (syntactic only) default, we
could take an inference engine implementing fuzzy RDF, let it parse plain RDF
statements, and get the same results of a conventional RDF inference engine.
Furthermore, as it would be clear in the description of fuzzy RDF inference rules
(section 4), even the complexity of the computation would be of the same order.</p>
      <p>
        We will not give an abstract syntax, nor a RDF/XML based syntax, as
they would not be useful. It can be shown that all “physical“ data (i.e., data
transmitted between host or processes) can be encoded using plain RDF reiefid
statements. The extended syntax will be used only in the paper to write down
the examples.
fuzzyNtripleDoc ::= line*
line ::= ws* ( comment | statement )? eoln
comment ::= ‘#’ ( character − ( cr | lf ) )*
statement ::= (value ws+)? subject ws+ predicate ws+ object ws* ‘.’ ws*
value ::= 1 | 0.[
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6 ref7 ref8 ref9">0–9</xref>
        ]+
subject ::= uriref | nodeID
predicate ::= uriref
object ::= uriref | nodeID | literal
uriref ::= ‘&lt;’ absoluteURI ‘&gt;’
nodeID ::= ‘_:’ name
literal ::= langString | datatypeString
langString ::= ‘"’ string ‘"’ ( ‘@’ language )?
datatypeString ::= ‘"’ string ‘"’ ‘^^’ uriref
language ::= [a–z]+ (‘-’ [a–z0–9]+ )*
      </p>
      <p>
        encoding a language tag.
ws ::= space | tab
eoln ::= cr | lf | cr lf
space ::= #x20 /* US-ASCII space - decimal 32 */
cr ::= #xD /* US-ASCII carriage return - decimal 13 */
lf ::= #xA /* US-ASCII line feed - decimal 10 */
tab ::= #x9 /* US-ASCII horizontal tab - decimal 9 */
string ::= character* (with escapes as defined in section Strings of [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ])
name ::= [A-Za-z][A–Za–z0–9]*
absoluteURI ::= character+ (with escapes as defined in section URI References
of [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ])
character ::= [#x20–#x7E] /* US-ASCII space to decimal 126 */
The RDF Model Theory[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] is based on the concept of extension. An
interpretation satisefis a triple s p o. if the couple formed by the interpretation of
the subject and the interpretation of the object belongs to the extension of the
interpretation of the property.
      </p>
      <p>In this fuzzy counterpart, a couple hsubject, objecti has a membership
degree to the extension of the predicate, given by the number prepended to the
statement. The extension is not an ordinary set of couples anymore, but a fuzzy
set of couples. In other words, a fuzzy RDF interpretation satisefis a statement
n: s p o. if the membership degree of the couple, formed by the
interpretation of the subject and the interpretation of the object, to the extension of the
interpretation of the predicate, is greater or equal than n.</p>
      <p>We have chosen not to make the mapping between vocabulary items and
domain fuzzy. Instead, the membership of a resource to the domain is fuzzy.
This is a step which poses some theoretical problems, in particular when we
have to deal with properties in simple interpretations. In RDF interpretation,
the property domain IP is a subset of the resource domain IR, so in fuzzy RDF
interpretations would be enough to make IP a fuzzy subset of IR; in simple
interpretations, instead, there is no formal relation between IP and IR, so when
the mapping IS from URI references to (IR ∪ IP ) becomes fuzzy we need a
further device. The chosen solution is to denfie a domain IDP for properties,
so that IP is a fuzzy subset of IDP , and to modify the denfiition of IS to a
mapping URI references ∈ V → (IR ∪ IDP ). RDF interpretations does not need
IDP , as IP can be shown to be a fuzzy subset of IR.</p>
      <sec id="sec-2-1">
        <title>Definition of a simple interpretation</title>
        <p>ulary V is defined by:</p>
        <p>A simple fuzzy interpretation I of a
vocab1. A non empty set IR of resources, called the domain or universe of I
2. A non empty set IDP , called the property domain of I
3. A fuzzy subset IP of IDP , called the set of properties of I
4. A fuzzy mapping IEXT : IP → 2IR× IR, i.e. the fuzzy set of pairs hx, yi
with x, y ∈ IR.
5. A mapping IS from URI references ∈ V → (IR ∪ IDP )
6. A mapping IL from typed literals ∈ V → IR
7. A distinguished subset LV ⊆ IR, called the set of literal values, which
contains all the plain literals of V</p>
        <p>The belonging of an element to the properties domain is strictly related to
the use of such element as a property in a statement. Therefore, we have defined
a membership degree to the property domain, intuitively related to the truth
value of the statements in which the resource is used as a property.
2.3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Denotations for ground graphs</title>
      <p>The next step is to denfie the semantic conditions an interpretation must satisfy
in order to be a model for a graph. We state the semantic conditions that relate
the membership degree of a couple hsubject, objecti to an extension and the
truth of a fuzzy statement.</p>
      <p>
        We will use the abbreviated Zadeh’s notation A(x) = n, instead of μ A(x) = n,
to state that the membership degree of the element x to the set A is equal to
n [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <sec id="sec-3-1">
        <title>Semantic conditions for ground graphs</title>
        <p>– if E is a plain literal aaa ∈ V , then I(E) = aaa
– if E is a plain literal aaa@ttt ∈ V , then I(E) = haaa, ttti
– if E is a typed literal ∈ V , then I(E) = IL(E)
– if E is a URI reference ∈ V , then I(E) = IS(E)
– if E is a ground triple n: s p o., then I(E) = true if s, p and o ∈ V ,</p>
        <p>IP (I(p)) ≥ n and IEXT (I(p))(hI(s), I(o)i) ≥ n, otherwise I(E) = false.
– if E is a ground RDF graph, than I(E) = false if I(E0) = false for some
triple E0 ∈ E, otherwise I(E) = true</p>
        <p>Only the condition of truth and falsity of a ground statement in the
interpretation is affected. The given formulation of the condition has as a consequence
that a graph where the same statement appears more than once, with
different membership degrees, is equivalent to a graph where the statement appears
only once, with a membership degree equal to the maximum of the membership
degrees.</p>
        <p>Note that whether a statement is a model for a graph or not is not a fuzzy
concept; it is either true or false. However, it could be interesting to compute
the minimum and maximum membership degree to an extensions a couple must
have in an interpretation to be a model of a given graph. This minimum degree
has a role similar to the degree of truth of a statement in a knowledge base.
2.4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Simple entailment</title>
      <p>The definition of simple interpretation is not affected. A set S of RDF graphs
(simply) entails a graph E if every interpretation which satisefis every member
of S also satisfies E.</p>
      <p>Given a graph G and a triple hs, p, oi, it could be interesting to compute
the minimum and maximum value of n such that G entails n: s p o.. Those
bounds must be taken in account when we compute the deductive closure of the
graph, as it is not unique.</p>
      <p>
        Section 2 of RDF Semantics [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] shows many lemmas that apply to simple
interpretations. All of them retain their validity within fuzzy RDF Model Theory,
making some adjustments in the proof of some of them. We will show these.
      </p>
      <p>The Empty Graph Lemma can be shown using the same proof. The denfiition
of an empty graph is the same as in plain RDF: an empty graph is a graph with no
statements at all. It is important to note that an empty graph can not be defined
as a graph with no not-zero-valued statements. Statements such as 0: s p o.,
although pretty useless, cannot be ignored, as the semantic requirement that s,
p and o must belong to the graph’s vocabulary still applies.</p>
      <p>Subgraph Lemma, Instance Lemma and Merging Lemma retain both their
validity and their proofs with the new semantics.</p>
      <p>
        Interpolation Lemma, Anonymity Lemma, Monotonicity Lemma and
Compactness Lemma make use in their proof of a way of constructing an
interpretation of a graph using lexical items in the graph itself, the so called Herbrand
interpretation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. To prove the lemmas, we need to construct a similar
interpretation for a fuzzy graph.
      </p>
      <p>The (simple) Herbrand fuzzy interpretation of G, written Herb(G), can be
denfied as follows.</p>
      <p>– LVHerb(G) is the set of all plain literals in G;
– IRHerb(G) is the set of all names and blank nodes which occur in subject or
object position of statements in G;
– IDPHerb(G) is the set of URI references which occur in the property position
of statements in G;
– IPHerb(G)(p) is the maximum of n for all statements in which p occur in
property position;
– IEXTHerb(G)(hs, oi) is the maximum n for all the statements n: s p o. in</p>
      <p>G
– ISHerb(G) and ILHerb(G) are both identity mappings on the appropriate
parts of the vocabulary of G.</p>
      <p>
        Using this definition of Herbrand interpretation instead of that in Appendix
A of [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], the proofs for cited lemmas still apply.
2.5
      </p>
    </sec>
    <sec id="sec-5">
      <title>RDF Interpretation</title>
      <p>RDF Semantic Conditions
– IP (x) = IEXT (I(rdf : type))(hx, I(rdf : Property))
– If ”xxx”∧∧rdf : XMLLiteral ∈ V and xxx is a well-typed XML literal string,
then
• IL(”xxx” ∧ ∧rdf : XMLLiteral) is the XML value of xxx;
• IL(”xxx” ∧ ∧rdf : XMLLiteral) ∈ LV ;
• IEXT (I(rdf : type))
(hIL(”xxx” ∧ ∧rdf : XMLLiteral),</p>
      <p>I(rdf : XMLLiteral)i) = 1
– If ”xxx”∧∧rdf : XMLLiteral ∈ V and xxx is an ill-typed XML literal string,
then
• IL(”xxx” ∧ ∧rdf : XMLLiteral) ∈/ LV ;
• IEXT (I(rdf : type))
(hIL(”xxx” ∧ ∧rdf : XMLLiteral),</p>
      <p>I(rdf : XMLLiteral)i) = 0</p>
      <p>The rfist RDF semantic condition has the consequence that IP must be a
subset of IR. Given such a fact, there is no more need of IDP , as it was for
simple interpretation. IP can be directly denfied as a fuzzy subset of IR.</p>
      <p>The second and third conditions equal to see the well-formedness of an XML
Literal as crisp truth-valued. We could conceive an external machinery that can
be considered completely trustworthy as it classify an XML literal as well-formed
or not.</p>
      <p>
        RDF axiomatic triples By definition, we give axiomatic triples a unit truth
value. Given the (syntactic) convention that a triple s p o. is equivalent to the
fuzzy statement 1: s p o., we can take the table of axiomatic triples of RDF in
section 3.1 of [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and copy it as-is as the table of axiomatic statements of fuzzy
RDF.
      </p>
      <sec id="sec-5-1">
        <title>Fuzzy RDF Schema</title>
        <p>The path from RDF Schema to Fuzzy RDF Schema follows the same guidelines
of the previous section.</p>
        <p>
          The RDFS semantics is conveniently stated in terms of a new semantic
construct: the class [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. A class is a resource with a class extension, ICEXT , which
represents a set of things in the universe which all have that class as the object
of their rdf:type property. Thus, the definition of a class roots in the denfiition
of extension.
        </p>
        <p>In fuzzy RDF, extensions are fuzzy set of couples; in fuzzy RDFS, class
extensions are fuzzy sets of domain’s elements.
3.1</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>RDFS Interpretation</title>
      <p>A RDFS interpretation denfie the domains for resources ( IR), literals (IL) and
literal values (LV ) in terms of classes. In fuzzy RDFS they are fuzzy subdomains
of IR.</p>
      <p>We will give RDFS semantic conditions and axiomatic triples, then we will
try to explain the more problematic definitions: domains/ranges (section 3.2)
and subproperties/subclasses (section 3.3).</p>
      <p>RDFS semantic conditions
– ICEXT (y)(x) = IEXT (I(rdf : type))(hx, yi)
• IC = ICEXT (I(rdfs : Class))
• IR = ICEXT (I(rdfs : Resource))
• IL = ICEXT (I(rdfs : Literal))
– ICEXT (y)(u) ≥ min(IEXT (I(rdfs : domain))(hx, yi), IEXT (x)(hu, vi))
– ICEXT (y)(u) ≥ min(IEXT (I(rdfs : range))(hx, yi), IEXT (x)(hu, vi))
– IEXT (I(rdfs : subPropertyOf)) is transitive and reeflxive on IP
– If IEXT (rdfs : subPropertyOf)(hx, yi) = n, then IP (x) ≥ n, IP (y) ≥ n,
minha,bi{1 − IEXT (x)(ha, bi) + IEXT (y)(ha, bi)} ≥ n
– IEXT (I(rdfs : subClassOf))(hx, I(rdfs : Resource)i) = IC(x)
– If IEXT (rdfs : subClassOf)(hx, yi) = n, then IC(x) ≥ n, IC(y) ≥ n,
mina{1 − IC(x)(a) + IC(y)(a)} ≥ n.
– IEXT (I(rdfs:subClassOf)) is transitive and reeflxive on IC
– IEXT (I(rdfs : subPropertyOf))(hx, I(rdfs : member)i) =</p>
      <p>ICEXT (I(rdfs : ContainerMembershipProperty))(x)
– ICEXT (I(rdfs : Datatype))(x) =</p>
      <p>
        IEXT (I(rdfs : subClassOf))(hx, I(rdfs : Literal)i)
RDFS axiomatic triples As for RDF axiomatic triples, fuzzy RDFS axioms are
the same of plain RDFS, from section 4.2 of RDF Semantics [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
Subproperties and subclasses are fully analogous concepts. The set inclusion is
between extensions for the former, between class extensions of the latter.
      </p>
      <p>To define the semantics of subClassOf and subPropertyOf, we need a
relation of set inclusion between fuzzy sets that takes into account also the degree
of the relation of inclusion itself. This relation must be transitive and reeflxive.</p>
      <p>
        Zadeh’s denfiition of fuzzy subset [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] 3 (A ⊆ B ⇐⇒ ∀x ∈ X A(x) ≤ B(x))
is transitive and reeflxive, but is not a fuzzy relation: either the set A is a subset
of B, or not. What we need is instead a weaker fuzzy subset relation; a relation
that reduces to the Zadeh’s one when the subclass/subproperty relation has a
unit truth value. It must also maintain the reeflxivity and transitivity properties.
      </p>
      <p>
        Dubois and Prade [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] denfie weak inclusion α as
      </p>
      <p>A α B</p>
      <p>⇐⇒ x ∈ (A ∪ B)α ∀x ∈ X ,
where α is a parameter and (· )α is the α -cut4. This relation is transitive only for
α &gt; 12 .</p>
      <p>Other definitions of weak inclusion make use of inclusion grades. An inclusion
grade I(A, B) is a scalar measure of the inclusion of the set A in the set B.
In general, A ⊆ α B iff I(A, B) ≥ α , where ⊆ α denote a weak inclusion with
inclusion grade α .</p>
      <p>
        We have chosen to use the inclusion grade denfied as [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]:
3 Again, we use the abbreviation A(x) for the membership function μ A(x).
4 The α -cut Aα of A is the set of all elements with a membership value to A greater
than α , with α ∈ (0, 1] Aα = {x|A(x) ≥ α }
      </p>
      <p>I(A, B) = infx∈X (A | − |
where inf is the infimum and | − | is the bounded difference 5.</p>
      <p>
        When A ⊆ B, I(A, B) = 1 [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>This inclusion grade could also be written as I(A, B) = infx∈X (1− max(0, A(x)−
B(x))) = infx∈X min(1, (1 − A + B)).</p>
      <p>Furthermore, let’s suppose that there is at least an x such that A(x) &gt; B(x).
Then I(A, B) could be written as infx∈X (1 − A + B). The semantic condition
requires such measure to be greater than or equal to n, where n is the truth
value of the statement. In this case the semantic condition reduces to
infx∈X (1 − A + B) ≥ n .</p>
      <p>It could be interesting to ask how much this denfiition differs from the
condition for classical fuzzy subsets, A(x) ≤ B(x).</p>
      <p>
        If A ⊆ B, then I(A, B) = 1, so the semantic condition holds for any n ∈ [
        <xref ref-type="bibr" rid="ref1">0, 1</xref>
        ].
      </p>
      <p>Let’s call d(x) the difference d(x) = A(x)− B(x), so that 1− A+B = 1− d. We
suppose that there is at least an x such that A(x) &gt; B(x), so d(x) has at least a
positive value. The semantic condition could then be written infx∈X (1 − d(x)) ≥
n. The maximum positive value of the difference d equal to 1 − n.</p>
      <p>As n is the truth value of the statement that asserts the relation of
subproperty or subclass, and 1 − n represent the lack of truth of the same statement, we
can conclude that the maximum allowable positive difference between A(x) and
B(x) is equal to the lack of truth on the subproperty or subclass relation.
4</p>
      <sec id="sec-6-1">
        <title>Fuzzy RDF entailment rules</title>
        <p>
          RDF Model Theory’s entailment rules [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] are all of the same form: add a
statement to a graph when it contains triples conforming to a pattern. Each rule
has only one or two antecedent statements and derive only one new inferred
statement; either P ` R or P, Q ` R.
        </p>
        <p>Given the way fuzzy RDF semantics is denfied, the corresponding inference
rules for fuzzy RDF are analogous; only the fuzzy truth values of inferred
statements must be computed. The simplest possible choice that respect the semantics
is:
– With rules as P ` Q, having only one antecedent, the truth value of the
consequent Q is taken to be the same of the antecedent P .
– With rules as P, Q ` R, the truth value of R is the minimum between the
truth values of P and Q.</p>
        <p>
          The inference rules for RDF/RDFS are shown in table 2. They were derived
from the rules used by the Sesame[
          <xref ref-type="bibr" rid="ref10 ref12">10</xref>
          ] forward-chaining inferencer.
5 ∀x ∈ X, (A | − |
        </p>
        <p>
          B)(x) = max(0, A(x) − B(x)) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]
        </p>
        <p>
          Sesame is a generic architecture for storing and querying RDF and RDF
Schema. It makes use of a forward-chaining inferencer to compute and store the
closure of its knowledge base whenever a transaction adds data to the
repository[
          <xref ref-type="bibr" rid="ref11 ref13">11</xref>
          ]. Sesame applies RDF-MT inference rules in a optimized way, making
use of the dependencies between them to eliminate most redundant inferencing
steps.
        </p>
        <p>To obtain a fuzzy RDF storage and inference tool it is only a matter of
modify Sesame RDF-MT inferencer, making it compute the correct truth values
for inferred statements, and to extend the underlying storage to make room for
a truth value (i.e., a number) for each statement.</p>
        <p>This shows how a simple proof-of-concept fuzzy RDF inferencer is easy to
implement. The starting point is the code base of an inference engine that
implements the RDF model theory.</p>
        <p>It can be shown that an inference engine implementing such rules is correct:
all its rules are valid, in the sense that a graph entails any larger graph that is
obtained by applying the rules to the original graph. There is no formal proof
that it is also complete, but there is not such a proof for plain RDF Model
Theory inference rules either.
consequent
iii: aaa rdf:type rdf:Property
kkk: xxx rdf:type zzz
where kkk = min(iii, jjj)
kkk: xxx rdf:type zzz
where kkk = min(iii, jjj)
kkk: uuu rdf:type zzz
where kkk = min(iii, jjj)
kkk: uuu rdf:type zzz
where kkk=min(iii, jjj)
jjj: xxx rdf:type rdfs:Resource
iii: uuu rdf:type rdfs:Resource
kkk: aaa rdfs:subPropertyOf ccc
where kkk=min(iii, jjj)
kkk: aaa rdfs:subPropertyOf ccc
where kkk=min(iii, jjj)
iii: xxx rdfs:subPropertyOf xxx
reflexivity of rdfs:subPropertyOf
kkk: xxx bbb yyy
where kkk=min(iii, jjj)
kkk: xxx bbb yyy
where kkk=min(iii, jjj)
iii: xxx rdfs:subClassOf rdfs:Resource
iii: xxx rdfs:subClassOf xxx
reflexivity of rdfs:subClassOf
kkk: xxx rdfs:subClassOf zzz
where kkk=min(iii, jjj)
kkk: xxx rdfs:subClassOf zzz
where kkk=min(iii, jjj)
kkk: aaa rdf:type yyy
where kkk=min(iii, jjj)
kkk: aaa rdf:type yyy
where kkk=min(iii, jjj)
iii: xxx rdfs:subPropertyOf rdfs:member
jjj: xxx rdfs:subClassOf rdfs:Literal
jjj: rdf:_* rdf:type rdfs:ContainerMembershipProperty
This is an extra rule for list membership
properties ( _1, _2, _3, ...). The RDF MT
does not specify a production for this.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Hendler</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lassila</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>The semantic web</article-title>
          .
          <source>Scientific American</source>
          (
          <year>2001</year>
          )
          <fpage>28</fpage>
          -
          <lpage>37</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Berners-Lee</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>What the semantic web can represent. W3C design issues</article-title>
          ,
          <source>World Wide Web Consortium (September</source>
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Hayes</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : RDF Semantics. W3C recommendation,
          <source>World Wide Web Consortium (10 February</source>
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Grant</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Beckett</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>RDF test cases</article-title>
          .
          <source>W3C recommendation, World Wide Web Consortium</source>
          (
          <year>2004</year>
          ) http://www.w3.org/TR/rdf-testcases/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Zadeh</surname>
            ,
            <given-names>L.A.</given-names>
          </string-name>
          :
          <article-title>A fuzzy set theoretic interpretation of linguistic hedges</article-title>
          .
          <source>Journal of Cybernetics</source>
          <volume>2</volume>
          (
          <year>1972</year>
          )
          <fpage>4</fpage>
          -
          <lpage>34</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Goldfarb</surname>
          </string-name>
          , W.D., ed.:
          <article-title>Logical Writings of Jacques Herbrand</article-title>
          . Harvard University Press, Cambridge (
          <year>1971</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Dubuois</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Prade</surname>
          </string-name>
          , H.:
          <article-title>Fuzzy sets and Systems</article-title>
          . Academic Press, New York, NJ (
          <year>1980</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Zadeh</surname>
            ,
            <given-names>L.A.</given-names>
          </string-name>
          :
          <article-title>Fuzzy sets</article-title>
          .
          <source>Information and Control</source>
          (
          <year>1965</year>
          )
          <fpage>338</fpage>
          -
          <lpage>353</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Zadeh</surname>
            ,
            <given-names>L.A.</given-names>
          </string-name>
          :
          <article-title>Calculus of Fuzzy Restrictions</article-title>
          . In:
          <article-title>Fuzzy Sets and Their Applications to Cognitive and Decision Processes</article-title>
          . Academic Press, New York (
          <year>1975</year>
          )
          <fpage>1</fpage>
          -
          <lpage>39</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Broekstra</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kampman</surname>
          </string-name>
          , A.,
          <string-name>
            <surname>van Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>Sesame: A generic architecture for storing and quering RDF and RDF Schema</article-title>
          . In Horrocks, I.,
          <string-name>
            <surname>Handler</surname>
          </string-name>
          , J., eds.
          <source>: Proceedings of the first International Semantic Web Conference (ISWC</source>
          <year>2002</year>
          ), Sardinia, Italy (
          <year>2002</year>
          )
          <fpage>54</fpage>
          -
          <lpage>68</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Broekstra</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kampman</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Inferencing and truth maintenance in RDF Schema: exploring a naive practical approach</article-title>
          .
          <source>In: Workshop on Practical and Scalable Semantic Systems (PSSS)</source>
          <year>2003</year>
          . Second International Semantic Web Conference (ISWC), Sanibel Island, Florida, USA (
          <year>2003</year>
          )
          <article-title># antecedents 1 iii: xxx aaa yyy 2.1 iii: xxx aaa yyy jjj: aaa rdfs:domain zzz 2.2 iii: aaa rdfs:domain zzz jjj: xxx aaa yyy 3.1 iii: xxx aaa uuu jjj: aaa rdfs:range zzz 3.2 iii: aaa rdfs:range zzz jjj: xxx aaa uuu 4a iii: xxx aaa yyy 4b iii: xxx aaa uuu 5a.1 iii: aaa rdfs:subPropertyOf bbb jjj: bbb rdfs:subPropertyOf ccc 5a.2 iii: bbb rdfs:subPropertyOf ccc jjj: aaa rdfs:subPropertyOf bbb 5b iii: xxx rdf:type rdf:Property 6.1 iii: xxx aaa yyy jjj: aaa rdfs:subPropertyOf bbb 6.2 iii: aaa rdfs:subPropertyOf bbb jjj: xxx aaa yyy 7a iii: xxx rdf:type rdfs:Class 7b iii: xxx rdf:type rdfs:Class 8.1 iii: xxx rdfs:subClassOf yyy jjj: yyy rdfs:subClassOf zzz 8.2 iii: yyy rdfs:subClassOf zzz jjj: xxx rdfs:subClassOf yyy 9.1 iii: xxx rdfs:subClassOf yyy jjj: aaa rdf:type xxx 9.2 iii: aaa rdf:type xxx jjj: xxx rdfs:subClassOf yyy</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <article-title>10 iii: xxx rdf:type rdfs:ContainerMembershipProperty</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <article-title>11 iii: xxx rdf:type rdfs:Datatype X1 iii: xxx rdf:_* yyy</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>