<!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>First Approaches on Knowledge Representation of Elementary (Patent) Pragmatics</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Shashishekar Ramakrishna</string-name>
          <email>s.ramakrishna@teles.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Freie Universitat Berlin, Konigin-Luise-Str.</institution>
          <addr-line>24-26, 14195 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Teles PRI GmbH</institution>
          ,
          <addr-line>Ernst-Reuter-Platz 8, 10587 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The focus of this article is to provide rst approachs to a possible key solution representation and construction of legal norms, especially the national patent law norms. A semantic-system based on these approaches, complementary to the FSTP/IES-Expert system, would aim at (semi)-automatically translating the parts of the notion legal certainty from its natural language non procedural presentation to a declarative logical presentation by formal modeling through interpreting the pragmatics facts based within a National Legal Systems. This paper covers the initial abstract solutions and possible outcomes as gathered during the rst year of PhD research3.</p>
      </abstract>
      <kwd-group>
        <kwd>Facts Screening and Transformation Processor (FSTP)</kwd>
        <kwd>Innovation Test</kwd>
        <kwd>35 U</kwd>
        <kwd>S</kwd>
        <kwd>C (xx 112</kwd>
        <kwd>102/103</kwd>
        <kwd>and 101)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Current emerging technologies are mostly 'Model' based inventions i.e. intangible
subject matter based. In general, an innovation claimed through its patent
application, can be seen as a pair &lt;claim, its claimed invention&gt;, wherein the
speci cation (including drawings) forms the second part of the pair. An inventive
property/statement of an invention, disaggregated on levels of abstraction or on
grains of mental resolution into elementarily properties henceforth referred as
binary inventive concept. It provides the required degrees of separation of concerns
for evaluating such properties independently in the light of its subject matter.
Next to trivial elementary inventive concepts are logically error resistant as they
represent a single/separated concern. The same holds for a non-inventive concept
of a claimed inventions element, describing one of its non-inventive properties.</p>
      <p>
        (Semi)-/Automatic evaluation by means of applying elementary
pragmatics, 'EP' and National Patent Laws on such binary (non-)inventive concepts
requires a semanticsystem for reasoning against the considered concepts, capable of
the acquisition and processing of enormous amounts of background knowledge
in a machine understandable format, keeping in mind its interdependence to
each other. Such a (sub)-system working in conjunction with the existing Facts
Screening and Transformation Processor, FSTP [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]/Innovation Expert System,
IES [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], enables a person of pertinent skill, who is needed for recognizing
nonelementary pragmatics, to recognize automatically and/or guided interactively
by the FSTP/-IES to consider whether such elementary properties of an
innovation at issue (after its disaggregation) can be considered as Anticipate (A),
Not-Anticipate (N) to its prior arts/considered reference set (RS).
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Background - The Fact Screening and Transformation</title>
      <p>
        As described in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] an innovation/creation over existing knowledge, provided
as a reference set RS of prior art documents, is representable by a technique
teaching, TT.0 which goes beyond the knowledge of the RS - just as in a
patent/application. This compound of knowledge, representing an innovation, is called
\PTR", standing for a \pair of TT.0 and RS".
      </p>
      <p>The Innovation Expert System (IES) thus is the PTR Expert System, de ned
by the epistemological and practical requirements it meets: For any PTR to
which it is applied, it is supporting its user in
1. deriving from it all technical and legal facts alias relations between TT.0 and
a given RS respectively a given context, such as a given legal system (in the
U.S e.g. to 35 U.S.C xx 112, 102/103, and 101) and then
2. leveraging on this analysis instantly recognizing and answering any
reasonable query for any such relation</p>
      <p>
        The PTR Expert System (ES) is built around the PTRs \FSTP Test" [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
hence is also called FSTP ES. The FSTP Test of a PTR supports structuring
of its PTR. This PTR-DS is disaggregated into three levels of knowledge
representations (KR), \o/AD/BID"-KR. Wherein, o refers to \original", AD to
\Aggregated ^ Disclosed", and BID to \Binary ^ Independent ^ Disclosed".
IES supports, initially screening its documents/technical teachings for
elementary building blocks of its creativity/inventivity, i.e. for its inventive and
noninventive concepts. Technical informal inventive and non inventive concepts/
properties are then transformed into technical formal inventive concepts/facts,
then transforming those into the technical primary facts, and nally
transforming them into the technical secondary facts, called basic resp. semantic (alias
creative) resp. textbfpragmatic (alias innovative) facts. These technical
secondary facts use metrics induced by the Highest Courts precedents on
creativity/innovation by their numbers of BID-inventive concepts embodied by TT.0.
From these BID-inventive concepts, the classical yes/no answer to the question,
whether TT.0 is indicated obvious over RS, can be derived by this metric. The
semantic/creative and pragmatic/innovative facts extend this metric much
further by rst de ning a PTR plcs speci c (plcs = patent law carrying semantic)
innovation geometry, which depicts the plcs-height/-creativity of its TT.0 over its
RS. Based on plcs-height/-creativity, TT.0s pragmat-ic/innovative height over
RS additionally takes into account the PTRs pmgp (pmgp= patent monopoly
granting pragmatics) in any National Patent System (NPS) which represents the
national/socio/economic principles underlying the idea of rewarding an
innovation by granting a 20 years monopoly to its TT.0.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Goals/Aim</title>
      <p>The object of our concern in this thesis is to create a semantic-system, capable of
