<?xml version="1.0" standalone="yes"?>
<Paper uid="P93-1015">
  <Title>Parsing Free Word Order Languages in the Paninian Framework</Title>
  <Section position="8" start_page="108" end_page="109" type="concl">
    <SectionTitle>
4 Conclusion and future work
</SectionTitle>
    <Paragraph position="0"> In summary, this paper makes several contributions: * It shows that the Paninian framework applied to modern Indian languages gives an elegant account of the relation between vibhakti and karaka roles. The mapping is elegant and compact. null  shown by dotted lines.) * The same basic account also explains active-passives and complex sentences in these languages. This suggest that the solution is not just adhoc but has a deeper underlying unity. * It shows how a constraint based parser can be built using the framework. The constraints problem reduces to bipartite graph matching problem because of the nature of constraints. Efficient solutions are known for these problems. null It is interesting to observe that such a parser (designed for free word order languages) compares well in asymptotic time complexity with the parser for context free grammars (CFGs) which are basically designed for positional languages. null A parser for Indian languages based on the Paninian theory is operational as part of a machine translation system.</Paragraph>
    <Paragraph position="1"> As part of our future work, we plan to apply this framework to other free word order languages (i.e., other than the Indian languages). This theory can also be attempted on positional languages such as English. What is needed is the concept of generalized vibhakti in which position of a word gets incoporated in vibhakti. Thus, for a pure free word order language, the generalized vibhakti contains preor post-positional markers, whereas for a pure positional language it contains position information of a word (group). Clearly, for most natural languages, generalized vibhakti would contain information pertaining to both markers and position.</Paragraph>
  </Section>
class="xml-element"></Paper>