Skip to content
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.

Sign up for GitHub

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

Jump to bottom

New element listNote as a wrapper for note elements #1879

Open
tuurma opened this issue May 7, 2019 · 5 comments
Open

New element listNote as a wrapper for note elements #1879

tuurma opened this issue May 7, 2019 · 5 comments
Assignees
@tuurma
Labels
Status: Go

Comments

@tuurma
Copy link
Contributor

tuurma commented May 7, 2019

Intended particularly for use in a standoff manner (within planned standoff) element but allowed within text as well. Ticket inspired by the discussion on #1833
@tuurma tuurma self-assigned this May 7, 2019
@martindholmes
Copy link
Contributor

Council F2F in Graz decided to defer this until decisions have been made about the standoff element.

@sydb
Copy link
Member

sydb commented May 2, 2020 •
edited by ebeshero
Loading

Council VF2F subgroup thinks the time is nigh for a discussion of this with full Council. While we have our reservations about yet another element to contain <note>s, it does make sense, and the use case is somewhat different than that of <listAnnotation> (in that <listAnnotation> is not intended for use in running prose, whereas <listNote> is, and thus will need to allow things like model.global.)

@ebeshero
Copy link
Member

@tuurma Council is wondering if we need <listNote> any longer given what we've developed for <listAnnotation>?

@jamescummings
Copy link
Member

I think <listNote> is useful also outside the area of standoff. I think it would be good to have anyway (and have it claim membership in model.listLike)

@ebeshero
Copy link
Member

ebeshero commented Oct 2, 2021 •
edited
Loading

Council VF2F discussion:

  • <listNote> should include <noteGrp>.
  • Allow <listNote> as child of <front>, <body>, <back>, and <div>
    also more generally available in the teiHeader (as alternative to unstructured <p> content)? At least in <noteStmt>
  • Also, inside <person>, <place>, <event>
  • Consider: membership in model.listlike?
  • probably it's not a good idea to make <listNote> available globally just like <note>. (not inside <p>)
    Follow attributes used on other list elements

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

@tuurma tuurma

Labels
Status: Go
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@sydb @jamescummings @tuurma @martindholmes @ebeshero @martinascholger