Hawkins: I think you can't put a @target on the <note> element itself [actually, you can!], so there would need to be a <ref> within the <note> in order to point back.

Mylonas: You don’t want the siglum character to be an attribute value because you need to be able to handle the case of a non-Unicode glyph used to link between a siglum and note.

Hawkins: Best to put <ref> on the superscript symbol which appears in the note itself.

Mylonas: Perhaps an alternative pointing

e. g. @sameAs

Bauman: Need to research this a bit

TEI wants to use <ref> for the prose

Nothing stated about what to do for the symbol within the <note>

Can use <ref>

@sameAs might be more appropriate, not certain

Narrower intended usages

Hawkins: Probably need to get an image of a page siglum and a footnote and encode this bit of text in order to make these conversations easier to follow.

Proposes that someone mockup a sample with a proposed way of encoding sigla and notes.

Mylonas: @corresp might be better

@sameAs won't suffice

Bauman: @corresp references a concept in mathematics

Must users don't employ @corresp in this manner

(Looking for examples)

Hawkins: Will find an image of a page with the footnotes

Produce a quick mockup of the encoding so that we have something concrete to discuss.

Mylonas: We have a set of problems

One option: stick note where it appears on the layout of the page, give it a reference, and ensure that it's rendered as footnote, margin note, endnote, etc.

Another option: place it within the text, linking it to another location (e.g., linking to notes at the bottom of the page within the text)

Wherever you put them, have a notation where they are anchored in the text

For cases where there are typos and the anchors don't correspond, what is the mechanism?

Hawkins: Leaving the footnotes at the bottom of the page makes sense in the case of mass OCR-encoding, where you don’t want to have to rearrange the OCR text when encoding.

Bauman: At what level are we discussing footnote numbers?

Hawkins: Recommended at Level 3, required at Level 4

Bauman: Not footnote numbers, but actual notes.

Hawkins: That’s what I meant. The BPTL don’t say what to do with footnote numbers appearing in the notes [though imply that you should put the value in the value of @n on <note>].

Bauman: Any sizable library project has recommended that footnote numbers not be encoded [because they are keyboarding].

Should only include footnote numbers at Level 4 or 5, not Level 3.

Hawkins: The BPTL is written under the fiction that someone might upgrade through the levels of encoding even though we have no evidence that people actually do this. If we continue with this fiction, I would hate to see us prescribe removing the sigla at Level 3 but then having to add them back in at Level 4 or 5.

Bauman: That burden is on the user

Mylonas: We recommend doing notes in Level 3 and require them in Level 4.

Hawkins: Best practices permits more than one option for certain problems

In Level 3, if the notes are encoded where they occur in the layout of the page, you should use either <ref> (implies that the siglum is right there, as the content of the <ref> element) or a <ptr/>; in the latter case, the siglum appearing on the page is not encoded as content.

Perhaps we should revise the BPTL so that at Level 4, the encoding of sigla becomes significant.

Probably need to permit both options [HAWKINS: NOT SURE WHAT I MEANT]

Mylonas: Mass-scale digitization [with OCR] preserves the location of the footnote in the layout on the page.