<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">First Approaches on Knowledge Representation of Elementary (Patent) Pragmatics</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Shashishekar</forename><surname>Ramakrishna</surname></persName>
							<email>s.ramakrishna@teles.de</email>
							<affiliation key="aff0">
								<orgName type="institution">Freie Universität Berlin</orgName>
								<address>
									<addrLine>Königin-Luise-Str. 24-26</addrLine>
									<postCode>14195</postCode>
									<settlement>Berlin</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Teles PRI GmbH</orgName>
								<address>
									<addrLine>Ernst-Reuter-Platz 8</addrLine>
									<postCode>10587</postCode>
									<settlement>Berlin</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">First Approaches on Knowledge Representation of Elementary (Patent) Pragmatics</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">7314C30E9E0F79F3A56E4F430C7ECCB3</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T01:07+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Facts Screening and Transformation Processor (FSTP)</term>
					<term>Innovation Test</term>
					<term>35 U.S.C ( § § 112</term>
					<term>102/103</term>
					<term>and 101)</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The focus of this article is to provide first 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 first year of PhD research 3 .</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Motivation</head><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 specification (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 <ref type="bibr" target="#b0">[1]</ref>/Innovation Expert System, IES <ref type="bibr" target="#b2">[2]</ref>, 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).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Background -The Fact Screening and Transformation</head><p>As described in <ref type="bibr" target="#b0">[1]</ref>, <ref type="bibr" target="#b2">[2]</ref> 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, 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 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 § § 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" <ref type="bibr" target="#b4">[3]</ref>, 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 finally 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 first defining a PTR plcs specific (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.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Goals/Aim</head><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 § § 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 <ref type="figure" target="#fig_0">1</ref>, shows few (10+) basic tests as proposed in <ref type="bibr" target="#b5">[4]</ref> 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 different 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:</p><p>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-off between required expressiveness of the knowledge representation and its computational complexity of the legal reasoning in FSTP.</p><p>(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 knowledge. This addresses e.g., collaborative knowledge engineering and management (versioning, different 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 refined and detailed after the literature review and baseline study, from the following general problem domains of a knowledge representation.</p><p>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:</p><p>(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:</p><p>(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).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Functional Requirements:</head><p>(a) e.g., expressiveness, ... 2. Non functional requirements at design time:</p><p>(a) e.g., composability and extensibility, interoperability, declarative implementability, modifiability and evolvability, reusability and interchangeability,...</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Non functional properties at runtime:</head><p>(a) e.g., usability, understandability and explanation, correctness and quality, scalability and efficiency, safety and information hiding (need-toknow principle),...</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Proposed Approach</head><p>An abstract model of the system envisioned as a solution to the problem can be seen in Figure <ref type="figure" target="#fig_1">2</ref>. An existing state-of-the-art prior art search module, using a semantic search engines like, Cognition <ref type="bibr" target="#b6">[5]</ref>, DeepDyve, etc retrieves patents through large databases which forms the required RS (if previously not specified 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 <ref type="bibr" target="#b7">[6]</ref>, an XML standard for legal knowledge representation based on RuleML <ref type="bibr" target="#b8">[7]</ref> which supports the modeling of norms.</p><p>Parallely, we map patent norms as used in landmark case law decisions to a workflow using some configurable workflow model. Where, each node on the workflow (B-tree) represents a complex legal rule represented using the Reac-tionRuleML <ref type="bibr" target="#b9">[8]</ref> 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 workflow itself is represented using Legal-RuleML, which provides the functionalities likes reusability, lifecycle management of nodes or the entire workflow 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 specific pragmatic contexts (skill ontologies, elementary pragmatics, standards etc.) for flexible 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 <ref type="bibr" target="#b10">[9]</ref>, a java based open source rule language for reactive agents and event processing.</p><p>Figure <ref type="figure">3</ref> shows the process of generating a generic workflow pertaining legal rule from landmark decisions' specific workflow. This allows capturing the different interpretations of the same law on different use cases and, thereby, arriving at a generalized workflow.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Elementary Pragmatics</head><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. We narrow down our focus on Elementary Pragmatics from Patentability Conditions, EP-P. Specifically on four paragraphs (35 USC § § 112, 102/103, and 101) of the U.S patent system <ref type="bibr" target="#b11">[10]</ref>. Figure <ref type="figure" target="#fig_3">5</ref> 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 satisfies all the patentability criterias or EP-P's.  We propose a legal information system framework <ref type="bibr" target="#b12">[11]</ref> as shown in Figure <ref type="figure" target="#fig_4">6</ref>. The proposed framework is based on a general information system research framework <ref type="bibr" target="#b13">[12]</ref>. 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 refined again. This iterative process of (re-)assessing and refining is completed when all criteria 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 is sent back to KB module.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.1">Methodologies</head><p>Elaborating on the process of mapping patent norms to workflow models we start with the representation of all landmark case-law decisions concerning a specific norm onto a workflow. Wherein, LegalRuleML is used for such representation. We reiterate the formal template of LegalRuleML showing the most general representation syntax as defined in <ref type="bibr" target="#b14">[13]</ref>.</p><p>/ &lt; l r m l : L e g a l R u l e M L &gt; &lt;! --Referencing the textual provisions --&gt; &lt; l r m l : L e g a l S o u r c e &gt; ... &lt;/ l r m l : L e g a l S o u r c e &gt; &lt;! --Capturing the ex -ternal temporal dimensions of the rules are represented --&gt; &lt; l r m l : T i m e I n s t a n t s &gt; ... &lt;/ l r m l : T i m e I n s t a n t s &gt; &lt; l r m l : T e m p o r a l C h a r a c t e r i s t i c s &gt; ... &lt;/ l r m l : T e m p o r a l C h a r a c t e r i s t i c s &gt; &lt;! --Agent and the authority of the rules for provenance --&gt; &lt; lrml:Agents &gt; ... &lt;/ lrml:Agents &gt; &lt; l r m l : A u t h o r i t i e s &gt; ... &lt;/ l r m l : A u t h o r i t i e s &gt; &lt;! --Associates property values to rules and also adds metadata such as jurisdiction , role , and strength --&gt; &lt; lrml:Context &gt; &lt; l r m l : a p p l i e s R o l e &gt; &lt; l r m l : a p p l i e s S t r e n g t h &gt; &lt; l r m l : a p p l i e s A u t h o r i t y &gt; ... &lt;/ l r m l : a p p l i e s A u t h o r i t y &gt; &lt; l r m l : a p p l i e s J u r i s d i c t i o n &gt; .. &lt;/ l r m l : a p p l i e s J u r i s d i c t i o n &gt; &lt;/ l r m l : a p p l i e s S t r e n g t h &gt; &lt;/ l r m l : ap p l i e s R o l e &gt; &lt;/ lrml:Context &gt; &lt;! --Rules ( constitutive and prescriptive ) are modelled --&gt; &lt; l rm l: St a te me nt s &gt; &lt; Rule &gt; .. &lt;! --Reactio nRuleML --&gt; .. &lt;/ Rule &gt; &lt;/ l rm l :S ta te m en ts &gt; &lt;/ lr m l : L e g a l R u l e M L &gt; Listing 1.1. General LegalRuleML syntax Each node on the workflow represents a disaggregated rule/norm. Such rule or set of rules are embedded inside &lt; lrml: Statements &gt; using Reaction-RuleML. Listing 1.2 shows a formal template of ReactionRuleML, showing the most general representation syntax as defined in <ref type="bibr" target="#b9">[8]</ref>. Disaggregated patent rules are wrapped to form a reactive agent as shown in Figure <ref type="figure" target="#fig_6">7</ref>. A generic module "semantic-interface" here is used to depict the need 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. For our analysis, we map the decision and its citations into workflow. Figure <ref type="figure" target="#fig_7">8[a]</ref> shows some excerpts from the decision itself. Figure <ref type="figure" target="#fig_7">8</ref>[b] shows the workflow 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 influencing this decision have to be handled. We propose to use inductive approaches by populating the workflow with related decisions ('Biomedino LLC v. Water Techs Corp' <ref type="bibr" target="#b16">[15]</ref>, 'MIT v. Abacus Software' <ref type="bibr" target="#b17">[16]</ref>, 'Greenberg v. Ethicon Endo Surgery, Inc' <ref type="bibr" target="#b18">[17]</ref> etc) to obtain a generic workflow for 6th paragraph of § 112 as shown in Figure <ref type="figure" target="#fig_8">9</ref>. Where, the norm in workflow 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 defined legal lexicons, PUBPAT as semantic interface for reasoning the norms. A person of pertinent ordinary skill and creativity (posc) as defined by USSC affirms every reasoned result. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9">Conclusion and Future Steps</head><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.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. 10+ In-C tests to be applied on an inventive concept for patent eligibility, in accordance to US patent law</figDesc><graphic coords="4,222.64,302.47,170.08,226.77" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Cognitive system (abstract model )</figDesc><graphic coords="6,165.94,115.83,283.47,155.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 3 .Fig. 4 .</head><label>34</label><figDesc>Fig. 3. specific workflow to generic workflow</figDesc><graphic coords="7,134.77,115.83,354.33,240.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Fig. 5 .</head><label>5</label><figDesc>Fig. 5. Evaluation procedure.</figDesc><graphic coords="8,236.81,208.98,141.74,85.04" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 6 .</head><label>6</label><figDesc>Fig. 6. Proposed Framework.</figDesc><graphic coords="8,151.77,390.21,311.81,155.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head></head><label></label><figDesc>-rule info and life cycle management , modu larizat ion --&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; &lt;! --rule implemen tation --&gt; &lt;! --qualifying declarations , e . g . priorities , validity --&gt; &lt; qualification &gt; ... &lt;/ qualification &gt; &lt;! --quantifying declarations , e . g . variable bindings --&gt; &lt; quantif ication &gt; ... &lt;/ quan tificati on &gt; &lt;! --event part --&gt; &lt; on &gt; ... &lt;/ on &gt;&lt;! --condition part --&gt; &lt; if &gt; ... &lt;/ if &gt; &lt;! --( logical ) conclusion part --&gt; &lt; then &gt; ... &lt;/ then &gt; &lt;! --action part --&gt; &lt; do &gt; ... &lt;/ do &gt; &lt;! --postcondition e . g . to check effects of execution --&gt; &lt; after &gt; ... &lt;/ after &gt; &lt;! --( logical ) else conclusion --&gt; &lt; else &gt; ... &lt;/ else &gt; &lt;! --alternative action , e . g . exception handling --&gt; &lt; elsedo &gt; ... &lt;/ elsedo &gt; &lt;/ Rule &gt; Listing 1.2. General ReactionRuleML syntax 7.2 Develop/Build (Legal Reasoner)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Fig. 7 .</head><label>7</label><figDesc>Fig. 7. Reactive agent with hybrid reasoning.</figDesc><graphic coords="10,165.94,420.40,283.48,198.43" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Fig. 8 .</head><label>8</label><figDesc>Fig. 8. CAFC decision 'Lighting Ballast v Philips Electron' [14] mapped to a workflow.</figDesc><graphic coords="11,137.62,383.28,340.13,198.41" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Fig. 9 .</head><label>9</label><figDesc>Fig. 9. 6th paragraph of § 112 (35. U.S.C Patent law)..</figDesc><graphic coords="12,137.60,219.86,340.14,283.44" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">This Ph.D thesis is being supervised by Prof. Adrian Paschke, Freie Universität Berlin, Germany.</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="10">Acknowledgements</head><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></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">THE FSTP EXPERT SYSTEM</title>
		<author>
			<persName><forename type="first">S</forename><surname>Schindler</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">WO</title>
		<imprint>
			<biblScope unit="page">22612</biblScope>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
	<note>A1. to Sigram Schindler Beteiligungsgesellschaft mbh. DE/DE</note>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Ernst-Reuter-Platz</forename></persName>
		</author>
		<imprint>
			<date type="published" when="2012-02-23">23 February 2012</date>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page">10587</biblScope>
			<pubPlace>Berlin (DE</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Schindler</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ptr-Ds ;</forename><surname>De</surname></persName>
		</author>
		<title level="m">INNOVATION EXPERT SYSTEM, IES, AND ITS PTR DATA STRUCTURE</title>
				<imprint/>
	</monogr>
	<note>Sigram Schindler Beteiligungsgesellschaft. DE/</note>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title/>
		<author>
			<persName><forename type="first">Ernst-Reuter-Platz</forename></persName>
		</author>
		<imprint>
			<date type="published" when="2013-05">May 2013</date>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="page">10587</biblScope>
			<pubPlace>Berlin (DE</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">The FSTP Test: a novel approach for an invention&apos;s non-obviousness analysis</title>
		<author>
			<persName><forename type="first">S</forename><surname>Ramakrishna</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Karam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Paschke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">JURIX</title>
		<imprint>
			<biblScope unit="page" from="129" to="132" />
			<date type="published" when="2012">2012. 2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
	</analytic>
	<monogr>
		<title level="m">Brief of Amicus Curiae Sigram Schindler Beteiligungsgesellschaft mbH in support of neither party, LIGHTING BALLAST</title>
				<imprint>
			<publisher>USSC</publisher>
			<date type="published" when="2008-05-28">2008. 28 May 2013</date>
			<biblScope unit="page" from="2012" to="1014" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Technical Overview of Cognition s Semantic NLP (as Applied to Search )</title>
		<author>
			<persName><forename type="first">K</forename><surname>Dahlgren</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ReCALL</title>
		<imprint>
			<biblScope unit="page">120</biblScope>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">LegalRuleML: XML-Based Rules and Norms</title>
		<author>
			<persName><forename type="first">M</forename><surname>Palmirani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Governatori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rotolo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Tabet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Boley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Paschke</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Rule -Based Modeling and Computing on the Semantic Web</title>
				<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2011">2011</date>
			<biblScope unit="volume">7018</biblScope>
			<biblScope unit="page" from="298" to="312" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">RuleML 1.0: The Overarching Specification of Web Rules</title>
		<author>
			<persName><forename type="first">H</forename><surname>Boley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Paschke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Shafiq</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2010">2010</date>
			<publisher>RuleML</publisher>
			<biblScope unit="page" from="162" to="178" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Reaction RuleML 1.0: Standardized Semantic Reaction Rules</title>
		<author>
			<persName><forename type="first">A</forename><surname>Paschke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Boley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Zhao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Teymourian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Athan</forename><forename type="middle">T</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">RuleML 2012</title>
				<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Kozlenkov</surname></persName>
		</author>
		<ptr target="http://prova.ws/index.html" />
		<title level="m">Prova Rule Language Version 3.0 User&apos;s Guide</title>
				<imprint>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m">Title 35 of the United States Code</title>
				<imprint>
			<date type="published" when="1952">1952</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Cognitive System for Knowledge Representation of Elementary Pragmatics</title>
		<author>
			<persName><forename type="first">S</forename><surname>Ramakrishna</surname></persName>
		</author>
		<ptr target="onlineceur-ws.org/Vol-874/paper2.pdf" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the RuleML2012 Challenge, at the 6th International Symposium on Rules</title>
				<meeting>the RuleML2012 Challenge, at the 6th International Symposium on Rules</meeting>
		<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Design science in information systems research</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Hevner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">T</forename><surname>March</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ram</forename><forename type="middle">S</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">MIS Quarterly</title>
		<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">OASIS LegalRuleML</title>
		<author>
			<persName><forename type="first">T</forename><surname>Athan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Boley</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Governatori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Palmirani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Paschke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Wyner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of 14th International Conference on Artificial Intelligence and Law (ICAIL 2013)</title>
				<meeting>14th International Conference on Artificial Intelligence and Law (ICAIL 2013)</meeting>
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">Philips Electronics and Universal Lighting Technologies</title>
		<idno>-1014</idno>
		<imprint>
			<date type="published" when="2012-01-02">2012. January 2, 2013</date>
			<publisher>Inc No</publisher>
		</imprint>
	</monogr>
	<note>Fed. Cir</note>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">Llc</forename><forename type="middle">V</forename><surname>Biomedino</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Waters Techs. Corp</title>
		<imprint>
			<biblScope unit="volume">490</biblScope>
			<biblScope unit="page">949</biblScope>
		</imprint>
	</monogr>
	<note>F.. Fed. Cir. 2007</note>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">MIT v. Abacus Software</title>
		<imprint>
			<biblScope unit="volume">462</biblScope>
			<biblScope unit="page">1353</biblScope>
		</imprint>
	</monogr>
	<note>Fed. Cir. 2006</note>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title/>
		<author>
			<persName><surname>Greenberg V</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Ethicon Endo-Surgery, Inc</title>
		<imprint>
			<biblScope unit="volume">91</biblScope>
			<biblScope unit="page">1583</biblScope>
		</imprint>
	</monogr>
	<note>F.. Fed. Cir. 1996</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
