UC Davis Information Technology Standards Repository

This repository contains UC Davis's collection of information technology standards, guidelines, and other informational documents that have been approved for us by UCD's IT organizations. #Definitions of some of the terms used in this repository follow at the end of this document.

The Specifications

Specification	Status	Compliance	Notes
Preliminary Recommendations for Application Platforms to Foster Interoperability, Sharing, and Reuse	Proposed	Guideline	Submitted to IT Roadmap Coordinating Council on 4/30/2010.

Definitions

Specifications in this repository may have any of the following three statuses:

Approved - The specification has successfully completed the vetting process.
Proposed - The specification has entered the vetting process, but that process has not completed. A special case is "Proposed, returned to authors" for proposed specifications that have been returned to the authors for revision.
Draft - The specification is being created. It has not yet entered the SSWG's vetting process.

Compliance with these specifications may or may not be required, depending on the specification's scope, as defined below:

Compliance - The degree to which UC's IT organizations are expected to conform with the specification. Compliance may be dependent on scope:
Scope - A description of the conditions under which a specification is a standard, guideline, or general information. Examples of scope might be "UCD-wide enterprise applications" or "applications local to a single department." A specification may have multiple compliance expectations for different scopes.
Standard - Compliance is required.
Guideline - Compliance is recommended.
General Information - The specification does not state recommendations or requirements, only analysis of issues that is deemed of general interest.

These concepts are defined more completely in UC Davis Information Technology Standards Process.