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 <https://www.marketdata.md/>*
>
> 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.
>
>
>
> [image: image.png]
>
> https://github.com/solid-lite/urn-solid/wiki
>
> Best
>
> Melvin
>

Received on Thursday, 22 May 2025 12:15:09 UTC