This Content Class contains metadata elements describing the actual intellectual content of a media asset or resource.

There are 9 containers and a total of 16 elements in the Intellectual Content grouping.

• The value of the identifier within the identification or cataloging scheme that designates or identifies a metadata record. A namespace specific string.
• Identifier is a globally unique label that identifies this metadata record.
• The Meta-Metadata category describes a metadata record itself (rather than the learning object that a record describes).This category describes how the metadata instance can be identified, who created this metadata instance, how, when, and with what references.

• Dublin Core defines its element *identifier* with regard to a unique designation for a media item itself, and not an identifier for a entire metadata record associated with a media item and all of its descriptions, formats, renditions and instantiations.
• PBCore's *identifier* element is different than Dublin Core's *identifier*, although it is tempting to map the two elements because of the similarity in names.
• PBCore's *formatIdentifier* more closely parallels the definition and usage of Dublin Core's *identifier*.

• The name or designator of the identification or cataloging scheme for this entry. A namespace scheme.
• Identifier is a globally unique label that identifies a metadata record.
• The Meta-Metadata category describes a metadata record itself (rather than the learning object that this record describes).This category describes how the metadata instance can be identified, who created this metadata instance, how, when, and with what references.

• Name given to this learning object.
• The General category groups the general information that describes a learning object as a whole.

• derivation from Dublin Core Metadata Registry

• Could be added as an Extension Option for the General category.
• 1.9:General.Extension
• The General category groups the general information that describes a learning object as a whole.

