Comments (9)
-
In the case of the blue circle, I don't see any problem, no need to correct the stemma:
O -> x
x -> alpha -
Depends on what the question marks mean. In many cases it could just be encoded in the label attribute:
Z [label="Z(?)"]
We could expand the available attributes to identify the meaning of those signs.
- What is the situation in the second example? Is that not just a hypothetical node descendant from beta?
from database.
So:
- Today we would skip
x
. I think @Jean-Baptiste-Camps agrees. - Mmmm… Why not!
- It should be the presence of an antigraph (« remoto legame di parentela » between β2 et β3).
- Similar problem with this stemma, especially the circles (Catullus, thanks to @Benedetta-Salvati for the image and the remark supra concerning Dante):
from database.
- For the blue circle, in the data I've created until now, I've simplified irregularities like this one by deleting spurious steps (so
O -> alpha
,with O as root), but I agree that in this project, we should perhaps stick to imitating the source (easy to simplify with a script afterwards).
Today we would skip x. I think @Jean-Baptiste-Camps agrees.
Today, we would skip x, indeed, BUT, skip omega and keep O… (I hope), because stating that all the tradition goes to an archetype is very important information (and very important for my research too !).
Depends on what the question marks mean. In many cases it could just be encoded in the label attribute:
Z [label="Z(?)"]
We could expand the available attributes to identify the meaning of those signs.
Good idea, something like color, etc. But I would aim for the simplest format possible, so, it boils down to: is uncertainty important enough for a special encoding ?
Similar problem with this stemma, especially the circles
I think circles are only there because they are printed editions, not mss ? In this case, the info can go in the WitList ?
from database.
OK we are mixing two different problems here. Technical details and what we do. I opened a new issue regarding guidelines.
from database.
Je me permets de prendre la parole sur la question des cercles. Il ne s’agit pas d’éditions imprimées: les éd. sont précédées par « ed. », le nom de l’imprimeur et la date de parution. C’est le cas de l’éd. aldine de 1502. Mais, je pourrais me tromper...
from database.
@Benedetta-Salvati , merci, j'ai lu trop vite !
Une idée sur ce dont il s'agit ? Est-ce évoqué dans le texte ?
from database.
L'auteur du teste n'explique pas le stemma en détail. Il se trompe lorsqu'il l'attribue à Reeve, l'éd. de la dernière édition (moderne) de Catulle (1997). Nous nous trouvons, au contraire, devant la généalogie de Thomson, l'auteur de l'éd. parue en 1978. Il faudra donc regarder l'intro de cette éd. pour comprendre le "mystère" des cercles. Personnellement, je n'arrive pas à m'expliquer pourquoi ils ont été insérés. Tout ce que je peux dire c'est que: Laur. 33-13 (Firenze, Biblioteca Laurenziana, Plut. 33.31) est l'un des deux ms. de base utilisés par Lachmann pour son éd. de Catulle (ensemble à D); Sen. (Siena, Biblioteca Comunale, H.V. 41), issu de R, est l’ancêtre de m u (r) w, manuscrits constituant une trad. partiellement indépendante ("Sen. w m r u form a closed group within the surviving manuscripts of Catullus: they regularly agree in error agaist all other manuscripts", D. Kiss). Désolée... @Jean-Baptiste-Camps
from database.
@Benedetta-Salvati Merci !
Je proposerais donc, pour le moment, de ne pas encoder cette subtilité en attendant d'en savoir plus.
En revanche, ça vaudrait peut-être le coup d'inclure dans le modèle un moyen de représenter les incertitudes sur les liens (à discuter, j'ouvre ce ticket, #25 ).
from database.
Closing this, as the remaining difficulty was moved to another ticket.
from database.
Related Issues (20)
- Old Occitan HOT 1
- Validate XML files HOT 1
- German
- Add schematron rules to check metadata values (`keywords` and `terms`)
- Improve Workflow for Tests and Transformation HOT 10
- contamination not included if "" missing HOT 2
- Post merge workflow committing ? HOT 12
- Old French Epics
- Unmarked contamination in not straightforward traditions HOT 1
- Non-oriented stemma HOT 1
- processing metadata as yaml and allowing absence of fields ?
- Different types of non-standard transmission HOT 2
- Field publicationStemmaNum not exported in tei ?
- Manuscripts in gv and not in picture (based on the text?) -- Rennewart
- Check how comments from gv are handled
- Pindar
- Complete / partial stemma HOT 12
- Workflow error ? HOT 9
- typo
- Epic Poetry Stemmata Collections
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from database.