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

Binding revisions #725

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from
Draft

Binding revisions #725

wants to merge 6 commits into from

Conversation

holfordm
Copy link
Collaborator

No description provided.

new rules for new elements in binding descriptions
-sample description (MS. Lyell 65)
-new rules in customizations.xsl for new elements
@holfordm holfordm marked this pull request as draft September 10, 2023 17:42
@andrew-morrison
Copy link
Contributor

You can define a prefix in the root element in the TEI record, same as in the XSLT, like this...

<TEI xml:id="manuscript_7799" xmlns="http://www.tei-c.org/ns/1.0" xmlns:msdesc="http://www.example.org/ns/msdesc">

...then this...

<spine xmlns="http://www.example.org/ns/msdesc">The binding has a slight round spine shape. No spine linings.</spine>

...could be replaced with this...

<msdesc:spine>The binding has a slight round spine shape. No spine linings.</msdesc:spine>

...and, because the default namespace would still be the TEI one, valid TEI tags could be used inside without re-declaring their namespace, like this...

<msdesc:spine>The binding has a slight round spine shape. <hi rend="bold">No spine linings.</hi></msdesc:spine>

It is all the same to an XML parser but more concise and clearer for humans.

In the XSLT, it would be better if the templates for each new element output a <div> instead of a <p>. That way, if they contain TEI <p> those would be transformed into HTML <p> without being nested inside another <p>, which is invalid (although web browsers will cope.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants