Add meta.xml filename to Darwin Core Text Guide #144
Comments
|
I would like to move this proposal and make explicit in the standard what is already in practice. It would be good to know, if possible, if there are any known exceptions to Darwin Core archives having the metafile named meta.xml. @timrobertson100 @MattBlissett Is this something known by GBIF? Does anyone have insights on publishing platforms that produce Darwin Core archives to check if there are any exceptions?
|
|
https://github.com/gbif/dwca-io/blob/master/src/main/java/org/gbif/dwc/Archive.java#L31 GBIF's DWCA library only recognizes |
|
I can confirm that the Specify 7 DwCA generator always uses |
|
Excellent, Thanks, Ben.
…On Wed, Sep 9, 2020 at 4:47 PM Ben Anhalt ***@***.***> wrote:
I can confirm that the Specify 7 DwCA generator always uses meta.xml for
the metadata file.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#144 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQ726NQMPSXJKYCAYFBQ3SE7LW3ANCNFSM4DYIPMKQ>
.
|
|
Confirmed that Symbiota uses the file name meta.xml as well. That should take care of the worry about backward compatibility and any obstacle to the change. |
tucotuco
added
Process - ready for public comment
and removed
Process - implement
labels
|
Would love to just do this, but it is a normative change and require public review. Removing from current milestone. |
|
Alright. Are we then considering all of the other RFC 2119 changes in the text, simple, and rdf docs to be only non-normative? I guess @timrobertson100 hasn't signed off on the text guide edits yet. |
|
I'll make an attempt at addressing #80 and then maybe @timrobertson100 can review all at once. |
tucotuco
added
Process - prepare for Executive review
and removed
Process - ready for public comment
labels
|
Implemented in a4b052f. Closing. |
The metadata file referenced in Darwin Core Text Guide needs a well known (specified) name, as it cannot be automatically discovered without unnecessarily adding another specification such as XML Catalog to the mix.
The well known name that is implemented in software is
meta.xml, and hence by the principle of specification-following-convention this should be added to the specification to give people reading the guide on its own an indication of what name they should give the file, without looking through the implementations to see what they variously support.The text was updated successfully, but these errors were encountered: