Federal Enterprise Architecture (FEA) SKOS Ontologies



As part of the eGov initiative, the U.S. federal government (led by the GSA and the OMB) developed the Federal Enterprise Architecture Reference Model (FEARM). The FEARM includes a wide variety of information assets that can be used to align descriptions of information architecture across multiple government agencies.

In 2006, TopQuadrant, under a contract with GSA, developed OWL models of FEARM, which were published as FEA-RMO, the FEA Reference Model Ontologies. A record of this work is accessible at web-services.gov. At oeGov, we are publishing a simplified form of the FEARM using SKOS, the W3C Recommendation for Simple Knowledge Organization Systems.


Essential to the FEARM is a set of four vocabularies; the Business Reference Model, the Performance Reference Model, the Service Component Reference Model and the Technology Reference Model. Each of these constitutes a hierarchy of controlled terms that can be used to describe the enterprise architecture of an agency. A fifth model is the Data Reference Model (DRM), this is currently not represented in an OWL model. However the National Information Exchange Model (NIEM) has been converted to OWL and may be made available at oeGOV in the future.

The FEA is currently published both in PDF (as descriptions of these terms) and in XML (concentrating on the structure of the terms). But neither of these official publications is amenable to use as linked data. In particular, there is no global unique identifier for any of the terms. Most applications of the FEA use the print name of a term as a reference. But these names do not constitute unique references; there are twenty-two occasions in which two terms in the FEA have the same name. They can, of course, be disambiguated by provided the complete context in which the name occurs, but the FEA provides no means for constructing such a reference. Hence many existing applications currently make ambiguous references to these twenty-two terms.

Motivation for SKOS-based publication of the FEA Model

As part of the GSA OSERA InfraStructure Project (OISP), we assigned URIs to all terms in the FEA. In most cases, the URIs end with a name that can be derived directly from the print name of the term. This is not possible when the print names are not unique. In those cases, we created URIs based on the long description of the term. The following table shows the twenty-two ambiguous terms, and the URIs we have chosen to disambiguate them. In a few cases, we had to create two new URIs; in most cases, we created one new URI for one usage of a term, and used the term itself as the basis for the other URI.

SKOS rendering of the FEA vocabularies does not represent any of the linkages between the vocabularies; in particular, the relation between Business Lines and Performance Measures outlined in the FEARM are not present. But all terms in the FEARM are represented in these files; extensions to represent these connections can be made as linked data extensions.

Classification FEA:DocumentClassification
Data Exchange FEA:Data_Exchange_Channel
Data Exchange FEA:Data_Exchange_Schema
Data Management FEA:Organization_Data_Management
Debt Collection FEA:Accounts_Receivable
Enterprise Application Integration FEA:Enterprise_Application_Migration
Enterprise Application Integration FEA:Enterprise_Data_Integration
Financial FEA:Technology_Finances
Financial Management FEA:Accounting_Management
Financial Management FEA:Financial_Planning
Information Sharing FEA:Information_Collaboration
Information Sharing FEA:Information_Interchange
Modeling FEA:Analytic_Modeling
Modeling FEA:System_Modeling
Platform Dependent FEA:Platform_Dependent_BL
Platform Independent FEA:Platform_Independent_BL
Quality FEA:Functional_Quality
Quality FEA:Non_Functional_Quality
Security Management FEA:Facilities_Security_Management
Security Management FEA:Information_Security_Management
Service Transport FEA:Transport_Protocol
Supply Chain Management FEA:Supply_Chain_Service
Video Conferencing FEA:Video_Conference_Technology
Availability FEA:Service_Availabilty
Efficiency FEA:Technical_Efficiency
Integration FEA:Service_Integration
Interoperability FEA:Discovery_Interoperability
Knowledge Management FEA:Knowledge_Asset_Management
Response Time FEA:System_Response_Time
Security FEA:Security_Service

FEA Ontologies

The following Ontologies make up the FEA SKOS Models:

Schema Description Details
cc Creative Commons (in RDF)

Namespace URI: http://creativecommons.org/ns#

RDF Format: http://creativecommons.org/schema.rdf

Dependencies: none

dc Dublin Core

Namespace URI: http://purl.org/dc/elements/1.1/

Dependencies: none

gc Government Core

Namespace URI: http://www.oegov.org/democracy/core/models/owl/gc#

N3 Format: gc.n3

RDF/OWL Format: gc

Dependencies: cc, dc

skos SKOS Ontology

Namespace URI: http://www.w3.org/2004/02/skos/core#

Source: http://www.w3.org/2004/02/skos/



Namespace URI: http://www.oegov.org/models/FEA#

N3 Format: FEA.n3


Dependencies: cc, dc, gc, skos

PRM Performance Reference Model

Namespace URI: http://www.oegov.org/models/PRM#

N3 Format: PRM.n3


Dependencies: cc, dc, gc, FEA

BRM Business Reference Model

Namespace URI: http://www.oegov.org/models/BRM#

N3 Format: BRM.n3


Dependencies: cc, dc, gc, FEA

SRM Service Reference Model

Namespace URI: http://www.oegov.org/models/SRM#

N3 Format: SRM.n3


Dependencies: cc, dc, gc, FEA

TRM Technical Reference Model

Namespace URI: http://www.oegov.org/models/TRM#

N3 Format: TRM.n3


Dependencies: cc, dc, gc, FEA

Last Updated August 14, 2009

Creative Commons License
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>