Metadata Assignment - Brian Landau

Part 1:

• John Muir Encoded with Dublic Core XML
• John Muir Encoded with Dublin Core RDF

Part 2:

BibTex for article:

@article{Doi:10.1045/april2002-weibel,
	    Author = {Erik Duval and Wayne Hodgins and Stuart Sutton and Stuart L. Weibel},
	    Doi = {10.1045/april2002-weibel},
	    Issn = {1082-9873},
	    Journal = {D-Lib Magazine},
	    Keywords = {metadata, Dublin Core Metadata Initiative, best practices},
	    Month = {April},
	    Number = {4},
	    Title = {Metadata Principles and Practicalities},
	    Url = {http://www.dlib.org/dlib/april02/weibel/04weibel.html},
	    Volume = {8},
	    Year = {2002}}
	

Summary:

• Principles provide a guiding framework for the development of practical solutions for semantic and machine interoperability in any domain using any set of metadata standards.

  • Modularity:
    

    allows designers of metadata schemas to create new assemblies based on established metadata schemas and benefit from observed best practice, rather than reinventing elements anew.

    • Allows for significant re-usability
    • One can put multiple pieces together like Legos
    • Mix a variety of semantic modules within a common syntactic foundation
    • Namespaces enhance modular portability
  • Extensibility:
    

    the notion of a base schema with additional elements that tailor a given application to local needs or domain-specific needs without unduly compromising the interoperability provided by the base schema.

  • Refinement:
    
    • Choose a level of detail that is appropriate
    • Addition of qualifiers that make an element more specific
    • Specification of a specific scheme, or value set, for a given element, allowing increased portability
  • Multilingualism

• Practicalities:

  • Application Profiles:
    

    The purpose of an application profile is to adapt or combine existing schemas into a package that is tailored to the functional requirements of a particular application, while retaining interoperability with the original base schemas.

    • Allows for semantic interoperability within a specific community or field, while keeping the underlying interoperability, and allowing for further customization.
  • Syntax and Semantics should be as separate as possible.
  • Association Models:
    • A standardization of how we associate metadata with a resource.
    • Three types of methods currently:
      • Embedded
      • Associated
      • Third-party
  • Metadata Registries:
    • Their purpose is to manage and disclose metadata schema declarations, application profile declarations, and value space declarations.
  • Completeness of Description:
    

    Applications should be designed to make evident that not every available element is necessarily appropriate for every resource type.

    • They should also help in selection of an appropriate element value.
    • There are tradeoffs between detailed descriptions and simple descriptions.
  • Other Concerns:
    • The issue of Mandatory vs. Optional elements
    • Subjective and Objective metadata
    • Automated metadata generation/creation

Personal Thoughts:

Overall this seems like some of the more important attributes to getting different metadata schemes, value sets, etc. to work together and be usable by as many users as possible. It will also allow for a common understanding among developers, allowing for more reuse of vocabularies and schemes.