Enquiry #2737

Require the use of id attribute for MD_DataIdentification elements

Added by Ilkka Rinne over 4 years ago. Updated over 4 years ago.

Status:NewStart date:23 Mar 2016
Priority:NormalDue date:30 Mar 2016
Assignee:Ilkka Rinne% Done:

0%

Category:-
Target version:TG2.0 RC1

Description

By: Angelo Quaglia

Chapter/section: 5.2.4

Paragraph/table: TG Req.3.6 and side note

Type: te

Comment: "Both the fragment identifier in the URL and the id attribute in the MD_DataIdentification element are necessary to respect the adopted specifications. There is no discussion about the possibile root elements of the returned xml document, i.e. MD_Metadata or GetRecordByIdResponse."

Proposal: Make the fragment identifier and the id attribute mandatory.

Note the section numbers refer to version TG v2.0 RC1 (https://ies-svn.jrc.ec.europa.eu/attachments/download/1570/TG_MD_20_RC1_2016-02-29.pdf)

History

#1 Updated by Peter Kochmann over 4 years ago

  • Description updated (diff)

As discussed while the meeting last week the alternative containing the URI only will not demand an explicit id attribute. Therefore it isn't suitable to flag it as mandatory for all metadata. The mentioned side note will be integrated in a packed form into our proposal for adding that alternative.

#2 Updated by Angelo Quaglia over 4 years ago

As I mentioned in my comment, the id attribute and fragment identifier are not needed if the URL returns a MD_DataIdentification element without any additional wrapper.

Also available in: Atom PDF