|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Publishing and sharing your metadata application profileA two-day workshop, 23-24th November 2000, Bonn, Germany
Friday 24th November 2000
Breakout One: Re-using application profilesThis session will look at requirements, benefits and potential problems in registering, finding and re-using application profiles. We will discuss issues related to the registration and maintenance of application profiles, the level of description and usage guidance and look at issues the registry would have to take into account to allow automatic processing. Breakout Two: Semantic versus operational profilesRDF Schemas are best at declaring the names and definitions of metadata terms in a machine-processable way, along with various types of hyperlinked cross-references to terms in other metadata vocabularies. XML Schemas, another emerging standard, are stronger at describing explicit structural, cardinality, and datatyping constraints on metadata values in a way that can be used directly in applications. Which requirements are important for which circumstances? Is the existence of two similar standards a bug or a feature? Breakout Three: Complexity in application profilesThis breakout session will consider how simple or complex application profiles might be. Should application profiles be viewed as simple declarations of the semantics attached to a particular application? or should they contain additional information describing typical implementations, rules for content, or other application specific data? How much information should an application profile contain?
Email comments to j.v.fraser@ukoln.ac.uk
Maintained by: UK Office for Library and
Information Networking (UKOLN)
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||