Next steps of cross-cutting requirements work (inc. compatibility and reviews of building block specs)
https://datatracker.ietf.org/doc/html/rfc2119
https://datatracker.ietf.org/doc/html/rfc8174
development, deployment, architecture, quality, security, data
REQUIRED, RECOMMENDED, DRAFT, DEPRECATED
required, expected, recommended, draft, deprecated
<?xml version="1.0" encoding="utf-8"?> <?xml-stylesheet type="text/xsl" href="cfr.xsl"?> <cross-functional-requirements> <requirement> <category>development</category> <en> <rule>This is a requirement</rule> <additional> ... </additional> </en> <level>REQUIRED</level> <extensability??>protected/open/etc</extensability> <reference>1</reference> </requirement> <requirement> ... <requirement> ... </cross-functional-requirements>
Creation of GovStack overarching terminology
https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/3-terminology
Other issues raised