Allow alternative to content-negotiation via url property on Labels

[ThisIsMissEm]

Currently we require content-negotiation for labels, such that human readable and machine readable are on the same IRI.

We could support non-content-neg by using the url property from Objects in AS2, but this would come with a client complication of "how do I discover the JSON-LD when I've been given a html page URI instead of the label IRI.

[bumblefudge]

a html page URI instead of the label IRI.

Do you mean like each label sharing the same exact URL, i.e.
"url"="https://example.com/moderation.html"
versus each label having a specific IRI like
"url"="https://example.com/moderation.html#hate-speech"
? or do you mean where url is being used for something other than human-readable definitions of arbitrary keys? I'm not sure I understand the client complication here

[ThisIsMissEm]

Yeah, so rather than doing content-neg on the id / @id of the Label, you follow the url property instead. The logic here is that legacy systems should be able to support being a label provider (e.g., a CMS like wordpress), where content-neg may be difficult to implement. So having a path for them to provide human-readable labels makes sense.

[ThisIsMissEm]

But then given that human readable IRI, I'd need to specify support for back-tracking to the json-ld, perhaps using something like:

<link href='https://fires.example/labels/123' rel='alternate' type='application/ld+json'>

I also still need to work out the "profile" thing in json-ld, such that I could include a profile there.