No subject

Fri Feb 8 18:42:25 UTC 2008

---
XRDS-Simple provides a format and workflow for the discovery of resources m=
etadata, and other linked resources. As web services continue to grow, appl=
ications utilize a wider range of web services and resources across multipl=
e providers. XRDS-Simple allows providers to document their resources in a =
machine-readable way, which can be automatically discovered by consumer app=
lications.

The XRDS-Simple specification builds on top of existing practices first int=
roduced by the XRI community and later adopted and further developed by Yad=
is, a discovery protocol widely used by the OpenID community. XRDS-Simple g=
oal is to provide an easy to implement solution that is focused on solving =
the most common discovery use cases.

The goal of XRDS-Simple is to provide a lightweight version of XRDS that si=
mplifies the implementation of parsers while maintaining full compatibility=
 with XRDS and any XRDS-compliant parsers and resolvers. It also serves as =
an introduction to XRDS, giving implementers an upgrade path to other XRDS =
features when appropriate.

By defining XRDS-Simple, implementers can both declare the scope of their a=
pplication and capabilities, as well as perform tests to assert that their =
application is capable of processing input documents exactly as they were i=
ntended. This is of particular importance when processing documents with se=
curity or identity information, where misinterpretation of the document can=
 lead to a breach of security.
---

XRDS-Simple is being developed with the full support and participation of t=
he XRI TC, and members of the OpenID, OAuth, and DiSo communities. The spec=
ification is available at http://xrds-simple.net/core/1.0 and its discussio=
n maintained at the XRDS-Simple Google Group (http://groups.google.com/grou=
p/xrds-simple).

Feedback is greatly needed and appreciated.

EHL
http://www.hueniverse.com/hueniverse/2008/03/announcing-xrds.html

--_000_1CF0CFAED429364597531B94A3D5905C0FA1FC5B51manhattanhuen_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><a href=3D"http://xrds-simple.net/core/1.0">http://xrd=
s-simple.net/core/1.0</a><o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

I&#8217;m happy to announce that XRDS-Simple 1.0 Draft=
 1 was
released today. What started as an appendix to OAuth Discovery, quickly fou=
nd
life of its own in the form of a generic and simple-to-implement discovery
protocol for web services. The specification is more about an editorial rev=
iew
of existing standards than an invention of something new, but written to re=
move
the need to study other specifications.<o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>From the XRDS-Simple specification:<o:p></o:p></p>

<p class=3DMsoNormal>---<o:p></o:p></p>

XRDS-Simple provides a format and workflow for the dis=
covery
of resources metadata, and other linked resources. As web services continue=
 to
grow, applications utilize a wider range of web services and resources acro=
ss
multiple providers. XRDS-Simple allows providers to document their resource=
s in
a machine-readable way, which can be automatically discovered by consumer
applications. <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

The XRDS-Simple specification builds on top of existin=
g
practices first introduced by the XRI community and later adopted and furth=
er
developed by Yadis, a discovery protocol widely used by the OpenID communit=
y.
XRDS-Simple goal is to provide an easy to implement solution that is focuse=
d on
solving the most common discovery use cases.<o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

The goal of XRDS-Simple is to provide a lightweight ve=
rsion
of XRDS that simplifies the implementation of parsers while maintaining ful=
l
compatibility with XRDS and any XRDS-compliant parsers and resolvers. It al=
so
serves as an introduction to XRDS, giving implementers an upgrade path to o=
ther
XRDS features when appropriate. <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

By defining XRDS-Simple, implementers can both declare=
 the
scope of their application and capabilities, as well as perform tests to as=
sert
that their application is capable of processing input documents exactly as =
they
were intended. This is of particular importance when processing documents w=
ith
security or identity information, where misinterpretation of the document c=
an
lead to a breach of security.<o:p></o:p>

<p class=3DMsoNormal>---<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

XRDS-Simple is being developed with the full support a=
nd
participation of the XRI TC, and members of the OpenID, OAuth, and DiSo
communities. The specification is available at http://xrds-simple.net/core/=
1.0
and its discussion maintained at the XRDS-Simple Google Group (<a
href=3D"http://groups.google.com/group/xrds-simple">http://groups.google.co=
m/group/xrds-simple</a>).<o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Feedback is greatly needed and appreciated.<o:p></o:p>=
</p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>EHL<o:p></o:p></p>

<p class=3DMsoNormal><a
href=3D"http://www.hueniverse.com/hueniverse/2008/03/announcing-xrds.html">=
http://www.hueniverse.com/hueniverse/2008/03/announcing-xrds.html</a><o:p><=
/o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

--_000_1CF0CFAED429364597531B94A3D5905C0FA1FC5B51manhattanhuen_--