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
23e78dae
Commit
23e78dae
authored
3 years ago
by
Alice Brenon
Browse files
Options
Downloads
Patches
Plain Diff
Finish the part about other schemes
parent
5baae11e
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
+47
-6
47 additions, 6 deletions
ICHLL_Brenon.md
with
47 additions
and
6 deletions
ICHLL_Brenon.md
+
47
−
6
View file @
23e78dae
...
...
@@ -118,9 +118,9 @@ Back to the "Encyclopédie" article we read that a dictionary remaining strictly
at the language level, a vocabulary, can be seen as the empty frame required for
an encyclopedic dictionary that will fill it with additional depth. Given how
d'Alembert insists on the importance of brevity for a clear definition in the
"Dictionnaire de Langues" entry, it is clear that
for
the
*encyclopédistes*
,
encyclopedia
aren't
superior to dictionaries but really
depart from them in
terms of purpose.
"Dictionnaire de Langues" entry, it is clear that the
*encyclopédistes*
did not
consider
encyclopedia
s
superior to dictionaries but really
as a new subgenre
departing from them in
terms of purpose.
## La Grande Encyclopédie
...
...
@@ -787,14 +787,55 @@ and a half.
## Comparison to other approaches
Before deciding to give up on the
*dictionaries*
module and attempting to devise
or own encoding scheme, several scenarios have been considered and compared to
find the most compatible with our .
The above section about the structure of the
*dictionaries*
module and the
features found in encyclopedias follows quite closely our own journey trying to
encode first manually then by automatic means the articles of our corpus. This
back and forth between trying to find patterns in the graph which reflects the patterns
found in the text and questioning the relevance of the results explains the
choice we ended up making but also the alternatives we have considered.
### Bend the semantics
Several times, the issue of the semantics of some elements which posess the
properties we need came up. This is the case for instance of the
`<sense/>`
and
`<node/>`
elements. It is very tempting to bend their documented semantics or to
consider that their inclusion properties is part of what defines them, and hence
justifies their ways in creative ways not directly recommended by the TEI
specifications.
This is the approach followed by project Basnum[^Basnum] which studies and
provides a XML-TEI encoding of the
*Dictionnaire Universel*
by Furetière, or
rather its second edition edited by Basnage, an encyclopedic dictionary from the
very early 18
\t
extsuperscript{th} century. In the articles encoded for this
project,
`<note/>`
elements are nested and used to structure the encyclopedic
developments that occur in the articles.
We have chosen not to follow the same path in the name of the FAIR principles to
avoid the emergence of a custom usage differing from the documented one.
[
^Basnum
]:
[https://anr.fr/Projet-ANR-18-CE38-0003](https://anr.fr/Projet-ANR-18-CE38-0003)
### Custom schema
The other major reason behind our choice was the inclusion rules which exist
between TEI elements and pushed us to look for different combinations. Another
valid approach would have consisted in changing the structure of the inclusion
graph itself, that is to say modify the rules. If
`<entry/>`
is the perfect
element to encode article themselves, all that is really missing is the ability
to accomodate nested structures with the
`<div/>`
element. Generating customized TEI
schemas is made really easy with tools like ROMA[^ROMA], which we used to
preview our change and suggest it to the TEI community.
[
^ROMA
]:
[https://roma.tei-c.org/](https://roma.tei-c.org/)
Despite it not getting a wide adhesion, some suggested it could be used locally
within the scope of project DISCO-LGE. However we chose not to do so, partially
for the same reasons of interoperability as the previous scenario, but also for
reasons of sturdiness in front of future evolutions. Making sure the alternative
schema would remain useful entails to maintain it regenerating it should the
schema format evolve, with the possibility that the tools to edit it changes or
stop being maintained.
# Conclusion
Despite long discussions and interesting proposals each with strong arguments both in
...
...
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