<?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">Advisory System for the Agricultural Tax Law</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Tomasz</forename><surname>Zurek</surname></persName>
							<email>zurek@kft.umcs.lublin.pl</email>
							<affiliation key="aff0">
								<orgName type="department">Institute of Computer Science</orgName>
								<orgName type="institution">Maria Curie-Sklodowska University</orgName>
								<address>
									<addrLine>Plac Marii Curie-Sklodowskiej 5</addrLine>
									<postCode>20-031</postCode>
									<settlement>Lublin</settlement>
									<country key="PL">Poland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Emil</forename><surname>Kruk</surname></persName>
							<email>emil.kruk@wp.pl</email>
							<affiliation key="aff1">
								<orgName type="department">Institute of Administration and Public Law</orgName>
								<orgName type="institution">Maria Curie-Sklodowska University</orgName>
								<address>
									<addrLine>Plac Marii Curie-Sklodowskiej 5</addrLine>
									<postCode>20-031</postCode>
									<settlement>Lublin</settlement>
									<country key="PL">Poland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Advisory System for the Agricultural Tax Law</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">18BFF94129F41F9DED12A3F99DCA84F8</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T20:20+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>Legal expert system</term>
					<term>agricultural tax law</term>
					<term>ontology building</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The authors of this study attempted to develop an advisory tool functioning in the scope of the Agricultural Tax Act. The focus of the authors in this study was on presenting the outcome of the efforts connected with building the ontology which would allow for representing individual cases. This study will also outline the structure and concept of the system in question.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>The law regulating the life of man in society has become so complex that for the average person it is extremely difficult to understand its letter even when considered solely at the basic level of legal social functioning. Nowadays, the old Roman rule stipulating that the lack of legal knowledge cannot be the excuse to anyone sounds almost like a mockery. Therefore, an IT tool advising on certain legal acts could be very useful both to the average 'users' of law, as well as to the state administrative bodies</p><p>The authors of this study attempted to develop an advisory tool functioning in the scope of the Agricultural Tax Act <ref type="bibr" target="#b11">[12]</ref>. The authors seek to create a tool which would provide the agricultural tax payers and officers with comprehensive advice in the scope of their rights and obligations. The choice of this Act was inspired by its specificity. The authors' primary emphasis was on the legal act being as deterministic as possible, as it would allow for considerably restricting the interpretation leeway which in the case of other legal acts is very wide. Another reason behind this choice stemmed from the fact that fiscal law calls for linguistic interpretation and utilisation of other ways of interpretation of law is not recommended (for example a contrario) or strictly forbidden (for example per analogiam). Legal acts of this kind significantly facilitate the development of advisory systems, reducing, though not fully eliminating, the impact of interpretation difficulties.</p><p>The Agricultural Tax Act governs such issues as tax calculation, tax rates, classification of taxpayers and farm land under various taxation classes, tax breaks and reliefs, payment conditions, land class changes, and the like. As the system is entirely based on the Polish statutory law, the Agricultural Tax Act, along with other statutory provisions of a more detailed nature serves as the only source of knowledge. So far, there has been no need to refer to any other legal acts although general legal expertise has often proven imperative to properly construe individual provisions.</p><p>The focus of the authors in this study was on presenting the outcome of the efforts connected with building the ontology which would allow for representing individual cases, and dealing with cases not expressly regulated by law. This study will also outline the structure and concept of the system in question.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Legal Act</head><p>Agricultural Tax Act <ref type="bibr" target="#b11">[12]</ref> regulates the issues of agricultural tax calculation, maximum tax rates, classification of taxpayers and farm land under various taxation classes, tax breaks and reliefs, tax payment conditions, land class changes, and the like. As the system is entirely based on the Polish statutory law, the Agricultural Tax Act, along with other statutory provisions of a more detailed nature, serves as the only source of knowledge. So far, there has been no need to refer to any other legal acts although general legal expertise has often proven imperative to properly construe individual provisions.</p><p>Agriculture in Poland is not only one of these sectors of economy where the number of employees is still relatively high, but it is also very fragmented (with plenty of relatively small agricultural farms). Therefore, the number of agricultural tax payers is huge. As intended by the authors, the advisory tool, providing legal information on the rights and obligations of the agricultural tax payers, will come in handy not only for the taxpayers but also for the officers dealing with agricultural matters. It can facilitate and speed up the law interpreting process, cutting down the number of frauds.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">System structure</head><p>Rules are the major carrier of legal expertise in the system developed by the authors. However, unlike in the classic expert systems, they are "incorporated" into certain elements of ontology, which allows for a case to be described. The ontology thus forms an interpretation "background". Particular instances of the ontology elements, i.e. input and output elements (conditions and conclusions) of the rules, make it possible to describe specific cases, and to introduce certain semantic aspect into the static knowledge (describing the reality). Apart from the classic legal rules, regulating changes to the legal status (e.g. deontic features), the system also contains more general rules which govern cases not expressly defined in the letter of law.</p><p>The JAVA language was selected as the system implementation tool, considering the ease it offers in representing and shaping such structures.</p><p>In turn, the PROLOG language was applied for pre-modelling the basic legal relations, especially those connected with the cases not expressly regulated by law. This choice was inspired by the huge possibilities in the scope of representing various logical relations, including the pretty complex ones, offered by PROLOG. Finally, the full version of the system also makes use of the JBOSS RULES engine, highly flexible and compatible with JAVA. As the JBOSS RULES knowledge representation is rule-based, the model developed in PROLOG was extremely useful in creating the system. The JBOSS RULES engine is based on the RETE algorithm, and the authors believe that it is particularly predisposed to operate together with the JAVAimplemented ontology</p><p>The real-life situations were expressed as instances of individual classes. Part of the procedural knowledge (e.g. the mechanisms used for calculating conversion hectares) was defined in the class-specific methods.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Ontology</head><p>Any problem encountered by lawyers is highly specific, and this specificity must be properly accounted for to become interpretable in the context of the existing legal regulations. Several authors have made attempts to create more or less complex ontologies to represent legal acts <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2,</ref><ref type="bibr" target="#b8">9,</ref><ref type="bibr" target="#b12">13]</ref>. In consequence, the authors suggest the use of ontology for expressing the legal aspect of cases analysed. Further details concerning ontology can be found in <ref type="bibr" target="#b15">[16]</ref>. It was implemented within the system as a structure comprising interfaces and classes, where an instant case is expressed through individual class instances. For example, if Mr. Bilbo Baggins is the owner of land in village Hobbiton, the description comprises the following class instances:</p><p>• Location ("The Hill") • Land ("Bag End"), class have attribute: Location. Value of the attribute: "The Hill" • Village ("Hobbiton") class has collection of attributes: Location. Value of the one of them: "The Hill" • Natural Person ("Mr. Bilbo Baggins") • Ownership ("Ownership of Mr. Baggins"). Attribute: Owner, value: "Mr. Bilbo</p><p>Baggins", attribute property: "Bag End"</p><p>Naturally, each class consists of several attributes, some of which allow for making connections between individual instances. For example, "Location" is one of the attributes of the Land class instance, and the Location class instance serves as its value.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Deontic logic</head><p>When analyzing legal interpretation, it is hardly possible to neglect deontic logic, defined as the field of logic which is concerned with the formal relation between the following deontic concepts-obligation, prohibition, and permission. Lawyers frequently apply these basic laws of deontic logic more or less intuitively. Some examples of implementations of deontic logic in legal expert systems were described in <ref type="bibr" target="#b13">[14]</ref>. These laws facilitate interpretation of the least complex cases not expressly regulated by law.</p><p>Deontic logic revolves around three principal concepts, namely the concept of permit, prohibited and obligatory (some authors advocate one additional conceptindifference, but this study will be confined to the three principal concepts mentioned) <ref type="bibr" target="#b14">[15]</ref>. Implementation of one of the basic deontic rules, stating that any actions obligatory are also permitted, proved indispensable in this study. This was modelled using the PROLOG language: permitted(Action, Performer) :-obligatory(Action, Performer), action(Action), person(Performer).</p><p>Other principles stating, inter alia, that any actions prohibited are neither permitted nor obligatory, and -on the contrary -that any actions permitted and obligatory are not prohibited, should result from the structure of the knowledge base of the system.</p><p>There is one more issue to be focused on as regards deontic logic. Namely, the proper choice of ontology makes it considerably easier and very often possible at all, to represent the reality in which a given act functions. However, at the same time, the maker of the system has to face the necessity to somehow adjust the deontic logic to the actual ontology. Generally, ontologies take the form of a hierarchical structure of beings, and the place of such concepts as obligation, prohibition, and permission in this structure is of key importance.</p><p>Assuming that action B constitutes a sub-group of action A, we may infer that: • permission to do A also means permission to do B, unless separate provisions stipulate otherwise, i.e. that B is forbidden • obligation to do A does not mean obligation to do B; for instance, we are obliged to pay taxes but we may not necessarily be obliged to pay the agricultural tax (provided that we do not conduct agricultural activity but we work, for instance, at university). • a prohibition on A means a prohibition on B, unless separate provisions stipulate otherwise, i.e. that B is permitted.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Rules</head><p>Rules are the major carrier of conditional legal norms in the system. In authors' opinion these rules should mirror legal principles, avoiding free interpretation of the act, as much as it is possible. Interpretation principles and reasoning should be separated from general knowledge base. Example of one of the rules is presented below:</p><p>rule "tax payer -owner" The above rule states whether the owner of the land is an agricultural tax payer. The first three provisions in the conditional part of the rule state that there should be a person who owns an instance of the class Land. The next three conditions exclude situations which defeat the rule. There are no other possibilities of defeasing this rule and theory of law forbids creating the new defeasing conditions out of any ways of interpretation (especially out of analogy).</p><p>Conclusion of the above rule changes the state of value of the attribute TaxPayer from false into true.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Interpretation of cases not expressly regulated</head><p>The legal theory and practice has given rise to a wide array of methods to deal with cases not expressly regulated by law, some of which were used by the authors. Implementation of one of the basic deontic rules, stating that any actions obligatory are also permitted, received top priority. In general, deontic logic is connected with the rules of instrumental obligation, and prohibition, and permission. Of these three, the rule of instrumental permission was the only one to be considered relatively unquestionable, and thus was implemented. The authors further considered the possibility to apply the a contrario interpretation method. The problem of interpretation of cases not expressly regulated by law is discussed wider in <ref type="bibr" target="#b16">[17]</ref>. The subject of deontic logic is widely discussed i.a. in <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b9">10,</ref><ref type="bibr" target="#b13">14]</ref> instrumental reasoning and a contrario is mentioned in <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b5">6,</ref><ref type="bibr" target="#b7">8]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8">Conclusions</head><p>Expert systems were among the first computer tools applied to support legal expertise. Given their specificity, they were mainly used in modelling the statute law rather than the common law. Following the initial enthusiasm, they became the object of vivid criticism. Critical judgements concerning the viability of rule-based systems as a tool supporting legal expertise usually focused on the difficulties related to representing unclear and exceptionally complex definitions or to converting some of the most complicated relations into rules. This criticism is by no means groundless. However, it should be emphasised that the level of detail differs among specific legal acts, thereby requiring different ways of interpretation. In certain cases, the theory of law requires very strict precision and grammatical interpretation.</p><p>The authors of this study have attempted to develop an advisory tool functioning in the scope of the Agricultural Tax Act. The principal goal of this is to provide automatic legal advice. Implementation of certain mechanisms which allow for advising on cases not expressly regulated in law is what makes this project exceptional. The system comprises three levels of representation of legal knowledge: the level of ontology, level of procedural knowledge and the level of rules. The ontology developed by the authors to allow for representing specific cases serves as the basic representation level, making it possible to describe the strictly legal concepts, as well as the commonsense-based concepts.</p><p>Elements of ontology serve as the conditions and conclusions of the rules which form the dynamic part of legal knowledge stored in the system. Apart from the rules which directly reflect the provisions of the legal act, the system also comprises a range of rules of a more general nature. The latter mirror the principles of legal interpretation, including the basic rules of deontic logic, and the rule of instrumental permission.</p><p>The elements implemented so far include the ontology and part of the deontic legal principles. The system is well capable of providing correct answers to the cases which clearly fall within the scope of the knowledge already implemented, as well as to certain questions not expressly defined in the provisions.</p><p>Future works will focus on implementing further provisions and on developing the module supporting interpretation of cases not expressly regulated in law. The authors envision introducing a distinction between various rules, based i.e. on the results of studies <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b10">11]</ref>, and are also going to focus on the more formal representation of legal knowledge. This distinction would aim to expand and to crystallize the possibilities related to interpreting some of the cases not expressly regulated by law. The authors are also going to focus on representation of consistency constraints in a knowledge base.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>(who == person &amp;&amp; what == land &amp;&amp; taxPayer == false); not possessor : Possessor(what == owner.what); not rent : Rent(what == owner.what); not user : User( what == owner.what ); then ownership.setTaxPayer(true); update(owner); end</figDesc></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Law and the Semantic Web: Legal Ontologies, Methodologies, Legal Information Retrieval, and Applications</title>
		<editor>Benjamins V. R., Casanovas P., Breuker J., Gangemi A.</editor>
		<imprint>
			<date type="published" when="2005">2005</date>
			<publisher>Springer</publisher>
			<pubPlace>Berlin/Heidelberg</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Legal Ontologies in Knowledge Engineering and Information Management</title>
		<author>
			<persName><forename type="first">J</forename><surname>Breuker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Valente</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Winkels</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence and Law</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="page" from="241" to="277" />
			<date type="published" when="2004">2004</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Some Problems with PROLOG as a Knowledge Representation Language for Legal Expert Systems</title>
		<author>
			<persName><forename type="first">T</forename><surname>Gordon</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Yearbook of Law, Computers &amp; Technology</title>
				<editor>
			<persName><forename type="first">C</forename><surname>Arnold</surname></persName>
		</editor>
		<imprint>
			<biblScope unit="page" from="52" to="67" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Greinke</surname></persName>
		</author>
		<ptr target="http://www.murdoch.edu.au/elaw/issues/v1n4/greinke14.txt" />
		<title level="m">Legal Expert System: A humanistic critique of Mechanical Legal Interface</title>
				<imprint>
			<date type="published" when="1994">1994</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Reasoning with Rules: An Essay on Legal Reasoning and Its Underlying Logic</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">C</forename><surname>Hage</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1997">1997</date>
			<publisher>Springer</publisher>
			<pubPlace>Berlin-Heidelberg</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<title level="m" type="main">Issues of theory of application of law in Polish Zakamycze</title>
		<author>
			<persName><forename type="first">L</forename><surname>Leszczynski</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">A Pragmatic Legal Expert System</title>
		<author>
			<persName><forename type="first">J</forename><surname>Popple</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1996">1996</date>
			<pubPlace>Dartmouth, Aldershot</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">A Typology of Moves Involved in Case Comparison</title>
		<author>
			<persName><forename type="first">B</forename><surname>Roth</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of 8 th International Conference of Artificial Intelligence and Law. St Luis</title>
				<meeting>8 th International Conference of Artificial Intelligence and Law. St Luis<address><addrLine>New York</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2001">2001</date>
			<biblScope unit="page" from="129" to="138" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">An OWL Ontology of Fundamental Legal Concepts in: Legal knowledge and information systems</title>
		<author>
			<persName><forename type="first">G</forename><surname>Sartor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Rubino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rotolo</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">JURIX 2006, the Nineteenth Annual Conference</title>
				<meeting><address><addrLine>Amsterdam</addrLine></address></meeting>
		<imprint>
			<publisher>IOS Press</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page" from="101" to="111" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">A Treatise of Legal Philosophy and General Jurisprudence</title>
		<author>
			<persName><forename type="first">G</forename><surname>Sartor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">A</forename><surname>Shiner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Rottleuthner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Peczenik</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Pattaro</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2005">2005</date>
			<publisher>Springer</publisher>
			<pubPlace>Berlin-Heidelberg</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">G</forename><surname>Sartor</surname></persName>
		</author>
		<ptr target="http://cadmus.iue.it/dspace/bitstream/1814/4351/1/LAW%202006.11.pdf" />
		<title level="m">Fundamental Legal Concepts A Formal and Teleological Characterisation</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m">The Journal of Laws of the Republic</title>
				<meeting><address><addrLine>Poland</addrLine></address></meeting>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Ontologies in the Design of Legal Knowledge Systems</title>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">R S</forename><surname>Visser</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">J M</forename><surname>Bench-Capon</surname></persName>
		</author>
		<ptr target="http://citeseer.ist.psu.edu/64358.html" />
	</analytic>
	<monogr>
		<title level="m">Towards a Library of Legal Domain Ontologies</title>
				<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Applications of Deontic Logic in Computer Science a Concise Overview se overview in Deontic Logic in Computer Science: Normative System Specification</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">J</forename><surname>Wieringa</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">J</forename><surname>Meyer</surname></persName>
		</author>
		<author>
			<persName><surname>Ch</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1993">1993</date>
			<publisher>John Wiley and Sons</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">Logika praktyczna (Practical Logic)</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Ziembinski</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1990">1990</date>
			<publisher>PWN</publisher>
			<pubPlace>Warsaw</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Knowledge Base Ontology in Legal Expert System</title>
		<author>
			<persName><forename type="first">T</forename><surname>Zurek</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Polish Journal of Environmental Studies</title>
		<imprint>
			<biblScope unit="volume">17</biblScope>
			<biblScope unit="issue">3B</biblScope>
			<biblScope unit="page" from="575" to="580" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Supporting of Legal Reasoning for Cases which are not Strictly Regulated by Law</title>
		<author>
			<persName><forename type="first">T</forename><surname>Zurek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Kruk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of 12 th International Conference of Artificial Intelligence and Law</title>
				<meeting>12 th International Conference of Artificial Intelligence and Law<address><addrLine>Barcelona; New York</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2009">2009</date>
			<biblScope unit="page" from="220" to="221" />
		</imprint>
	</monogr>
</biblStruct>

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