I'm not aware of any problem with the XPath, however, it is common practice for the value used to include the DataONE resolve service URL, for example:
The check currently performs an HTTP HEAD request on the URL, to see if it is resolvable. The DataONE resolve service returns an HTTP 500 (Server Error) status for any HEAD request, even if the URL is valid. This means that many DataONE documents will fail this check, even if the URL is valid.
For the check
ResourceDistribution
, the EML XPath used isI'm not aware of any problem with the XPath, however, it is common practice for the value used to include the DataONE
resolve
service URL, for example:The check currently performs an HTTP
HEAD
request on the URL, to see if it is resolvable. The DataONEresolve
service returns an HTTP 500 (Server Error) status for anyHEAD
request, even if the URL is valid. This means that many DataONE documents will fail this check, even if the URL is valid.A DataONE Redmine issue has been logged for this problem.