Skip to content

Atom validation: TG Requirement 28 too strict? #1210

@damienmulder

Description

@damienmulder

Running the validation on the following Atom https://service.pdok.nl/provincies/aardkundige-waarden/atom/index.xml results in an error:
Missing at least one link to a registry (a /atom:feed/atom:link element with attributes rel='describedby' and type='text/html').

According to TG Requirement 28

  • There has to be a link element referring to either the INSPIRE registry or a local schema
  • Such links should have rel='describedby' and type='text/html'

In our case we have multiple links.

<link href="https://service.pdok.nl/provincies/aardkundige-waarden/atom/ps-aw.xml" rel="self" hreflang="nl"></link>
<link href="https://service.pdok.nl/provincies/aardkundige-waarden/atom/index.xml" rel="up" type="application/atom+xml" hreflang="nl" title="Top Atom Download Service Feed"></link>
<link href="https://www.nationaalgeoregister.nl/geonetwork/srv/dut/csw?service=CSW&amp;version=2.0.2&amp;request=GetRecordById&amp;outputschema=http://www.isotc211.org/2005/gmd&amp;elementsetname=full&amp;id=f002bfc5-7d87-46b6-819e-8415422b65c9" rel="describedby" type="application/xml" hreflang="nl"></link>
<link href="https://www.nationaalgeoregister.nl/geonetwork/srv/dut/catalog.search#/metadata/f002bfc5-7d87-46b6-819e-8415422b65c9" rel="describedby" type="text/html" hreflang="nl" title="NGR pagina voor deze dataset"></link>

Note that we do have a link element with rel='describedby' and type='text/html' (.4th element)
Also, we have additional link elements with rel='describedby' but another type (type="application/xml", 3rd element).

The 3rd element seems to cause a validation error in the following code:
a.notExists("//atom:feed/atom:link[(@rel='describedby') and @type!='text/html']/@href","TR.missingLinkToRegistry");

However, TG Requirement 28 does not seem to require that all link elements with rel='describedby' should also have type='text/html'?

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready for testingSolution provided to reporter or developed & deployed in staging (or beta), waiting for testing

    Type

    No type

    Projects

    Status

    Staging: for acceptance

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions