Now includes the manifest - aggregation relation Copyright Notice: Copyright © 2012 by  IEEE.  All rights reserved. The IEEE  grants a general, royalty-free license to copy, distribute, display and make derivative works from this material, for all purposes, provided that any use of the material contains the following attribution: "Reproduced with permission from IEEE Std 1484.13.1 "Standard for Learning Technology - Conceptual Model for Resource Aggregation for Learning, Education, and Training". Warning: This ontology file accompanies the approved version of IEEE Std 1484.13.1 and reflects the content of the standard at the time of approval. This and other ontology files it references may reflect approved or draft editions or be subject to amendment. As such, this ontology file is subject to change. USE AT YOUR OWN RISK! Should you require additional information, contact the Manager, Standards Intellectual Property, IEEE Standards Association (stds-ipr@ieee.org). Use of this ontology file: This ontology file accompanies IEEE Std 1484.13.1, “Standard for Learning Technology - Conceptual Model for Resource Aggregation for Learning, Education, and Training".  This ontology file is provided on an informative basis.   This ontology file is a World Wide Web Consortium (W3C) Resource Description Framework/Extensible Markup Language (RDF/XML) representation of the Web Ontology Language (OWL) binding of the conceptual model defined in IEEE Std 1484.13.1. This ontology file is informative. This ontology file contains URIs which resolve to the latest version of the ontology files for the core ontology standard and each of the mapping recommended practices. If a specific version of a particular ontology file is required, the RAMLET core ontology file should be associated with the URI of that specific version. A registry of ontology file versions and URIs can be found at the following URI:https://mentor.ieee.org/ramlet/bp/RAMLET_URI_Registry. Notice and Disclaimer of Liability Concerning the Use of IEEE Documents: IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained in its standards. Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon any IEEE Standard document. The IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained in its standards is free from patent infringement. IEEE Standards documents are supplied "AS IS." The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation, or at least every ten years for stabilization. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. In publishing and making its standards available, the IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards documents represent a consensus of concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE. Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Comments on standards and requests for interpretations should be submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Laws & Regulations: Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights: IEEE Standards documents are copyrighted by the IEEE. They are made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making these document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to the documents. Updating of IEEE Documents: Users of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE Standards Association website at standards.ieee.org, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA website at standards.ieee.org. Errata: Errata, if any, for all IEEE standards can be accessed at the following URL: http://standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations: Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/index.html. Patents: IEEE Standards are developed in compliance with the IEEE Standards patent policy, which can be accessed at the following URL: http://standards.ieee.org/board/pat/index.html. IMPORTANT NOTICE: IEEE Standards documents are not intended to assure safety, security, health, or environmental protection in all circumstances. Implementers of IEEE Standards documents are responsible for determining appropriate safety, security, environmental, and health practices or regulatory requirements. Approved Version 1 Copyright Notice: Portions of this software may use RDF schemas Copyright © 2011 DCMI, the Dublin Core Metadata Initiative [http://dublincore.org/]. These are licensed under the Creative Commons 3.0 Attribution license.[http://creativecommons.org/licenses/by/3.0/] Version Mapped: XML Linking Language (XLink) Version 1.0, W3C Recommendation 27 June 2001; http://www.w3.org/TR/2001/REC-xlink-20010627/ The W3C Xlink specification is used by a number of resource aggregation formats to add hyperlink features to resource aggregations. Because it is already a shared vocabulary, there is no need to map it to a new, shared representation in the RAMLET core ontology. At the time of writing, however, there appears to be no expression of the XLink datamodel in OWL, which would limit the implementability of RAMLET. For that reason, the RAMLET working group have modelled XLink in OWL, and made it available with the standard. Scope note: A related resource that is included either physically or logically in the described resource. Scope note: A related resource in which the described resource is physically or logically included. Scope note: Expresses the fact that the associated component describes another component. Scope note: A hierarchical relationship between two components. The component with the includes property is the parent of the other component, known as the child. This property describes a purely syntactic relationship between components; it does not imply a refinement relationship. This property is a refinement of the Dublin Core relation metadata term. The relation metadata element defined by IEEE Std 1484.12.1-2002 is semantically equivalent to Dublin Core's relation metadata term. Scope note: Expresses the fact that the associated component describes another component. Scope note: A hierarchical relationship between two components. The component with the isIncludedBy property is the child of the other component, known as the parent. This property describes a purely syntactic relationship between components; it does not imply a refinement relationship. Scope note: The inverse of the references property. Scope note: An arbitrary association between components signaled by an identifier reference to an identifier elsewhere. The component with the references property carries the reference to an identifier or identifiers of one or more other components. This property is a refinement of the Dublin Core relation metadata term. The relation metadata element defined by IEEE Std 1484.12.1-2002 is semantically equivalent to Dublin Core’s relation metadata term. Definition: See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI Definition: See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#string Definition: See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#token Scope note: Contains information about the management of digital resources in an aggregation instance. Scope note: A locator that associates administrative metadata with a digital resource or groups of digital resources that share the administrative metadata. (See: locator.) Scope note: An identifier for an aggregation instance as a whole. Generally, the aggregationID is used by external systems. Scope note: An identifying string for a formal schema binding of an aggregation format. Scope note: An identifier for the version of a formal schema binding of an aggregation format. Scope note: The category of an aggregation instance, e.g., IMS-CP or METS. Scope note: An identifying string by which an associated component is known in another system. Scope note: Locates a resourceGroup that has different media accessibility properties from the resourceGroup that includes the altResourceRef. (See: resourceGroup.) Scope note: Contains components that identify and describe a portion of or location within a digital resource, e.g., a specific point in time in an audio file, or a shape within a larger image. Scope note: The unit of measurement used by an anchor, e.g., time or byte. (See: anchor.) Scope note: Defines a full or partially configured state of a choice by asserting true or false values for some number of predicate tests associated with the selections for that choice. If no assertion is made, the choice is undecided. For example, an assertion could be used to 'save' a configuration within an aggregation definition document. The assertion would target the format choice and might assert true for the predicate test of the MPEG-1 Audio Layer 3 (MP3) selection so that the MP3 component is selected by default. (See: choice, true, false.) Scope note: Indicates at what point within a digital resource an anchor starts. (See: anchor.) Scope note: Elements that define a label for an order sequence, e.g., 'I', 'a)' or '1'. Scope note: A value used to ensure the integrity of a digital resource after the resource has been stored or transmitted. Scope note: The algorithm used to calculate the checksum of a digital resource, e.g., CRC-32-IEEE-802.3 or MD5. Scope note: Contains components of a dynamicStructure that identify members of a set of selection(s) that enable a processing application to choose among options for processing a digital resource. (See: dynamicStructure, selection.) Scope note: An anchor that identifies or describes a portion of a resource dynamically at runtime, e.g., via an XML Path Language (XPath) expression that is encapsulated in a Uniform Resource Locator (URL). (See: anchor.) Scope note: A logical condition. In a particular aggregation instance, it denotes that its parent component is conditional on a set of predicate tests (see the example of choice). The require component lists the set of predicate tests that must become true and the except component lists the set of predicate tests that must become false in order for the condition to be satisfied. Each predicate test is identified by the value of the dynamicStructureId included in a selection. (See: choice, dynamicStructureId, except, require, selection.) Scope note: The boundaries of the shape of an anchor. Typically, this class is used with shapeIndicator, e.g., to define a region within an image. (See: anchor, shapeIndicator.) Scope note: A recognized creation date related to a digital resource or an aggregation instance, e.g., the date a digital resource was made available in a system or when an aggregation instance was created. Scope note: The dynamicStructureId(s) associated with a selection that should be chosen by a processing application automatically in the absence of any actively chosen selection(s). (See: dynamicStructureId, selection.) Scope note: Information to support finding, identifying, selecting, and obtaining a digital resource. Scope note: A locator that associates descriptive metadata with digital resources or resource groupings. (See: locator.) Scope note: Information that describes a digital resource for purposes of discovery and identification by a human reader. Scope note: The category for the type of metadata contained in a component, e.g., MARC, LOM, DC. Scope note: Refers to a digital resource contained in an aggregation instance. Scope note: A part of a digital resource described within an aggregation instance. Scope note: Contains the relationships among structureNode(s) in an aggregation instance that depend on factors true only for one state. The state of the relationships depends upon the processing at run time, e.g., the state may change after user interactions. Scope note: Identifies components eligible to be included in a dynamicStructure. (See: dynamicStructure.) Scope note: The category for a dynamicStructure within an aggregation instance, e.g., display behavior or authentication approval. (See: dynamicStructure.) Scope note: A local identifier for a data element in an aggregation instance. Scope note: The encoding method for a digital resource, e.g., an audio track encoded as base64. Scope note: Indicates at what point within a digital resource an anchor ends. (See: anchor.) Scope note: The set of predicate tests that are required to become false in order to satisfy a condition. (See: condition.) Scope note: Measures the sequential or contiguous portion of a digital resource defined by an anchor, e.g., the duration of an audio clip or the coordinates of an area within an image. (See: anchor.) Scope note: Asserts an associated condition to be false. (See: condition.) Scope note: Contains file descriptors relating to a single digital resource, e.g., locators, file size. Scope note: The size of a file or bit stream referenced in an aggregation instance. The expression of the unit of measurement is specified by the mapping. Scope note: Contains a collection of fileDescriptor(s) for a set of functionally related digital resources. (See: fileDescriptor.) Scope note: The tool used to create an aggregation instance. The version of the tool used to create an aggregation instance. Scope note: Associates multiple digital resources into a group by means of a single group identifier. Scope note: A preferred order by sequence for digital resources and/or portions of digital resources within an aggregation instance, e.g., for rendering pages in a book in a preferred sequence. Scope note: A preference by rank for digital resources and/or portions of a digital resource within an aggregation instance. A digital resource or portion thereof may have no rank, the same, or a different rank from another. For example, the beginning of an audio clip may be denoted as the starting point for a whole session. A second point placed at 17 minutes and 30 seconds past the beginning of the audio clip begins a drum solo section within the audio file that is described separately but still included within the aggregation instance. By assigning a high hasRank value to the beginning point of the audio clip and either a lower or no hasRank value to the drum solo, a user interface would display the beginning of the session first when displaying the list of byte streams within the file and make the beginning of the session the default display. 0 Scope note: The category for the human language in which a digital resource is rendered, e.g., en-GB or fr-CA. Scope note: An image that visually identifies an aggregation instance or a digital resource to a user via an appropriate tool, e.g., a logo. Scope note: The category for an identifier used within an aggregation instance, e.g., ISBN or DOI. Scope note: How a digital resource is expected to be used, e.g., as an archival-quality image, thumbnail, or audio sample. Scope note: Contains components that point to a definition of a single behavior or a set of behaviors associated with a digital resource. The definition may be either human or machine readable. Alternatively, interfaceDefLink can point directly to the single behavior or set of behaviors, e.g., a piece of executable code. interfaceDefLink may be embedded within a resourceProcessingSet. (See resourceProcessingSet.) Scope note: Contains resourceIntraAggregationLink(s). (See: resourceIntraAggregationLink.) Scope note: Contains the list of all digital resources included in an aggregation instance. Scope note: A locator for a component within an aggregation definition document. (See: locator.) 0 Identifies a network location of a component or a digital resource and may be used to obtain it. Scope note: Descriptive information about locator(s). (See: locator.) Scope note: The maximum number of selection(s) that are required to be made for a choice to be resolved by a processing application. (See: choice, selection.) 0 The Multipurpose Internet Mail Extension (MIME) type of a digital resource referenced in an aggregation instance, e.g., text/html. Scope note: The minimum number of selection(s) that are required to be made for a choice to be resolved by a processing application. (See: choice, selection.) Scope notes: The last date of modification of one or more associated components. Scope note: An identifier for a structureNode in an external aggregation instance that describes a digital resource. The external aggregation instance that contains the structureNode may use a different aggregation format. For example, nodeId might identify a structureNode denoting an article of a journal that is fully described within an aggregation instance of the journal, but is also included by means of the nodeId as a structureNode within an aggregation instance for a course bibliography. (See: structureNode.) Scope note: Specifies whether a structureNode in an aggregation instance should be rendered to the user. (See: structureNode.) rdfs:comment Scope note: Any additional information not described elsewhere Scope note: Contains components that indicate parallel relationships between digital resources within an aggregation instance, e.g., two pages in a bilingual text containing the same content, or a topographical map and a road map of the same area. Scope note: Contains information about a person or group performing a role in relationship to a specific community. (Taken from ISO 2146). Scope note: An e-mail address where the party can be contacted. (See: party.) Scope note: The name of the party. (See: party.) Scope Notes: The relationship the party has to an aggregation instance or its component. (See: party.) The category for the party that describes its nature, e.g., person or organization. (See: party.) 0 Scope note: A Uniform Resource Identifier (URI) that may be de-referenced to find more information about the party. (See: party.) Scope note: Information describing the circumstances related to the creation and custody over time of a digital resource. Scope note: Contains components that locate an instance of a remote descriptorObject. (See: descriptorObject, locator.) Scope note: Contains a locator for a part of an aggregation definition document located outside of an aggregation instance. (See: locator.) Scope note: Contains components that locate a remote digital resource. (See: locator.) Scope note: Contains components that locate an instance of a remote topNode. (See: locator, topNode.) Scope note: The set of predicate tests that are required to become true in order to satisfy a condition. (See: condition.) Scope note: Digital resources of diverse types that are gathered together to form a new complex object. Information is contained in the resource aggregation for purposes of specifying the categories of and the relationships among the aggregated resources. A resource aggregation may be contained in an exchange file or not, and may be self-contained or reference resources held in other locations. A resource aggregation may be disaggregated into its component digital resources. Resource aggregations are stored and processed using system formats (internal representations) and are usually transmitted between systems using aggregation formats. Scope note: Contains a collection of fileDescriptor(s) for digital resources. For example, a resourceGroup might comprise the digital resources associated with a Web page. (See: fileDescriptor.) Scope note: Specifies links between two structureNode(s) within an aggregation instance structure to declare an association between them, e.g., two embedded hyperlinks within one or more Web page structures. (See: dynamicStructure, staticStructure, structureNode.) Scope note: Contains machine- or human-readable statements and instructions required to process a digital resource, e.g., how to uncompress and render a compressed digital resource. NOTE- Making a digital resource renderable may require multiple processes. For example, a digital resource may have to be both decrypted and uncompressed. Scope note: A processing algorithm used to make a digital resource renderable. (See: resourceProcessing.) Scope note: Locates a component within an aggregation instance that describes the behavior of a process in a technology specific way, e.g., a Perl script or an Extensible Stylesheet Language Transformation (XSLT). (See: resourceProcessing.) Scope note: Describes a required parameter for a processing algorithm for a digital resource, e.g., a string that tells the processing agent which output format is required. (See: resourceProcessing.) Scope note: Contains collections of dynamicStructure(s) for an aggregation instance and the relationships among them, e.g., the relationship between computer programming code that is used to render a digital resource and that digital resource. (See: dynamicStructure, resourceProcessing.) Scope note: The category for a process required to make a digital resource renderable, e.g., decompression. (See: resourceProcessing.) Scope note: Provides a broad categorisation of the media type of the associated digital resource. e.g. 'webcontent' or 'software application' Scope note: Contains an inline encoding of a digital resource that is represented within the aggregation definition document that describes an aggregation instance, e.g., a base64 encoding. Scope note: Contains resourceWrapper instances. (See: resourceWrapper.) Scope note: Contains information about the rights, obligations, and restrictions governing the use of an aggregation instance or a digital resource, e.g., 'Creative Commons Attribution-ShareAlike' or an Open Digital Rights Language (ODRL) instance. Scope note: Identifies one of a set of options within a dynamicStructure that can be chosen by a processing application to process the dynamicStructure depending upon parameters such as user interaction. The members of the set, i.e., the selection(s), represent the possible decisions of a particular choice. (See: choice, dynamicStructure.) Scope note: The category for the shape of an anchor, e.g., polygon or circle. Typically, this class is used with still-image or video-frame digital resources. (See: anchor.) Scope note: Contains information about the original source of a digital resource, e.g., the technical characteristics of the audio tape from which an audio file has been digitized. Scope note: Contains the relationships among structureNode(s) within an aggregation instance. These relationships hold true regardless of the processing state of an aggregation instance. (See: structureNode.) staticstructureset Scope note: Contains collections of staticStructure(s). (See: staticStructure.) Scope note: The category for the staticStructure of an aggregation instance, e.g., tree or graph. (See: staticStructure.) Scope note: The status of the associated component, e.g., whether it is current or superceded information. Scope note: Contains locator(s) to descriptorObject(s) for a byte stream within a digital resource, e.g., an audio stream within an MPEG–4 video file. (See: descriptorObject, locator.) Scope note: The category for the stream identified within a digital resource, e.g., an audio waveform audio format (WAV) stream within a video resource. (See: stream.) Scope note: A locator from resourceProcessing to a structureNode, e.g., from a piece of executable code designed to display an Enhanced Archival Description (EAD) finding aid to the finding aid text, or from a computer-aided design (CAD) rendering program to the CAD files. (See: locator, resourceProcessing, structureNode.) Scope note: A node in a structure that organizes digital resources in an aggregation instance. For example, a node may be a chapter within a book. (See: dynamicStructure, staticStructure.) Scope note: The category for a structureNode, e.g., page or Shareable Content Object (SCO). (See: structureNode.) Scope note: Contains information about technical aspects of a digital resource, e.g., a file's format characteristics, such as the color profile and compressor-decompressor (CODEC) used to create a Joint Photographic Experts Group (JPEG) image. The format for text used in an associated container node, e.g., plain text or Hyper Text MarkUp Language (HTML). 0 Scope note: A human-readable descriptor for a component in an aggregation instance. Scope note: The highest class level of an aggregation defined by an aggregation format. Scope note: A preferred order among instructions for processing a digital resource or portion thereof. (See: resourceProcessing.) Scope note: Asserts an associated condition to be true. (See: condition.) Scope note: A reference to a resourceGroup to avoid repeated direct inclusion of its fileDescriptor(s). For example, each unique digital resource in a Web page could be listed in an aggregation instance as resourceGroup A. A set of similar Web pages could have many files, such as scripting language scripts or style sheets, in common. Rather than list the common files with every resource group in an aggregation instance, they could be declared once as resourceGroup B. A virtualResourceGroup indicates that resourceGroup A depends on another resourceGroup B. (See: fileDescriptor, reference, resourceGroup.) Scope note: Contains information about an aggregation instance itself, rather than the digital resources it aggregates, e.g., date of creation or lifecycle status.