META-SHARE CMDI conversion: Validation errors

Oct 11, 2013 at 06:33

We have run our META-SHARE data through the provided CMDI converter. When validating the converted records afterwards, one specific validation error concerning the element userNature occurs in each record:

Description: cvc-complex-type.2.4.a: Invalid content was found starting with element 'userNature'. One of '{"http://www.clarin.eu/cmd/":licensorPerson, "http://www.clarin.eu/cmd/":licensorOrganization, "http://www.clarin.eu/cmd/":distributionRightsHolderPerson, "http://www.clarin.eu/cmd/":distributionRightsHolderOrganization, "http://www.clarin.eu/cmd/":membershipInfo}' is expected.

According to the corresponding profile in CLARIN Component Registry the value of userNature must be academic or commercial, and the XSD against which I validate is downloaded from there. Please advise.

Tags: CMDI, Validation, conversion to CMDI

Discussion 4 answers

  • avatar
    Answer by editor on Oct 11, 2013 at 14:13

    Hi,

    The validation error doesnot have to do with the values of "userNature". The problem most probably arises from the documented difference in ordering between XML and the CMDI mechanism: XML allows mingled ordering between components and elements, while CMDI requires a strict ordering of all elements first and thereafter components (cf. https://github.com/metashare/META-SHARE/blob/master/misc/tools/CMDIConverters/report_on_META-SHARE_CMDI_converters.pdf). Thus, in the MetaShare xsd, the element "userNature" is before the membershipInfo and right after two other components (licensor and distributionRightsHolder), while in the CMDI version, it is found before all these three components. The XSL converters provided at https://github.com/metashare/META-SHARE/tree/master/misc/tools/CMDIConverters/ make the appropriate re-ordering. If you have used them and still have the same problem, please notify us by sending an email at the technical helpdesk: helpdesk-technical@meta-share.eu

     

    Best regards,

    Haris Papageorgiou

     

     

     

  • avatar
    Answer by olufine on Oct 22, 2013 at 09:29

    Hi again,

    I have just looked into it, and I think the problem is caused by mismatch in cardinality between the CMDI and MetaShare versions. In the CMDI version, "userNature" is restricted to 0-1 occurrence, while unbounded in the MetaShare xsd. 

    Many of our records have 2 instances of userNature, and the validator recats to the second occurrence.

    Since this may be of common interest, I answer here instead of contacting the helpdesk.

     

     

  • avatar
    Answer by pennyl67 on Oct 25, 2013 at 06:21

    Thanx for spotting it.

    We will correct the mistake in the CMDI profile and let you know asap.

    Best,

    Penny Labropoulou

  • avatar
    Answer by pennyl67 on Oct 29, 2013 at 09:39

    The CMDI profiles have been corrected. You can use the correct XSD's by downloading them from the registry.

    Best,

    Penny Labropoulou

  • avatar
    Log in or Register to reply to this post.