-
Notifications
You must be signed in to change notification settings - Fork 84
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
p5odds: Allow "URN" as value of @type
of <idno>
#2630
Conversation
Note: I am not sure the “TEI: ODD” label is correctly applied to this — it might be for the TEI language defined by the Guidelines, not the TEI language defined for the Guidelines. Sigh. Anyway, this is high priority because it is holding up work on #2516. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All tests pass and the changes seem reasonable to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Upper case for URL brings it in line with the others in P5.
of handNotes, courtesy of Christian Thomas. This commit will not build as is, it needs the change to p5odds of #2630 before it will build properly.
I've tested and built guidelines and exemplars with it. All good, and the update is definitely useful in the cause of new and wider-ranging examples of |
Per Slack conversation with @raffazizzi , add "URN" as possible value to
@type
of<idno>
in p5odds. While I was there I also:I have checked. Use of
<idno type="URN">
results in output that is not really pretty in the HTML Guidelines (specifically, in the Bibliography), but not particularly ugly, either, and does not falsely imply that your web browser will open a URN. (Which use of<ptr target="urn:duck:billed:platypus"/>
would.)I have also checked, and there were no occurrences of
<idno type="url">
in P5, so changing this to "URL" should not cause problems.