Propose content to put on https://interledger.org/ns#hasPaymentPointer

[michielbdejong]

No description provided.

[michielbdejong]

git clone https://github.com/interledger/paymentpointers.org
cd paymentpointers.org
[install jekyll](https://jekyllrb.com/docs/installation/macos/)
jekyll serve

And adding 7-ns.md to see if I can get the desired effect.

[michielbdejong]

Developing in https://github.com/michielbdejong/paymentpointers.org/tree/namespace-for-rdf

[michielbdejong]

OK, we're not there yet, but there is progress. :)

The formats that have been used so far for linking a webId to a PaymentPointer are:

1. pp:PaymentPointer (http, PascalCase)

<#me> <http://paymentpointers.org/ns#PaymentPointer> "$example.com" .

2. US:paymentPointer (https, camelCase)

<#me> <https://understory.coop/vocab/garden#paymentPointer> "$example.com" .
(here)

3. ITME:paymentPointer (https, camelCase)

<#me> <https://itme.online/vocab#paymentPointer> "$example.com" .
(here

4. pp:hasPaymentPointer (https, reified)

@prefix pp: <https://paymentpointers.org/ns#>.
<#me> pp:hasPaymentPointer [
    a pp:InterledgerPaymentPointer;
    pp:paymentPointerValue "$example.com".
  ].

5. ilp:hasPaymentPointer (https, reified)

@prefix ilp: <https://interledger.org/ns#>.
<#me> ilp:hasPaymentPointer [
    a ilp:InterledgerPaymentPointer;
    ilp:paymentPointerValue "$example.com".
  ].

In the light of interledger/paymentpointers.org#9 (comment), let's all switch to format 5?

[rubensworks]

Pinging @Falx and @MisterTimn, as they've been working on format 4 on our end. I guess it shouldn't be a problem to migrate to format 5. But I'd like to await their confirmation first.

@michielbdejong Are we certain that we can claim https://interledger.org/ns?

[Falx]

Fine for us!

[michielbdejong]

Creating a PR on https://github.com/interledger/interledger-website now.

[michielbdejong]

Staging it at:

• http://interledger-staging.pondersource.net:4000/ns#hasPaymentPointer
• http://interledger-staging.pondersource.net:4000/ns#paymentPointerValue
• http://interledger-staging.pondersource.net:4000/ns#InterledgerPaymentPointer

[michielbdejong]

PR created in interledger/interledger-website#47

[AlexLakatos]

Hey, I'm Alex and I'm the new Technology Lead at the Interledger Foundation. Can someone give me more context here, and maybe more specifically why interledger.org/ns has to be the URL?

[michielbdejong]

Hi!
Yes. We had originally proposed paymentpointers.org/ns but then Adrian proposed to use interledger.org/ns instead, because paymentpointers.org content is likely to be folded into interledger.org in the near future.

if payment pointers and SPSP are considered a sub-technology of Interledger then this makes sense.

Regarding the context, the easiest way to achieve interoperability in linked data, is if everybody uses the same predicates.
These predicates need to be dereferenceable URLs.
So whenever we choose a predicate to express a new type of relation (in this case, the relation between a Solid user profile and that user's payment pointer), we need to pick a URL for it.