New Work Item: Application Capability
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 活発
調査の方向性
まず CONTRIBUTING.md の新しい作業項目に関するガイダンスを確認し、次にリンクされている Application Capability の提案と、PR #805 を含む 2026-07-15 の会議議事録を読んでください。提案のスコープが確定し、コミュニティからのフィードバックに対応し、その場と次のステップについて合意されていれば完了です。
索引モデルが issue の本文から書いたものです。
説明
As per https://github.com/w3c-cg/solid/blob/main/CONTRIBUTING.md#new-work-item-proposal
and following the action of initial presentation/discussion in 2026-07-15 Solid CG meeting (minutes under review).
Application Capability: https://dokieli.github.io/application-capability/
Editors/Authors: Sarven (@csarven) and Virginia (@VirginiaBalseiro)
- Explain what you are trying to do, using no jargon or acronyms.
We want to communicate the capabilities and requirements of an application so that it can be used by other applications or servers to make more informed decisions.
- How is it done today, and what are the limits of the current practice?
To the best of our knowledge, information with regards to an application's capabilities and requirements is scattered across mechanisms that each cover a slice, such as web app manifests, browser permissions, and security policies. None of them lets a server or another application (e.g., an Web OS, launcher, catalogue, resource manager, etc.) discover what an application supports or needs. The result is hardcoded application lists, manual catalogue updates, and overly permissive policies.
- What is new in your approach, and why do you think it will be successful?
An application publishes one discoverable, structured description of its actions, supported resource types, how it can be invoked, and what permissions it needs, e.g., from a web user agent or server. It reuses existing vocabularies and notification mechanisms as much as possible.
There is a need in the community, with implementers already tackling parts of the problem outlined in Application Capability, and there is some implementation experience. This spec tries to bring prior discussions and work together (see CG minutes for background references) into something coherent that we can use.
- How are you involving participants from multiple skill sets and global locations in this work item? (Skill sets: technical, design, product, marketing, anthropological, and UX. Global locations: Africa, the Americas, APAC, Europe, Middle East, Antarctica.)
The authors/editors are based in Europe and have some familiarity with the web =) For more details, see their WebID, CV, etc.
- What actions are you taking to make this work item accessible to a non-technical audience?
We have tried to explain the problem space and related work as clearly as possible. Some of the use cases in the specification are written from the point of view of a user (with different abilities or roles).
We are available to answer questions, revise, and join meetings that have better open lines or access to a non-technical audience.
We also want to note that this work is not strictly limited to the Solid community. We have considered sharing it more widely with other groups and initiatives in W3C, e.g., Web Application(s) (Security) WGs, WICG, and elsewhere (see "related efforts" in the spec) that may be equally or more appropriate.
We want to make sure this is compatible with Solid and related efforts, and to incubate and gather experience here, while remaining open to migrating the work to another venue as we better understand where it can best mature and be useful in different context.
- 主要言語
- HTML
- スター
- 563
- フォーク
- 113
- 平均マージ
- 5日 16時間
- マージ済み PR（30日）
- 3
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
solid/specification のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
solid/specification#804 · コメント 9 件 · リアクション 2 件 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 20/100
solid/specification#799 · リアクション 1 件 ·
-
topic: resource access
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
solid/specification#797 · コメント 4 件 · リアクション 2 件 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
solid/specification#788 · コメント 4 件 · リアクション 1 件 ·
-
難易度 5/5 1週間以上 初心者へのやさしさ 38/100
solid/specification#787 · コメント 19 件 · リアクション 10 件 ·
solid/specification の issue をすべて見る
似ている issue
-
agent-butler-finding chore
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
jordansmall/spindrift#5575 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
[workshop-sim] Improve: Add verifiable checkpoint and bridge to Step 5 (What Are Agentic Workflows?)オープンfeedback simulation workshop
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
githubnext/gh-aw-workshop#4715 ·
メンテナーはふだん 1 日以内に返信
-
spec: discovery input example can contain multiple aliases for one parameter, with no canonical oneオープン
難易度 1/5 1時間未満 初心者へのやさしさ 95/100
x402-foundation/x402#3841 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 95/100
datawhalechina/deepagents-in-action#157 ·
メンテナーはふだん 1 日以内に返信