You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some guys at Solid are trying to get WebID to become an official recommendation, by creating a superspec that would encompass the old one and add a reference to JSON-LD, without bringing in breaking changes since it's overused:
For WebIDs without fragment identifiers, an HTTP request on the WebID MUST return the status code 303 See Other with a Location header URI referring to the Identity Document.
So if I understand correctly, to be in the clear, we'd have to create a resource of type foaf:PersonalProfileDocument for each WebID, and link it to the WebID via this header 303.
The text was updated successfully, but these errors were encountered:
I'd just like to clarify that, and as referenced in the first proposed WG charter, the Solid CG has only considered and proposed taking the WebID 1.0 ED as a deliverable (including editorial changes that are in https://github.com/w3c/WebID/ but not yet published). Alternative draft proposals to WebID are neither mature, implemented, or have "wide" consensus.
Some guys at Solid are trying to get WebID to become an official recommendation, by creating a superspec that would encompass the old one and add a reference to JSON-LD, without bringing in breaking changes since it's overused:
solid/solid-wg-charter#39
For the moment, it looks like this:
https://jacoscaz.com/WebID/superspec/webid.html
This sentence concerns us:
So if I understand correctly, to be in the clear, we'd have to create a resource of type
foaf:PersonalProfileDocument
for each WebID, and link it to the WebID via this header 303.The text was updated successfully, but these errors were encountered: