<!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>Cognitive System for Knowledge Representation of Elementary 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>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>AG Corporate Semantic, Department of Computer Science Freie Universitaet Berlin</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Background - The Fact Screening and Transformation</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>TelesPRI GmbH Berlin</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The focus of this article is to throw light on the imminent need for an effective system for extraction, representation and construction of legal norms, especially the national patent law norms. This system, complementary to the FSTP-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 first year of PhD research.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Facts Screening and Transformation Processor (FSTP)</kwd>
        <kwd>Innovation Test</kwd>
        <kwd>Innovation Expert System (IES)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation</title>
      <p>
        As described in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], “an innovation/creation over existing knowledge, provided as
a reference set RS of prior art documents, is representable by a technique teaching
TT.p which goes beyond the knowledge of the RS – just as in a patent/application.
      </p>
      <p>Elementary pragmatics are disclosures (explicit/implicit) of certain art which can be easily
understood by a person of pertinent skill
This compound of knowledge, representing an innovation, is called “PTR”, standing
for a “pair of TT.p and RS”.</p>
      <p>The Innovation Expert System (IES) thus is the PTR Expert System, defined 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 a PTR all technical facts for determining the “creativity geometrical”
height of TT.p over RS, and
2. Instantly recognizing and replying to any rational query as to any relation between
this TT.p and this prior art RS.</p>
      <p>The PTR Expert System (ES) is built around the PTR’s “FSTP Test” (FSTP
=“facts screening &amp; transforming processor”), and hence is also called FSTP ES. The
FSTP Test of a PTR supports initially screening its documents for all technical
informal fundamental facts, then transforming them into technical formal fundamental
facts, then transforming those into the technical primary facts, and finally
transforming them into the technical secondary facts, called basic resp. semantic (alias
creative) resp. pragmatic (alias innovative) facts. These technical secondary facts use
metrics induced by the Highest Courts precedents’ on creativity/innovation – by their
numbers of RS-orthogonal and independent thoughts embodied by TT.p. From the
basic facts the classical yes/no answer to the question, whether TT.p is indicated
obvious over RS, can be derived by this metric. The semantic/creative and
pragmatic/innovative facts extend this metric much further by first defining a PTR plcs
specific (plcs = patent law carrying semantic) innovation geometry, which depicts the
plcsheight/-creativity of its TT.p over its RS. Based on plcs-height/-creativity, TT.p’s
pragmatic/innovative height over RS additionally takes into account the PTR’s
“patent monopoly granting pragmatics”. A pmgp, 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.p. Hence a
subsystem capable of (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 pmgp based on NLS/ (NNI =
National Normative judicial Interpretation of facts).</p>
      <p>Figure 1, shows different Knowledge Representation (KR) domains with
subdomains which cause an impact on a PTR during FSTP Test. The object of our
concern in this thesis is to create KR domain dealing with NPS, and having EU PS, US
PS, AU PS etc. as sub-domains. The formal modeling involves modeling of NLS/NNI
by ontologies and rules using deductive (non-monotonic) reasoning for legal
interpretations and inductive logics for learning.
3</p>
      <p>Goals/Aim
1. To analyze and extract the rules and ontological concepts described in the natural
language descriptions of NPSs.
2. To identify the required semantics and inference rules needed for legal reasoning
with NPSs and for the legal interpretation enabling the separationg 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 ontologies domains representing the
conceptualization of the NPSs 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-off between required expressiveness of the knowledge
representation and its computational complexity of the legal reasoning in the FSTP
(b) Provide support for the different roles involved, such as inventor, person of
pertinent skill, examiner, patent agent etc. This requires different 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-specific executable formats on the logical
reasoning layer
(c) Provide support for life cycle management of the knowledge. This addresses
e.g., collaborative knowledge engineering and management (versioning,
different roles such as author, maintenance), updates in the NPSs by new decisions
which lead to corresponding isomorphic updates in the NPSs knowledge bases,
integration of internal and external (semantic) background knowledge e.g.
about skill, elementary pragmatics, usage data (annotations, proofs, etc.)
4</p>
    </sec>
    <sec id="sec-2">
      <title>Research Questions</title>
      <p>The research question will be refined 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 different representation layers? (human-oriented computational
independent, platform-independent supporting integration and interchange,
platform-specific 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”, …)</p>
      <sec id="sec-2-1">
        <title>3. Association problem:</title>
        <p>(a) How to connect the formal representation with the real-world resources and
norms?</p>
      </sec>
      <sec id="sec-2-2">
        <title>1. Fig. 1. Interdepence of domain ontologies (Source: [1])</title>
        <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).</p>
        <p>

</p>
        <p>Functional Requirements</p>
        <p>– e.g., expressiveness, …
Non functional requirements at design time
– e.g., composability and extensibility, interoperability, declarative
implementability, modifiability and evolvability, reusability and
interchangeability, …
Non functional properties at runtime
– e.g., usability, understandability and explanation, correctness and
quality, scalability and efficiency, safety and information hiding
(need-to-know principle), …
5</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <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="ref2">2</xref>
        ], DeepDyve, etc… retrieves patents through large
databases which forms the required RS (if previously not specified by the jury) for the
TT.p. Thus formed PTR will be transformed from their natural language texts into
some standard representation formats like XML, using text-mining and semantic
recognition and annotation techniques supporting human knowledge engineers in the
fact screening and transformation process.
      </p>
      <p>
        Similar to the PTR, the existing patent rules from NPS have to be transformed
from their natural language format to more standardized rule representation formats
like Reaction-RuleML [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], LKIF [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], or the upcoming Legal RuleML etc… 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 specific pragmatic contexts (skill ontologies, elementary pragmatics,
standards etc.) for a flexible processing and legal reasoning [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The required (patent)
rules/constraints are built by the rule creator module, which uses a rule-based agent
networks like Prova [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] for realizing distributed rule inference services.
      </p>
      <p>Such built rules maybe;
1. Simple: Built based simple on Patentable Subject Matter (PSM) constraints,
which are readilyavailable out of any NPS. Like,
/*Invention dealing with plant, animals or seeds are not permitted to be patented */
or</p>
      <p>/*Process of learning language, playing chess, teaching or operating machineryare
not patentable */
PSMCriteria1 ≡ (Invention Λ (Product V Process) Λ (¬</p>
      <p>Plant V ¬ Seed V ¬ Animal))
PSMCriteria2 ≡ (Process Λ (¬ LearningLanguage V ¬
PlayingChess V ¬ OperatingMachinery</p>
      <p>V ¬Teaching))
2. Complex : Built based on deductive logic [8] to match the elementary patent rules
with background facts then using inductive logic in generalizing goal facts into
rules that connect with background facts.</p>
      <p>/* use of any radioactive substance or any process for atomic energy production,
control or disposal cannot be patented */
PSMCriteria3 ≡ ∀ Invention ∃ SubjectMatter (Process Λ (¬
AtomicEnergy Λ (¬Production V ¬ Disposal V ¬</p>
      <p>Control)) Λ (∃ Element (¬RadioactiveSubstance)).
3. Compound: Built based on combination of several rules (deductive rule chaining).</p>
      <p>/*for prior-claiming, the invention claiming priority should have been patented in
US, the inventions priority-claim-date should be before the newly claimed invention
and publishing date should have been before the newlyclaimed invention*/
Criteria4 ≡ Invention Λ (Product V Process) Λ (Country
(US)))
Criteria5 ≡ InventionPriorityDate (ClaimingInvention &lt;
ClaimedInvention)</p>
      <p>Such built rules are assigned priorities using, e.g.defeasible logic and scoped
reasoning for distributed modularization of the knowledge bases (such as used in the
Rule Based Service Level Agreement project and supported by Reaction RuleML
(and the new upcoming Legal RuleML).</p>
      <p>Standardized rules with priorities enable arguments to be created, evaluated and
compared. One such category of rules are Elementary Pragmatic (EP) rules, which
including legal rules that can be applied at different fact gathering stages of the FSTP
expert system on a PTR. Few examples for such discretization stages and their
applicable elementary rules are as shown in Table 1.</p>
      <p>Elaborating more on the concept identification stage, validation of identified
concept/concepts is a process of filtering the concepts identified from a patent document,
TT.0 based on existing EP’s. Thereby, segregating them into non-patent-eligible,
‘npe’ and patent-eligible, ‘pe’ concepts. A concept under ‘pe’ may also be known as
creative concepts, Cr-C. Certain complex concepts need a combination of EP’s to be
applied together to classify them as ‘npe’ which would otherwise have been
considered as ‘pe’ concept.
5.1</p>
      <sec id="sec-3-1">
        <title>Proposed Framework</title>
        <p>
          We propose a legal information system framework as shown in Figure 3. The
proposed framework is built based on a general information system research framework
[
          <xref ref-type="bibr" rid="ref7">7</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’s, are fed by the Environment module and the
syntax, semantics, pragmatics and instantiations encompassing a norm are fed by the
Knowledge Base (KB) 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 norm’s expressiveness, extensibility and
interoperability criteria’s. Based on the results, the rules and the reasoner are refined
again. This iterative process of (re-)assessing and refining is completed when all
criteria’s are effectively 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 are is sent back to KB module.
        </p>
        <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>
      <sec id="sec-3-2">
        <title>FSTP discretization stages</title>
        <sec id="sec-3-2-1">
          <title>Element identification stage Attribute identification stage</title>
        </sec>
        <sec id="sec-3-2-2">
          <title>Concept identification stage</title>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>Elementary rules applicable</title>
        <p>PSMCriteria1</p>
        <sec id="sec-3-3-1">
          <title>PSMCriteria2</title>
        </sec>
        <sec id="sec-3-3-2">
          <title>PSMCriteria3</title>
        </sec>
      </sec>
      <sec id="sec-3-4">
        <title>Explanation</title>
        <sec id="sec-3-4-1">
          <title>Elements with Plant or Animals or Seeds not permitted</title>
        </sec>
        <sec id="sec-3-4-2">
          <title>Attributes having below methods</title>
          <p>are not permitted
a. Method of learning language
b. Method of teaching
c. Method of operating machine
Concepts with below references are
not permitted
a. Musical notations
b.Coloring substance for
identifi</p>
          <p>cation
c. Atomic energy
i. Production
ii. Control
iii. Disposal
d. Radioactive substance</p>
          <p>EP can be divided into 4 types, table 2 shows few trivial example concepts
considered as ‘npe’ for each EP mentioned above:</p>
        </sec>
        <sec id="sec-3-4-3">
          <title>EP from Natural Laws of Nature, EP-NL EP from Natural Phenomenon’s, EP-NP EP from National Legal(Patent) Systems, EP-NPS EP from Skill Documents/Standards, EP-STD</title>
          <p>EP
EP-NL
EP-NP
EP-NPS
EP-STD</p>
        </sec>
      </sec>
      <sec id="sec-3-5">
        <title>Concepts related to</title>
        <p>Speed of light
Theory of relativity E= mc2
Dijkstra Algorithm
Gravity
Human metabolism
Method of learning Language
Method of teaching
Production/Control/Disposal of atomic energy
Maximum delay for data transfer in ordinary telephone is 0.5 secs</p>
        <p>ISDN line has a stack of three protocols
Concepts:</p>
        <p>C1: Physician administers the drug given to the patient using ‘administering step’
C2: Physician measures the resulting metabolic levels in the patient’s blood
C3: Physician compares the patients metabolic level against known safe and effect
tive metabolic levels and then decided to increase or decrease the drug dosage.
Even though all concepts defined above seems to qualify all criteria’s at the first
glance, On addition of pragmatic context (using micro-ontologies) to our analysis,
Concepts, C2 and C3 identified in the above example fail to qualify the ‘criteria 9’,
while concept C1 qualifies the ‘PSMCriteria1’, ‘Criteria 8’ and ‘criteria 9’, it fails to
qualify ‘PSMCriteria2’. Thus, grouping all identified concepts as ‘npe’.</p>
      </sec>
      <sec id="sec-3-6">
        <title>Newman vs United States Patent Office.</title>
        <p>Invention summary: A device which will produce mechanical power exceeding the
electrical power being supplied to it.</p>
        <p>Concepts:</p>
        <p>C1: Electromagnetic energy can be rendered by a rotating permanent magnet
spinning inside an electromagnetic pulsating conducting coil.</p>
        <p>C2: Rotating permanent magnet spinning inside an electromagnetic pulsating coil
utilizes the coil mass energy and turns in into torque.</p>
        <p>{EP-NL, EP-STD}
{EP-STD}
{EP-NPS}
Concepts C1 and C2 do not pass the ‘criteria 9’ while a concept formed by combining
concept C1 and C2 would also fail to qualify the PSMCriteria1. Thus making the
entire invention as ‘npe’.
6</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>The solution to have a sub-system, based on configurable 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
scientific fact determined during FSTP analysis. This would then help in applying the
(elementary) cognitive norms required for interpretation and evaluation of such
identified facts.
7
8</p>
    </sec>
    <sec id="sec-5">
      <title>Acknowledgements References</title>
      <p>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>
            <given-names>S.</given-names>
            <surname>Schindler</surname>
          </string-name>
          , “
          <article-title>THE FSTP EXPERT SYSTEM (FSTP = Facts-Screening-andTransforming-</article-title>
          <string-name>
            <surname>Processor</surname>
            <given-names>)</given-names>
          </string-name>
          ,”
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>K.</given-names>
            <surname>Dahlgren</surname>
          </string-name>
          , “
          <article-title>Technical Overview of Cognition's Semantic NLP TM ( as Applied to Search</article-title>
          ),” ReCALL, pp.
          <fpage>1</fpage>
          -
          <lpage>20</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <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>
          , &amp;
          <string-name>
            <surname>Athan</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          (
          <year>2012</year>
          ).
          <source>Reaction RuleML 1</source>
          .0:
          <string-name>
            <given-names>Standardized</given-names>
            <surname>Semantic Reaction</surname>
          </string-name>
          <article-title>Rules</article-title>
          .
          <source>RuleML</source>
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Thomas</surname>
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Gordon</surname>
          </string-name>
          . (
          <year>2008</year>
          ).
          <article-title>The Legal Knowledge Interchange Format ( LKIF ).</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Hans</given-names>
            <surname>Weigand</surname>
          </string-name>
          , Adrian. Paschke. (
          <year>2012</year>
          ).
          <article-title>The Pragmatic Web: Putting Rules in Context</article-title>
          .
          <source>RuleML</source>
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Paschke</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Boley</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          (
          <year>2011</year>
          ). RULE RESPONDER:
          <article-title>Rule-Based Agents for the Semantic-Pragmatic Web</article-title>
          .
          <source>International Journal on Artificial Intelligence Tools (IJAIT)</source>
          ,
          <volume>20</volume>
          (
          <issue>06</issue>
          ),
          <fpage>1043</fpage>
          -
          <lpage>1081</lpage>
          . doi:
          <volume>10</volume>
          .1142/S0218213011000528.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hevner</surname>
          </string-name>
          , Alan R.; March, Salvatore T.; Park, Jinsoo; and Ram, Sudha.
          <year>2004</year>
          .
          <article-title>"</article-title>
          <source>Design Science in Information Systems Research," MIS Quarterly</source>
          , (
          <volume>28</volume>
          : 1)
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>