In respose to the discussion recently about modularizing the discovery
part of OpenID Authentication 2.0, I've put together a possible first
draft of a specification for doing service discovery using XRDS.
This document is really just the XRDS-related parts of Yadis but
refactored slightly.
In particular:
* XRI Resolution 2.0 is no longer required reading for implementors.
Instead, it defines its own proper subset of XRDS/XRD which is
completely defined within this document.
* The various sentences referring to authentication services and
specifically to OpenID, LID, etc. have been rewritten or removed.
My intention here is that the remaining parts of Yadis that are not
included in this new specification will become XRDS Discovery for HTTP
and HTTPS URLs.
It'd be cool if it could be restructured in such a way that XRI
Resolution 2.0 becomes only an informative rather than a normative
reference, but as it currently stands it's used in conjunction with a
couple of MUST clauses and therefore needs to be normative.
(I was going to put a more readable version of this on the wiki as well,
but sadly it seems that OpenID login isn't working today... for me, at
least.)
?xml version=1.0 encoding=utf-8?
?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?
!-- ?xml-stylesheet type='text/css' href='style.css' ? --
!-- * File Inclusion * --
!-- The parameter value is the name of the file to be included which can also be a URI.
In the case of local files the XML_LIBRARY environment variable provides a search
path of directories in which the file may be located. See section 4.1.2 of README --
!-- include=n/a --
!-- * Rigor Control * --
!-- Try to enforce the ID-nits conventions and DTD validity --
?rfc strict=yes ?
!-- * Rendering Control * --
!-- Put the famous header block on the first page --
?rfc topblock=yes ?
!-- Include boilerplate from Section 10.4(d) of [1] (Bradner, S., The Internet Standards
Process - Revision 3, October 1996.) --
?rfc iprnotified=no ?
!-- Use anchors as symbolic tags rather than numbers for references --
?rfc symrefs=yes ?
!-- Sort references according to symbolic tags - irrelevant if symrefs=no --
?rfc sortrefs=yes ?
!-- Items useful for reviewing document --
!-- Render cref information --
?rfc comments=no ?
!-- If comments is yes, then render comments inline; otherwise render them in an
Editorial Comments section --
?rfc inline=no ?
!-- Insert editing marks for ease of discussing draft versions.
Editing marks are strings such as 29 printed at the beginning of the blank line before
each paragrpah of text. --
?rfc editing=no ?
!-- Items useful when using xml2rfc to produce technical documents other than RFCs and I-Ds --
!-- Produce a private memo rather than an RFC or Internet-Draft.
The value of the PI is used as the title of the document.
Omits the topblock and standard boiler plate when . --
?rfc private=Draft ?
!-- Override the center footer string --
?rfc footer= ?
!-- Override the leftmost header string --
?rfc header= ?
!-- * Table of Contents Control * --
!-- Generate a table-of-contents --
?rfc toc=yes ?
!-- Control whether the word Appendix appears in the table of contents. --
?rfc tocappendix=yes ?
!-- If toc is yes, then this determines the depth of the table of contents. --
?rfc tocdepth=3 ?
!-- If toc is yes, then setting this to yes will indent subsections in
the table-of-contents. --
?rfc tocindent=yes ?
!-- If toc is yes, then setting this to no will make it a little less compact. --
?rfc tocompact=yes ?
!-- Affects horizontal spacing in the table-of-content. --
?rfc tocnarrow=yes ?
!-- * Format Control * --
!-- Automatically force page breaks to avoid widows and orphans (not perfect). --
?rfc autobreaks=yes ?
!-- Put two spaces instead of one after each colon (:) in txt or nroff files. --
?rfc colonspace=no ?
!-- When producing a txt/nroff file, try to conserve vertical whitespace
(the default value was no up to v1.30; from v1.31 the default is the current value
of the rfcedstyle PI).
Will default to (rfcedstyle) in future. --
?rfc compact=no ?
!-- If compact is yes, then you can make things a little less compact by setting this
to no (the default value is the current value of the compact PI). --
?rfc subcompact=no ?
!-- An integer hint indicating how many contiguous lines are needed at this point in
the output.
Can appear as many times as necessary in the source. --
!-- needLines=0 --
!-- * HTML Specials * --
!-- When producing a html file, use the image in this file. --
?rfc background= ?
!-- Automatically replaces input sequences such as |*text| by,
e.g., strongtext/strong in html output. --
?rfc emoticonic=no ?
!-- Generate mailto: URL, as appropriate. --
?rfc linkmailto=yes ?
!-- When producing a html file, produce multiple files for a slide show. --
?rfc slides=no ?
!-- When producing a html file,
