[uf-discuss] rel="payment" officially added to Atom Registry of Link Relations

[Joshua Kinberg]

> I there any kind of requirement as to what is at the other end of the
> rel-payment URI?

This is the original proposal that Robert Sayre and I completed and
sent to the Atom folks many months ago... it may also be the first
such proposal to include a reference to Wu-Tang Clan:
------------------------------------------------------------
== Registry ==

http://www.iana.org/assignments/link-relations

== Attribute Value ==

"payment"

== Description ==

rel="payment" indicates a URI where payment is accepted. It is meant
as a general way to facilitate acts of payment, and thus this
specification makes no assumptions on the type of payment or
transaction protocol. Examples may include a WWW page where donations
are accepted or where goods and services are available for purchase.
rel="payment" is not intended to initiate an automated transaction.

A link element with a rel="payment" attribute may exist at the
feed/channel level and/or the entry/item level. For example, a
rel="payment" link at the feed/channel level may point to a "tip jar"
URI, whereas an entry/item containing a book review may include a
rel="payment" link that points to the location where the book may be
purchased through an online retailer.

== Display Characteristics ==

End-user software could support rel="payment" by displaying a "payment
button" along with the content. Alternatively, content aggregators may
display a payment hyperlink containing the text specified in a
corresponding title attribute within the <link> element, for example:

<link rel="payment"
    href="http://example.com/c.r.e.a.m"
    title="give me the loot" />

May display either a payment button or a hyperlink containing the
text, "give me the loot."

== Security Considerations ==

The link element is subject to tampering and observation, as is the
linked resource. For that reason, implementations should clearly
signal the level trust and privacy a linked resource provides.  If
present, digital signatures provide authentication, message integrity,
and non-repudiation with proof of origin. Encryption provides data
confidentiality. Implementations should also consider the level of
confidentiality and message integrity provided by the transport used
to reach the payment resource.



On 2/2/06, Charles Iliya Krempeaux <supercanadian at gmail.com> wrote:
> Hello Josh,
>
> I there any kind of requirement as to what is at the other end of the
> rel-payment URI?
>
>
> See ya
>
>
> On 2/2/06, Joshua Kinberg < jkinberg at gmail.com> wrote:
> >
> > See message below... rel="payment" is now officially included in the
> > Registry of Atom Link Relations. Nice work to those involved!
> >
> > -Josh
> >
> > http://FireAnt.tv
> >
> > ---------- Forwarded message ----------
> > From: Michelle Cotton via RT < iana-prot-param at icann.org>
> > Date: Feb 2, 2006 1:38 PM
> > Subject: [rt.icann.org #4032] FW: Application for addition to Atom
> > Registry of Link Relations (link-relations)(completed)
> > To:
> > Cc: jkinberg at gmail.com, sayrer at gmail.com
> >
> >
> > Dear Joshua and Robert,
> >
> > The IESG has approved your request to add 1 new value to the Link
> > Relations Registry.
> >
> > We have registered the following:
> >
> > payment
> >
> > Please see:
> > http://www.iana.org/assignments/link-relations
> >
> > If there is a change in contact information, please send an e-mail to
> > iana at iana.org.
> >
> > Thank you,
> >
> > Michelle Cotton
> > IANA
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss at microformats.org
> >
> http://microformats.org/mailman/listinfo/microformats-discuss
> >
>
>
>
> --
>     Charles Iliya Krempeaux, B.Sc.
>
>     charles @ reptile.ca
>     supercanadian @ gmail.com
>
>     developer weblog: http://ChangeLog.ca/
>
>
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>
>
>