Misplaced Pages

#709290

80-529: The information in this article is provided for reference and background information only. Universal Core is an XML-based information exchange specification and implementation profile which provides a framework for sharing the most commonly used data concepts of Who, What, When, and Where. The purpose of UCore is to improve information sharing by defining and exchanging a small number of important, universally understandable concepts between data-sharing communities, without requiring complex mediations. The specification

160-422: A signed memorandum on 28 March 2013. The released versions of UCore are expected to remain in place for as long as programs continue to use them, and may also support platforms that are somehow incompatible with NIEM. In addition to XML, UCore incorporated the following specifications and standards: A joint 2008 DoD / ODNI Memorandum cited the availability of UCore's initial release. The Memorandum reinforced

240-776: A MarriageAssociationType to represent the fact they are married. The MarriageAssociationType could contain its own properties, such as date of marriage, number of children, date of divorce, death of one spouse, etc. Augmentation of a NIEM data type allows the addition of domain- or model-specific information to the concept embodied in the NIEM type, without creating a new NIEM type. It would be impractical and unwieldy to include all possible domain model-specific properties in NIEM Core schemas for general use. Instead, domain modelers need to be able define data for their use, independently from common definitions. Furthermore, that data needs to be applicable to

320-486: A RELAX NG schema across multiple validators requires either providing those user-defined data types to that validator or using only the two basic types. In practice, however, most RELAX NG processors support the W3C XML Schema set of data types. Schematron is a fairly unusual schema language. Unlike the main three, it defines an XML file's syntax as a list of XPath -based rules. If the document passes these rules, then it

400-463: A cohesive group of data stewards who are subject matter experts (SMEs), have some level of authority within the domains they represent, and participate in the processes related to harmonizing conflicts and resolving data component ambiguities. Communities of Interest. Communities of interest (COIs) are collaborative groups of users who exchange information in pursuit of shared goals, interests, missions, or business processes and who therefore must have

480-611: A common vocabulary that enables effective information exchanges across diverse public and private organizations. NIEM is currently developing the NIEM Metamodel and Common Model Format which can be expressed in any data serialization that NIEM supports, including, but not limited to JSON . Formed from an interagency partnership, NIEM has come to represent a collaborative partnership of agencies and organizations across all levels of government (federal, state, tribal, and local) in addition to private industry. The purpose of this partnership

560-453: A correct subset, however the IEPD specification requires that an IEPD include an exchange schema (along with the reference schemas or subsets) to be considered a complete IEPD. The NIEM schemas may import additional schemas, such as code table schemas, as needed. An optional extension schema may be used to add extended types and properties for components not contained in NIEM, but which are needed for

640-411: A degree of modularity in their languages, including, for example, splitting the schema into multiple files. And both of them are, or can be, defined in an XML language. RELAX NG does not have any analog to PSVI . Unlike W3C XML Schema, RELAX NG was designed so that validation and augmentation (adding type information and default values) are separate. W3C XML Schema has a formal mechanism for attaching

720-545: A focus on mapping or recording location history. An instance of this SA message format will contain components which reuse the RDCs; however, a COI can still construct message payloads with the RDCs without making use of the SA message format. In October 2012, the Department of Defense elected to move towards adopting National Information Exchange Model (NIEM) . This decision was formalized in

800-595: A particular element, and so forth. A schema is analogous to a grammar for a language; a schema defines what the vocabulary for the language may be and what a valid "sentence" is. There are historic and current XML schema languages: The main ones (see also the ISO 19757's endorsed languages ) are described below. Though there are a number of schema languages available, the primary three languages are Document Type Definitions , W3C XML Schema , and RELAX NG . Each language has its own advantages and disadvantages. DTDs are perhaps

880-524: A potential security problem. For WXS validators that will follow a URI to an arbitrary online location, there is the potential for reading something malicious from the other side of the stream. W3C XML Schema does not implement most of the DTD ability to provide data elements to a document. Although W3C XML Schema's ability to add default attributes to elements is an advantage, it is a disadvantage in some ways as well. It means that an XML file may not be usable in

SECTION 10

#1732851047710

960-415: A role when the role has specific data associated with it and its own life cycle. A role type has a property, RoleOf, which indicates what object is assuming this role. A single entity may assume multiple roles. For example, many different entities may assume the role of a weapon. Therefore, if a vehicle is used as a weapon (to attempt to injure or kill a person), then an instance of WeaponType would contain

1040-502: A schema can be regarded as a conceptually separate operation from XML parsing. In practice, however, many schema validators are integrated with an XML parser. There are several different languages available for specifying an XML schema. Each language has its strengths and weaknesses. The primary purpose of a schema language is to specify what the structure of an XML document can be. This means which elements can reside in which other elements, which attributes are and are not legal to have on

1120-584: A schema to an XML document, while RELAX NG intentionally avoids such mechanisms for security and interoperability reasons. RELAX NG has no ability to apply default attribute data to an element's list of attributes (i.e., changing the XML info set), while W3C XML Schema does. Again, this design is intentional and is to separate validation and augmentation. W3C XML Schema has a rich "simple type" system built-in (xs:number, xs:date, etc., plus derivation of custom types), while RELAX NG has an extremely simplistic one because it

1200-534: A shared vocabulary for the information they exchange. COIs reuse data components and artifacts found in NIEM to document their information exchanges. One or more COIs can coordinate to develop new domain content as they identify gaps in the data components needed for documenting information exchanges. NIEM Conformance. There are NIEM conformance rules that serve as guidelines for agencies utilizing NIEM to implement their information sharing exchanges. Grantees developing inter-agency XML-based exchanges must comply with

1280-474: A training video series on NIEM.gov/learn that includes a technical deep dive and is intended to support developers and implementers. Monthly users can sign up for virtual training sessions which includes the pre-recorded videos in addition to a live session with a NIEM expert who will answer questions in real-time. NIEM.gov provides written training materials, such as briefings and process-related documentation on NIEM GitHub , as well as other resources, such as

1360-574: A universal component, consensus by all domains is needed on the semantics and structure of the component. The set of NIEM universal components is stable (once established) and relatively small. Domains. For purposes of NIEM, a domain refers to a business enterprise broadly reflecting the agencies, units of government, operational functions, services, and information systems which are organized or affiliated to meet common objectives. NIEM domains are organized to facilitate governance, and each has some measure of persistency. Each domain traditionally includes

1440-563: A user friendly interface and smarter search results. It is also open source: the community who inspired its creation can contribute to it. The Migration Tool enables the user to upgrade a NIEM XML Schema release subset generated by the SSGT to the next release. Multiple migrations can be run to upgrade to a non-consecutive release. See the NIEM Tools Catalog for other tools developed by the NIEM community. As of December 2022 , NIEM 5.2

1520-497: Is a tangible representation of the entire NIEM data dictionary. It includes all of the element names that are organized hierarchically under core data components (person, property, organization, etc.) with hyperlinks to related elements. This spreadsheet also provides information on the type of data being represented (date, integer, string, etc.) and a precise, context-rich definition of each dictionary component. The Schema Subset Generation Tool (SSGT) enables users to search through

1600-466: Is actually an XSLT transformation that transforms the Schematron document into an XSLT that validates the XML file. As such, Schematron's potential toolset is any XSLT processor, though libxml2 provides an implementation that does not require XSLT. Sun Microsystems 's Multiple Schema Validator for Java has an add-on that allows it to validate RELAX NG schemas that have embedded Schematron rules. This

1680-550: Is commonly referred to as XSD. The process of checking to see if a XML document conforms to a schema is called validation , which is separate from XML's core concept of syntactic well-formedness . All XML documents must be well-formed, but it is not required that a document be valid unless the XML parser is "validating", in which case the document is also checked for conformance with its associated schema. DTD-validating parsers are most common, but some support XML Schema or RELAX NG as well. Validation of an instance document against

SECTION 20

#1732851047710

1760-416: Is complex and hard to learn, although that is partially because it tries to do more than mere validation (see PSVI ). Although being written in XML is an advantage, it is also a disadvantage in some ways. The W3C XML Schema language, in particular, can be quite verbose, while a DTD can be terse and relatively easily editable. Likewise, WXS's formal mechanism for associating a document with a schema can pose

1840-453: Is designed to make manipulation of the XML instance easier in application programs. This may be by mapping the XSD-defined types to types in a programming language such as Java ("data binding") or by enriching the type system of XML processing languages such as XSLT and XQuery (known as "schema-awareness"). RELAX NG and W3C XML Schema allow for similar mechanisms of specificity. Both allow for

1920-407: Is designed to permit "definable levels of interoperability" across user communities. To facilitate adoption, UCore looks to Communities of Interest, or knowledge domains, to encourage adoption of common vocabularies. UCore is not expected to replace complex data sharing within highly developed domains. UCore traces its roots to several predecessor initiatives: The Defense Information Systems Agency

2000-458: Is known as the compact syntax. Tools can easily convert between these forms with no loss of features or even commenting. Even arbitrary elements specified between RELAX NG XML elements can be converted into the compact form. RELAX NG provides very strong support for unordered content. That is, it allows the schema to state that a sequence of patterns may appear in any order. RELAX NG also allows for non-deterministic content models. What this means

2080-553: Is meant to use type libraries developed independently of RELAX NG, rather than grow its own. This is seen by some as a disadvantage. In practice it is common for a RELAX NG schema to use the predefined "simple types" and "restrictions" (pattern, maxLength, etc.) of W3C XML Schema. In W3C XML Schema a specific number or range of repetitions of patterns can be expressed whereas it is practically not possible to specify at all in RELAX NG (<oneOrMore> or <zeroOrMore>). W3C XML Schema

2160-483: Is modeled with an extensible XML schema , a taxonomy of high-level entities and events to categorize the concept of What, and supporting documentation and extension strategies. The final released version is v3.0. A key objective in creating UCore was to keep it simple, easy to explain, and easy to implement. UCore supports the National Information Sharing Strategy, a post-9/11 initiative. UCore

2240-459: Is not technically a schema language. Its sole purpose is to direct parts of documents to individual schemas based on the namespace of the encountered elements. An NRL is merely a list of XML namespaces and a path to a schema that each corresponds to. This allows each schema to be concerned with only its own language definition, and the NRL file routes the schema validator to the correct schema file based on

2320-457: Is of relatively limited capability, but that also has other uses in XML aside from the expression of schemas. Two more expressive XML schema languages in widespread use are XML Schema (with a capital S ) and RELAX NG . The mechanism for associating an XML document with a schema varies according to the schema language. The association may be achieved via markup within the XML document itself, or via some external means. The XML Schema Definition

2400-763: Is sponsored by the Joint Staff J6 Directorate within the U.S. Department of Defense, the Department of Homeland Security Science and Technology Directorate (DHS S"&"T), the FBI Criminal Justice Information Services (CJIS) within the U.S. FBI, Equivant, Georgia Tech Research Institute, the National Association for Justice Information Systems, sFractal Consulting LLC, the IJIS Institute, the US Department of Transportation, and

2480-424: Is that RELAX NG allows the specification of a sequence like the following: When the validator encounters something that matches the "odd" pattern, it is unknown whether this is the optional last "odd" reference or simply one in the zeroOrMore sequence without looking ahead at the data. RELAX NG allows this kind of specification. W3C XML Schema requires all of its sequences to be fully deterministic, so mechanisms like

Universal Core - Misplaced Pages Continue

2560-452: Is the data component. Data components are the basic business data elements that represent real-world objects and concepts. Information exchanged between agencies can be broken down into individual components – for example, information about people, places, material things, and events. Components that are frequently and uniformly used in practice are specified in NIEM and can then be reused by practitioners for information exchanges, regardless of

2640-465: Is to effectively and efficiently share critical information at key decision points throughout the whole of the justice , public safety , emergency and disaster management , intelligence , United States Department of Defense and homeland security enterprise. NIEM is designed to develop, disseminate, and support enterprise-wide information exchange standards and processes that will enable jurisdictions to automate information sharing. Today, NIEMOpen

2720-444: Is valid. Because of its rule-based nature, Schematron's specificity is very strong. It can require that the content of an element be controlled by one of its siblings. It can also request or require that the root element, regardless of what element that happens to be, have specific attributes. It can even specify required relationships between multiple XML files. While Schematron is good at relational constructs, its ability to specify

2800-533: The National Information Sharing Standards Help Desk and Knowledge Base . Training provides the knowledge and know-how stakeholders need to use the tools and other capabilities provided by NIEM. NIEM tools and training opportunities are further described below. Other training materials, such as executive briefings, marketing material, and briefings for conferences and workshops, are offered from time to time and are tailored depending on

2880-593: The United States , but has transitioned to an OASIS Open Project . This initiative formalizes NIEM's designation as an official standard in national and international policy and procurement. NIEMOpen's Project Governing Board recently approved the first standard under this new project; the Conformance Targets Attribute Specification (CTAS) Version 3.0. A full collection of NIEMOpen standards are anticipated by end of year 2024. NIEM offers

2960-573: The United States Department of Justice 's Global Justice XML Data Model (GJXDM) project. As an interagency project it was expanded to include other federal and state agencies such as the Office of the Director of National Intelligence , United States Department of Defense , Federal Bureau of Investigation , Texas , Florida , New York , Pennsylvania , and others. NIEM is designed to facilitate

3040-611: The JADC2 Reference Architecture (RA) Version 3.0 Enclosure D (JADC2 Capability Development and Analytical Framework) within the Application and services, Interface and Data & Information principals. JADC2 Reference Design (RD) Version 1.0, Standard View 2 (StdV-2). NIEM most recently was referred to as the National Information Exchange Model. That interagency government project was an outgrowth of

3120-547: The NIEM NDR. See Tools section below for information on creating EIEM dictionaries. NIEM provides a reference set of tools freely available with each NIEM release. The tools implement all of the structural and content features of the release, including the NIEM NDR. NIEM's well-defined interfaces and output products also support the development of independent third-party tools. Example supporting third-party tools are listed below. The NIEM XML data dictionary spreadsheet

3200-527: The NIEM User Guide and the NIEM NDR. The NIEM data model uses concepts originating from object-oriented programming (OOP). OOP defines a class as a specific entity in the data model, which may represent a real-world object but may also represent any conceptual object , such as relationships and messages. An object's properties are said to describe the object. When the NIEM XML Schemas are generated from

3280-412: The NIEM data model, data model classes are represented as XML Schema types, and data model properties are represented as XML elements and attributes. There are two approaches for extending the NIEM data model for use in information exchange schemas and documents. Specialization is used when a base object class (type) contains or can be subcategorized into a more specific subclass. When this can be done,

Universal Core - Misplaced Pages Continue

3360-416: The NIEM data model, view information about NIEM elements and types, and build a custom XML Schema subset of a NIEM release. The NIEM data model contains over 12,000 elements and represents over a dozen domains; subsets allows users developing an IEPD to select only what they need based on the specific requirements of the exchange. With this tool users can: The Conformance Testing Assistant (ConTesA) enables

3440-458: The NIEM data object itself, and reusable in multiple exchanges. The augmentation approach built into NIEM utilizes XML Schema constructs to reuse the existing XML schema representations for the data model, by allowing them to be augmented with the new information. NIEM uses several techniques from XML Schema to allow as-needed element substitutions for pre-existing NIEM properties and into pre-existing NIEM types. Element substitution techniques allow

3520-601: The UCore Taxonomy with logical definitions for each term or relation defined within. This effort targeted UCore 2.0, which is now deprecated. National Information Exchange Model (NIEM) XML schema An XML schema is a description of a type of XML document, typically expressed in terms of constraints on the structure and content of documents of that type, above and beyond the basic syntactical constraints imposed by XML itself. These constraints are generally expressed using some combination of grammatical rules governing

3600-517: The Virginia Office of Data Governance and Analytics. NIEM provides a working and collaborative partnership among governmental agencies, operational practitioners, systems developers, and standards bodies across Federal, State, Local, Tribal, Territorial, International and Private organizations. NIEM has been identified as a key enabler for Joint All Domain Command and Control (JADC2) . NIEM is cited in

3680-538: The Web site will expand as the hub for these supplemental resources. NIEM adopts standard XML schema constructs and methods, such as roles, associations, and augmentation from industry standards, such as the World Wide Web Consortium (W3C) XML Schema language. The NIEM reference schemas are a set of interrelated schemas that define NIEM data components. Each schema defines its own target namespace. Schemas in

3760-405: The above must be either specified in a different way or omitted altogether. RELAX NG allows attributes to be treated as elements in content models. In particular, this means that one can provide the following: This block states that the element "some_element" must have an attribute named "has_name". This attribute can only take true or false as values, and if it is true, the first child element of

3840-424: The absence of its schema, even if the document would validate against that schema. In effect, all users of such an XML document must also implement the W3C XML Schema specification, thus ruling out minimalist or older XML parsers. It can also slow down the processing of the document, as the processor must potentially download and process a second XML file (the schema); however, a schema would normally then be cached, so

3920-504: The audience. A selection of online materials are also available both from the main NIEM.gov web site and resources such as Youtube.com (search on NIEM training). The NIEM Web site serves as a primary means by which NIEM can provide the latest documentation and downloads to those interested in NIEM. It also serves as a starting point for those wishing to contact NIEM staff with questions, support, and information requests. As related projects, tools, and support resources develop around NIEM,

4000-453: The basic structure of a document, that is, which elements can go where, results in a very verbose schema. The typical way to solve this is to combine Schematron with RELAX NG or W3C XML Schema. There are several schema processors available for both languages that support this combined form. This allows Schematron rules to specify additional constraints to the structure defined by W3C XML Schema or RELAX NG. Schematron's reference implementation

4080-551: The connection between UCore and DoD 8320.2 "Data Sharing in a Net-Centric Department of Defense," and DoD 8320.2-G "Guidance for Implementing Net-Centric Data Sharing." Within the Department of Defense, the Marine Corps explicitly mandated UCore for certain applications according to U.S. Marine Corps Order 5231.3. While no OPNAV Instruction related to UCore was issued, the Navy accepted a role as DoD lead and served as overall co-lead for

SECTION 50

#1732851047710

4160-444: The cost comes only on the first use. WXS support exists in a number of large XML parsing packages. Xerces and the .NET Framework 's Base Class Library both provide support for WXS validation. RELAX NG provides for most of the advantages that W3C XML Schema does over DTDs. While the language of RELAX NG can be written in XML, it also has an equivalent form that is much more like a DTD, but with greater specifying power. This form

4240-475: The creation of automated enterprise-wide information exchanges which can be uniformly developed, centrally maintained, quickly identified and discovered, and efficiently reused. The following key concepts are essential to understanding the purpose, architecture, processes, and other capabilities of NIEM, as well as to establish a common knowledge base with which to develop the ability to use NIEM effectively. Data Components. The fundamental building block of NIEM

4320-402: The definition of many more. In theory, the lack of a specific list allows a processor to support data types that are very problem-domain specific. Most RELAX NG schemas can be algorithmically converted into W3C XML Schemas and even DTDs (except when using RELAX NG features not supported by those languages, as above). The reverse is not true. As such, RELAX NG can be used as a normative version of

4400-524: The element must be "name", which stores text. If "name" did not need to be the first element, then the choice could be wrapped in an "interleave" element along with other elements. The order of the specification of attributes in RELAX NG has no meaning, so this block need not be the first block in the element definition. W3C XML Schema cannot specify such a dependency between the content of an attribute and child elements. RELAX NG's specification only lists two built-in types (string and token), but it allows for

4480-545: The exchange. The naming and design rules for NIEM are documented in the NIEM NDR , which specifies the data model, XML components, and XML data for use with NIEM and provides a basis for NIEM conformance . The current version is NDR v5.0, which was released on December 18, 2020. NIEM is based on several concepts from the International Organization for Standardization (ISO) 11179 , which provides guidelines for

4560-729: The federal effort. The Space and Naval Warfare Systems Command is providing engineering leadership for Navy UCore initiatives. The March 2009 acceptance of UCore by the Air Force ESC suggested a level of commitment from that service. A letter from U.S. Strategic Command (USSTRATCOM) to the UCore Executive Steering Committee cited USSTRATCOM's sponsorship of UCore from UCore 1.0 through a UCore pilot completed in 2006. The Universal Core Working Group chartered in April 2007 included DoD lead representative Daniel Green. Green discussed

4640-612: The form of the data represented. These terms have been derived from ISO 11179 representation terms, and include Amount, Code, Date, Time, Indicator, Measure, Name, Numeric, Percent, Picture, Quantity, Rate, and Time. Qualifier Term: The object class and property terms can have qualifiers; i.e., a word or words that help define and differentiate the element name. The NIEM technical modeling and schema concepts and mechanisms which support building new data components that meet specific requirements and reusing existing NIEM data components are briefly described below. More detail can be found in

4720-408: The foundational building blocks of a custom Community of Interest (COI) vocabulary or information exchange specification. Developers who reuse the designated UCore types are expected to gain a minimum level of understandability and interoperability. UCore 3.0 also defines a message format for Situational Awareness (SA) messages, which report upon the time and location of entities and events, often with

4800-665: The goals and challenges of the Group in a 2008 Masters thesis for the Naval Postgraduate School. While Green remained with the project through the release of UCore 2.0 in April 2009, the thesis offers additional insight into UCore tradeoffs, challenges to technical adoption, and strategies adopted to cultivate involvement of various intelligence agencies. UCORE-SL was an effort sponsored by the US Army Net-Centric Data Strategy Center of Excellence to augment

4880-409: The individual arrested (i.e., the person component described above) but also information about the person's alleged offense, the location of the offense, the arresting officer, etc. The IEP represents a set of data that is actually transmitted between agencies for a specific business purpose (e.g., initiating a charging document by the local prosecutor). It includes the actual XML instance that delivers

SECTION 60

#1732851047710

4960-846: The most widely supported schema language for XML. Because DTDs are one of the earliest schema languages for XML, defined before XML even had namespace support, they are widely supported. Internal DTDs are often supported in XML processors; external DTDs are less often supported, but only slightly. Most large XML parsers, ones that support multiple XML technologies, will provide support for DTDs as well. Features available in XSD that are missing from DTDs include: XSD schemas are conventionally written as XML documents, so familiar editing and transformation tools can be used. As well as validation, XSD allows XML instances to be annotated with type information (the Post-Schema-Validation Infoset (PSVI) ) which

5040-479: The namespace of that element. This XML format is schema-language agnostic and works for just about any schema language. Capitalization in the schema word: there is some confusion as to when to use the capitalized spelling "Schema" and when to use the lowercase spelling. The lowercase form is a generic term and may refer to any type of schema, including DTD, XML Schema (aka XSD), RELAX NG, or others, and should always be written using lowercase except when appearing at

5120-464: The naming and definition of data elements, as well as information about the metadata captured about data elements. Part 5 of the ISO 11179 standard establishes a methodology for naming items in data dictionaries. The ISO 11179-based NIEM NDR naming convention uses object class, property, and representation terms to constitute a multiple-part name as shown in the figure below: Object Class Term: Represents

5200-523: The nature of their business or the operational context of their exchanges, provided they are semantically consistent. Information Exchange Package Documentation. The information that is commonly or universally exchanged between participating domains can be organized into information exchange packages (IEPs) in the form of XML Schemas. An example of this collection of information is data associated with an arrest. The data to be exchanged includes not only descriptive and personal identification data regarding

5280-405: The object to which the property is applicable. In NIEM, we interpret that object to be the real-world object. (An object class refers to a group of objects that share the same attributes, operations, methods, relationships, and semantics.) Property Term: Identifies the property that the data element represents (e.g., last name, expiration date, height, total). Representation Term: Describes

5360-408: The order of elements, Boolean predicates that the content must satisfy, data types governing the content of elements and attributes, and more specialized rules such as uniqueness and referential integrity constraints. There are languages developed specifically to express XML schemas. The document type definition (DTD) language, which is native to the XML specification, is a schema language that

5440-608: The payload or information. Additional information regarding this specific exchange can be further documented in the form of an information exchange package documentation ( IEPD ), which also contains data describing the structure, content, and other artifacts of the information exchange. An IEPD supports a specific set of business requirements in an operational setting. NIEM Core. Data components within an information exchange that are universally shared and understood among all (or almost all) domains are identified as universal components (e.g., person, address, and organization). To become

5520-679: The pedigree or source (when reported, who reported, how reliable, etc.) of instance data to any data component of the model (type or object, property, association, role, or augmentation) in any namespace. It allows sets of metadata to be extended with additional properties for local requirements and enables metadata properties to be repeated. NIEM has introduced the concept of Enterprise Information Exchange Model (EIEM) dictionaries to allow NIEM implementers to position local collections of components specific to their own enterprise. Typically these may be drawn from an Enterprise Data Model (EDM) and then exported and refactored as XML components that conform to

5600-431: The property, RoleOf, which references the vehicle instance used as the weapon. The WeaponType (the role) might also contain properties that describe the persons and activities involved, dates and times of involvement, and how the entity was used as a weapon. An association type is an object that represents a relationship between data components. For example, two PersonType instances, Abigail and Bob, could be referenced by

5680-460: The reference set may import one another by namespace in order to use (or reuse) components they define. In general, domain reference schemas import schemas from the Core. The NIEM reference schema set represents the full set of data components in NIEM. The following kinds of XML schemas are associated with the NIEM architecture: The only mandatory schemas for validation are the NIEM reference schemas or

5760-402: The schema, and the user can convert it to other forms for tools that do not support RELAX NG. Most of RELAX NG's disadvantages are covered under the section on W3C XML Schema's advantages over RELAX NG. Though RELAX NG's ability to support user-defined data types is useful, it comes at the disadvantage of only having two data types that the user can rely upon. Which, in theory, means that using

5840-520: The special condition language contained in the grant, and follow the associated NIEM implementation guidelines. The NIEM Management Office (NMO) operates to: NIEM is a continually evolving program, and new agencies and COIs are joining the effort all the time. As new stakeholders come on board, they need to receive information to gain understanding and knowledge of the core capabilities of NIEM and how to engage in NIE information exchanges. In 2022, NIEM created

5920-653: The start of a sentence. The form "Schema" (capitalized) in common use in the XML community always refers to W3C XML Schema . The focus of the schema definition is structure and some semantics of documents. However, schema design, just like design of databases, computer program, and other formal constructs, also involve many considerations of style, convention, and readability. Extensive discussions of schema design issues can be found in (for example) Maler (1995) and DeRose (1997). Languages: NIEM NIEMOpen ( neemopen ), frequently referred to as NIEM, originated as an XML -based information exchange framework from

6000-437: The subclass derived from the base class inherits the properties of the more general base or parent class. This mechanism is used to share or reuse properties between the general data component and its specialization. For example, a vehicle type (or class) is identified as a data component with properties of vehicle identification number (VIN), make, and model. Truck type (or class) is a specialization of vehicle and thus inherits

6080-402: The substitution of new XML Schema elements, representing derived NIEM properties that can be used where the parent properties are expected. There are three XML Schema techniques that support the NIEM use of element substitutions: In addition to adding new NIEM types and properties to NIEM, it is possible to adapt existing external (non-NIEM) namespaces for use in the NIEM framework. This allows

6160-469: The use of external standards within NIEM IEPDs, without requiring that the external standards themselves be NIEM-conformant. The intent here is to allow use of external standard components exactly as they were defined. Metadata , or data about data, defines information that supports the actual content of XML instances. The metadata feature provides a mechanism for attaching structured properties that describe

6240-478: The user to test NIEM XML schemas against the automated rules from the NIEM Naming and Design Rules (NDR) . This is an important first step in verifying NIEM conformance . Users can upload a single NIEM XML schema or a zip file (typically representing an IEPD) and view or download the results as a conformance report. Movement enables the user to search and explore the content of the latest NIEM release. It provides

6320-414: The vehicle's properties but also has its own characteristic properties, such as truck bed length. Specialization is time independent and is generally used only when the base class and subclass always exist. A role is a special type which represents a particular function, purpose, context, or activity for an entity. Roles are generally time dependent and, therefore, temporary. A new type can be created for

6400-732: Was the Technical Agent for UCore, working on behalf of the DoD Chief Information Officer (DoD CIO) to create and support UCore 3.0. UCore Version 3.0 was released on 14 April 2012 and contains modifications approved by the UCore Council and enacted by the UCore Technical Working Group. In this release, UCore is a set of reusable data components (RDCs) for the four interrogatives, an entity-to-entity relationship model, and supporting metadata types. These RDCs can be

#709290