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.

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

note in msItemStruct #9

Open
atoboy opened this issue Feb 15, 2022 · 1 comment
Open

note in msItemStruct #9

atoboy opened this issue Feb 15, 2022 · 1 comment
Assignees
Labels

Comments

@atoboy
Copy link
Collaborator

atoboy commented Feb 15, 2022

We have various notes as children of <msItemStruct> element. Some of them do not have attributes at all, some of them have various encoding, e.g. AA1322NBKM:

 <note place="foot" xml:id="note1">The text presents the type of Thunderbook,
                            predicting by the Zodiac circle. ...</note>

or from the same description:

<note place="foot" type="articleData" xml:id="note2">The text is wrongly
                            titled as Lunary. ...</note>

In most of the descriptions <note> in this context has no attributes at all.

Suggestion:
Use <note> without any attributes. When it is a child of <msItemStruct> display it as paragraph, not as footnote.

It will be good if the content of <note> is presented in HTML edition of the description.

@djbpitt
Copy link
Owner

djbpitt commented Feb 15, 2022

@atoboy I agree with your proposal. I'll move this Issue to the To be implemented column in the project board so that you can modify the ODD and adapt the existing manuscript description files. Once you've done that, if you can move the card to the Update documentation column, I'll update our documentation addendum file at http://repertorium.obdurodon.org/encoding-policies-update.xhtml and close the issue.

@djbpitt djbpitt added bug and removed help wanted labels Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants