-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting #9 2021 10 28
Knut Jetlund edited this page Oct 28, 2021
·
3 revisions
Zoom meeting 2021-10-29 13:00-15:00 CEST
| Attendees: |
|---|
| Knut Jetlund, Norway, HMMG Convenor |
| Ronald Tse, CalConnect |
| Reese Plews, JISC, TC211/TMG |
| Magnus Karge, Standards Norway |
| Tobias Spears, HMMG/XMG |
| Evert Bleys, Australia, XMG Convenor |
| Robert Gibb (NZ) |
- Towards a TC211 good practice on document style #9
- Recent experiences with ADD (Ron)
- Outline for the report: Report
- Next meeting 2021-11-25
Towards a TC211 good practice on document style #9
There was consensus in the group on these conclusions:
- URIs should be complete, not fragments.
- URIs should be resolvable URLs.
- URIs should lead to an address where the requirement is described. For example, for automated conformance testing: An error message could link to the requirement for further explanation.
- We believe that with an MA for resources, the requirements can be handled as suggested above.
Furthermore,
- Internal numbers can be added in addition to the URIs, but the URIs are mandatory and will be used for reference.
- Write the whole word "Requirement" or "Recommendation" in documents, not abbreviations.
- The word "Shall" must not be used outside of requirements. Except for the data dictionary, but then in constraints that are also specified as requirements.
- Each identified requirement should have one specified requirement. Several parts can be handled as linked requirements.
- There is a need for some way of separating the requirement text from the rest of the document.
Ronald Tse presented the work being done in cooperation with British Standard Institute on implementation tools for standards.
Link to the report: Report The goal is to fulfil as much as possible of the report before the next meeting in November.