LID 2.0

From LID Wiki

1 Architecture
2 Further Simplification
3 Disambiguation
4 Vocabularies
5 Parameters

Architecture

For version 2, LID has been split into

Yadis discovery, and
a number of LID Services on top of it. This allows different LID implementors to easily support that subset of LID that they need for their application, and stop right there.

For example, a LID URL may or may not implement the LID Relying Party Service, depending on whether or not it wishes to serve different information to different clients. Similarly, a Personal LID representing a human may support the LID 2.0 vCard Service, but a LID representing a software agent likely will not.

More information at LID Services. Throughout LID, we follow the rules for LID URL Parameters and for LID_2.0_Canonical_LID_URLs.

[edit]

Further Simplification

A number of actions defined for LID 1.0 turned out to be unnecessary, by applying the concept of authenticated user more consistently. For example, sso-approved, message-approve and trackback-approve were eliminated for LID 2.0. Only sso-approve remains of this list.

[edit]

Disambiguation

The action parameter has been split into two:

lid-action for true actions such as sso-approve
lid-format for the format in which requested information shall be returned, such as mime:text/html. See [LID 2.0 Format Negotiation Service].

The new parameters also now start with the lid- prefix.

[edit]

Vocabularies

{tbd} Is FOAF the right format to support for social networking? Is it too complex?

{tbd} We need to nail down the use of XML Namespaces. The choices seem to be, using VCARDs as an example:

xpath=/VCARD/N/GIVEN: the first element in the XPath defines the vocabulary.
xpath=/VCARD:N/VCARD:GIVEN: we use qualified names for each element in the XPath, where the prefix corresponds to the prefixes defined in the document returned in response to the lid-meta=vocabularies request.

[edit]