Re: urn:solid: for prototyping predicates

po 26. 5. 2025 v 9:33 odesílatel Christoph Braun <braun3@fzi.de> napsal:

> Dear all,
>
> On 25/05/2025 08:54, Melvin Carvalho wrote:
>
> čt 22. 5. 2025 v 15:32 odesílatel Christoph Braun <braun3@fzi.de> napsal:
>
> Dear all,
>>
>> [...]
>>
>> I would like to propose dogfooding our own technology.
>>
>> An app developer wants to build an app:
>> - they search the Solid Catalog (or similar to other vocab repos [1] )
>> for suitable vocabularies
>> - if they do not find a suitable vocabulary, they create a new vocabulary
>> - they use their Solid Pod to host the new vocabulary
>> - they Link it in/from the Solid Catalog for discovery
>> - so other developers can search the Solid Catalog, discover the
>> vocabulary and re-use it in their app
>>
>
> Just a small note on the idea of dogfooding vocab publishing via personal
> Pods. It’s a lovely ideal, but maybe a bit too heavy for many devs.
>
>
> It is lovely indeed.
> In particular, because every developer who wants to build a Solid app can
> go to solidcommunity.net and create a Pod there.
> Getting a (hosted) Pod is not a problem.
> If afraid of tying the vocabulary to a Pod Provider's domain, use w3id or
> purl to re-direct whereever the vocabulary is currently hosted.
>
> For development, just using a test account on solidcommunity.net is much
> more convenient than hosting you own local Pod server instance.
> From my project experience (see presentation at Solid World [1]), a
> developer of a Solid app creates a test account for testing their app at
> some point anyway instead of going through the hassel of learning how to
> setup a local Pod.
>

I would caution against this approach to hosting vocabularies.

- That site is not a CDN, it's a volunteer-run VPS. Heavy traffic can hit
its acceptable-use limits and add latency for many users.

- Using it for lots of vocabs becomes DDoS vector, which can impact regular
users

- If it runsout of funding, then there are no “Cool URIs.”

- Duplicate terms, extra inference. Two teams may mint different domains
for the same concept, forcing us to patch things up later with owl:sameAs
or other mapping logic.

- Privacy leakage.  Every GET request exposes client IPs, User-Agent
strings, and timestamps to a third party.

So it can be *one* approach, but it shouldn’t be the *only* one.


>
> Even experienced folks often don’t run their own Pod infra. [...]
>
> That's exactly the point here.
>
> Using a hosted Pod to publish your vocabulary is easy.
> *Lovely!*
>
> No need to use URNs instead of URIs.
>
> Cheers
> Christoph
>
> [1] https://youtu.be/fSRe-fyshmQ?si=fGNSRgaYyWHmBVRY&t=2779
>
>
>