Open carlwilson opened 1 year ago
The issue is going to be discussed by the DILCIS Board
I have nothing to opose to this suggestion. Its just better documentation.
The DILCIS Board have agreed to approve this suggestion on its meeting 2023-12-06.
This can go ahead then. This will need a proper pass over the specifications but @stephenmackey and I should be able to get it done for some time in Feb 2024.
@johnmackey actually, way beyond me. 😊
Stephen Mackey Senior Consultant Penwern Limited +33 668 397 453 @.***
From: Carl Wilson @.> Sent: Tuesday, January 9, 2024 12:08 AM To: DILCISBoard/E-ARK-CSIP @.> Cc: Stephen Mackey @.>; Mention @.> Subject: Re: [DILCISBoard/E-ARK-CSIP] Using dictionary pairs for requirement history (Issue #710)
This can go ahead then. This will need a proper pass over the specifications but @stephenmackeyhttps://github.com/stephenmackey and I should be able to get it done for some time in Feb 2024.
— Reply to this email directly, view it on GitHubhttps://github.com/DILCISBoard/E-ARK-CSIP/issues/710#issuecomment-1881962583, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIKSFYJ6FTPQONTBLJVM3DDYNR357AVCNFSM6AAAAAA4PSKGDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRHE3DENJYGM. You are receiving this because you were mentioned.Message ID: @.***>
The suggestion is:
<dl xmlns="http://www.w3.org/1999/xhtml">
<dt>since</dt><dd>v2.1.0</dd>
</dl>
Board members acknowledgment of the issue: Tick the box in front of you name to indicate that you have looked at the suggestion.
Voting (Decision making will be carried out on the basis of majority voting by all eligible members of the Board. In the case of a tied vote, decisions will be made at the discretion of the Chair)
Tick the box in front of you name to say yes to the suggestion.
7 DILCIS Board members have acknowledge the issue 7 DILCIS Board members agree with the solution
The suggestion of updated encoding of requirement addition will be part of the next release of the specifications.
Issues will be created in the relevant repositories.
Record the version of the specification in which a requirement was introduced. The validation developers have requested the field. Implementation could be fairly simple, again the examples have had the current XPath and Cardinality information removed see #707 :