Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
ICHLL11 Article
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Alice Brenon
ICHLL11 Article
Commits
0ea1d173
Commit
0ea1d173
authored
3 years ago
by
Alice Brenon
Browse files
Options
Downloads
Patches
Plain Diff
Developping description of XML-TEI some more
parent
5853ebcf
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ICHLL_Brenon.md
+39
-13
39 additions, 13 deletions
ICHLL_Brenon.md
with
39 additions
and
13 deletions
ICHLL_Brenon.md
+
39
−
13
View file @
0ea1d173
...
...
@@ -212,24 +212,50 @@ near the "surface" of article entries.
The central element of the
*dictionaries*
module is the
`<entry/>`
element meant
to encode one single entry in a dictionary, that is to say a head word
associated to its definition. It is the natural
entry po
in
t
from the
`<body/>`
associated to its definition. It is the natural
way
in from the
`<body/>`
element to the dictionary module: indeed, although
`<body/>`
may also contain
`<entryFree/>`
or
`<superEntry/>`
elements, the former is a relaxed version of
`<entry/>`
while the latter is a device to group several related entries
together. Both can contain an
`<entry/`
directly while no obvious inclusion
exists the other way around. Most of the inclusion paths of "reasonable" depth
(which we define to strictly inferior to 5, that is twice the average shortest
depth between any two nodes) seem to either include
`<figure/>`
exists the other way around. Most (> 96.2%) of the inclusion paths of
"reasonable" depth (which we define as strictly inferior to 5, that is twice the
average shortest depth between any two nodes) seem to either include
`<figure/>`
or
`<castList/>`
, two elements unrelated to encyclopedia articles in the general
case. Hence, not only the semantics conveyed by the documentation but also the
structure of the elements graph evidence
`<entry/>`
as the natural top-most
element for an article.
### Information about the word itself
Once a block for an article is created, it may contain elements useful to
represent features such as
-
its written and spoken forms:
`<form/>`
-
a group of grammatical information:
`<gramGrp/>`
, that may itself contain as
we've seen above
`<case/>`
,
`<gen/>`
,
`<number/>`
or
`<pers/>`
to describe the
form itself for instance, but also information about the categories it belongs
to like
`<iType/>`
for its inflexion class or
`<pos/>`
for its part-of-speech
-
its etymology
-
its variants if there is a different spelling in a variety of the language or
if it has changed through time
All these are examples and by no means an exhaustive list; the complete set
provides the encoder with a toolbox to describe all the information related to
the form the entry is found at and seem general enough to accomodate the
structure of any book indexing entries by words.
### Cross-references
A common feature shared by dictionaries and encyclopedias is the ability to
connect entries together by using a word or short phrase as the link, referring
the reader to the related concept. This is known as cross-references and can
appear either when the definition of a term is adjacent to another one or to
catch alternative spellings where some readers might expect the word to appear
and redirect them to the form chosen as the reference. In XML-TEI, this is done
with the
`<xr/>`
element.
### Content
Once a block for an article is created
It contain elements useful to represent the features occurring at the begining
of an article such as its written and spoken forms (
`<form/>`
), a group of
grammatical information (
`<gramGrp/>`
), that may itself contain as we've seen
above
`<case/>`
,
`<gen/>`
,
`<number/>`
or
`<pos/>`
to describe the form itself for instance, or
`
All these are quite exhaustive and seem general enough to accomodate any book
structure indexing entries by words. A more
# A new standard ?
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment