solid/specification

Issues

• Inconsistency in identifiers for apps: WebIDs and ClientIDs

  #463 opened 2 years ago
  36

• URI persistence, ownership, and representation management

  #462 opened 2 years ago
  0

• Bump Solid Protocol to 0.10 (was 2.0) for the indirection between WebID and Solid Profile

  #461 opened 2 years ago
  11

• Immutable Resources - create strategy and document best practices

  #459 opened 2 years ago
  1

• WebHookSubscription2022 subscription type

  #457 opened 2 years ago
  6

• Web of Things (WoT)

  #456 opened 2 years ago
  0

• Proposal: expose alternative query interfaces via `pim:storage`

  #455 opened 2 years ago
  10

• Create serialization format goals and strategy

  #454 opened a year ago
  3

• Consider application of Solid for (everyday) Emergency Management

  #453 opened 2 years ago
  1

• Unsufficient restriction over user supplied containment triples

  #451 opened 2 years ago
  3

• Contradicting requirements on contained resource metadata

  #450 opened 2 years ago
  2

• Impact of the storage description resource in v0.9.1

  #449 opened 2 years ago
  1

• Adding ACP to Authorization Mechanisms in Solid Protocol

  #447 opened 2 years ago
  24

• TR rights and license

  #411 opened 3 years ago
  0

• Include alternative views for PRs

  #410 opened 3 years ago
  3

• Make `#uri-slashes-hierarchical-identifier` a `spec::Requirement` in spec rdfa

  #406 opened 3 years ago
  2

• Document and inform about the level of adoption of Technical Reports

  #402 opened 3 years ago
  0

• There is no way specified for upward navigation.

  #400 opened 3 years ago
  0

• Proposal: Containment chain auxiliary resource

  #399 opened 3 years ago
  6

• Link to subject resource in get response of an auxiliary resource

  #396 opened 3 years ago
  1

• Issue with the scope of ?person in EXAMPLE: Applying an N3 patch.

  #395 opened 3 years ago
  2

• Processing HTTP messages

  #394 opened 3 years ago
  1

• Delegated computation (proposal)

  #393 opened 3 years ago
  4

• Server-side scripts registration

  #390 opened 3 years ago
  6

• Which documents are working copies and which static snapshots?

  #389 opened 3 years ago
  4

• Add a contributing guide to repository

  #387 opened 3 years ago
  0

• Allow clients to configure caching headers

  #385 opened 3 years ago
  2

• Implicit assumptions about status codes

  #384 opened 3 years ago
  2

• Implementation reports

  #383 opened 3 years ago
  2

• AuthN/AuthZ when accessing protected resource directly with a web browser

  #382 opened 3 years ago
  2

• How should %2F in resource URLs be interpreted?

  #381 opened 3 years ago
  3

• Why is Write on C enough for PUT C/R?

  #380 opened 3 years ago
  1

• Any resource server implementation is forced to couple authorization and storage

  #379 opened a year ago
  11

• Introduce different storage types

  #377 opened 3 years ago
  1

• Requirements for WebID document server

  #376 opened 2 years ago
  19

• Creating an LDN inbox in a uniform way

  #375 opened 3 years ago
  1

• Include "Success Criteria" (or "Exit Criteria")

  #373 opened 3 years ago
  2

• Mechanics to publish EDs separately from releases

  #370 opened 3 years ago
  5

• Specify resource naming constraints unambiguously

  #368 opened 3 years ago
  7

• Specification release automation

  #367 opened 3 years ago
  0

• Complete Self-Review Questionnaire: Societal Impact

  #359 opened 3 years ago
  0

• Servers responding to request targets using the asterisk-form or the origin-form

  #356 opened a month ago
  12

• Server Description

  #355 opened 3 years ago
  22

• Add references for "triple" (and "triple pattern") to the protocol document

  #348 opened 3 years ago
  7

• Use IRIs for resource identification

  #347 opened 3 years ago
  18

• Where to make write requests for resources that return 303 for retrieval?

  #344 opened 3 years ago
  10

• Specify existing practice for Container data about contents

  #343 opened 3 years ago
  12

• Content of Turtle and RDFa documents should be wholly and entirely preserved

  #342 opened 3 years ago
  29

• ETag might need a weak validator instead

  #340 opened a year ago
  3

• Server should partially encode Slug header values

  #339 opened 3 years ago
  1