Coder Social home page Coder Social logo

irish-gen's People

Contributors

cyocum avatar eystein-thanisch avatar zacharywhitley avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

irish-gen's Issues

fer_manach.ttl: ambiguous linkage between pedigrees

There are two possibile ways of interpreting this second pedigree. "Gilla Crist mac Meic Uidir" could be Gilla Crist, son of Éicnig, son of Dalaig, son of Uidir" from the previous pedigree. If so, perhaps it is there as an alternative ancestry for Uidir, as they differ thereafter? Or is Dub Darach the brother of Gilla Crist from the first pedigree i.e. another son of <#Éicnig>? I am assuming the latter.

rig_ceniuil_conaill.ttl: ambiguous linkage between pedigrees

I can see no way of determining which Flathbertach from the previous pedigree this is without consulting other sources. It is presumably not the first, otherwise there would surely just be one pedigree, but there are two others. Can we it to be the second, because of the lack of further specification?

Fosterage?

In n_echach.ttl, a fosterage relationship is described (Da mc Echach .i. Crimthand et Lugaid Cichech o tát .h. Lugdech. Is eside ro alt da mc Crimthaind .i. Aed & Loegaire...). Do we want to represent that in the database? I notice that rel:mentorOf already exists. Could we appropriate it?

rig_ulad.ttl and ríg_ulad.ttl

We have two files with almost identical names. They contain two different versions of the same pedigree, which is going to be super interesting once it's in the system, but should we change the filenames to distinguish them? I'm not sure if doing that from my repo would be treated as just another change or whether it would cause a conflict.

Conflicts Between Stated and Actual Numbers of Offspring

As I am sure you have noticed, the genealogies sometimes give the number of sons a person has as well as listing their names.

e.g. (Sil_Birn.ttl) "Cóic mc Fhindchada mc Dega .i. Oengus. Mc Cuilind. Dúnlang a quo .h. Dega Draignech. Eichen. Barrfhind."

Occasionally, this ennumeration is contradicted, either by the number of sons then listed or by the addition of extra sons elsewhere in the genealogies. In relation to the example just given, we later encounter "Scellán & Cummin dá mc Dimma m Fhindchada mc Dega."

This kind of discrepency has the potential to reveal important faultlines in the text, which is a key objective of this project. However, at present, we do not seem to have an efficient way of recording that the text put a number on someone's offspring, only that the offspring are listed. Is there any way this could be included?

Unknown Nominatives

I though we could pool both problems and information with nominative forms of names by posting the problematic items here.

irishRel:numChild ambiguity

Up to now, the irishRel:numChild predicate has been used to record the numbers of sons, presumably on the assumption that these are the only figures that our sources will provide. However, in Rawl_B502/_94.ttl, the number of Úgáine Mór's sons and daughters is given (22 sons, 30 daughters). Using the irishRel:numChild predicate would imply he had 52 sons but it would be a shame to omit the data about the daughters by only recording 22 as the datum.

Two options:

  1. Record 52 children and put the text in an rdfs:comment.
  2. Create irishRel:numSons and irishRel:numDaughters predicates.

I am easy as to which we choose :-)

clanna_ébir_i_l-leith_chuind.ttl not finished

Major booby on my part, sorry. clanna_ébir_i_l-leith_chuind.ttl is barely half finished. I have no idea why I stopped where I did. I think it was one of the first I worked on. I'll get it complete and updated to Phase 2 standard asap.

Single Versus Multiple Individuals

Sometimes, one version of the genealogies will interpret a name as denoting one person and another version will take it as multiple people. For example, in their respective sections on Síl Birn, Rawl.B.502 has two brothers called "Daig" and "Linga", whereas LL has one person called "Daig Linguae".

In such situations, is it acceptable to use owl:sameAs to link the multiple people in one version to the single person in the other version? On the one hand, this seems the best intepretation of the latter but, on the other, it could imply that the multiple people in the former are the same as each other, when the point is that they are different.

Imchada maybe sameas another in erand.ttl

In erand.ttl from lines 67--71 there is a section:

<#Imchada> a foaf:Person; foaf:name "Imchada"; rel:childOf <#FirChorb>. #sameas http://example.com/LLdal_corpri_arad.ttl#Imchad ? - CY

Do some research to find out if this Imchada is the same as Imchad in dal_corpri_arad.ttl.

Representing generation counting

The Laud Misc 610, in its history of the Eoganachta, presents a new sort of data that might need to be represented in a triple. The text occasionally chooses an ancestor figure (A) and then specifies various descendants (D) in terms of how many generations (n) they are from this ancestor figure, taking the following approximate form:

A, the _n_th man out from him: D

For example,

Clann Núadat Decláim fodecsa .i. in sechtmad fer húadside .i. Munemón

The numbers of generations can quite large (up to 11 so far), so it would be cumbersome (although possible) to represent this with a succession of empty nodes. So could we add some sort of triple that would qualify rel:descendantOf with a generation count? I realise this might not be possible, as it essentially involves three objects: the ancestor URL, the descendant URL, and the generation count numeral, which would need to be linked together. Alternatively, it might be an interesting challenge.

Prefaces versus poems

http://www.ucc.ie/celt/published/G105003/text001.html

In Rawl.B.502, the poems 'Enna Labraid luad caích' and 'Nuadu Necht ní dámair anfhlaith' are introduced by prefaces that describe them each as a pedigree of a king of Leinster back to Adam. However, the poems contain no genealogical data: they are just lists of names. We have decided to assume that those named are to be arranged into a patrilineal pedigree in the database, with reference to other sources in cases of ambiguity. This should be noted as a methodological decision.

Inconsistent filenames

Three files (ríg_lagen.ttl, ríg_mide.ttl, and ríg_ulad.ttl) use a fada on "rig" where all other similar filenames do not. I am going to attempt to remove all instances of "-í-" from where these filenames occure but am posting this year, in case you have been using them in another context...?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.