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

<derivation> should allow <bibl> in its content model #1830

Closed
martindholmes opened this issue Oct 22, 2018 · 6 comments
Closed

<derivation> should allow <bibl> in its content model #1830

martindholmes opened this issue Oct 22, 2018 · 6 comments

Comments

@martindholmes
Copy link
Contributor

<derivation> can be used to specify that a text is a translation from another text:

<derivation type="translation">

but there's no easy way to specify what it's a translation of. I think the content model of <derivation> should allow <bibl> so that information about the original text can be supplied.

@lb42
Copy link
Member

lb42 commented Oct 22, 2018

The spec for derivation says that info about the sources from which a text is derived should be supplied in the sourceDesc. Which makes more sense to me

@sydb sydb changed the title <derivation> should allow <bibl> in its content model <derivation> should allow <bibl> in its content model Dec 7, 2018
@emylonas
Copy link
Contributor

Council F2F with @martindholmes agree that the bibliography for a translation or other type of derivation information belongs in <sourceDesc>. It will be helpful to add an example showing this to <sourceDesc> and assign to Martin to add the example that caused this issue.

@martindholmes
Copy link
Contributor Author

Pull request issued.

@peterstadler peterstadler added this to the Guidelines 3.7.0 milestone Sep 16, 2019
@martindholmes
Copy link
Contributor Author

This is now just waiting on pull request #1924.

@tuurma
Copy link
Contributor

tuurma commented Oct 17, 2019

Happy to merge unless requested reviewers would like to have a say @jamescummings @emylonas @martinascholger

sydb added a commit that referenced this issue Feb 11, 2020
Fixed example added for issue #1830.
Merge confirmed at Council meeting.
@martinascholger
Copy link
Member

This has been merged, so I'm closing this.

hcayless pushed a commit that referenced this issue Jun 26, 2022
hcayless pushed a commit that referenced this issue Jun 26, 2022
hcayless pushed a commit that referenced this issue Jun 26, 2022
Fixed example added for issue #1830.
Merge confirmed at Council meeting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants