Specifications

From Konfidi

Jump to: navigation, search

Konfidi re-uses specifications wherever possible. Only a few areas have required us to create our own specifications.

Contents

New for Konfidi

These need to be formally documented.

Trust Ontology

OWL specification for RDF

FOAF Server Protocol

API exposed through REST. Synchronization.

Trust Server Protocol

Internal, no public API

Frontend Trust Server Protocol

API exposed through REST

Email Clients

TODO: consolidate these pages

Documents

Internet (e-mail) Message

RFC 2822 (obsoletes arpa message RFC 822)

OpenPGP mail and news header - internet draft (expired, but with some adoption); a recent status email

MIME

RFC 2045 Part One: Format of Internet Message Bodies

RFC 2046 Part Two: Media Types (including multipart)

(Parts Three through Five are not directly applicable)

OpenPGP

RFC 2440 (builds on PGP RFC 1991)

MIME & cryptography

RFC 1847

Defines mime content types: multipart/signed and multipart/encrypted

MIME & PGP

RFC 3156 (updates RFC 2015)

Defines mime content types: application/pgp-encrypted,application/pgp-signature and application/pgp-keys.

RDF

w3c RDF

FOAF

Namespace & description at [1]; project at [2]

WOT

Namespace & description at [3]

XML

w3c XML

Web Ontology Language (OWL)

w3c OWL

Communication

HTTP/1.1

RFC 2616

HTTP Authentication

RFC 2617

Defines WWW-Authenticate: and Authorization: headers.

PGP Scheme for HTTP Authentication

RFC 2543 section 15

The SIP: Session Initiation Protocol RFC includes a section defining a PGP scheme for HTTP Authentication. The RFC was obsoleted by RFC 3261 but that removes the PGP definitions from SIP. But we are using the PGP scheme independently of SIP anyway. Why PGP scheme was removed from updated SIP RFC

REST (Representational State Transfer)

http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm

Personal tools