New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt <etym> to allow for encoding of typed and complex etymological processes: (i) add to att.typed class; (ii) allow recursion; #1512

Closed
iljackb opened this Issue Oct 4, 2016 · 3 comments

Comments

Projects
None yet
6 participants
@iljackb

iljackb commented Oct 4, 2016

(i) add to att.typed class;
In any analysis or representation of the etymology of a lexical item, it is normal and necessary practice to describe this in terms of etymological processes. The element currently lacks any practical means of labeling this information, thus a natural solution for this would be using @type so that users may have the means to make typological distinctions in etymology, analogously to the way it is done in the synchronic section of an entry, e.g. <form type="lemma">. Typical types of etymological processes that can occur on one or more lexical levels are: borrowing, inheritance (from "parent language"), metaphor, metonymy, compounding, various phonological, morpho-syntactic, processes as desired by the encoder. A simple example is as follows from a French entry for the loanword "week-end":

    <etym type="borrowing">
      <lbl>source:</lbl> <lang>English</lang>
      <cit type="etymon" xml:lang="en">
        <oRef>weekend</oRef>
      </cit>
    </etym>

(ii) allow recursion of <etym>;
Given that etymological processes can co-occur with one another, and that the occurence of one process may provide the necessary basis or circumstance for another to occur, it should be possible to encode such interdependent relationships recursively within the TEI. An example of this is from an entry for the German compound 'Handschuh', meaning 'glove', which is composed of the German cognates of the English 'hand' and 'shoe' ('Hand'+'Schuh'). The process of word formation is compounding. Additionally, in this etymology, the use of 'shoe' is metaphorical since it involves a change in domain from FOOT to HAND (see: Lakoff and Johnson, 1980; Lakoff, 1987; Lakoff, 1993). The <etym type="metaphor"> is nested within the <etym type="compounding"> due to the fact that it is a sub-process which occured as a part of the larger process of lexical innovation in the formation of the compound word form 'Handschuh'.

    <etym type="compounding">
      <cit type="etymon" xml:lang="de">
        <oRef>Hand</oRef>
        <pRef notation="ipa">ˈhant</pRef>
        <gloss>hand</gloss>
      </cit>
      <etym type="metaphor">
        <cit type="etymon">
          <oRef>Schuh</oRef>
          <pRef notation="ipa">ʃuː</pRef>
          <gloss>shoe</gloss>
        </cit>
      </etym>
    </etym>

Note: These examples show the use of <oRef> and <pRef> being placed inside <cit> to contain etymological forms, which of course is not established practice. This usage is described as part of a larger effort to overhaul and refine the markup of etymology in TEI. (see the working draft of the paper here: https://hal.inria.fr/hal-01296498 )

@raffazizzi

This comment has been minimized.

Show comment
Hide comment
@raffazizzi

raffazizzi Feb 6, 2017

Contributor

F2F subgroup: these requests sound reasonable and we suggest to green light.

Contributor

raffazizzi commented Feb 6, 2017

F2F subgroup: these requests sound reasonable and we suggest to green light.

@laurentromary

This comment has been minimized.

Show comment
Hide comment
@laurentromary

laurentromary Aug 13, 2017

Contributor

I don't see this one implemented in the last release. Could someone take care to it?

Contributor

laurentromary commented Aug 13, 2017

I don't see this one implemented in the last release. Could someone take care to it?

@jamescummings jamescummings added this to the Guidelines 3.3.0 milestone Sep 28, 2017

hcayless added a commit that referenced this issue Jan 23, 2018

Resolution for #1512
Added att.typed and permitted recursive <etym> elements. Adapted
examples from the issue.
@hcayless

This comment has been minimized.

Show comment
Hide comment
@hcayless

hcayless Jan 23, 2018

Contributor

I've pushed the suggested changes. I modified the examples above so that they don't use not-yet-valid oRef and pRef in cit. Will close if Jenkins is happy.

Contributor

hcayless commented Jan 23, 2018

I've pushed the suggested changes. I modified the examples above so that they don't use not-yet-valid oRef and pRef in cit. Will close if Jenkins is happy.

@hcayless hcayless closed this Jan 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment