nodeSolidServer / nodeSolidServer/node-solid-server
Use URI for X-Powered-By value
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.8k
- 分支
- 308
- PR 合併指標
- 30 天內沒有已合併 PR
描述
[The following is not strictly a node-solid-server issue but I think it can go a long way in setting it as a practice that other Solid server implementations or variations can follow suite. Eventually, this 'feature' can bubble up to the solid-spec - given that it is a common practice (aka sufficiently "incubated")]
The X-Powered-By header value eg solid-server can be more specific/unique. After all, which Solid server or which version? So, Solid servers should announce a URI as a value instead which can potentially be self-descriptive when dereferenced ie. another agent can find out about its capabilities, what specs it implements, making use of vocabs like DOAP stuff. This is beyond content or time negotiation etc.
Edit: granted that the string "solid-server" can mean that it is an implementation of the Solid spec, but that may be under the assumption that the server conforms to the latest state of the spec. While the clients could make that assumption, they can be mislead given what the server actually performs. So, the reality is that, there are indeed different versions of the application, as well as its conformance to the specs. All of that information and more can be discoverable through the URI.
eg curl -I https://linkedresearch.org/ldn/tests/ uses X-Powered-By: https://github.com/csarven/mayktso but it can also point to something more granular and actually return RDF.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
Issue 中沒有指出實作檔案或測試。先找出 node-solid-server 設定回應標頭 X-Powered-By 的位置,接著檢視現有註解與 Solid-server 慣例,再決定哪些 URI 與表示方式是可接受的。完成的標準是:該標頭一致地公開約定的自我描述 URI,且其行為有測試涵蓋。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, nodejs
- 領域
- backend
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100