MetadataTechnical

From oaibp

Main Page >> Archive >> ShareableMetadataWorkArea

[edit] Metadata Technical Issues

Note: Please add a brief introduction on what's covered under Metadata Technical Issues and why it's important.
Note: Please add a one-sentence summary for each major bullet point.

• Namespaces and Schemas - follow the protocol! [Clay, Muriel, metadata primer]

• Character Encoding Issues - (UTF-8, URL, XML�) [Clay, Tim]

• Implementing Crosswalks - information about options for ways to map metadata from one format to another [Jeff] - see CrosswalkingLogic

• Supporting multiple formats without multiple workflows - see also MultipleMetadataFormats
  • This is one of the benefits of providing a richer, fuller metadata standard than simple Dublin Core. The more the specificity, the easier it is to crosswalk to other metadata formats that are equally expressive. More expressive metadata standards are much easier to crosswalk to less expressive, summarized formats such as simple Dublin Core, MARC, etc. Going from the general to the specific (e.g., simple DC to FGDC) proves much more complicated, often resulting in too little data to ensure compliance or validation with the more expressive standard.
  • Using XML Web Services like REST or SOAP to expose XSL transformation services for a given type of metadata. Also, to provide crosswalks between metadata types, schema, etc.

See also MetadataContent Issues