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
Compare revisions
92b761c2df18d8f1c27a0d44c68b2e807790e578 to 89df888f2c8560dd34b51ad89cfa2ce1c3d3d685
Compare revisions
Changes are shown as if the
source
revision was being merged into the
target
revision.
Learn more about comparing revisions.
Source
abrenon/ichll11-article
Select target project
No results found
89df888f2c8560dd34b51ad89cfa2ce1c3d3d685
Select Git revision
Branches
feedback1
main
preprint
Swap
Target
abrenon/ichll11-article
Select target project
abrenon/ichll11-article
1 result
92b761c2df18d8f1c27a0d44c68b2e807790e578
Select Git revision
Branches
feedback1
main
preprint
Show changes
Only incoming changes from source
Include changes to target since source was created
Compare
Commits on Source (2)
Minor rephrasing
· 5f603452
Alice Brenon
authored
4 months ago
5f603452
Fix typos
· 89df888f
Alice Brenon
authored
4 months ago
89df888f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ICHLL_Brenon.md
+4
-4
4 additions, 4 deletions
ICHLL_Brenon.md
with
4 additions
and
4 deletions
ICHLL_Brenon.md
View file @
89df888f
...
...
@@ -93,7 +93,7 @@ and digitally native dictionaries [@bowers_bridging_2018]. In addition, a
specific guidelines tailored at encoding dictionaries named TEI-Lex0 has also
been published [@banski_tei_lex0_2017].
The TEI effort is described
as "first steps"
by @ide_background_1998 to reach a
The TEI effort is described by @ide_background_1998
as "first steps"
to reach a
standard to encode corpora and lay a common basis for corpora comparison and
reuse. They point some light inconsistencies in the design, remark that there is
generally more than one way to encode a given text in XML-TEI and identify nine
...
...
@@ -241,7 +241,7 @@ subgenre departing from them in terms of purpose.
# The *dictionaries* TEI module {#sec:dictionaries-module}
One of the main motivation behind project DISCO-LGE was to produce data useful
One of the main motivation
s
behind project DISCO-LGE was to produce data useful
to future scientific projects, which in particular requires it to be
*interoperable*
and
*reusable*
. These are the two last key aspects of the FAIR
(
[
https://www.go-fair.org/fair-principles/
](
https://www.go-fair.org/fair-principles/
)
)
...
...
@@ -478,7 +478,7 @@ apparatus — is less clear, is to wrap together several versions of the same
excerpts, for instance when there are several possible readings of an unclear
group of words in a manuscript, or when the encoder is trying to compile a
single version of a piece of work from several sources which disagree over some
passage. In both case, it appears obvious that it is not something that is
passage. In both case
s
, it appears obvious that it is not something that is
expected to occur naturally in the course of an article in general.
Thus, despite a rather dense internal connectivity, the
*dictionaries*
module
...
...
@@ -673,7 +673,7 @@ not mere remarks in the margins or at the foot of pages.
The remarks made in section @sec:dictionaries-module explain why the
*dictionary*
module is unable to represent encyclopedias, where the notion of
"meaning" is less central tha
t
in dictionaries and where discourse with nested
"meaning" is less central tha
n
in dictionaries and where discourse with nested
structures of arbitrary depth can occur. Even composite encodings using elements
outside of the
*dictionaries*
module under an
`<entry/>`
element do not meet the
requirements of the project. Since the
*core*
module obviously accomodates these
...
...
This diff is collapsed.
Click to expand it.