diff options
author | fr33domlover <fr33domlover@riseup.net> | 2018-07-06 23:29:06 +0300 |
---|---|---|
committer | bill-auger <mr.j.spam.me@gmail.com> | 2019-04-23 03:24:18 -0400 |
commit | 00add663c0228adef85b9cb71ba1192a4b5633b6 (patch) | |
tree | 889f38d51ad22af0e97e44d52c70cf07fec5d7dc | |
parent | 324c84ad5af77ada5440c4d22663c9e262380fd9 (diff) |
Suggest custom prefix URI
-rw-r--r-- | README.md | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -40,3 +40,15 @@ guidelines for the stuff that should be included in JSON-LD data sent between servers! For example, if we reuse `dc:author` from the Dublin Core ontology, eventually `ISSUE.md` should have an example for a JSON-LD issue object, to show the use of `dc:author` there. + +We may need a base URI for the ActivityPub extension. I suggest we add the +following mapping to the JSON-LD context: + +`"rfv": "https://peers.community/ns/repo-fed-vocab#"` + +And we can put in this namespace everything that doesn't come from other +places. Later that mapping could be changed into a remote context URL, but, +let's leave that cosmetic detail for later (also I must say, I don't like this +pretentious cramming of everything into 1 remote context like AP does; I like +the general RDF way where you just freely add namespace prefixes and use +whatever you like from the RDFiverse). |