1. ViCoS and ‘non-linguistic’ relations: Visualizing Kinship Systems Carolina Pasamonik (University of Cologne)‏ DoBeS Team Beaver

2. I.Ideas & Goals II.Overview Beaver Kinship & Social Organization III.ViCoS for representation of kinship data IV.ViCoS Wishlist Structure of the talk:

3. Why deal with Kinship Systems? - unstructured knowledge space kinship system as central point combined with cultural, linguistic, historical, biographical and geographical information I. Ideas & Goals

4. Why deal with Kinship Systems? - important speaker information I. Ideas & Goals

5. Why deal with Kinship Systems? - important speaker information - not for community work I. Ideas & Goals

6. Why deal with Kinship Systems? - important speaker information - not for community work - scientific explorations and analyses - anthropological surveys - ethnographies I. Ideas & Goals

7. Why deal with Kinship Systems? - important speaker information - not for community work - scientific explorations and analyses - anthropological surveys - ethnographies - women’s points of view I. Ideas & Goals

8. Why deal with Kinship Systems? - important speaker information - not for community work - scientific explorations and analyses - anthropological surveys - ethnographies - women’s points of view - linguistic research - linguistic variation - kinship terms I. Ideas & Goals

9. Kinship in general: - kinship behaviour does not have to be isomorphic with the terminological structure - kin systems are subject to time and other external factors II. Beaver Kinship System

10. Living conditions correlate with kinship and social system II. Beaver Kinship System

11. Living conditions correlate with kinship and social system consequences: - flexible organization II. Beaver Kinship System

12. Living conditions correlate with kinship and social system consequences: - flexible organization - local group size II. Beaver Kinship System

13. Living conditions correlate with kinship and social system consequences: - flexible organization - local group size - exogamy alternatives II. Beaver Kinship System

14. Dravidian Kinship Type - four semantic dimensions: sexrelative age generationcrossness II. Beaver Kinship System

15. Dravidian Kinship Type - four semantic dimensions: sexrelative age generationcrossness II. Beaver Kinship System

16. Dravidian Kinship Type - four semantic dimensions: sexrelative age generationcrossness - crossness category ego generation & adjacent ones (+1/-1 generations)‏ distinction parallel & cross relatives II. Beaver Kinship System

17. ∞ ∞∞∞ FBS = II MBS = X Marriage Patterns Crossness defined by a linking cross-sex relative: FBD = II MBD = X MBFB male ego

18. II. Beaver Kinship System ∞ ∞∞∞ Marriage Patterns Terminology in the Beaver System: ashtéédzé ʼ – “y.sister” ságe ʼ̨ – “cousin / in-law” tłasee – “cousin / in- law” ashidle – “y.brother”

19. II. Beaver Kinship System ∞ ∞∞∞ Marriage Patterns Terminology in the English System: cousin

20. II. Beaver Kinship System ∞∞ Marriage Patterns Ideal constellation: - preference for bilateral cross cousin marriage sibling pairs

21. II. Beaver Kinship System ∞∞ Marriage Patterns Ideal constellation: - preference for bilateral cross cousin marriage - system not corresponding to actual relatives - concepts of “cross (marriageable)” vs. “parallel” relative

22. II. Beaver Kinship System ∞∞ Marriage Patterns Ideal constellation: - preference for bilateral cross cousin marriage - system not corresponding to actual relatives - concepts of “cross (marriageable)” vs. “parallel” relative - classificatory vs. descriptive terms

23. 1. Toolbox Template for LEXUS III. ViCoS Workflow

24. 1. Toolbox Template for LEXUS III. ViCoS Workflow \lx speaker name \lname last name \mname maiden name \bd birthday \lg languages \fra from area

25. 1. Toolbox Template for LEXUS III. ViCoS Workflow possible fields: \cd code \lingpallinguistics / palatalization \lingvarlinguistics / variation \lingmisclinguistics / miscellaneous...

26. 1. Toolbox Template for LEXUS III. ViCoS Workflow \esibelder sibling \ysibyounger sibling \1chfirst child \2chsecond child \3chthird child...

27. III. ViCoS Workflow 2. Starting Point in ViCoS

28. III. ViCoS Workflow 2. Starting Point in ViCoS

29. III. ViCoS Workflow 2. Starting Point in ViCoS

30. 3. Relation Types Manager III. ViCoS Workflow

31. 3. Relation Types Manager

32. Relations needed for representing kinship systems: I. symmetric relation A related to B and B related to A in the same way e.g. spouses (/ siblings)‏ II. functional relation for each A there is a single B in its range e.g. mother of / father of III. ViCoS Workflow 3. Relation Types Manager

33. III. ViCoS Workflow 3. Relation Types Manager

34. III. ViCoS Workflow 5. Editor & Navigator

35. III. ViCoS Workflow 5. Editor & Navigator

36. III. ViCoS Workflow 5. Editor & Navigator

37. III. ViCoS Workflow 5. Editor & Navigator

38. III. ViCoS Workflow 5. Editor & Navigator

39. III. ViCoS Workflow 5. Editor & Navigator

40. III. ViCoS Workflow speaker name geo I lingpal I lingvar I sp.info 5. Editor & Navigator

41. III. ViCoS Workflow 5. Editor & Navigator

42. III. ViCoS Workflow 5. Editor & Navigator

43. III. ViCoS Workflow 5. Editor & Navigator: Variation Patterns

44. general: - automatically created relations (using toolbox file)‏ - automatically generated relations (e.g. transitive relation)‏ - “save” button for arrangements - re-import into toolbox - off line version - links to archive - export function (e.g..jpg)‏ - display of more than one focused entry - use other data categories as main / visible category - partitioned pop-up windows‏ - show only subset of relations (e.g. only symmetric relations)‏ - staggered lines for multiple relations between two entries IV. ViCoS Wishlist

45. specific: - symbols for female / male (circle / triangle)‏ - additional coloured symbols (e.g. for variation patterns)‏ - automatically generated kinship relations, e.g. cross cousin relation (MBS / MBD / FZS / FZD)‏ - links to archive (based on speaker, link to e.g. biographical stories)‏ - show only subset of relations (e.g. only palatalization patterns)‏ - use other data categories (e.g. code)‏ as main / visible category - partitioned pop-up windows, also for relations IV. ViCoS Wishlist

46. III. ViCoS Workflow = tuu = tyuu = chuu 5. Editor & Navigator: Variation Patterns

47. III. ViCoS Workflow 5. Editor & Navigator: Variation Patterns