change teiCorpus content model #1922
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
as per Council face2face at Graz #1823
tuurma
approved these changes
Oct 17, 2019
|
@peterstadler — I think I would prefer to see this work done in the standOff branch, no? Can you take a look at the teiCorpus tagdoc there (in particular commit 10991f7) and see if you think it addresses #1823 or not? |
|
@peterstadler @sydb can be close this PR? |
|
@martinascholger: I think so. The content model of thus requiring 1 or more of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
as per Council face2face at Graz #1823.
The one thing I couldn't solve is to allow for interleaved
<TEI>or<teiCorpus>. Those have to be put at the end now.The underlying problem of creating an ambiguous content model was already imminent with the old content model once you designed a schema without a member of
model.resourceLike.