- From: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>
- Date: Thu, 9 Nov 2023 16:47:45 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>, public-webid@w3.org
Hi Kingsley, do we actually still need to think in terms of documents. What if we removed the documents from the equation? URIs denote entities. When you resolve them you should get a representation of the requested partition/entity. What does the detour over the document/URL/address actually add? Provenance could be added to the delivered representation. Versioning info is mostly not existent. I see the necessity for the WWW, but not for the GGG. -- Sebastian On 11/9/23 15:16, Kingsley Idehen wrote: > > On 11/9/23 8:57 AM, Melvin Carvalho wrote: >> FWIW: when we defined WebID at TPAC, TimBL explicitly said no 303s. > > Because he knows what he is talking about, since he designed the > components that lead to the World Wide Web. > > An HTTP URI that names an Agent unambiguously simply needs a "#" > tacked on to it. > > You make the URI (pointer) from the Profile Doc URL (address). > > As I keep on trying to explain to you, right now the Web is full of > WebIDs that resolve to WebID-Profile documents using this importance > piece of Web magic. > > The whole thing "just works" and it's happening without or without a > WebID spec from anyone. > > ChatGPT and similar tools already understand this stuff too, so whom > exactly is some alternative spec going to bring on board? >
Received on Thursday, 9 November 2023 15:47:57 UTC