Issue found on line 12454 of MergedAllCoreOntology-v1.5-2024-02-14.ttl about commoncoreontologies

[swartik]

Actually, that may be valid. From the definition of xsd:anyURI:

anyURI represents an Internationalized Resource Identifier Reference (IRI) ... as defined in RFC 3987 ...

From RFC 3987:

Systems accepting IRIs MAY also deal with the printable characters in
US-ASCII that are not allowed in URIs, namely "<", ">", '"', space,
"{", "}", "|", "\", "^", and "`", in step 2 above.

So it shouldn't necessarily yield a parsing error. But of course any program blindly fetching that URI literal is going to receive a 404. For what it's worth, Protege is smart enough to create a hyperlink only for the URL portion.

[cameronmore]

Thank you for pointing this out. This warrants including as a policy whether the accessed date should be preserved in another annotation, or the datatype be changed, or access date dropped.

Looking more broadly, the only other terms that mention the accessed date are dc terms bibliographic citation, in which the access date is of course warranted. This is the only case where an access date is used with the annotation cco:definition_source.

This also raises the issue of making sure that external URIs are routinely checked to make sure no terms point to dead links or links to webpages which have changed that do not reflect the definition.

@mark-jensen @johnbeve @mark-jensen