DANS Dataset Metadata (DDM) This schema specifies a metadata-format for describing datasets. An instance of this metadata-format can be used for ingest of datasets with the Sword protocol. Created 2012-10-26 Last modified 2020-03-03 Change since 2019/10 * no longer allow an X as 17th digit, lowercase 'x' is no longer allowed Change since 2019/07 * Remove GROUP_ACCESS from EasyAccessCategoryType * Remove 'group' attribute from ddm:accessRights Change since 2019/01 * allow scheme attribute in all ddm:LinkedRelationType, restricted to known EASY-schemes Change since 2018/05 * Upgrade to 2019/01/dcx-dai * Upgrade to datacite v4.1 Change since 2018/03 * Add attribute 'group' in ddm:accessRights Change since 2018/02 * Use 2018/03/dcx-dai.xsd * Introduce ddm:description and add descriptionType-attribute Change since 2017/09 * Add ddm:temporal Copyright (c) 2012 DANS-KNAW Root element of DANS Dataset Metadata. DDM-instances MUST have one ddm:profile element and MAY have one ddm:dcmiMetadata element and one ddm:additional-xml element. Container for Easy-specific information. (Required) The information in this group is essential for profiling the dataset in the Easy application. Container for dcmi metadata. (Optional) All elements of the http://purl.org/dc/elements/1.1/ namespace can be used. All elements of the http://purl.org/dc/terms/ namespace can be used. All elements defined in this schema that are extensions or restrictions of dc or dcterms elements can be used. Where applicable the use of the xml:lang attribute is recommended. Where applicable the use of the xsi:type attribute is recommended. See also: https://dublincore.org/documents/dcmi-terms/ https://dublincore.org/schemas/xmls/qdc/dcterms.xsd Some xml-elements from the dc and dcterms namespace have possible values for the xsi:type attribute that will be interpreted during ingest.

dc:identifier

can have an xsi:type from the "id-type" namespace. This will be interpreted as described there.

dc:language

can have xsi-type="dcterms:ISO639-2". It should then be formatted accordingly: ISO639-2. Both `B` and `T` variants are supported.

dc:format

can have an xsi:type="dcterms:IMT" if the value provided is valid according to that vocabulary

dcterms:type

can have an xsi:type="dcterms:DCMIType". Only values from the set {`Collection`, `Dataset`, `Event`, `Image`, `InteractiveResource`, `MovingImage`, `PhysicalObject`, `Service`, `Software`, `Sound`, `StillImage`, `Text`} are valid.

dc:license | dcterms:license

At most one license-node is allowed. If xsi:type="dcterms:URI" is provided, this URI should denote a known license.

Restriction on dcterms:description. If used, the descriptionType attribute is required. Use dcterms:description otherwise. Restriction on dcterms:created. Element value MUST conform to the dcterms:W3CDTF format. See also: http://purl.org/dc/terms/created Restriction on dcterms:available. Element value MUST conform to the dcterms:W3CDTF format. See also: http://purl.org/dc/terms/available Restriction on dcterms:audience. Element value MUST conform to the narcis:DisciplineType. See also: http://purl.org/dc/terms/audience Use as substitute for dcterms:accessRights. Element value MUST conform to ddm:EasyAccessRightsType. See also: http://purl.org/dc/terms/accessRights all dcterms relation types can also extend this linkedRelation, and take a 'href' attribute to include a webresource and a required scheme to indicate the scheme of the related identifier. If only the webresource is known, use @scheme=URL For the first five values, see https://easy.dans.knaw.nl/schemas/vocab/2017/identifier-type.xsd for the documentation on the allowed elements Use STREAMING_SURROGATE_RELATION for the location on the video streaming service. The URI of the relation. Any valid xml-element will do as a child of this element, as long as its namespace is ##other. If a schemaLocation is provided on the element, validating agents will validate the provided xml against that schema. The element may be complex. Detailed specification of the information that is essential for profiling the dataset in the Easy application. Use on dcterms:accessRights or members of its substitutionGroup. Unrestricted access. Deprecated, kept for backwards compatibility. Unrestricted access for all registered EASY users. Registered EASY users, but only after depositor permission is granted. The data are not available via Easy (they are either accessible in another way or elsewhere). Restriction on dcterms:subject. Use this instead of dcterms:subject when the subject-term adheres to a formal subjectScheme. The URI of the scheme. For a SKOS scheme, the ConceptScheme in the 'skos:inScheme' value is expected The URI of the value given in the text-node. A human readable title of the scheme used. Restriction on dcterms:temporal. Use this instead of dcterms:temporal when the temporal-term adheres to a formal scheme.