[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: RDDL (was RE: Negotiate Out The Noise)

• To: "Bullard, Claude L \(Len\)" <clbullar@i...>
• Subject: RE: RDDL (was RE: Negotiate Out The Noise)
• From: "Leigh Dodds" <ldodds@i...>
• Date: Fri, 18 Jan 2002 17:17:34 -0000
• Cc: <xml-dev@l...>
• Importance: Normal
• In-reply-to: <2C61CCE8A870D211A523080009B94E4306DF629A@HQ5>

> So far so good.  I also asked, what about other solutions? 
> How does RDDL compare to web service discovery systems? 

Well I'll have to pass on web service discovery systems, as 
I've not given them a great deal of attention. These are 
the alternatives I've seen mentioned here, and during 
the initial discussions:

1. Forbid Anything
2. XLink
3. RDF
4. Topic Maps
5. XHTML

I don't think (1) will work as I think time has shown that 
people expect *something* at an NS URI. (2, 3, 4) 
allow the possibility of human readable documentation to 
be associated, but is not immediately accessible. i.e. there's 
an extra software component needed to allow people to 
get something useful. However they seem flexible solutions 
for communicating with machines. (4) isn't so good for machines.

So, IMO, RDDL offers a reasonable compromise between providing 
content for both consumers.

Not sure if this answers you question satisfactorily.

Cheers,

L.

• Follow-Ups:
  • Re: RDDL (was RE: Negotiate Out The Noise)
    • From: "Jeff Greif" <jgreif@a...>

• References:
  • RE: RDDL (was RE: Negotiate Out The Noise)
    • From: "Bullard, Claude L (Len)" <clbullar@i...>

• Prev by Date: Re: RE: RDDL and XML element behaviors was: Re: RDDL (was RE: Negotiate Out The Noise)
• Next by Date: Re: RE: RDDL and XML element behaviors was: Re: RDDL (was RE: Negotiate Out The Noise)
• Previous by thread: RE: RDDL (was RE: Negotiate Out The Noise)
• Next by thread: Re: RDDL (was RE: Negotiate Out The Noise)
• Index(es):
  • Date
  • Thread