The CLARIN Metadata (MD) Toolkit

Transcription

1 The CLARIN Metadata (MD) Toolkit

2 Key Features of the MD Toolkit simple structure: easy to learn and to use relatively powerful and flexible modular and reusable users are restricted in creating MD schemas fully compatible with xsd

3 Current Status schema to restrict component creators example components (on the CLARIN web site) components have to be created "by hand" short how-to (on the CLARIN web site)

4 Next Steps (planned) software that aids users in creating components central component repository extensive documentation

5 How to use the CLARIN Metadata Toolkit? 1. (create components that comply to generalcomponent-schema.xsd) 2. create a profile that consists of included components 3. transform the profile using comp2schema.xsl 4. use the generated schema to create/validate metadata instances

6 Example Components Photo Component Actor Component

7 Anatomy of a Component have a name and a cardinality <CMD_Component name="actor" CardinalityMin="0" CardinalityMax="unbounded"> cardinality mapped to xsd MinOccurs/MaxOccurs can have four different kinds of child elements: one optional AttributeList zero, one or more CMD_Element zero, one or more CMD_Component (recursion) zero, one or more CMD_ComponentList

8 Anatomy of a Component - AttributeList <CMD_Component name="description"> <AttributeList> <Attribute> <Name>LanguageID</Name> <Type>string</Type> </Attribute> </AttributeList> </CMD_Component> possible for elements or components has to be first child each attribute a separate sub element mapped to xsd Attributes four possible types: string, float, boolean, decimal

9 Anatomy of a Component - CMD_Element optional AttributeList <CMD_Element name="description" ValueScheme="string"> <AttributeList> <Attribute> <Name>LanguageID</Name> <Type>string</Type> </Attribute> </AttributeList> </CMD_Element> optional CardinalityMin & CardinalityMax <CMD_Element name="actor" CardinalityMin="0" CardinalityMax="unbounded"> mapped to xsd MinOccurs/MaxOccurs default to 1 (as MinOccurs/MaxOccurs)

10 Anatomy of a Component - CMD_Element ValueScheme simple type (string, float, decimal, boolean) <CMD_Element name="ethnicgroup" ValueScheme="string"/> pattern (using xml regular expressions) <CMD_Element name="birthdate"> <ValueScheme> <pattern>(1 2)\d{3}-(0[1-9] 1[012])-(0[1-9] [12][0-9] 3[01])</pattern> </ValueScheme> </CMD_Element>

11 Anatomy of a Component - CMD_Element ValueScheme enumeration of allowed values <CMD_Element name="sex"> <ValueScheme> <enumeration> <item>male</item> <item>female</item> <item>hermaphrodite</item> <item>unknown</item> </enumeration> </ValueScheme> </CMD_Element>

12 Anatomy of a Component - CMD_Component components can contain other components you can either define them inline <CMD_Component name="actor"> <CMD_Component name="actorlanguage" CardinalityMin="0" CardinalityMax="1"> <CMD_Element name="actorlanguagename" ValueScheme="string"/> </CMD_Component> </CMD_Component> or reference them via XIncludes (preferred way) <CMD_Component name="actor"> <xi:include href="component-actor.xml" xpointer="element(/1/2)" /> </CMD_Component>

13 Anatomy of a Component - CMD_ComponentList used to override a component's cardinality example: Language Component <CMD_Component name="language" CardinalityMin="0" CardinalityMax="unbounded"> <CMD_Element name="name" ValueScheme="string"/> <CMD_Element name="id" ValueScheme="string"/> </CMD_Component> can occur 0 - times

14 Anatomy of a Component - CMD_ComponentList (cont'd) Actor Component (1 - languages) <CMD_Component name="actor" CardinalityMin="0" CardinalityMax="unbounded"> <CMD_ComponentList CardinalityMin="1" CardinalityMax="unbounded"> <xi:include href="component-language.xml" xpointer="element(/1/2)" /> </CMD_ComponentList> </CMD_Component> Project Component (exactly 1 language) <CMD_Component name="project" CardinalityMin="1" CardinalityMax="1"> <CMD_ComponentList CardinalityMin="1" CardinalityMax="1"> <xi:include href="component-language.xml" xpointer="element(/1/2)" /> </CMD_ComponentList> </CMD_Component>

15 Creating a Profile from Existing Components in principle same structure as a component general-component-schema is used use other components as references Example Profile

16 Generating the XML Schema transform into xsd with comp2schema.xsl the resulting XML Schema always has a <Header> element (for meta information, e.g. author, creation date,...) the resulting XML Schema always has a <Resources> element (for describing and linking the resources associated with the metadata) you can directly link to specific resources from certain metadata elements Example MD Instance

17 Thank you for your attention!