nodeSolidServer / nodeSolidServer/node-solid-server
Support container updates
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.8k
- 分支
- 308
- PR 合併指標
- 30 天內沒有已合併 PR
描述
First off: this issue is different than creating LDPC on route to creating an LDP-RS as a member of an LDPC that doesn't exist yet. That particular case was covered in https://github.com/solid/node-solid-server/pull/513.
This issue is about creating or updating an LDPC (ie an LDP-BC, at the time of this writing). It will conform to LDP provided that the information in the update payload doesn't get in the way of changing the containment triples ( https://www.w3.org/TR/ldp/#h-ldpc-put-mbrprops ). So, for example, adding a label to a container (<> rdfs:label "Foo") would be fine, but PUT/PATCH that inserts or deletes ldp:contains relations should not succeed.
The use cases are generally about including additional "metadata" as part of the container description. It is partly discussed in https://github.com/solid/node-solid-server/issues/547 .
If this feature is implemented, https://github.com/solid/node-solid-server/issues/547 can be revisited, and as far as I can tell, the feature where updating a container's description through /.meta can be removed altogether (as interacting directly with the URI in question would be generally preferable.)
Edit: rel="describedBy" .meta in HTTP header can also be dropped as the interaction will only go through container URI, and that .meta will only be internal to the server.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
首先查看 LDP 容器更新需求以及 issue #547 中的相關討論,接著找出處理 LDPC URI 更新的伺服器進入點。確定 PUT 和 PATCH payload 如何處理 ldp:contains 三元組,以及如何處理其他中繼資料。完成的標準是:可以透過容器 URI 更新容器中繼資料,同時不允許變更包含關係,且不再需要所描述的 .meta 行為。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript
- 領域
- api, backend
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100