https://www.w3.org/ns/iana/link-relations/relation#payment |
|
http://purl.org/dc/terms/description
|
Indicates a resource where payment is accepted.
|
|
https://www.w3.org/ns/assignments/reg#spec
|
_:15
|
|
http://www.w3.org/2000/01/rdf-schema#label
|
payment
|
|
http://www.w3.org/2000/01/rdf-schema#definedBy
|
https://www.w3.org/ns/iana/link-relations/link-relations
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
This relation type registration did not indicate a
reference. Requested by Joshua Kinberg and Robert Sayre. 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 web page where
donations are accepted or where goods and services are available
for purchase. rel="payment" is not intended to initiate an
automated transaction. In Atom documents, 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.
|
https://www.w3.org/ns/iana/link-relations/relation#webmention |
|
http://purl.org/dc/terms/description
|
Identifies a target URI that supports the Webmention protcol.
This allows clients that mention a resource in some form of publishing process
to contact that endpoint and inform it that this resource has been mentioned.
|
|
http://www.w3.org/2000/01/rdf-schema#label
|
webmention
|
|
https://www.w3.org/ns/assignments/reg#spec
|
_:5
|
|
http://www.w3.org/2000/01/rdf-schema#definedBy
|
https://www.w3.org/ns/iana/link-relations/link-relations
|
|
http://purl.org/dc/terms/date
|
2016-04-19
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
This is a similar "Linkback" mechanism to the ones of Refback, Trackback, and Pingback.
It uses a different protocol, though, and thus should be discoverable through its own link
relation type.
|
https://www.w3.org/ns/iana/link-relations/relation#convertedFrom |
|
http://purl.org/dc/terms/description
|
The document linked to was later converted to the
document that contains this link relation. For example, an RFC can
have a link to the Internet-Draft that became the RFC; in that case,
the link relation would be "convertedFrom".
|
|
http://www.w3.org/2000/01/rdf-schema#label
|
convertedFrom
|
|
https://www.w3.org/ns/assignments/reg#spec
|
_:31
|
|
http://purl.org/dc/terms/date
|
2016-08-12
|
|
http://www.w3.org/2000/01/rdf-schema#definedBy
|
https://www.w3.org/ns/iana/link-relations/link-relations
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
This relation is different than "predecessor-version" in that
"predecessor-version" is for items in a version control system. It
is also different than "previous" in that this relation is used for
converted resources, not those that are part of a sequence of
resources.
|
https://www.w3.org/ns/iana/link-relations/relation#describes |
|
http://purl.org/dc/terms/description
|
The relationship A 'describes' B asserts that
resource A provides a description of resource B. There are no
constraints on the format or representation of either A or B,
neither are there any further constraints on either resource.
|
|
http://www.w3.org/2000/01/rdf-schema#label
|
describes
|
|
https://www.w3.org/ns/assignments/reg#spec
|
_:63
|
|
http://www.w3.org/2000/01/rdf-schema#definedBy
|
https://www.w3.org/ns/iana/link-relations/link-relations
|
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
|
http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
|
|
http://www.w3.org/2000/01/rdf-schema#comment
|
This link relation type is the inverse of the 'describedby'
relation type. While 'describedby' establishes a relation from
the described resource back to the resource that describes it,
'describes' established a relation from the describing resource to
the resource it describes. If B is 'describedby' A, then A
'describes' B.
|