Correct URI scheme to http

[zepheiryan]

Correct this property scheme to match all others in this file.

[github-actions]

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit f79e9dd. ± Comparison against base commit 42bd36e.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zburke]

Yay for consistency, and I will approve this simple PR on that principle and the fact that I recognize the users involved here and I know that you know what you're doing, but:

• Moving to http from https feels like a step backward. While this one https feels like the outlier, how do we know it's not the last Right Thing holding down the fort of authentication and data integrity? as noted below, this value looks like a URL but here it's just an identifier, so http vs https is insignificant.
• Is there a related Jira that describes why this work is necessary, i.e. countering the point above? That'll also provide visibility in Jira (where version information is tracked) into which release contains this fix. While we sometimes accept documentation changes that are unattached to tickets, it is expected that every code-change PR is linked to a Jira.

[pkjacob]

Yay for consistency, and I will approve this simple PR on that principle and the fact that I recognize the users involved here and I know that you know what you're doing, but:

• Moving to http from https feels like a step backward. While this one https feels like the outlier, how do we know it's not the last Right Thing holding down the fort of authentication and data integrity?
• Is there a related Jira that describes why this work is necessary, i.e. countering the point above? That'll also provide visibility in Jira (where version information is tracked) into which release contains this fix. While we sometimes accept documentation changes that are unattached to tickets, it is expected that every code-change PR is linked to a Jira.

Hi @zepheiryan
These are RDF IRIs defined in the builde vocabulary - https://bibfra.me/
IRIs are usually http.

This is what chatgpt says -

[zburke]

Thanks, @pkjacob , "RDF IDIs are identifiers, not necessarily fetch URLs" is exactly the kind of context I was looking for. The code in the file being changed here offers some misdirection (the variable containing this value is BFLITE_URIS) and the PR itself lacks direction (there is no explanation of why this change is happening, or a reference to a ticket).

If your team wants feedback from @folio-org/fe-tl-reviewers, please make sure the PRs provide us with enough context to evaluate them :) I trust you to validate what ChatGPT is saying, but on my own I wouldn't know if that summary was legit or a hallucination.