Fwd: [apps-discuss] Approved: draft-ietf-appsawg-webfinger-18

FYI: The Webfinger technology is ready for approval by the IETF.

http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-18

For those unaware of webfinger, it started out as a per domain way of
getting an HTTP URL from an email address, and tying key value pairs to
it.  Over the years it has become a generic discovery mechanism for any URI
(including an HTTP URI) based on a well-known location (webfinger).  The
preferred URI scheme is the new acct: scheme which is used to indicate
"accounts at domains"

Webfinger introduces a mandatory serialization JRD (application/json+jrd),
which follows he Entity Attribute Value model of linked data.

*Differences between JRD and RDF data models:*

1. Each document can have at most one subject per document.

2. Although the subject is optional in JRD, bnodes are not explicitly
covered.

3. There are three named objects associated with a subject, links
(analogous to predicate / URI pairs) and properties (analagous to predicate
/ literal pairs), aliases (much like owl : sameAs)


4. The literals are restricted to string and null (RDF uses the xsd types)



5. Each link relation can have a type attribute, which is a MIME type

6. Each link relation can have a "title" which provides
internationalization e.g.:

     "titles" :
     {
       "en-us" : "The Magical World of Steve",
       "fr" : "Le Monde Magique de Steve"
     }

7. Each link relation can additionally have further properties which
describe the link relation (similar to RDF reification)

8. The link relations are an *ordered* list, ordered by preference


9. The properties object can contain at most 1 of each predicate, the links
object can have multiple predicates of the same type.  So for example if
telephone number were a field you could have at most one telephone number
literal.

10. The properties object will have a new registry maintained by IANA so
that predicates can be literals


Note: similar functionality can be achieved via the well-known location
void and sparql, but would involve another round trip.

---------- Forwarded message ----------
From: Barry Leiba <barryleiba@computer.org>
Date: 27 August 2013 16:11
Subject: [apps-discuss] Approved: draft-ietf-appsawg-webfinger-18
To: IESG <iesg@ietf.org>
Cc: "webfinger@ietf.org" <webfinger@ietf.org>, Apps Discuss <
apps-discuss@ietf.org>


IESG Secretary (bcc), with FYI to the webfinger and apps-discuss lists:

The subject draft is ready for approval, with all DISCUSSes cleared,
non-blocking comments reasonably addressed, and final reviews and
cross-checks done.  No RFC Editor notes needed.  Please send out the
approval notice, and thanks.

Barry
_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss