The AARC project, in collaboration with partners such as the Infrastructure, AEGIS, IGTF, REFEDS, FIM4R and WISE, periodically releases guidance to the community on how to best support authentication and authorisation for research and collaboration. This guidance takes the form of Guideline Documents that are public and have are persistently identifiable (and can be so referenced). This pages describes the document process, assignment of identifiers, maintenance of document status information, and publication.
...
Documents are numbered sequentially, and take an identifier of the form "AARC-Gxxx", or "AARC-Ixxx" (for informational white papers), where xxx is a three-digit monotonically increasing number. Numbers are assigned
...
An AARC Guidelines identifier MUST be assigned to all versions of the BPA, to all technical recommendations that pertain to the BPA, to all policy guidance that pertains to Infrastructure proxies and consortia of service providers or IdPs, and for specifications that should be adopted or implemented by the AARC peer organisations. It MUST be assigned to all document that will be published, and MAY be assigned to project deliverables and milestone documents that have value as guidance.
| Assign numbers and review/Number assignment, review, and edit status here :https://docs.google.com/spreadsheets/d/1rvxtSyZBucT0xUTcajWa4YOJ-A8_v4KKgun0aJR1AF4 |
|---|
Document numbers can be assigned by the PMT members. Everyone can comment and suggest improvements (e.g. to the abstract or status)AARC management team members.
A workable document template for those using MS Word is also attached to this page (it actually uses document properties correctly so can be indexed). For non-project documents, drop the "Contractual Date" (up to ..."Lead Partner") bit from it, since for guideline documents it does not make sense. Do keep the copyright and EC funding tag line!
...