-
Notifications
You must be signed in to change notification settings - Fork 24
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
Values of the @function attribute of the <metamark> element in examples #214
Comments
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:
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?
The text was updated successfully, but these errors were encountered: