Re: Trade-offs Matrix: Solid Term Definition Strategies

Melvin, my thoughts:

 

It looks like your definition of urn:solid:diagnosis has ‘embedded’ or predefined semantics, and everyone building must agree on the meaning?

 

I think the myth of IP privacy only works in hacking movies.

 

Your device has your IP, the WiFi has the IP, the network provider has the IP, any DNS resolution has an IP, if you go on a mobile phone walking in a city, the mobile provider can pinpoint your location within 3 sqm.

 

You will not get away from the possibility of pattern matching – your authentication messages will follow a pattern (even if you upgrade to http3, it will statistically start having ‘some duration’), traffic for applications will also have certain order ( you will be able to spot who are the clients and who are the sources ). 

 

But you’ll need to have sufficient infrastructure and time for that – a network sniffer at scale is expensive and hard to place, but if someone needs to find a source, nothing is stopping them; the only ‘full privacy’ scenario is “no network”.

 

You also must consider that any hospital/clinic/doctor asking for Melvin’s pod access will do it over a network that sits between the 2 parties (maybe more, depending on the actual solution topology).

 

If you have a disconnected app – then not sure what the use is for solid, which are “decentralised data stores for the Web” (https://solidproject.org/about).  

 

 

___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era

 

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thursday, 22 May 2025 at 13:15
To: Joshua Cornejo <josh@marketdata.md>
Cc: public-solid <public-solid@w3.org>
Subject: Re: Trade-offs Matrix: Solid Term Definition Strategies

 

 

 

čt 22. 5. 2025 v 13:48 odesílatel Joshua Cornejo <josh@marketdata.md> napsal:

Hi Melvin,

 

IMHO for Global Standard:

 
“encourages rapid prototyping” & “simple for developers” there can always be a section of an ontology for *.unstable or *.beta – further, you should provide examples as JSON-LD to encourage adoption (not everyone will understand RDF)
“privacy preserving” – no idea what is the criteria for saying this?
 

Good point — to clarify, by “privacy-preserving” I just mean:

If a term like https://w3id.org/health/terms#diagnosis gets dereferenced, it might ping GitHub (Microsoft), revealing metadata like IPs or usage patterns — even if the data stays private.

With something like urn:solid:diagnosis, there's no network lookup at all. So nothing leaks unless you choose to share it.

Hope that makes sense :)

 

 
“works offline” – sure they do, you can download a public ontology (they usually are shared because they are stable).
___________________________________

Joshua Cornejo

marketdata

smart authorisation management for the AI-era

 

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thursday, 22 May 2025 at 12:15
To: public-solid <public-solid@w3.org>
Subject: Trade-offs Matrix: Solid Term Definition Strategies
Resent-From: <public-solid@w3.org>
Resent-Date: Thu, 22 May 2025 11:15:06 +0000

 

Hi all,

Following up on recent discussions, here's a draft summary of the trade-offs between different strategies for defining RDF predicates in Solid apps — particularly useful during early-stage development and prototyping.

 

https://github.com/solid-lite/urn-solid/wiki

Best

Melvin