Post APX6zKvhMsYYRSNRQW by simongray@indieweb.social
 (DIR) More posts by simongray@indieweb.social
 (DIR) Post #APX6zKvhMsYYRSNRQW by simongray@indieweb.social
       2022-11-12T09:39:43Z
       
       0 likes, 0 repeats
       
       How come the #JSONLD @context value seems to imply a final hashtag rather than just include one explicitly...? I thought the @context was analogous to an #RDF namespace.So would a JSON-LD context *only* work with RDF namespaces that use a hashtag—as opposed to e.g. a forward slash—as the final character of the namespace?... e.g. looking at https://www.w3.org/TR/activitystreams-vocabulary/ every use of @context omits the final hashtag, but the spec clearly expects them there for the fully realised URIs.
       
 (DIR) Post #APX6zLSfOIva5hnloW by valerauko@pawoo.net
       2022-11-12T16:29:04Z
       
       0 likes, 0 repeats
       
       @simongray i think it's a w3 convention thing rather than json-ld itself. for example the ostatus and toot namespaces explicitly include the # in the end
       
 (DIR) Post #APX78mblpSo4tLYniq by valerauko@pawoo.net
       2022-11-12T16:30:44Z
       
       0 likes, 0 repeats
       
       @simongray ah it's here included at the end of the `as`: https://www.w3.org/ns/activitystreams#h-introduction
       
 (DIR) Post #APX8xE7LvL7EdywxGa by simongray@indieweb.social
       2022-11-12T16:51:04Z
       
       0 likes, 0 repeats
       
       @valerauko Hm... confusing...
       
 (DIR) Post #APX9ogNZZvD9dy1heC by simongray@indieweb.social
       2022-11-12T17:00:42Z
       
       0 likes, 0 repeats
       
       @valeraukoBut still, if it's written in an official @w3c recommendation, the JSON-LD standard must assume that this hashtag is—at least occasionally—implicit inside a JSON-LD @context, which in turn would break compatibility with quite a few RDF namespaces that use a / rather than a # as the separator.