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

new attribute @assertionRank #74

Closed
2 of 9 tasks
SJagodzinski opened this issue Oct 15, 2019 · 2 comments
Closed
2 of 9 tasks

new attribute @assertionRank #74

SJagodzinski opened this issue Oct 15, 2019 · 2 comments
Assignees

Comments

@SJagodzinski
Copy link
Contributor

Add new attribute @assertionRank, added to a parent element of <evidence>.

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. [email protected]

The issue relates to

  • EAC-CPF schema issue
  • EAC-CPF Tag Library issue
  • EAD schema issue
  • EAD Tag Library issue
  • Schema issue
  • Tag Library issue
  • Suggestions for all schemas
  • Suggestions for all Tag Libraries
  • Other

Wanted change/feature

Add new attribute @assertionRank, added to a parent element of <evidence>, cf #73, that can be used when assertions of the same type contradict.

Suggested Solution

Add new attribute @assertionRank, added to a parent element of <evidence>, cf #73, that can be used when assertions of the same type contradict or use the new attribute @status, cf #70.

Context

Proposal as a result of the discussion on Topic: Assertion description during the f2f meeting 2019, see minutes.

Proposal to solve #43

@fordmadox
Copy link
Member

fordmadox commented Dec 17, 2019

In my notes, I wrote down that we would prefer to use @status for this instead of creating yet another attribute. If @status is added, then I agree that it could/should also be used in this context (e.g. status='deprecated', etc.)

@SJagodzinski
Copy link
Contributor Author

The topic assertion description was discussed for revision and is solved with a new element and a range of new attributes. Follow the discussion with our topic papers and see the following related issues:

<citedRange> #162
@conventionDeclarationReference #174
@sourceReference #172
@maintenanceEventReference #173
@unit #255

The solution will be explained in our Best Practise Guide.

The attribute @assertionRank will not be added.

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

2 participants