wiki:CmdiNews

2013-02-26

The <Header> element of the component specification gets copied into a profile's XML schema as <xs:annotation> content.

For details and examples, see ticket #282. For the changes in comp2schema.xsl, see [2626].

2012-09-12

Added (code) to AppInfo? elements for ISO-639-3, ISO-639-1, ISO-639-5, ISO-countries and ISO-continents

2012-08-31

2012-08-29

Added an ​FAQ on the mimetype for CMDI

2012-08-24

Changed the controlled vocabulary (ValueScheme?) from ​cmdi-content to string, adding the suggested items to the documentation instead, as suggested by Florian Schiel.

2012-08-23

Harmonized some component names (iso-country, iso-language-639-1, iso-language-639-3, iso-languagefamily-639-5). Changes are backward compatible but should allow to find relevant components more easily. Also updated the ​recommended components FAQ.

2012-08-21

  • Upon request of Christina Hopperman there now can be ​multiple <MdCreator/> elements in the Header section of a CMDI file.
  • A ​new version (1.12.0) of the Component Registry has been deployed, new features are:
    • browser: depending on the workspace (public or private), there are now buttons to start editing the selected component, a copy of it or start a new one
    • browser: search bar and public/private switch have moved to the right to make place for the buttons
    • browser: if there are unsaved changes in the editor and you choose to edit a component, a confirmation dialog will appear asking you whether you want to discard the changes
    • editor: the dialog for choosing a type now has tabs to edit as a standard type, a vocabulary, or pattern
    • editor: ISOcat search dialog (concept link field) now has a clickable search button
    • Navigation with the flex UI is no longer centred around the tabs on the top, but by selection actions from the buttons or context menu in the component browser, and close/cancel actions to go back. This leads to a more constrained and less confusing work flow.
    • Component editor has collapse/expand buttons for all child components and elements (and links to collapse/expand everything)

2012-08-09

Added 2 new ResourceProxy? types: SearchPage? and SearchService?. Updated the ​FAQ on CMDI and SRU

2012-08-07

Some work on the license type classification:

2012-07-18

Added quite some missing ISOcat links to:

2012-07-17

The imdi2clarin.xsl has been improved (now creates ResourceProxy? for infolinks)

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

2012-3-19

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

2012-1-4

2011-12-23

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)
Last modified 11 years ago Last modified on 02/28/13 14:37:19