@heluecht @jaywink What's the thinking RE: https://talk.feneas.org/t/what-is-the-correct-way-of-setting-the-ap-context/152

I had designed go-fed to always generate JSON-LD contexts where non-AxtivityPub vocabularies are aliased so that there's no property name and no type name collisions between different things.

I'd like to standardize on that so we can be future proof for further RDF compatibility.

Don't know if @Gargron and @nightpool and @kaniini@spacepub.space would be interested as well.

@heluecht @jaywink @Gargron @nightpool @kaniini@spacepub.space Alternatively, the cats already out of the bag, and since no one really parses JSON-LD at runtime, we'll just standardize on what's already out there, I'll change go-fed, and we'll live with the possibility of vocab collisions. Which avoids painful migrations.

@cj @Gargron @jaywink @kaniini @nightpool Friendica is indeed using a JSON-LD library to compact the JSON. So an invalid JSON-LD will lead to parsing problems.

@cj I'm not sure I understand the question. The PR linked doesn't look like valid JSON-LD at all. Valid JSON-LD would look something like:

{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"sec": "https://w3id.org/security/v1"
}
],
"sec:publicKey": {
"id": "http://localhost:8080/api/v1/ap/actor/lukas#publicKey",
"sec:owner": "http://localhost:8080/api/v1/ap/actor/lukas",
"sec:publicKeyPem": "-----BEGIN PUBLIC KEY...",
"type": "sec:PublicKey"
},
}