Rep (2) : simple information lookup services

[Ascan Woermann <[e-mail]>]

I take the liberty of forwarding this to the list:

> Ascan,
> 
> I looked at your proposal. It seems to be quite interesting, but I would make
> it even simpler. Typically:
> 
> 	Question = question-id,
> 		   target name (in UFN format),
> 		   attribute types sought.
> 
> 	Response = question-id (for linkage),
> 		   result:
> 			precise name,
> 			attribute values.
> 		   or error:
> 			solved name parts,
> 			problem explanations.
> 
> Indeed, we can even add some form of navigation control, also some
> "precise/loose" match property. But the generic idea is that this could be
> kept simple and short...
> 
> Christian Huitema

The UFN server in ISODE uses a similar protocol to the one you propose.
Whilst I agree about the simple and short, it would be difficult to offer 
the variety of services I had in mind with an entirely UFN oriented protocol.
For example:
1) find me the address of the distribution list(s) in the XYZ department.
2) give me the names of all secretaries in the XYZ division of the company -
	I'd like to constitute a private mailing list.
3) find me a restaurant in Antibes that serves fish
4) get me the telephone number of the head of department
	[search on Class=Person & Title="Head of Department OR Class=Role &&
	CN="Head of Department"]
The implications on the protocol are:
- the search criteria for the target object may contain object type, name
	and non-name search attributes - putting all of these in a UFN as
	a "purported" multi-AVA RDN is possible but might seem a little
	bizarre
- the target object search criteria may contain multiple conditions linked
	by AND/OR 
- there may be multiple entries in the result

Ascan