In selection reference object, do we want that to be an `URI` or `URL`?

[ahouseholder]

Extending a comment from #821.

SSVC/src/ssvc/selection.py

Lines 165 to 175 in 6dbe00d

	class Reference(BaseModel):
	"""
	A reference to a resource that provides additional context about the decision points or selections.
	This object is intentionally minimal and contains only the URL and an optional description.
	"""
	model_config = ConfigDict(extra="forbid")
	uri: AnyUrl
	description: str

Do we want that to be an URI or URL?

Originally posted by @tschmidtb51 in #821 (comment)

[ahouseholder]

I don't personally care. Whatever keeps us from having people starting a remark on the field with well, actually.... is my preference.

I can imagine a world in which we could put non-url'ed things in resources, for example:

{ "uri": "urn:isbn:978-0-321-71243-1#page=873", "summary"="CERT RMM TM:SG1.SP1 Prioritize Technology Assets provides a potential interpretation of the High Value Asset decision point" }

But will anyone want that?

(AnyUrl does not require any particular scheme or domain part, so my testing says it's ok with the urn:isbn example above.)

[j---]

Does using URI instead of URL let us replace bibtex in the documentation pipeline with URIs?

[ahouseholder]

Does using URI instead of URL let us replace bibtex in the documentation pipeline with URIs?

So right now these are scoped to the selection object, but one possible direction emerging from #832 could be that we actually want to allow for an optional reference list in the DecisionPoint data structure. If we were to do that, I could imagine that we might capture references specific to a particular decision point in that way. Then we'd need to adapt the markdown rendering helper that spits out the tabular & json examples of decision points to turn those into links in the docs. But that's a possibility. I'll spawn this into a new issue.