2012-07-11

The ​list of preferred components and profiles has been extended

2012-05-16

A bug in the imdi2cmdi.xsl was killed and now the referential integrity between the MdSelfLink? element and the ResourceProxy? elements from the type metadata is OK again for ​the cmid'fied IMDI set.

2012-05-08

• New release of the VLO deployed

2012-05-03

• VLO issues fixed, importer running correctly again.
• ComponentRegistry issues also fixed

2012-05-02

Issues with the VLO importer (on catalog.clarin.eu), resulting in a lower record count. Herman is looking at this.

2012-04-27

Issue with component registry identified. Hopefully it can be fixed on May 2.

2012-3-22

​Newest version of the VLO deployed

2012-3-20

• Added an FAQ on container datcats (​http://www.clarin.eu/faq/3493) and a pointer to further FAQs on ISOcat (​http://www.clarin.eu/faq/3492)
• new CMDI provider: ​http://catalog.clarin.eu/oai-harvester/Saarland_University.html

2012-3-19

• Added an FAQ on multilingual: ​http://www.clarin.eu/faq/3490
• Added an "outdated" warning to ​http://www.clarin.eu/node/2856
• Added a wiki page on recommended components: CmdiRecommendedComponents (used as input for ​http://www.clarin.eu/faq/3491)

2012-3-6

FAQ restructured: ​http://www.clarin.eu/faq/technical-infrastructure/metadata

2012-3-5

The metadata/trunk/toolkit/xslt/comp2schema-v2 XSLT files that are used to generate XML schema files from profile specifications have been modified.

Previously these XSLT's depended on two features (saxon:indent-spaces and saxon:next-in-chain) that are no longer available in the free version of the SAXON XSLT processor since version 9.2 of Saxon. The calls to these features have been removed. As a result of this, resulting schema files will no longer have pretty indentation.

Users of the XSLT that still wish to create schema files with indentation can pass the option indent="yes" to their XSLT processor. The current version of the Component Registry does this, and thus still produces indented schema files. Future versions will use an up-to-date version of Saxon and will produce unindented schema files.

2012-2-3

Some outcomes of the CMDI namespace discussion:

- We will keep the single namespace (http://www.clarin.eu/cmd/) for all
CMDI instances. The arguments for having a specific namespace per
profile do not outweigh the extra work and worries it will create.
People still can have their own namespace and change the instances to
the standard namespace when offering these CMDI files over OAI-PMH.

- In the next version of CMDI (1.2) we will make the <MdProfile> element
obligatory. The current version (1.1) will stay the default one that is
generated by the component registry. Only when the REST entry point
explicitly mentions a version the 1.2 XSDs will be generated. We will
however encourage all CMDI creators to fill the MdProfile element already.

(As a side note: CMDI v. 1.2 could also accomodate the renaming of Res1
and Res2 in the <ResourceRelation/> node)

2012-1-5

• addition of FAQs about Arbil as CMDI editor: ​http://www.clarin.eu/faq/technical-infrastructure/standards/metadata/arbil-as-cmdi-editor

2012-1-4

• ​added dateTime to the allowed ValueSchemes? for CMD_Element (and attributes) in general-component-schema.xsd

2011-12-23

• set showInEditor to false for most obvious cases
• fixed maxOccurences of CLARIN-NL root component
• removal of obsolete profiles (olac, textDesc, ...)
• Addition of new CMDI FAQs: ​http://www.clarin.eu/faq/technical-infrastructure/standards/metadata-0

2011-12-20

Some changes to general-component-schema are proposed:

• add some schematron rules, to check eg that there is only 1 root component (Menzo)
• extra FAQs will be added on the extra restrictions by the schema (Dieter)
• these schematron rules will be checked by the Component Registry (Twan)