General Cross Level Coding Module

Cross level coding modules

Module name: Cross-level reference coding module

Module purpose: Building reference elements to phenomena that are already marked up.

Coding level: <xr>

Data source: Existing and marked up levels of description.

Module references: Existing and marked up levels of description.

Markup declaration:

Attributes and values of `<xlr>` elements
attribute	values
`id`	`[ASCII]`
`href`	`[ASCII]`
`who`	`[ASCII]`
`cmt`	`[ASCII]`
`cert`	`0 .1 .2 .3 .4 .5 .6 .7 .8 .9 1`
`stat`	`draft, reviewed, done`
`elmname`	`[ASCII]`
`restyp`	`evs, knr`
`refvar`	`[ASCII]`
`props`	`[ASCII]`

Example:

...

<xlr

id="xlr_052"

href="wordutt.xml#id(w_4413)"

who="Q4M"

cmt="first word"

cert="1"

stat="done"

elmname="w"

restyp="evs"

refvar="w1"

props="($d 1^ $w1) and

($w1 <>1 $w2) and

($w1 # ~ $w2 #) and

($w1 # ~ $lw #)"

/>

<xlr

id="xlr_053"

href="wordutt.xml#id(w_4414)"

who="Q4M"

cmt="second word"

cert="1"

stat="done"

elmname="w"

restyp="evs"

refvar="w2"

props="($d 1^ $w2) and

($w1 <>1 $w2) and

($w1 # ~ $w2 #)"

/>

<xlr

id="xlr_054"

href="lexw.xml#id(lexw_00766)"

who="Q4M"

cmt="word type"

cert="1"

stat="done"

elmname="lexword"

restyp="knr"

refvar="lw"

props="($lw freq >= 500) and

($lw 1^ $ll)"

/>

<xlr

id="xlr_055"

href="lexf.xml#id(lexf_0487)"

who="Q4M"

cmt="word lemma"

cert="1"

stat="done"

elmname="lexlem"

restyp="knr"

refvar="ll"

props="($lw 1^ $ll) and

($ll pos ~

"noun")"

/>

...

Coding procedure:

procedural guideline
formulate the constraints/the description of the phenomenon in terms of information available. This includes knowledge on the elements available knowledge on the attributes and values of the elements available in the data or procedures for the generation of the necessary information on properties knowledge on the exact constellation of the elements and their properties the elements involved their properties and their relations to one another the combination of individual properties or relations of elements
Then, there are two options: A standard procedure and an optimized procedure. The optimized procedure aims at fast results.
standard procedure	optimized procedure
for each element type defined look for tokens of these elements check whether they have the properties necessary check whether they are in the relations to other elements specified markup those sets of elements that match all the requirements	for each of the value constraints defined begin from the type of element which are fewest for each of the elements found, check the value constraints in an order that starts with those properties which are least likely fulfilled, delete elements from the list whenever they do not match a criterion continue with the next least frequent type of elements until all value constraints of the elements have been checked for all of the constraints involving two elements check the constraints in an order that starts with those which are least likely fulfilled and keep only those elements which match all of the relation criteria for all of the logical constraints again check the constraints in an order that starts with those which are least likely fulfilled and keep only those element pairs for which all of the logical constraints are true markup those sets of elements that match the requirements This procedure aims at identifying elements that do not match as early as possible in order to reduce the number of checks.

Creation notes:

Module name: Cross-level element coding module

Module purpose: Encoding of phenomena that can be described be reference to other phenomena that are already marked up.

Coding level: <xlnt>.

Data source: <xlr> elements

Module references: Cross-level reference coding module.

Markup declaration:

Attributes and values of `<xlnt>` elements
attribute	values
`id`	`[ASCII]`
`who`	`[ASCII]`
`cmt`	`[ASCII]`
`desc`	`[ASCII]`
`phename`	`[ASCII]`
`cert`	`0 .1 .2 .3 .4 .5 .6 .7 .8 .9 1`
`stat`	`draft, reviewed, done`
`calc`	`[ASCII]`

Example:

...

<xlnt

id="xlnt_001"

href="xlr.xml#id(xlr_001)..id(xlr_004)"

who="Q4M"

cmt="why cows?"

desc="repitions of nouns caused by high token frequency"

phename="rnhf"

cert="1"

stat="done"

calc="w.freq"

/>

...

<xlnt

id="xlnt_007"

href="xlr.xml#id(xlr_052)..id(xlr_055)"

who="Q4M"

cmt="houses"

desc="repitions of nouns caused by high token frequency"

phename="rnhf"

cert="1"

stat="done"

calc="w.freq"

/>

...

<xlnt

id="xlnt_021"

href="xlr.xml#id(xlr_127)..id(xlr_130)"

who="Q4M"

cmt="wall"

desc="repitions of nouns caused by high token frequency"

phename="rnhf"

cert="1"

stat="done"

calc="w.freq"

/>

...

Coding procedure:

Identify elements that satisfy a given description of the phenomenon and mark them up as an <xlnt> element.

Creation notes:

Module name: Cross-level document coding module

Module purpose: Holds together a collection of <xlnt> elements.

Coding level: <xdct>.

Data source: <xlnt> elements..

Module references: Cross-level element coding modue.

Markup declaration:

Attributes and values of `<xldct>` elements
attribute	values
`id`	`[ASCII]`
`who`	`[ASCII]`
`cmt`	`[ASCII]`
`cert`	`0 .1 .2 .3 .4 .5 .6 .7 .8 .9 1`
`stat`	`draft, reviewed, done`
`srtelm`	`[ASCII]`
`srtatt`	`[ASCII]`
`srtcrt`	`str, num`
`srtord`	`std, rev`
`crea`	`[ASCII]`
`refnstab`	`yes, no`
`reftstab`	`yes, no`

Example:

...

<xldct

id="xldct_001"

href="xlnt.xml#id(xlnt_001)..id(xlr_033)"

who="Q4M"

cmt="are there semantic issues involved?"

cert="1"

stat="done"

srtelm="lw"

srtatt="freq"

srtcrt="num"

srtord="rev"

crea="($w1 w)($w2 w)($lw lexw)($ll lexw);

($w1 <>1 $w2) and ($w1 # ~ $w2 #) and

($w1 # ~ $lw #) and ($lw freq >= 500) and

($lw 1^ $ll) and ($ll pos ~ "noun")"

refnstab="yes"

reftstab="yes"

/>

...

Coding procedure:

Collect valid

<xlnt>

elements and put them together into one <xldct> element.

Creation notes: