Yadis Services
From LID Wiki
History
When LID was first proposed at the beginning of 2005, URL-based identity was unheard of. So we made up protocols and terms, because there was nothing to build on.
Later, when Yadis came along and made LID discovery more powerful, what we used to call a "LID Profile" became what Yadis calls a "Service". Correspondingly, we have changed our terminology and use the term "LID Service" going forward.
Mapping
Within the Yadis Capability Discovery Document (also known as XRDS file), individual services can be specified. Each of those Yadis services supports one or more service types, and can be available at one or more URIs.
To map, each LID profile is mapped onto a Yadis service type. As LID URLs often support multiple profiles/services at the same service URL, the Yadis XRDS document generally contains either a single Yadis service element which supports multiple types (one for each supported LID Service), or multiple Yadis services at the same URL.
For all LID Services, we define the following default: if no URI element is given in a Yadis service declaration that supports one more LID service types, the URI is assumed to be the LID URL that was queried in the first place. (One of the consequences of this default is that hosting providers that implement the same LID profiles for all of their subscribers can generally share the same Yadis document among all of their subscribers).
LID Services
See LID Services.
![[LID enabled]](http://lid.netmesh.org/images/lid-relying-party-anonymous.gif)

