Page History

Introduction

Internet2 Trust and Identity's document stewardship process is intended to formalize the management of documents as they are drafted, proposed, vetted, and approved for use, and published for open access.  It is intended to address any documents that are products of work sponsored by Trust and Identity or one of its community advisory groups. Examples of such products include:

...

The foundational document establishing and governing the Document Stewardship process is found here (click on the link to the PDF).

Authorized Sponsors

Submissions to the Document Repository must be approved by a Sponsor.  The authorized Sponsors are::

• CACTI (Community Architecture Committee for Trust and Identity)
  
• The Trust and Identity Program Advisory Group (PAG)
• Internet2 Trust and Identity executive management
  
• Incommon Technical Advisory Committee (TAC)
• InCommon Community Trust Assurance Board (CTAB)
• InCommon Steering Committee

Getting a Doc ID for a document that will go into the Repository

For a document that will eventually go into the repository, it is recommended to get a document ID and format the document with the needed components during the time that you are developing the document, prior to it being finalized. (You will submit the document to go into the repository later when it has been finalized and approved.)

• Contact the librarian, ti-librarian@internet2.edu, to get the document repository ID, DOI and Persistent URL.  (The document will not be placed in the repository and the DOI and Persistent URL will not be active until a later stage when the document is final and approved.)
• Follow the steps below to add the needed elements to the document.

Preparing a Document to go into the Repository

To prepare a document to go into the Document Repository:

...

Here is an example of a repository page that has the attachment of the authoritative doc.

When it's time to update a document

An updated document is a new document with its own new row in the document repository, even though much of its content may be the same as the original document. 
Just as with the original document, the update is subject to review and approval, as specified by its sponsor.

...

• The Repository ID of the original document should be listed as a "superseded document" on updated document's cover page and its repository metadata page.
• The "Deprecated" field of original document's repository metadata page should be "yes."
• The Repository ID of the updated document will be the Repository ID of the original document after adding 1 to the version number. 
  For example, an update to TI.22.3 will have TI.22.4 for its Repository ID. 

Additional Info

Working group chair and flywheel guidelines with regard to the Document Stewardship process are found here.

...