(semi-) automatically translating the parts of the notion \legal certainty" such
as patent laws (e.g. in U.S, 35 U.S.C xx 112, 102/103, and 101) from its natural
language non procedural presentation to a declarative logical presentation by
formal modeling through interpreting pmgp based on NLS/ (NNI = National
Normative judicial Interpretation of facts).</p>
      <p>
        Figure 1, shows few (10+) basic tests as proposed in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] enabled by its
inventive concepts, automatically prompting their user through exploratively checking
its meeting the requirements as stated by few NPS'es (e.g.: 35 USC 112, 102/103,
and 101). Applying these tests to inventive concepts requires the requirements
of the NPS'es to be modeled into declarative rules, due to their modular feature
and their capability to use the same knowledge in many di erent ways. Modeled
rules are used in deductive (non-monotonic) reasoning for legal interpretations.
NPS'es, like complex computer systems, constantly face questions that aim to
ascertain the state of things or the correctness of a certain contention, like these
modeled rules/tests. Hence, the legal questions regarding which of a number of
modeled/competing legal rules could apply in a given situation amount to some
error and inconsistencies, thereby leading to inconsistent reasoned
output/legal interpretations. One such non-trivial approach would be that such modeled
rulebases are updated manually/guided by the system using inductive learning
techniques (applying rules on case laws). Such an approach would be a long term
goal and is not considered for the current use-cases shown in this thesis. The list
below re- expresses the intended aim, providing possible approaches/solutions
to the research question stated in Section 4 of this thesis in detail:
1. To manually(and/guided-by-system) analyze and extract the rules and
ontological concepts described in the natural language descriptions of NPS'es.
2. To identify the required semantics and inference rules needed for legal
reasoning with NPS'es and for the legal interpretation enabling the separating
of novel innovations from obvious steps.
3. Logic-based declarative representation of these chains of complex rules for
legal reasoning on top of structured formal ontology domains representing
the conceptualization of the NPS'es and the underlying domains of skill and
elementary pragmatics.
4. Developing a legal reasoning sub-system to the FSTP ES which allows pmgp
dependent information to be derived from the NPS knowledge bases and to
be used in the FSTP for semi-automated legal decision support and
compliance checks with the applicable NPS for a PTR. This includes
(a) Address the trade-o between required expressiveness of the knowledge
representation and its computational complexity of the legal reasoning
in FSTP.
(b) Provide support for the di erent roles involved, such as inventor,
person of pertinent skill, examiner, patent agent etc. This requires di erent
representation languages from natural language format for expressing
questions, answers, proofs and explanations to platform-independent
serializations in XML and Semantic Web formats to platform-speci c
executable formats on the logical reasoning layer.
(c) Provide support for life cycle management of knowledge. This addresses
e.g., collaborative knowledge engineering and management (versioning,
di erent roles such as author, maintenance), updates in the NPSes by
new decisions which lead to corresponding isomorphic updates in the
NPSes knowledge bases, integration of internal and external (semantic)
background knowledge e.g. about skill, elementary pragmatics, usage
data (annotations, proofs, etc.).
The research question will be re ned and detailed after the literature review
and baseline study, from the following general problem domains of a knowledge
representation.
1. Syntax:
(a) Which representation and interchange format for the representation of
the knowledge on di erent representation layers? (human-oriented
computational independent, platform-independent supporting integration and
interchange, platform-speci c logical reasoning).
2. Semantics:
(a) Which inference and interpretation semantics (non-monotonic vs.
monotonic, expressiveness vs. computational complexity, closed-world vs. open
world, \ontologies vs./and rules", )
3. Association problem:
(a) How to connect the formal representation with the real-world resources
and norms?
      </p>
      <p>Requirements derived from these knowledge representation problem domains
can be distinguished according to functional requirements for the concrete
knowledge representation and non-functional requirements during design time
(development / engineering of the knowledge) and run time (use of the knowledge).
1. Functional Requirements:</p>
      <p>(a) e.g., expressiveness, ...
2. Non functional requirements at design time:
(a) e.g., composability and extensibility, interoperability, declarative
implementability, modi ability and evolvability, reusability and
interchangeability,...
3. Non functional properties at runtime:
(a) e.g., usability, understandability and explanation, correctness and
quality, scalability and e ciency, safety and information hiding
(need-toknow principle),...
5</p>
    </sec>
    <sec id="sec-4">
      <title>Proposed Approach</title>
      <p>
        An abstract model of the system envisioned as a solution to the problem can
be seen in Figure 2. An existing state-of-the-art prior art search module, using
a semantic search engines like, Cognition [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], DeepDyve, etc retrieves patents
through large databases which forms the required RS (if previously not speci ed
by the jury) for the TT.0. Thus formed PTR-DS will be transformed from their
natural language texts into some standard representation formats like XML,
using text-mining, semantic recognition and annotation techniques supporting
human knowledge engineers in the fact screening and transformation process.
Similar to the PTR-DS, the existing patent rules from NPS have to be
transformed from their natural language format to more standardized rule
representation formats. We propose to use LegalRuleML [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], an XML standard for legal
knowledge representation based on RuleML [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] which supports the modeling of
norms.
      </p>
      <p>
        Parallely, we map patent norms as used in landmark case law decisions to
a work ow using some con gurable work ow model. Where, each node on the
work ow (B-tree) represents a complex legal rule represented using the
ReactionRuleML [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] representation format. This resolves complex legal questions and
automates the analysis of a large number of patent norms with respect to their
logical coherence in a given NPS. The work ow itself is represented using
LegalRuleML, which provides the functionalities likes reusability, lifecycle
management of nodes or the entire work ow to capture the changes over time of the
rules when the legal binding text changes.
      </p>
      <p>
        LegalRuleML is also be used to point out logical inconsistencies in current
case law decisions and can also be used to evaluate the compliance of semantic
facts with case law and positive law. Thereby, providing a powerful and
declarative way to control and reuse such semantically linked meanings with the help
of independent micro-ontologies about the NPSs and domain speci c pragmatic
contexts (skill ontologies, elementary pragmatics, standards etc.) for exible
processing and legal reasoning. The required (patent) rules/constraints are built by
the rule creator module, which uses a distributed rule inference services network
like Prova [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ], a java based open source rule language for reactive agents and
event processing.
      </p>
      <p>Figure 3 shows the process of generating a generic work ow pertaining legal
rule from landmark decisions' speci c work ow. This allows capturing the di
erent interpretations of the same law on di erent use cases and, thereby, arriving
at a generalized work ow.
6</p>
    </sec>
    <sec id="sec-5">
      <title>Elementary Pragmatics</title>
      <p>Elementary Pragmatics are disclosures (explicit/implicit) of certain art which
can be easily understood by a person of pertinent skill. According to certain
National Patent Systems, an EP must not be just claimed to exist, but must be
documented in an enabling way.</p>
      <sec id="sec-5-1">
        <title>EP can be divided into 4 types as shown in Figure 4 :</title>
      </sec>
      <sec id="sec-5-2">
        <title>1. EP from Formal Rules for Filing, EP-PFP 2. EP from Patentability Conditions, EP-P 3. EP from Post Grant Procedures, EP-PGP 4. EP from Litigation, EP-L</title>
        <p>
          We narrow down our focus on Elementary Pragmatics from Patentability
Conditions, EP-P. Speci cally on four paragraphs (35 USC xx 112, 102/103, and
101) of the U.S patent system [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. Figure 5 shows the general evaluation
procedure for an inventive concept under patentability. A set of inventive concepts
is patent eligible, 'pe' if and only if it satis es all the patentability criterias or
EP- P's.
        </p>
        <p>
          We propose a legal information system framework [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] as shown in Figure 6. The
proposed framework is based on a general information system research
framework [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. The central 'Research' module is fed with information from both
'Environment' and 'Knowledge Base (KB)' modules. Information/raw material
such as FSTP facts, which include the norms from various NPS'es, are fed by the
'Environment' module and the syntax, semantics, pragmatics and instantiations
encompassing a norm are fed by the 'Knowledge Base' module. The central
research module works towards building the inference rules required for the legal
reasoner. The 'develop/build' sub-module including legal reasoner is evaluated
for the norms expressiveness, extensibility and interoperability criteria's. Based
on the results, the rules and the reasoner are re ned again. This iterative process
of (re-)assessing and re ning is completed when all criteria are e ectively
evaluated. Processed information is fed back to the environment module for its actual
usage within the FSTP ES. Additional information for the lifecycle management
of a norm and its contexts is sent back to KB module.
7.1
        </p>
        <p>
          Methodologies
Elaborating on the process of mapping patent norms to work ow models we start
with the representation of all landmark case-law decisions concerning a speci c
norm onto a work ow. Wherein, LegalRuleML is used for such representation.
We reiterate the formal template of LegalRuleML showing the most general
representation syntax as de ned in [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ].
        </p>
        <p>
          Each node on the work ow represents a disaggregated rule/norm. Such rule
or set of rules are embedded inside &lt; lrml: Statements &gt; using
ReactionRuleML. Listing 1.2 shows a formal template of ReactionRuleML, showing the
most general representation syntax as de ned in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
/&lt;Rule &gt;
&lt;! --rule info and life cycle management , modularization --&gt;
&lt;! --( semantic ) metadata of the rule --&gt;
&lt;meta &gt; ... &lt;/ meta &gt;
&lt;! --scope of the rule e.g. a rule module --&gt;
&lt;scope &gt; ... &lt;/ scope &gt;
&lt;! --rule interface description --&gt;
&lt;! -- intended semantic profiles --&gt;
&lt; evaluation &gt; ... &lt;/ evaluation &gt;
&lt;! --rule interface signature and modes --&gt;
&lt; signature &gt; ... &lt;/ signature &gt;
Disaggregated patent rules are wrapped to form a reactive agent as shown in
for hybrid reasoning due to the fuzzy nature of patent rules. ReactionRuleML
messaging is used for distributed reasoning. Listing 1.3 shows general message
syntax.
        </p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Examples</title>
      <p>
        35 U.S.C x 112 6th paragraph
Consider the latest Court of Appeals of Federal Circuit (CAFC) decision on
x 112 6th paragraph in Lighting Ballast Control LLC v. Philips Electronics
and Universal Lighting Technologies, Inc' [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Under this decision the court
reexplained the norms within the 6th paragraph of x 112 (35. U.S.C Patent law).
For our analysis, we map the decision and its citations into work ow. Figure 8[a]
shows some excerpts from the decision itself. Figure 8[b] shows the work ow
mapped from the decision for the analysis of \Means-Plus-Functions-Claiming"
In its decision, the CAFC with the help of citations explains how other factors
in uencing this decision have to be handled.
      </p>
      <p>
        We propose to use inductive approaches by populating the work ow with
related decisions ('Biomedino LLC v. Water Techs Corp' [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], 'MIT v. Abacus
Software' [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], 'Greenberg v. Ethicon Endo Surgery, Inc' [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] etc) to obtain a
generic work ow for 6th paragraph of x 112 as shown in Figure 9. Where, the
norm in work ow format is represented using LegalruleML representation format
described before and the nodes/rules are represented using ReactionRuleML. For
this example we use Stanford parser, SentiwordNet, Prova and Pre de ned legal
lexicons, PUBPAT as semantic interface for reasoning the norms. A person of
pertinent ordinary skill and creativity (posc) as de ned by USSC a rms every
reasoned result.
      </p>
    </sec>
    <sec id="sec-7">
      <title>Conclusion and Future Steps</title>
      <p>The solution to have a sub-system, based on con gurable EP which connects
the FSTP ES, thus making it full/-semi automatized in handling queries
pertaining to EP and NLS thereby, providing a uniform platform for standardizing
the generation and representation of complex rules (built using fewer NPS goal
clauses/(patent) rules. Such a system would serve as a ready reckoner in
drawing legal conclusions on top of scienti c fact determined during FSTP analysis.
This would then help in applying the (elementary) cognitive norms required for
interpretation and evaluation of such identi ed facts.
10</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgements</title>
      <p>The author would like to thank Prof. Adrian Paschke and Prof. Sigram Schindler
for their constructive comments and suggestions. This work has been partially
supported by the Fact Screening and Transformation Project (FSTP) funded by
the TelesPRI GmbH: www.fstp-expert-system.com.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Schindler</surname>
            <given-names>S.:</given-names>
          </string-name>
          <article-title>THE FSTP EXPERT SYSTEM</article-title>
          ,
          <year>WO 2012</year>
          /
          <article-title>022612 A1 (to Sigram Schindler Beteiligungsgesellschaft mbh</article-title>
          [DE/DE];
          <article-title>Ernst-Reuter-Platz 8 10587 Berlin</article-title>
          (DE)),
          <fpage>23</fpage>
          <string-name>
            <surname>February</surname>
          </string-name>
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Schindler</surname>
            <given-names>S.:</given-names>
          </string-name>
          <article-title>INNOVATION EXPERT SYSTEM, IES, AND ITS PTR DATA STRUCTURE, PTR-DS (to Sigram Schindler Beteiligungsgesellschaft mbh</article-title>
          [DE/DE];
          <article-title>Ernst-Reuter-Platz 8 10587 Berlin</article-title>
          (DE)), May
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Ramakrishna</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karam</surname>
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paschke</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The FSTP Test: a novel approach for an invention's non-obviousness analysis</article-title>
          ,
          <source>JURIX</source>
          <year>2012</year>
          , pp
          <fpage>129</fpage>
          -
          <lpage>132</lpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <article-title>Brief of Amicus Curiae Sigram Schindler Beteiligungsgesellschaft mbH in support of neither party, LIGHTING BALLAST v</article-title>
          .
          <source>PHILIPS ELECTRON</source>
          (
          <year>2008</year>
          ), No.
          <year>2012</year>
          -
          <fpage>1014</fpage>
          (USSC, pending),
          <source>28 May</source>
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dahlgren</surname>
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Technical Overview of Cognition s Semantic NLP (as Applied to Search )</article-title>
          , ReCALL, pp.
          <fpage>120</fpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Palmirani</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rotolo</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tabet</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            <given-names>H.</given-names>
          </string-name>
          , and Paschke A.:
          <article-title>LegalRuleML: XML-Based Rules and Norms</article-title>
          ,
          <source>in Rule - Based Modeling and Computing on the Semantic Web</source>
          , vol.
          <volume>7018</volume>
          , Springer Berlin Heidelberg,
          <year>2011</year>
          , pp.
          <fpage>298</fpage>
          -
          <lpage>312</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Boley</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paschke</surname>
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Sha</surname>
          </string-name>
          q O.:
          <article-title>RuleML 1.0: The Overarching Speci cation of Web Rules</article-title>
          , in RuleML,
          <year>2010</year>
          , pp.
          <fpage>162</fpage>
          -
          <lpage>178</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Paschke</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Teymourian</surname>
            <given-names>K.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Athan</surname>
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Reaction RuleML 1.0: Standardized Semantic Reaction Rules</article-title>
          , in
          <source>RuleML</source>
          <year>2012</year>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kozlenkov</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Prova Rule Language Version 3.0 User's Guide</article-title>
          , Internet: http://prova. ws/index. html,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>Title 35 of the United States Code</article-title>
          .
          <year>1952</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Ramakrishna</surname>
            <given-names>S.:</given-names>
          </string-name>
          <article-title>Cognitive System for Knowledge Representation of Elementary Pragmatics</article-title>
          ,
          <source>in Proceedings of the RuleML2012 Challenge, at the 6th International Symposium on Rules</source>
          ,
          <year>2012</year>
          , online ceur-ws.
          <source>org/</source>
          Vol-
          <volume>874</volume>
          /paper2.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Hevner</surname>
            <given-names>A R.</given-names>
          </string-name>
          , March S T.,
          <string-name>
            <surname>Park</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <source>and Ram S.:Design science in information systems research, MIS Quarterly</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Athan</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Boley</surname>
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmirani</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paschke</surname>
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Wyner</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>OASIS LegalRuleML</article-title>
          ,
          <source>in Proceedings of 14th International Conference on Articial Intelligence and Law (ICAIL</source>
          <year>2013</year>
          ),
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <article-title>Lighting Ballast Control LLC v. Philips Electronics and Universal Lighting Technologies</article-title>
          , Inc No.
          <year>2012</year>
          -
          <volume>1014</volume>
          (Fed.
          <source>Cir. January 2</source>
          ,
          <year>2013</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Biomedino</surname>
          </string-name>
          , LLC v. Waters Techs. Corp.,
          <volume>490</volume>
          F.3d
          <volume>946</volume>
          ,
          <issue>949</issue>
          (Fed. Cir.
          <year>2007</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. MIT v.
          <source>Abacus Software</source>
          ,
          <volume>462</volume>
          F.3d
          <volume>1344</volume>
          ,
          <issue>1353</issue>
          (Fed. Cir.
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. Greenberg v. Ethicon
          <string-name>
            <surname>Endo-Surgery</surname>
          </string-name>
          , Inc., 91 F.3d
          <volume>1580</volume>
          ,
          <issue>1583</issue>
          (Fed. Cir.
          <year>1996</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>