Re: What is a WebID?

On Thu, Nov 9, 2023 at 2:17 PM Kingsley Idehen <kidehen@openlinksw.com>
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?
>

You said it yourself:

>  having a MUST for RDF-Turtle (solely) compromised a powerful
conceptual abstraction

> JSON and/or JSON-LD are the formats that developers will use because
there are a boatload of tools out their to aid their productivity.

to implement a specification requires Turtle, but most developers use
JSON(-LD), and the MUST precludes them or defines they must implement
conneg to turtle

This is why a respec is needed, to define webid without a media type
constraint (x a Agent) - superset
Then to define a subspec (webid-json(-ld)) that can be liberated of the the
requirement for tutle - even if some other subspec like webid-rdf requires
conneg & at least tutle, say in SOLID)