Information Exchange Packaging Policy Vocabulary (IEPPV) assigns To specify additional rules or restrictions to an information element. Derived from: to fix or specify in correspondence or relationship, http://www.merriam-webster.com/dictionary/assign. comprises to be made up of (something), to include or consist of (something) Source: http://www.merriam-webster.com/dictionary/comprise contains To have within a larger container concept. Derived from: to have (something) inside, to have or include (something). http://www.merriam-webster.com/dictionary/contain encloses to surround (something), to put something around (something), to include along with something else in a parcel or envelope. Source: http://www.merriam-webster.com/dictionary/enclose governs to control or direct actions to be taken in the processing of information. Derived from: to control the way that (something) is done, to control or guide the actions of (someone or something), http://www.merriam-webster.com/dictionary/govern governs the formatting of to control or direct actions to be taken in the formatting of information. governs the release of to control or direct actions to be taken during the release of information. governs the rendering of to control or direct actions to be taken in the rendering of information for presentation or visualization. includes to make (someone or something) a part of something, to take in or comprise as a part of a whole or group. Source: http://www.merriam-webster.com/dictionary/include owns to have (something) as property, to legally possess (something). Source: http://www.merriam-webster.com/dictionary/own produces To generate, compute or produce a transformation of attributes and generate a result. Derived from: to make (something) especially by using machines, to cause (something) to exist or happen, to cause (a particular result or effect), http://www.merriam-webster.com/dictionary/produce references To identify an association between one element and another. Derived from: to mention (something or someone) in speech or in writing, to refer to (something or someone). http://www.merriam-webster.com/dictionary/references Note: Although minimum cardinality is identified as 1 in some uses of this property, in some environments the reference infers the existence of Unique / or Globally Unique identifier or keyed relationship between the concepts.  (e.g., foreign key relationships in between tables in a relational construct). restricts to confine within bounds. Source: http://www.merriam-webster.com/dictionary/restricts results in an effect generated through the execution of a process, procedure, or rules. Derived from http://www.merriam-webster.com/dictionary/results: to proceed or arise as a consequence, effect, or conclusion specifies To explicitly state the policies, rules and instructions for generating a specific output. Derived from http://www.merriam-webster.com/dictionary/specify: to name or state explicitly or in detail, to include as an item in a specification acknowledge instruction An instruction to the recipient of an information exchange directing the issuance of an acknowledgment to the receipt of the information to the provider of the information. action instruction An instruction directing the producer or receiver of a message to take a specific action, (1) message specific rules governing the release of the information, or (2) message specific actions to be taken upon receipt of the message. attachment element A binary file or (e.g., PDF file, image or video) or document, and information about the binary or document, such as the size and type and description. Source: Logical Entity Exchange Specification (LEXS): Attachment (N): A binary, such as an image or PDF file or video, as well as information about the binary, such as the size and type and description. attachment formatting instruction An instruction to the provider of information defining the rules for formatting the data set in accordance with the agreed protocol for the exchange. attachment rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying an attachment or set of attachments. attachment semantic A Semantic that specifies the rules for assembling the attachments to a message. It also provides the rules for generating an attachment summary and linkages. attachment specification A specification of the rules governing attachment of binary information elements to an information exchange or message. attachment summary A summary or list of attachments for a specific data package. attachment summary rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying an attachment summary. attribute A defined property of an entity, object, triple, schema, etc. Source: A Dictionary of Computing. Oxford University Press, 2008. Oxford Reference Online. Oxford University Press. binary data rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying binary data. container A receptical for results of an aggregation of data and information elements. Derived from http://www.merriam-webster.com/dictionary/container, a receptacle (as a box or jar) for holding goods. data creator metadata Metadata tags and markings that identify the creator of data or information elements. data element Representation of information (data) in a formalized manner suitable for communication, interpretation, or processing by humans or by automated means. In the context of IEPPV, data elements are atomic facts. Derived from UPDM. data owner metadata Tags and markings that identify the owner or steward of the data or information elements. digest An information structure, format and syntax common to all communities. It provides the ability for systems to handle heterogeneous data without having to understand the specific context and or semantics of the source. As long as the entities relevant to the packaged data items are represented in the Digest, users will be able to discover, link, map, etc. the information within. Source: the concept for digest is derived from and intended to support the Logical Entity eXchange Specification (LEXS). http://130.207.211.107/content/lexs-overview. The Digest provides the common level of understanding, it does not mean that all sources have to populate all elements, or that all consumers have to use all elements; merely that at a schema level all applications understand the Digest. Implementers only need to build one module in order to produce or consume a basic set of data understandable by many. It also means that implementers do not have to develop large applications for each exchange, but rather build one that handles the basics and then additional smaller modules in order to produce or consume more complex exchanges. The objective of the Digest is to present the most common characteristics of real-world objects that can be supported by any data source or data consumer. Digest-level data objects may be further augmented or described with additional details in included packages or narrative text integrated into the message. The information in the digest must be semantically complete for both the data source or data consumer; the information package contents may rely on the digest to complete its semantics. The enforcement of a "Digest Semantic" by a software service will result in the generation of the digest for the instance of the Information Package. In other applications, where the digest is not used, the "Payload" comprises the entire data portion of the message content. digest formatting instruction An instruction to the provider of information specifying the rules for formatting the data set for a Digest in accordance with the agreed protocol for the exchange. digest semantic A SemanticElement that specifies the rules for assembling data and information elements for a Digest. digest specification A specification and set of rules governing the preparation (generation) of a digest. discard instruction An instruction to the recipient of an information exchange specifying the rules for destruction or discarding of data included within an information package or message. distribution specification A specification of the rules governing the assignment of InformationElements to a specific information dissemination service (e.g., User Application, Service Interface and Middleware). do not forward instruction An instruction to the recipient of an information exchange specifying that the information must not be forwarded to any other recipient or destination. do not persist instruction An instruction to the recipient of an information exchange directing the recipient not to persist any of the information or data in a payload or message. dynamic filter Rules for a data or domain filter whose parameters may be configured at run-time. enclosed transactional element A TransactionalElement included as part of the build pattern of a TransactionalElement or SemanticElement. enclosing transactional element A TransactionalElement that includes one or more TransactionalElements or WrapperElements. encryption instruction An instruction or set of instructions to the producer of the information directing that the message or elements of the message need to be encrypted prior to release. entity Independent, separate, or self-contained existence. Source: Merriam-Webster Dictionary. file A collection of information, referred to by file name; for example, a user-created document, program data, or the program itself. With a program, the information is held on backing store (i.e. usually on magnetic disk) in order (a) to enable it to persist beyond the time of execution of a single job and/or (b) to overcome space limitations in main memory. Files with a very brief existence (i.e. in case (b) above, or where they simply carry information between one job and the next in sequence) are called work files. See also master file, data file. Source: A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. filter A profile or script containing the rules to restrict the assembly of data or information elements. Source: Defined for the Information Exchange Policy Vocabulary. Derived from "A general term used to describe software which examines some content and prevents it from reaching its destination, based on a number of rules stored in a script or a profile." A Dictionary of the Internet. Darrel Ince. Oxford University Press, 2009. Oxford Reference Online. Filter Rule A rule or rules governing the inclusion of or rejection of data or information elements based on the value of a specified attribute, or values of specified attributes. filtered semantic element Specifies rules for the assignment of one or more DynamicFilters to a specified SemanticElement. Source: Derived from SOPES IEDM V1. filtered transactional element Rules specifying the WrapperAttributes that are filterable at runtime. formatting instruction An instruction to the provider of information defining the rules for formatting a generated data set. forward instruction An instruction to the recipient of an information exchange to forward the information to authorized recipients in accordance with any provided list, or in accordance with specified information sharing agreements. handling instruction An instruction to the recipient of an information exchange specifying how this information must be handled. identifier Identifies the element (TransactionalElement or WrapperElement) that holds a unique identifier or key needed for the construction of a data set. This subtended class would contain, as a minimum, the base global unique identifier (e.g., database key, foreign keys or unique identifier) that would differentiate which Transactional or Wrapper instance (information element instances) is included in the construction of the composite. (e.g., foreign key relationships) There exists one and only one identifier for each SemanticElement or TransactionalElement. Source: Derived from UML Profile for DODAF and MODAF (UPDM) V2.0, formal/2012-01-03 and Shared Operational Picture Exchange Services (SOPES) Information Exchange Data Model (IEDM) Version 1.0, formal/2011-05-04 information element An item of information that flows between operational activities and nodes. For IEPPV, an information element refers to a grouping of data elements (including other information elements) providing meaning within the context of an operation or situation. Derived from: MODAF: A formalized representation of information subject to an operational process. DoDAF: Information that is passed from one operational node to another. Associated with an information element are such performance attributes as timeliness, quality, and quantity values. (DoDAF) Information Exchange: The collection of information elements and their performance attributes such as timeliness, quality, and quantity values. (DoDAF). Note: Within the architectural context of the UPDM, SOPES and IEPPV, the Information element provides a description of, or specification for, the data or information processed or exchanged. The Information element does not refer to the instance data or information being processed or exchanged, as this can only be determined at run-time. information exchange specification Specifies the information elements shared as part of a specific information sharing agreement and the information dissemination services to be used. information package A standard representation of structured, semi-structured and binary information applicable to an information sharing agreement. Packages may contain metadata, a Digest, a Structured Payload, Rendering Instructions, and optional linkages depending on the established agreements. information package formatting instruction An instruction to the provider of information defining rules for formatting the elements of a Data Package in accordance with the agreed protocol for the exchange. information package metadata Tags and markings that identify and describe the contents of an information package. information package metadata formatting instruction An instruction to the provider of information defining the rules for formatting the Data Package Metadata in accordance with the agreed protocol for the exchange. information package metadata semantic A SemanticElement that specifies the rules for assembling the data elements to be included within Information Package Metadata. information package release instruction An instruction to the producer of an information exchange specifying instructions (e.g., Encrypt) pertaining to the release of the information package or message. information package rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying an Information Package. information package specification The rules and constraints governing the construction preparation of an information or data package. information payload A formatted dataset without protocols and metadata required for an information exchange. Derived from: Body (payload) The part of a cell or packet in a network that holds the information supplied by the end-user for transmission from the sender to the receiver. A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. Data Payload: Refers to the "actual data" in a packet or file minus all headers attached for transport and minus all descriptive meta-data. In a network packet, headers are appended to the payload for transport and then discarded at their destination. In a key-length-value structure, the key and length are descriptive data about the value (the payload) http://www.pcmag.com/encyclopedia_term/0,1237,t=payload&i=48909,00.asp information payload formatting instruction An instruction to the provider of information defining the rules for formatting the information payload in accordance with the agreed protocol for the information exchange. information payload specification The rules governing the assembly and processing of a structured dataset for an information exchange. information specification Specifies the InformationElements that are included as part of the Information Exchange Agreement. Source: Defined for the Information Exchange Packaging Policy Vocabulary. Instruction The description of an operation that is to be performed by a computer or human operator. Derived from: "The description of an operation that is to be performed by a computer. It consists of a statement of an operation to be performed and some method of specifying the operands (or their locations) and the disposition of the result of the operation." A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. message A formatted InformationElement transferred by a message switching system (or Network). Messages may be of any length, from a few bits to a complete file, and no part of a message is released to its final recipient until all of the message has been received at the network node adjacent to the destination. Source: A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. message element An identifiable part of a message structure containing contextually relevant data or information elements. Message elements are integrated and formatted in accordance with contract or information exchange specification rules and instructions prior to release. message formatting instruction An instruction to the provider of information defining the rules for formatting the elements of a Message in accordance with the agreed protocol for the exchange. message metadata Set of tags and markings (including their established Values) that describe the content of a message. message metadata formatting instruction An instruction to the provider of information defining the rules for formatting the elements of MessageMetadata in accordance with the agreed protocol for the exchange. message metadata rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying message metadata. message metadata specification The rules governing the assembly of message metadata. message rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying a message. message sensitivity Metadata Tag or marking that provides an indication of the sensitivity of the information with reference to privacy, confidentiality or security. structured message specification Specifies the rules and constraints governing the assembly of a community compliant structured or semi-structured message in accordance with a specified message protocol. (e.g., LEXS, EDXL-DE and ATOM). message time stamp Metadata Tag indicating when the Message was created. message type Metadata tag that identifies the type of message being exchanged. metadata Data (tags and markings) which describes other data. Source: A Dictionary of the Internet. Darrel Ince. Oxford University Press, 2009. Oxford Reference Online. Oxford University Press. metadata rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying metadata. metadata semantic A SemanticElement that specifies the rules for assembling the metadata elements. metadata specification The rules governing the assembly of metadata to be attached to a message, package,or information elements of an exchange covered by the contract. narrative text Identifies the location and rules for attaching a narrative of free text field to a message or package of information elements. package metadata specification The rules governing the assembly of metadata and tags for an information package. participant A List of entities to produce or receive the information or message. DODAF: Any entity - human, automated, or any aggregation of human and or automated - that participates in an information exchange agreement. persist instruction An instruction to the recipient of an information exchange indicating that the information may be persisted in local stores. privacy metadata Tags and or markings that support the enforcement of privacy policy. publish metadata Tags and markings that support the publishing of sharable information to a data registry, repository or publication-subscription middleware infrastructure. This metadata provides the structures required to represent the data as well as that associated with publishing and storage of data. The data registry, repository or middleware receives and records the published metadata in a manner for users and systems to discover the associated information elements. Derived from: Logical Entity Exchange Specifications 4.0 (LEXS) User Guide ( http://130.207.211.107/sites/all/lexs/docs/lexs-4.0/LEXS_4_UserGuide%209-27-2011.pdf). quality of service instruction An instruction or set of instructions to the producer or publisher of the information specifying the quality of services requirements for the exchange of the information. receipt instruction An instruction to the recipient of an information exchange to perform a particular, operation, or multiple operations, upon the receipt of that information. releaseable data set The assembly of data elements resulting from the enforcement of rules enclosed by a SemanticElement or FilteredSemanticElement. release instruction An instruction or set of instructions to the producer or publisher of the information specifying actions to be taken prior to the release of the information. (e.g., Encryption requirements). rendering instruction An instruction or set of instructions to the receiver of information describing the rules for rendering or displaying the information. retention instruction An instruction to the recipient of an information exchange defining the rules regarding the allowable persistence of the information. retrieval metadata Tags and markings included in a message or information package that assists in the retrieval of that information. safeguard Policies, rules, services and technologies that serve to guard or protect data and information elements from malicious or inadvertent release of sensitive or protected information. Derived from http://www.thefreedictionary.com/safeguard, one that serves as protection or a guard. search metadata Refers to metadata that broadly identifies the information elements being sought and results in a response that returns possible candidates for the user to examine further. This metadata provides the characteristics of a query to the registry, repository or publication-subscription infrastructure that responds with information pertaining to the sharable information elements, topics or channels that can be accessed. The response provides the information needed to request specific information elements, topic or channel subscription. The intent is that the requesting entity can narrow the search by reviewing the search response and then request more detailed information on a specific information element, topic, or channel. Depending on the implementation, metadata could include a text-string and request for a text search on unstructured data in a registry or repository (e.g., report), or on structured data, such as a name, attachment or narrative element. A data item metadata search looks for one or more information elements containing information matching the criteria described in the SearchMetadata. Derived from Logical Entity Exchange Specifications 4.0 (LEXS) User Guide ( http://130.207.211.107/sites/all/lexs/docs/lexs-4.0/LEXS_4_UserGuide%209-27-2011.pdf). security filter A specialization of a filter that provides the rules that restrict the assembly of data and information elements based on the values of a security tag or label. security metadata Tags and markings that assist in the enforcement of security policy and malicious or inadvertent release of classified information to unauthorized recipients. security policy A set of objectives, rules of behavior for users and administrators, and requirements for the configuration, operation and management of computer systems to enhance the security of organization or enterprise people, operations and systems. Note: This specification is focused on the specification of policies and rules for the packaging and release of information for authorized recipients. A Security Policy might include sections on: 1. Virus detection and prevention; 2. Firewall use and configuration; 3. Password strength and management; 4. Host System administration practices; 5. Access Control rules; 6. Use of Access Logs; 7. Use of screen locking software; 8. Logging out of unattended workstations; 9. Physical security; 10. Account termination; and 11. Procedures for granting and revoking system access. semantic attribute An attribute assigned to a semantic element. Derived from UPDM. semantc element Composite of rules governing the assembly of data elements in accordance with commitments defined by an information exchange agreement and policies pertaining to the safeguarding of sensitive information. Derived from SOPES IEDM V1: Semantic. session The software connection to the information dissemination services to be used for the exchange of information under the informationExchangeSpecification. Derived from the Seven Layer Reference Model: 1. Session Layer - Identifies the service of binding two presentation service entities together logically and controls the dialogue between them as far as message synchronization is concerned; and 2. Presentation Layer - Provides a set of services that may be selected by the application to enable it to interpret the meaning of the data exchanges. Such services include management of the entity exchange, display and control of the structured data. The presentation layer is the heart of the seven layer proposal, enabling disparate terminal and computer equipment to intercommunicate. A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. Oxford University Press. session specification Specifies the rules governing communications between the data services and information distribution services (or middleware). source data Raw data (sometimes called source data or atomic data) is data that has not been processed for use. A distinction is sometimes made between data and information to the effect that information is the end product of data processing. Source: http://searchdatamanagement.techtarget.com/definition/raw-data. specification A detailed precise presentation of something. Within the context of the IEPPV, a detailed and precise presentation of rules governing the assembly or processing of information elements. Derived from http://www.merriam-webster.com/dictionary/specification: a detailed precise presentation of something or of a plan or proposal for something. static filter A filter created at design-time that cannot be modified at run-time. structured data rendering instruction An instruction to the recipient of an information exchange defining the rules for rendering or displaying structured data. submitter metadata Tags and markings identifying the submitter of the information. subtended element An Element (TransactionalElement or WrapperElement) forming part of another element (TransactionalElement or SemanticElement). Wrapper is always a subtended information element since it cannot exist outside of a TransactionaElement definition. subtended attribute An attribute assigned to a SubtendedElement. subtended transactional A TransactionalElement included as part of another TransactionalElement or SemanticElement. aka Supporting Transactional. table A collection of records. Each record may store information associated with a key by which specific records are found, or the records may be arranged in an array so that the index is the key. In commercial applications the word table is often used as a synonym for matrix or array. Source: A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. Oxford University Press. time stamp A tag or mark indicating the time when the message was created. transactional attribute An attribute assigned to a TransactionalElement. Derived from UPDM. transactional element Specifies a reusable pattern comprising rules governing the assembly and processing of data and information elements. Derived from SOPES IEDM V1: Transactional. transformation The conversion of data from one form to another. In this instance the specification of rules governing the conversion or transformation of data. Source: A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. Oxford University Press. transformation resulting attribute An attribute resulting from a transformationElement. triple An RDF triple consists of three components: - the subject, which is an IRI or a blank node; - the predicate, which is an IRI; and - the object, which is an IRI, a literal or a blank node. An RDF triple is conventionally written in the order subject, predicate, object. Source:  http://www.w3.org/TR/2013/CR-rdf11-concepts-20131105/#section-triples tuple An ordered set with an unspecified but finite number (n) of elements. Source: A Dictionary of Computing. Ed John Daintith and Edmund Wright. Oxford University Press, 2008. Oxford Reference Online. validate instruction An instruction to the recipient of an information exchange containing criteria for the validation of the content and semantics of the message or information payload. watch point A trigger mechanism used by an application to commence the assembly of a TransactionalElement. A data model assigns this tagged value to a WrapperElement aggregation arc in the Transactional pattern. Additions to the underlying data store for this WrapperElement triggers the application to start building the composite. Derived from SOPES IEDM V1: Wrapper watch point transactional A TransactionalElement with an associated Watchpoint data event that triggers the assembly of an enclosing TransactionalElements and SemanticElements. Source: Derived from SOPES IEDM V1. wtaqpper attribute An attribute assigned to a WrapperElement. Source: derived from UPDM. wrapper A logical construct that wraps or encapsulates the definition of a data set, table entity, triple, file, etc. A Wrapper directly maps to a data instance (e.g., row of data in a database application) in the logical data model and the physical data model. Derived from Derived from SOPES IEDM V1: Wrapper. 1 0 0 1 1 1 0 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 0 1 1 1 1 1 1 1 1 1 1 0 1 0 1 1 1 1 1 1 1 1 Copyright (c) 2012-2014 Object Management Group Copyright (c) 2012-2014 Advanced Systems Management Group LTD Copyright (c) 2012-2014 Thematix Partners LLC http://www.omg.org/techprocess/ab/SpecificationMetadata/MITLicense ieppv.rdf ief-ieppv http://www.omg.org/spec/IEF/IEPPV/20131101/IEPPV1-0/ The http://www.omg.org/spec/IEF/IEPPV/20131101/IEPPV1-0.rdf version of this ontology was modified per the issue resolutions identified in the IEPPV 1.0 FTF report. http://www.omg.org/spec/ODM/ http://www.w3.org/standards/techs/owl#w3c_all