• PBCore does not maintain a separate and distinct element for an *Alternative Title* to the formal *Title* given a media item (a refinement to Dublin Core's *Title*). Instead PBCore repeats the pbcoreTitle container, supplies the *Alternative Title*, then from the element *titleType,* selects *Alternative* from the picklist of terms.

• A keyword or phrase describing the topic of a learning object. This data element should not be used for characteristics that can be described by other data elements within IEEE LOM.
• The General category groups the general information that describes a learning object as a whole.

• derivation from Dublin Core Metadata Registry

• The name of the classification system. This data element may use any recognized "official" taxonomy or any user-defined taxonomy.
• A Taxonomic Path refers to a specific classification system.
• The Classification category describes where a learning object falls within or in relation to a particular classification system.

• PBCore recommends several related schemes (as does Dublin Core) and supplies additional authorities, some of which are specific to Public Broadcasting applications.

• A textual description of the content of a learning object.
• The General category groups the general information that describes a learning object as a whole.

• derivation from Dublin Core Metadata Registry

• Could be added as an Extension Option for the General category.
• 1.9:General.Extension
• The General category groups the general information that describes a learning object as a whole.

• PBCore maintains a robust list of description types, many of which are unique to media production and Public Broadcasting applications. Two of the suggested 22 *descriptionType* terms are refinements derived from Dubin Core...
  • abstract
  • tableOfContents

• A keyword or phrase describing the topic of a learning object. This data element should not be used for characteristics that can be described by other data elements within IEEE LOM.
• The General category groups the general information that describes a learning object as a whole.

• Although Dublin Core uses the word "genre" in its definition of *type*, it must not be confused with PBCore's element *genre* that has a completely different definition and usage more closely aligned with program keywords found in program guides and TiVo-like applications.

• The name of the classification system. This data element may use any recognized "official" taxonomy or any user-defined taxonomy.
• A Taxonomic Path refers to a specific classification system.
• The Classification category describes where a learning object falls within or in relation to a particular classification system.

• Nature of the relationship between a learning object and a target learning object, identified by 7.2:Relation.Resource.
• The Relation category defines the relationship between a learning object and other related learning objects, if any.

• the types of relations defined in PBCore parallel those of Dublin Core's *relation* element...
• Has Format
  NOTE: PBCore prefers to repeat the container for *pbcoreInstantiation* to catalog a different format or rendition of exactly the same intellectual content. PBCore is able to accommodate multiple renditions of an item within a single metadata record. Dublin Core requires that each rendition or format receives its own unique metadata record with rendundant intellectual content and property descriptions.
• Is Format Of
• Has Part
• Is Part Of
• Has Version
• Is Version Of
• References
• Is Referenced By
• Replaces
• Is Replaced By
• Requires
• Is Required By

• The value of the identifier within the identification or cataloging scheme that designates or identifies the target learning object. A namespace specific string.
• Identifier is a globally unique label that identifies the target learning object.
• Resource is the target learning object that this relationship references.
• The Relation category defines the relationship between a learning object and other related learning objects, if any.

• equivalent to the Dublin Core element *relation* in which related resources are identified by text and/or number strings derived from specific identification systems.

• The time, culture, geography or region to which a learning object applies.
• The extent or scope of the content of the learning object.
• Coverage will typically include spatial location (a place name or
  geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity).
• The General category groups the general information that describes a learning object as a whole.

• In following a "container architecture" in its metadata dictionary and schema, PBCore reconfigures the Dublin Core coverage elements of *spatial* and *temporal* into a single element that carries the descriptive data. An associated element called *coverageType* identifies the kind of descriptive data, i.e., *spatial* or *temporal*.
• If both *spatial* and *temporal* coverage descriptions exist, PBCore repeats the *pbcoreCoverage* container.

• Could be added as an Extension Option for the General category.
• 1.9:General.Extension
• The General category groups the general information that describes a learning object as a whole.

• PBCore's *coverageTypes* parallel those found in Dublin Core...
  • Spatial
  • Temporal

• The principal environment within which the learning and use of a learning object is intended to take place.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.
• NOTE:--This is the pedagogical information essential to those involved in achieving a quality learning experience. The audience for this metadata includes teachers, managers, authors, and learners.

• PBCore parallels the definition of the Dublin Core element *audience* in that it identifies for whom a media item is intended or useful.
• A refinement to Dublin Core's *audience* is *Education Level* in which a description is made of the educational or training context. A specific statement of the location of the audience in terms of its progression through an education or training context can be used.
• PBCore uses a picklist of terms derived from the Library of Congress vocabulary for educational sectors. Thus PBCore's *audienceLevel* could map to Dublin Core's *Audience Education Level*.

• Age of the typical intended user. This data element shall refer to developmental age, if that would be different from chronological age.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• The principal environment within which the learning and use of a learning object is intended to take place.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.
• NOTE:--This is the pedagogical information essential to those involved in achieving a quality learning experience. The audience for this metadata includes teachers, managers, authors, and learners.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *audienceRating* (which parallel those of the FCC V-Chip codes and the MPAA ratings) can be mapped to the Dublin Core element *audience* as another indicator for whom a media item is intended or useful.

• Age of the typical intended user. This data element shall refer to developmental age, if that would be different from chronological age.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

This Content Class contains metadata elements related to the creation, creators, usage, permissions, constraints, and use obligations associated with a media asset or resource.

There are 4 containers and a total of 7 elements in the Intellectual Property grouping.

• Maps if 2.3.1:LifeCycle.Contribute.Role has a value of "Author"
• The identification of and information about entities (i.e., people, organizations) contributing to this learning object. The entities shall be ordered as most relevant first.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected this learning object during its evolution.

• derivation from Dublin Core Metadata Registry

• Kind of contribution.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected this learning object during its evolution.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *creatorRole* can be mapped to the Dublin Core element *creator* as another indicator or attribution to the individual or group responsible for the intellectual content of a media item.

• Maps if 2.3.1:LifeCycle.Contribute.Role has a specified value.
• The identification of and information about entities (i.e., people, organizations) contributing to a learning object. The entities shall be ordered as most relevant first.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• derivation from Dublin Core Metadata Registry

• Kind of contribution.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *contributorRole* can be mapped to the Dublin Core element *contributor* as another indicator or attribution to the individual or group responsible for the intellectual content of a media item.

• Maps if 2.3.1:LifeCycle.Contribute.Role has a value of "Publisher"
• The identification of and information about entities (i.e., people, organizations) contributing to a learning object. The entities shall be ordered as most relevant first.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• derivation from Dublin Core Metadata Registry

• Kind of contribution.
• Contribute refers to those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *publisherRole* can be mapped to the Dublin Core element *publisher* as another indicator or attribution to the individual or group responsible for the publication or distribution of a media item.

rights
date copyrighted
provenance
rights holder
license

• Whether copyright or other restrictions apply to the use of this learning object.
• The Rights category groups the intellectual property rights and conditions of use for a learning object.

• derivation from Dublin Core Metadata Registry
• Dublin Core maintains a separate element for the date of copyright for a media item--*date copyrighted*. PBCore does not; however that information can be entered into *rightsSummary*.
• Dublin Core maintains a separate element for the ownership or custody of a media item--*provenance*. It could be argued that such information is entered into PBCore's *rightsSummary*.
• Dublin Core maintains a separate element to designate the person or organization owning or managing rights over a media item--*rights holder*. It could be argued that such information is entered into PBCore's *rightsSummary*.
• Dublin Core maintains a separate element to identify legal documentation for usage permissions over a media item--*license*. It could be argued that such information is entered into PBCore's *rightsSummary*.

• Comments on the conditions of use of this learning object.
• The Rights category groups the intellectual property rights and conditions of use for a learning object.

• Whether use of this learning object requires payment.
• The Rights category groups the intellectual property rights and conditions of use for a learning object.

This Content Class contains metadata elements that identify the nature of the media asset as it exists in some form or format in the physical world or digitally.

There is a single parent container, with 3 sub-containers, and a total of 28 elements in the Instantiation & Formats grouping. For each new instantiation or format for a media asset/title, the entire parent container can be repeated.

• The date of the contribution.
• Contribute represents those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• PBCore's *dateCreated* parallels the definition of Dublin Core's refinement *created* to the element *date*.
• PBCore does not restrict the data entry for temporal designations to a specific scheme, such as the W3CDTF profile of ISO 8601, although their syntax for entering dates (year month day) is recommended.

• Maps when IEEE-LTSC LOM 2.3.1:LifeCycle.Contributor.Role has a value of "Publisher".
• The date of the contribution.
• Contribute represents those entities (i.e., people, organizations) that have contributed to the state of a learning object during its life cycle (e.g., creation, edits, publication).
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• PBCore's *dateIssued* parallels the definition of Dublin Core's refinement *issued* to the element *date*.
• PBCore does not restrict the data entry for temporal designations to a specific scheme, such as the W3CDTF profile of ISO 8601, although their syntax for entering dates (year month day) is recommended.

• Technically speaking, IEEE LOM doesn't refer to physical formats, such as video and audio tapes.
• Such information could be inserted into the 4.1:Technical.Format element.
• Perhaps a more satisfying approach, and one in tune with IEEE LOM best practices, is to add PBCore's *formatPhysical* descriptors as an Extension in the Technical category
• 4.8:Technical.Extension
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• PBCore separates the designation of the format for a media item into *formatPhysical* and *formatDigital* elements.
• Dublin Core uses the refinement *medium* of the element *format* to identify the material or physical carrier of the resource.

• The technology required to use this learning object, e.g., hardware, software, network, etc.
• MIME types are recommended values.
• OrComposite represents within IEEE LOM Format a grouping of multiple requirements. The composite requirement is satisfied when one of the component requirements is satisfied, e.g., Type.
• Format refers to technical datatype(s) of (all the components of) a learning object. This data element shall be used to identify the software needed to access a learning object.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• PBCore separates the designation of the format for a media item into *formatPhysical* and *formatDigital* elements.
• The picklist of MIME types that PBCore uses for *formatDigital* parallels how Dublin Core uses the element *format*.

• A string that is used to access a learning object. It may be a location (e.g., Universal Resource Locator), or a method that resolves to a location (e.g., Universal Resource Identifier).
• NOTE:--This is where the learning object described by this metadata instance is physically located.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Specific kind of learning object.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.
• NOTE:--This is the pedagogical information essential to those involved in achieving a quality learning experience. The audience for this metadata includes teachers, managers, authors, and learners.

• PBCore offers a picklist of media types that parallels the picklist used by Dublin Core in its element *type*.
• Dublin Core uses its *format* element to describe file formats, physical media, and dimensions of a media item.
• Although Dublin Core uses the word "genre" in its definition of *type*, it must not be confused with PBCore's element *genre* that has a completely different definition and usage more closely aligned with program keywords found in program guides and TiVo-like applications.

• The edition of a learning object.
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatGenerations* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• The completion status or condition of a learning object.
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• The technical capabilities necessary for using a learning object.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Could be argued that PBCore's definition of *formatStandard* is a near equivalent to Dublin Core's type of *relation* identified as *conformsTo*.
• In Dublin Core, *conformsTo* is defined as "A reference to an established standard to which the resource conforms."

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatEncoding* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• The size of the digital learning object in bytes (octets). The size is represented as a decimal value (radix 10). Consequently, only the digits "0" through "9" should be used. The unit is bytes, not Mbytes, GB, etc.
• This data element shall refer to the actual size of a learning object. If the learning object is compressed [for distribution, e.g., .zip or .sit or .bin], then this data element shall refer to the uncompressed size.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• Time a continuous learning object takes when played at intended speed.
• This data element is especially useful for sounds, movies or animations.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatDataRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatBitDepth* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatSamplingRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."
• It could be argued that the *frameSize* defined in PBCore can map to Dublin Core's *extent*.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatAspectRatio* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatFrameRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatColors* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatTracks* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatChannelConfiguration* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• The primary human language or languages used within this learning object to communicate to the intended user.
• The General category groups the general information that describes a learning object as a whole.

• derivation from Dublin Core Metadata Registry

• Information about other software and hardware requirements.
• NOTE:--This element is intended for descriptions of requirements that cannot be expressed by the data element 4.4:Technical.Requirement.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• If additional granularity is desired in order to capture many of the PBCore technical instantiation/format descriptions, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• The availability of a media item as expressed in PBCore's *dateAvailableStart* seems best suited as a Extension to be created under the LifeCycle category in IEEE LOM.
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• Dublin Core combines the start and end dates for the availability of a media item into a single date-related element *available*.
• Dublin Core accommodates a date range for *available*.
• PBCore preferred to separate possible start and end dates in order to facilitate better searching criteria often needed in Public Broadcasting.

• The availability of a media item as expressed in PBCore's *dateAvailableEnd* seems best suited as a Extension to be created under the LifeCycle category in IEEE LOM.
• The Life Cycle category describes the history and current state of a learning object and those entities that have affected a learning object during its evolution.

• Dublin Core combines the start and end dates for the availability of a media item into a single date-related element *available*.
• Dublin Core accommodates a date range for *available*.
• PBCore preferred to separate possible start and end dates in order to facilitate better searching criteria often needed in Public Broadcasting.

• The value of the identifier within the identification or cataloging scheme that designates or identifies a learning object. A namespace specific string.
• Identifier refers to a globally unique label that identifies a learning object.
• The General category groups the general information that describes a learning object as a whole.

• Dublin Core defines its element *identifier* with regard to a unique designation for a media item itself, and not an identifier for a entire metadata record associated with a media item and all of its descriptions, formats, renditions, and instantitions.
• PBCore's *formatIdentifier* parallels the definition and usage of Dublin Core's *identifier*.

• The name or designator of the identification or cataloging scheme for this entry. A namespace scheme.
• Identifier refers to a globally unique label that identifies a learning object.
• The General category groups the general information that describes a learning object as a whole.

• The PBCore *annotation* metadata element is housed within the pbcoreInstantiation container. Therefore, its contents could be considered to technical in nature. This is not a hard and fast rule, since *annotation* is merely related to a particular rendition or format for a media item.
• If the annotation is related to technical matters, then the IEEE LOM best practice is to create an extension to the Technical category.
• The Technical category groups the technical requirements and technical characteristics of a learning object.

• Entity (i.e., people, organization) that created this annotation.
• The Annotation category provides comments on the educational use of a learning object and provides information on when and by whom the comments were created. This category enables educators to share their assessments of learning objects, suggestions for use, etc.

• Date that an annotation was created.
• The Annotation category provides comments on the educational use of a learning object and provides information on when and by whom the comments were created. This category enables educators to share their assessments of learning objects, suggestions for use, etc.

• The content of the annotation.
• The Annotation category provides comments on the educational use of a learning object and provides information on when and by whom the comments were created. This category enables educators to share their assessments of learning objects, suggestions for use, etc.

• Create an Extension to the category Annotation to house any other annotations.
• The Annotation category provides comments on the educational use of a learning object and provides information on when and by whom the comments were created. This category enables educators to share their assessments of learning objects, suggestions for use, etc.

This Content Class contains additional descriptions that have been crafted by organizations outside of the PBCore Project. These extensions fulfill the metadata requirements for these outside groups as they identify and describe their own types of media with specialized, custom terminologies unique to their needs and community requirements.

There is a single container and a total of 2 elements as a starter kit for the addition of metadata extensions to the PBCore.

Many PBCore users have inquired about educational utilization metadata to accompany their media items. Such descriptions answer questions related to how a media item is best integrated into educational settings.

PBCore does not maintain its own set of utilization metadata elements. However IEEE LOM certainly does, since the metadata schema is based on describing Learning Objects!

We summarize 12 of these fields from IEEE LOM below. All are taken from the IEEE LOM category called *Educational*. They can be considered as extensions to PBCore. For each of these extensions, the PBCore schema would require you to identify the Authority Used for the extension's creation and maintenance. Although entered only once under extensionAuthorityUsed, all 12 elements would be attributed to IEEE LOM.

IEEE LOM and the hierarchy of metadata elements that it maintains are designed to readily accommodate *extensions* to its base structures.

Each of LOM's main categories (content classes) can append one or more metadata extensions within the overall meaning and definition for that category.

IEEE LOM simply demands that catalogers do not amend the base structure of their metadata schema, but add extensions as needed.

However, IEEE LOM cautions that extensions only be added if the base structure does not accommodate the descriptions a cataloger is attempting to input. Use the existing structures according to IEEE LOM best practices, then add extensions if required.

• Predominant mode of learning supported by a learning object.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• Specific kind of learning object.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• The degree of interactivity characterizing a learning object. Interactivity in this context refers to the degree to which the learner can influence the aspect or behavior of a learning object.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• The degree of conciseness of a learning object. The semantic density of a learning object may be estimated in terms of its size, span, or --in the case of self-timed resources such as audio or video-- duration.
• The semantic density of a learning object is independent of its difficulty. It is best illustrated with examples of expositive material, although it can be used with active resources as well.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• Principal user(s) roles for which a learning object was designed.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• The principal environment within which the learning and use of a learning object is intended to take place.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• Age of the typical intended user. This data element shall refer to developmental age, if that would be different from chronological age.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• How hard it is to work with or through a learning object for the typical intended target audience.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• Approximate or typical time it takes to work with or through a learning object for the typical intended target audience.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• Comments on how a learning object is to be used.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• The human language used by the typical intended user of a learning object.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.

• If other educational utilization descriptions don't fit within the IEEE LOM structure, then extensions can be added, e.g., the identification of *academic disciplines* associated with a media item when used in higher education settings.
• The Educational category describes the key educational and pedagogic characteristics of a learning object.