Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 20.6

Java Metadata Interface (JMI)
Java Metadata Interface (JMI) Standard or Specification

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: The Java Metadata Interface (JMI) specification, Java Specification Request (JSR) 040, enables the implementation of a dynamic, platform-independent infrastructure to manage the creation, storage, access, discovery, and exchange of metadata. JMI is based on the Meta Object Facility (MOF) specification from the Object Management Group (OMG), an industry-endorsed standard for metadata management. The MOF standard consists of a set of basic modeling artifacts described using Unified Modeling Language (UML). Models of any kind of metadata (called metamodels) can be built up from these basic building blocks. JMI defines the standard Java interfaces to these modeling components, and thus enables platform-independent discovery and access of metadata. JMI allows for the discovery, query, access, and manipulation of metadata, either at design time or runtime. The semantics of any modeled system can be completely discovered and manipulated. JMI also provides for metamodel and metadata interchange via Extensible Markup Language (XML) by using the industry standard XML Metadata Interchange (XMI) specification.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: Prohibited. This entry is not (currently) permitted to be used under any circumstances.

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v13.9
Decision Date: 09/30/2013
Introduced By: Extended Tool List (ETL)
Standards Body: Oracle
- The information contained on this page is accurate as of the Decision Date (09/30/2013).