Open daliboris opened 9 months ago
In my opinion, Delimiter is enough and I have arguments in favour.
I'm ok with unifying this in the examples and using "Delimiter". The values of the function attribute here are not hard-coded in the schema, but I do see the benefit of uniformity in the values we use in the examples.
Boris, shall we use this simple update to refresh your knowledge of the workflow we discussed a while back? You would need to:
dev
examples.xml
only; the "stripped" version, i.e. one without the TEI namespace, which is needed for inclusion into egXML
elements, will be created automatically using oXygen transformations) <listChange>
for version 0.9.4 in <revisionDesc>
in TEILex0.odd
I would then check the PR and merge it into the dev branch. As you may remember, I'm not merging individual commits into master. We do individual commits into dev, and then periodically merge the dev branch as a new release into the master.
Hi @ttasovac, just noticed this assignment for me. I will try to do my best (in the next week?).
@daliboris just a small reminder...
I looked at the
<metamark>
element in the examples in the Guidelines and found very similar main names for the@function
attribute. i.e.Marker
,Separtator
,Delimiter
:Is the difference between Marker, Separator and Delimiter so significant that we should keep them all, or can we just use one or two preferred names?