Issue 477

[evanp]

Close issue #477 by including sec: namespace, used for HTTP signatures.

(Note: I accidentally referenced #447; I'll fix that when merged.)

[gobengo]

Discussed in CG meeting today. @puckipedia raised a point that just adding the curie-prefix 'sec:' wouldn't be enough to make all the linked-data stuff work nicely

[16:55] <cwebber2> eprodrom: I realize that it does not also mean adding the aliases, I wonder if it's valuable to us to separate those two changes, first add the namespace then add the aliases, or must we do both simultaneously
[16:55] <cwebber2> puckipedia: I would like to point out there is a small issue with doing this and it is id values, eg sec:owner is id, so if you put a string in it it becomes a url
[16:55] <cwebber2> puckipedia: if you just use the prefix it doesn't do this
[16:57] <cwebber2> {"sec:publicKeyPem": "..."}
[16:57] <cwebber2> {"publicKeyPem": {"@type": "@id", "@id": "..."}}
[16:58] <puckipedia> {"sec:owner": "https://puckipedia.com/"} is either {"@value": "https://puckipedia.com/"} or an object {"id": "https://puckipedia.com/", "preferredUsername": "puckipedia"}

Conversatoin deferred but a good way to help would be to make a version of this PR that would resolve @puckipedia's concern.

Personally, I think that can be done separate from adding this curie prefix, which I support.