NISS Knowledge Base

The GJXDM and NIEM contain DocumentType components from which standard XML document schemas can be derived. The DocumentTypes include commonly used properties such as control and records management metadata, security and classification metadata, and general document descriptive metadata.

Within its own target namespace, each reference document schema will import the GJXDM or NIEM namespace (or a subset of them) and extend DocumentType for its root element. For example, a CitationDocument schema would import the GJXDM or NIEM namespace and create

(1) a CitationDocumentType that extends DocumentType and
(2) a complex root element CitationDocument of type CitationDocumentType. Consequently, CitationDocumentType inherits all of the standard metadata properties of DocumentType, however, each document designates its own target namespace, enabling local document customization and preventing name conflicts.

The Service Component Reference Model (SRM) is a business- and performance-driven functional framework that classifies service components with respect to how they support business and/or performance objectives. SRM is intended for use to support the discovery of government-wide business and application service components in IT investments and assets.

The SRM serves to identify and classify horizontal and vertical service components that support Federal agencies and their IT investments and assets. The model will aid in recommending service capabilities to support the reuse of business components and services across the Federal Government.

Source:

http://sites.google.com/site/consolidatedreferencemodelv23/Home/service…

The main components are the Service Description and one or more Service Interface Descriptions. A Service Description describes all aspects of a service that are not directly tied to the physical implementation or service interface while a Service Interface Description is a description of the physical implementation or service interface used in a specific implementation of a service. Since a service can implement multiple Service Interfaces, the Service Specification might contain more than one Service Interface Description.