jsonldからNamespace作れるように JSON.LD.Context に decoder 実装するとかあるんだろうけどちゃんと *非規範的* なHTMLドキュメントからowl turtle書いて読ませた方が数倍いい気がするし、なんなら go-fed/activity の `astool` にあるjsonld読ませた方が楽
go-fed/activity: ActivityStreams & ActivityPub in golang, oh my!
https://github.com/go-fed/activity
go-fed/activity: ActivityStreams & ActivityPub in golang, oh my!
https://github.com/go-fed/activity
- replies
- 1
- announces
- 1
- likes
- 1
> Yes, there is not normative machine readable document. Even if we had a maintained OWL document, it would have to be non-normative—having multiple normative references for the same terms would invite a host of inconsistencies and contradictions.
> Also, correct me if I'm wrong, but I believe that since the spec has reached TR and the WG is no longer active, there is no longer scope for major normative changes like the one—the CG is only empowered to add narrow extensions to the current spec.
Properly maintain OWL or other ontological information in machine-readable format · Issue #516 · w3c/activitystreams
https://github.com/w3c/activitystreams/issues/516#issuecomment-805915476
🦉はメンテされないしTRまで行ってしまったからもう改善する可能性はないみたいなニュアンスでいいのかしら
> Also, correct me if I'm wrong, but I believe that since the spec has reached TR and the WG is no longer active, there is no longer scope for major normative changes like the one—the CG is only empowered to add narrow extensions to the current spec.
Properly maintain OWL or other ontological information in machine-readable format · Issue #516 · w3c/activitystreams
https://github.com/w3c/activitystreams/issues/516#issuecomment-805915476
🦉はメンテされないしTRまで行ってしまったからもう改善する可能性はないみたいなニュアンスでいいのかしら