[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [higgins-dev] IDS Page
|
Hi,
Yes the XDI Engine (
http://wiki.eclipse.org/IdAS_XDI_Engine) is one possible implementation of the IDS concept. It exposes the functionality of IdAS at a so-called "XDI endpoint", which is basically a URI to which you can send XDI messages that correspond to IdAS operations. For example, you could expose an LDAP directory, and then access and modify the contents of that directory with XDI messages.
If you like to try that yourself, do this:
1. Go to
http://graceland.parityinc.net/xdi-messenger/XDIMessenger. This is a simple application for sending XDI messages.
2. Delete the text in the big textarea and paste the following XDI message into it:
=sender
$get
/
=(uid=saba,dc=parityinc,dc=net)
The indentation must be done with tabs, not spaces, or it won't work. It's the "X3 Simple" format, one of several possible serialization formats in which XDI messages can be sent.
3. Change the URL in the "Send to endpoint" text field to the following:
https://graceland.parityinc.net/xdi-idas/context-ldap/
The "XDI Engine" is deployed at this URL, waiting for incoming XDI messages.
4. Click "Go". This will send the XDI message to the XDI endpoint. This sounds a bit scary maybe, but it's nothing more than a plain HTTP POST.
5. As a result you should now see some data from the LDAP directory, i.e. some attributes and values of the uid=saba,dc=parityinc,dc=net entry.
Markus
On Sun, Apr 19, 2009 at 6:34 PM, Paul Trevithick
<ptrevithick@xxxxxxxxx> wrote:
This IDS term is very new, and a work in progress...
IDS (Identity Data Service) is a name for a set of web services bindings over the IdAS Java Interfaces. The IDS name was chosen to make a distinction between a true web service (IDS) and IdAS which despite having “Service” in its name, isn’t a web service.
We created this new umbrella term, IDS, so that we could talk about a set of services each using its own protocol. We have in Higgins, for example, created a prototype “XDI Engine” that lives under this umbrella. Sitting alongside the high-abstraction XDI protocol, we envision more purpose-built low-abstraction protocol bindings for IdAS such as Portable Contacts. Novell’s non-Higgins OTIS work is an illustrative example of a RESTful web service binding for IdAS. Over time we envision a number of these. We hope that low-abstraction web services (e.g. PoCo) will make Higgins IDS much more accessible and familiar to at least the web 2.0 crowd.
So that’s our intent.
As you point out, we need to fill in the content on the blank page. The XDI Engine work can be a starting point that we can reference from this blank page. [The XDI engine isn’t quite finished. My understanding, for example, is that authentication aspects are not complete. But it is a place to start.]
Does this make sense to folks? (esp. Markus)?
--Paul
