Methodology to describe chinese code

Overview

In this projet we use a double methodolgy to transcirbe chinesse code and describe relation of different rule. We use XML as a langage for transcribe each edition of chinesse code as a hierechical tree, and we use a formal language close to predicat logici to describe relation.  Both tools allow us to have an ontological approach to the Chinese code and his transformation. In the following sections we give a list of elements does our language for both the descriptive part and party transformation.

Hierachical transcription of Chinese code.

Each edition of the code is written in an XML format. XML is a format of information based on the principle of a hierarchical element (referred to as tag), which can have attributes and forming a single shaft description.
To solve the problems of semantic different parts of the code we did not use a predefined schema (such as TEI, ...), but we voluntarily leave the option to add tags as and when the transcript. In the diagram, we have grouped the tags into four categories: tags for hierarchical structure, content tags, tags and formatting tags indexing.

Hierarchical tag

  • part
  • lu
  • li

Content tag

  • TITLE
  • CONTENT
  • JIJIE : collected commentaries (commentaires collationnés)
    ZUANZHU: compilers' notes (notes des compilateurs)
    BEIKAO: observations and references (remarques et références)

Formating tag

  • P
  • I

Indexing tag

  • propername
  • bookname

This list is completed as and when the transcript.

Ontology description of relation

To capture the transformation of the code, we consider that defined the existence of a law and its presence or absence in this particular edition of the code. To capture this relationship, we define a semantic relationship based on the presence or absence of association between two segments of text editing. In the XML transcription of code we are doing each part is identified by a unique number that serves as an identifier for establishing relationships. At present, we have identified the following relationships:

Unary relationship

  • Delete: a law that is no longer found in a future edition of the Code
  • Appears: means a law XML description

Binary Relationship

  • Becomes: is a law which is converted in the form of another law.

Relation to multiple parties

  • Amalgamates designates several laws which are converted into a single law
  • Split: refers to a law that has been cut in several laws
  • Variation: refers to a relationship of similarity between the two laws

This list is completed as and when the transcript.

 

 

 


Last update on Thursday 2 May 2013 (23:39) by  G. Foliot