Myths on Maps

So in tackling the Calydonian Boar Hunt issue, Greg and I had to figure out how to include an event in a character's description. It's a bit complicated so: EXAMPLE!

<person xml:id="eurytion_1">
<persName>Eurytion</persName>
<note type="description">A participant in the <listEvent>
<event corresp="events.xml#event_101">
<desc>Calydonian Boar Hunt</desc>
</event>
</listEvent>, killed unintentionally by <persName corresp="#peleus"
>Peleus</persName>.</note>
<age n="9"/>
<note><listPerson>
<personGrp/>
<relation name="father" active="#antigone_2"/>
</listPerson></note>
<sex value="1">male</sex>
</person>

So within the description add <listEvent> then <event (and the xml id of the event you want)> then <desc>(put the name of event here) and close all the tags.

~Simon

Added at group greeksAtTroy. I have included achaeans, argives and danaans as subgroups, and should perhaps also include them as akas (I don't know if this would even work). I plan also to include as subgroups the contigent groups of the Greeks as they are described in the CoS, for now.

I am unsure whether or how to add the trojanWar group that already exists, and gives a long list of names from Apollodorus, without sources or citation, and without sorting the participants into subgroups, which I think is useful. I will leave this entry alone for now, but it might be good in the future to edit it to include all the subgroups who participated in the Trojan war, and then edit out from the long list of characters all the characters already included in the subgroups.

Homer, in the Catalogue of Ships, and later, Apollodorus both describe the contributions of men and ships that various city-states made to the Greek expedition against Troy. As it stands, there are two separate sets of events in the events list; those drawn from Homer's description, and those drawn from Apollodorus' description. Homer and Apollodorus are clearly describing the same thing, although the information they provide is not identical.

For example, event 1078 cites Apollodorus saying that the Boeotians contributed 10 leaders and 40 ships, event 1406 cites Homer, who names the Boeotian leaders and says they contributed 50 ships with 120 men each. Homer and Apollodorus are referring to the same thing, and so we need to be able to see that, but we also need to be able to see and preserve the differences in their accounts.

Greg proposes two possible solutions. The first is to keep two separate events with two separate ids in the list of events, and to include a "same as" thing, so that the two events can be associated. This has the advantage of keeping each version of the events simply and unambiguously associated with its proper citation, but poses possibly insurmountable difficulties for when it comes time to incorporate ordered series of events into journeys (it will not be possible, it a journey, to have to contemporaneous and notionally identical events).

The second possible solution is to merge the two events under one id, and include bibl references for each of the sources (ie, Apollodorus, Homer, and whichever authors are added to the project in the future). The downside of this is that it could become difficult to present the information correctly, while also sorting out differences and showing clearly what info is contained in what source.

A third possibility is some system that combines these two possibilities, which would be dependent on subjective judgement of the difference of events.

I want to build a "browse by text" widget that provides a categorized list of stuff within the fragment a user chooses. For example, clicking on "browse by text -> Apollodorus -> Places" will display a list of all places mentioned by Apollodorus, and choosing Characters or Events or Groups will show a list of all characters, events and groups mentioned by Apollodorus.

The XPath for showing all unique places in Apollodorus:
//p/placeName[not(@corresp=preceding::placeName/@corresp)]/@corresp
This should only provide placeNames that are direct children of p elements - meaning it will ignore placeNames nested in notes, bibls and cits.

I removed 'abdera' and 'apollod' from the character list, and corrected the one reference to 'Apollod' in Apollodorus to "Apollo."

I have come across the following characters in the characters list which almost certainly need to be removed: cercopes, chthonic (this is an adjective, not a name, erichthoniius (almost certainly a misspelling of "erichthonius")

I think the following probably also need to be removed: curetes, byblus (place, not a person)

Attention should be paid to the character entries "humanity_1" and "humanity_2" -- I'm not sure they are properly characters.

I suspect cycnus_1 and cycnus_2 may be the same character, should investigate.

SBE, LM and I sorted out at least the xml-side of a couple of issues today: sub-groups, and how to deal with disputed parentage.

1) When we have a group that clearly belongs to another group how do we mark up the relationship? For example, the group leadersOfTheBoeotians already exists. If there are leaders, clearly there are followers, and also clearly, there is a larger group containing them all. Solution:

<org xml:id="boeotians">
    <name>Boeotians</name>
    <org corresp="#boeotiansLeaders"/>
    <org corresp="#boeotianMinions"/>
    <personGrp>
    	<persName corresp="characters.xml#tim" source="apollodorus.xml#apollodorus-epitome_1.1.23">Tim</persName>
    </personGrp>
</org>

** please note the addition of the source attribute to the persName element.

2) When a claim of parentage is made that is in dispute with another claim - e.g. Apol. says Tim is the father of one child (Keith) but Homer says that Tim is the father of a different only child (Kevin) we need a way to render this in the xml. Previously we just did this:

<relation name="father" active="#keith #kevin"/>

but now we're going to do this:

<relation name="father" active="#keith" corresp="#apol_1.1.1"/>
<relation name="father" active="#kevin" corresp="#homer_1.120"/>

To sum up as a rule/guideline for RAs
When you add a group to another group use a self-closing org tag with a corresp for group you are including. In the case of individuals being added directly to a group, be sure to include a citation using the source attribute. The citation may be the first reference in a text of the character's membership in the group, or the most explicit.

When you add a relation tag to a person please provide a corresp for each occurrence of the relation element. Not to say that each child of someone needs a relation element of their own. Rather, only add a new relation element when ambiguity/dispute occurs, as in our example above. When we have an undisputed collection of children we can provide a single corresp for all. That is, if author A tells us that Tim is the father of Keith, Kevin, and Kathy and no other author disputes this we only need one relation tag

<relation name="father" active="#keith #kevin #kathy" corresp="#authorA_1.1.1"/>

The application now displays a character's gender.
TEI uses ISO 5218:1977 Representation of Human Sexes as a guide, thus 0 indicates unknown; 1 indicates male; 2 indicates female; and 9 indicates not applicable.
So, when editing the gender of a character be aware that it works this way:
The xml tag looks like

<sex value="1">male</sex>