Clarify protocol to use for URIs in EML annotations. (was: check link for qudt's hasUnit)

[twhiteaker]

Chapter 7 (annotations) includes this example:

  <propertyURI label="has unit">
    http://qudt.org/schema/qudt/Unit
  </propertyURI>

I think the URI should instead be http://qudt.org/schema/qudt/hasUnit, as in:

  <propertyURI label="has unit">
    http://qudt.org/schema/qudt/hasUnit
  </propertyURI>

Side question: Does it matter if it's http or https in those URI's within EML?

[gremau]

Looks like you are correct. I fixed this link in commit e75693e.

However - I'm leaving this open for the side question. I'm not actually sure if it matters whether URIs for EML annotations are referenced using http or https. QUDT uses http in its reference documentation, but https requests for the same URI also work fine. But, I suppose it could matter if the EML contains an http URI and the repository will only allow https requests.

Maybe @clnsmth or @servilla will chime in and we can establish some guidance.

[clnsmth]

Hey @gremau and @twhiteaker.

It's acceptable for legacy data to contain HTTP-prefixed URIs because these were standard practice before HTTPS became widespread. Changing all historical data can be a massive undertaking, often impractical or impossible. However, moving forward, using HTTPS URIs is the recommendation and best practice due to enhanced security, user trust, etc.

While old HTTP links might exist, many websites implement HTTP to HTTPS redirection (https://qudt.org/ does this). This server-side mechanism automatically redirects users from the insecure HTTP version of a site to the secure HTTPS version, ensuring a safe browsing experience even when encountering old links.

So the BP examples should probably use HTTPS.