RE: In Solid apps, let’s stop using RDF terms that 404

Sorry I didn't make it yesterday due to a clashing overrun meeting. The 
consensus seems very reasonable. Hope to read the more structured 
version of it (like what others have mentioned). I also have the 
following specific comment.


On 5/22/25 08:06, Michiel de Jong wrote:

>
> For newly proposed terms let’s advise app devs and spec devs to 
> publish them at the same time they publish their app or spec, 
> using something like webId.org instead of leaving them undocumented 
> for months or years, stuck in unreviewed PRs or in unmaintained vocabs.


Do you mean to use webid.org (guess you meant w3id.org?) (or alike 
services) as the URL (domain part) for the new terms/vocabulary/ontology?

Probably useful to see some clarification:

What should be placed at the URL when accessing it?

Should there be an ontology / OWL file, RDFS specification, SHACL shape, 
or an HTML document?

If an HTML document *and* a specification are both required (or heavily 
suggested), are there any suggested hosting services that supports this?


E.g. W3C's PROV-O supports *both* HTML and RDF specification at its 
namespace https://www.w3.org/ns/prov#, differentiated by the Accept 
header of the request.

I'm aware Solid is able to convert between different RDF serializations 
with the same method, but HTML is a different thing.


Best,

Rui