# Presentation: 861670

## POC: Jay Chin
jchin@fgm.com
FGM Inc
Aug 18 2004

**jchin@fgm.com**
**FGM Inc**
**Aug 18 2004**

**DoD Metadata Registry And Clearinghouse**
**Version 5.0 New Features **

**Unclassified**

## Agenda

**Overview of current Version 4.1**
**Why version 5**
**New Features**
**Standard Support**
**NCES / Core Service **
**Notional components**
**Future Gallery Map**

## DoD Metadata Registry Portal

- “One Stop” Publish & Subscribe for:
**Build Time Metadata Registration **
**Pulling Re-usable Data Components**
**Information Community Management**
- Now Vending:** **
**Database Segments**
**Reference Sets**
**Transformations**
-  XML
**Data/Metadata Tools**
**Taxonomies**
**More Products soon (e.g., symbology, translations)**
- Over 3,500 registered users

_**http://metadata.dod.mil**_

***Purpose: visibility and re-use, ***_***not***_*** standardization through mandate!***

- Web-based!

**Notes:**
As of Aug 17,2004 – there are 3,789 registered users
We have an extensible structure that allows us to quickly set up new galleries for specific types of metadata
The intention is to have a central place for all types of structural metadata where an end user may make assertions about items from one gallery to another

## DoD XML Gallery

***IOC: 19 May 1999 - Current Version = 4.1***

***- Global Net Access***
***- Pub-Sub Registry***
***- Business Rules***
***- Organizations***
***- Over 80,000 registered components***
***- 86 Namespaces***

***http://metadata.dod.mil/xmlreg/user***

**Notes:**
On the Unclassified (private) instance of the registry, there are 82,630 components:
Packages - 249
Schemas – 2,123
Elements – 60,253
Attributes – 2,331
Facets – 11,655
Domain Values – 4,618
Docs - 882
XML Sample - 469
Style Sheets -33
Source Code - 17

## Architecture of v4.1Current Version

**GIG-ES Portal**

**Developers, Architects, etc.**

- 3rd Party
- Portlets

**Transformation Services**

**Mediation Engine(s)**

**Translations Schemas**

**CORE Services**** **

**Oracle DB**

**XML Gallery**

**BEA Weblogic Server & ColdFusion**

**Data Elements Gallery**

**Reference Data Sets Gallery**

**Database Segments Gallery**

**Web Services**
**REST**
**WS-I**

**Metadata**
**Registry Portal**

**GIG-ES Portal**

**Home page uses Weblogic Portal**
**Remaining pages are written in ColdFusion**
**DB is Oracle**
**Web server is Netscape Enterprise**

**Taxonomy Gallery**

## 20,000 Foot View

**XML Schema**

**Data Elements**

**Taxonomy**

**Reference Data Sets**

**DB Segments**

- Users

- Systems

**DoD**
**Metadata Registry and**
**Clearinghouse**

*HTTP Access*

*Metrics:*
*   **User & System Access*
*   **Re-use*
*   **Downloads*
*   **Viewing*

*Search & Discovery*

*Web Service Access*

*Categorization*

**Data Models**

**Assertions**

*Change *
*Notifications*

**Notes:**
Having a central registry for artifact metadata enables several things
Web Service provides the building block for other systems to build off the registry.  For example, the NCES mediation service uses a MDR web service to look up style sheets for transformations
Most objects will be retrievable via HTTP – very useful for XML schemas

## Why version 5.0

**Consolidate COTS products**
**BEA Portal Platform**
**Oracle 9i (10g?)**
**Portals give end user more options**
**BEA is better suited for run-time services**
**Core data model for all types of artifact metadata**
**Increased reliability and uptime via clustering**
**Part of the NCES Discovery core service**
**Support other services such as mediation**

**Notes:**
The registry has always been in a spiral development process – 2 releases per year
By consolidating on fewer COTS products, we reduce license costs and increase stability.  
DOD has an enterprise BEA license and other programs are moving to this platform.  With MDR on the same platform, we will be in a position to interoperate with those programs
Having a core data model positions the MDR to readily add new galleries 

## New Features

**Taxonomy gallery**
**OWL encoded format**
**Provides capability to tie any information resource to a node in a taxonomy**
**HTTP access to most artifacts in a W3C compliant manner**
**Branding**
**Improved Security**
**Auditing**
**Multiple authorization routes**
**Granular access rights**
**Federation capability**
**Portal – end user customization**
**Additional Web services**
**Search for all Information Resources**
**Retrieval for all information Resources**

**Notes:**
And, there will be no loss of functionality from previous versions.

## Standards Support

**ebXML API compliance**
**Will have a standard profile for semantic interoperability**
**JAXR (registry API)**
**WSRP (Portals)**
**WS-I (web services)**

## Notional Components	

- XML
- Portlets

- Taxonomy
- Portlets

- Data Elements
- Portlets

- RDS
- Portlets

- DB
- Portlets

-             **MDR Portal    **

- BEA Auditing and Security Services

- NCES Security - BAH SDK

- Oracle RAC

- MDR v5.0 DB

- JAXR API

- Web Service

- Increase reliability and performance

- Standard support
- Leverage Open-Source

- Implement NCES security services (Interchangeable layer)

- SIPR and JWICS security accreditation

- Inter-operate with other NCES portals via WSRP

**Notes:**
The security layers may be removed/addressed per installation requirements

## Future Gallery Map

***adds***** progressively more metadata* “galleries” from various resources**

**Emporium Baseline**
**(Ref Sets v1)**

**XML Reg**
**v1**

**Transformations**

**Ref Tabs**
**(Ref Sets v2) **

**Data Elements**
**(DDDS)**

**DB Segs v0**

**Messages**

**XML Reg**
**v2**

**DB Segs v1**

**XML Reg**
**v3**

**ISO 11179 **

**Models(DDA)**

**Symbology**

**Other**

**Taxonomy**

**EBXML**

**Ontologies**

**Future Gallery Map**

**XML Reg**
**v4**