-
Notifications
You must be signed in to change notification settings - Fork 88
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
Make small fixes to event and eventName #2466
Comments
@joeytakeda could you do the change for German in this branch so that I don’t have to git checkout various upstream changes? @martinascholger could you doublecheck my prose?
|
Okay I have now done all of what I (and my monolingualism) can do :-) But in working spending a bit more time with this, I have a few questions (which have to do with
<alternate minOccurs="0" maxOccurs="unbounded">
<elementRef key="event" minOccurs="1" maxOccurs="1"/>
<elementRef key="listEvent" minOccurs="1" maxOccurs="1"/>
</alternate>
<alternate minOccurs="0" maxOccurs="unbounded">
<classRef key="model.personLike" minOccurs="1" maxOccurs="1"/>
<elementRef key="listPerson" minOccurs="1" maxOccurs="1"/>
</alternate>
<alternate minOccurs="0" maxOccurs="unbounded">
<classRef key="model.placeLike" minOccurs="1" maxOccurs="1"/>
<elementRef key="listPlace" minOccurs="1" maxOccurs="1"/>
</alternate>
<classRef key="model.objectLike" minOccurs="0" maxOccurs="unbounded"/>
<alternate minOccurs="0" maxOccurs="unbounded">
<elementRef key="relation" minOccurs="1" maxOccurs="1"/>
<elementRef key="listRelation" minOccurs="1" maxOccurs="1"/>
</alternate> Personally, I don't think it should matter in what order you put any of these things (in the current guidelines, the only one of these entities that |
Thanks for those. I fully agree, and thus came up with the following snippet, which I would ask you again to include in your branch to avoid git hassle:
I also considered removing a few agenda items, which can still be done, but they are funny enough to read and show the diversity of the concrete agenda of this body of government. Feel free to just delete a few if brevity is the goal… |
@joeytakeda re my previous comment I also committed that file into my branch at skurzinz@85f0774 |
@joeytakeda Is this now complete with the merging of the PR for eventName? (The last task unmarked here was updating all the |
@joeytakeda Just close if it's complete, okay? |
From Paderborn F2F: We've now merged @skurzinz wonderful work (#2427) into a new branch (https://github.com/TEIC/TEI/tree/issue_2382_eventName) so that we can easily make little adjustments (rather than dipping into @skurzinz 's fork ) before moving into
dev
.In council discussion, we decided to make the following adjustments:
event
s content model to allowidno
as a first child (to preserve backwards compatibility) and placeeventName
in exclusive alternation withmodel.labelLike
andmodel.pLike
desc
of event to "contains data relating to anything of significance that happens in time."desc
s to matchThe text was updated successfully, but these errors were encountered: