> understand the semantics of the information being exchanged and act
> on them accordingly.
My understanding is the basics of HTTP and REST (i.e. representations
of state and state machines) could accomodate machines to increasingly
interpret semi-formal, commonly accepted representations of
information, e.g. maps, calendars, events, contacts, purchase orders,
etc. I would agree a deeply automated intelligent "semantic web" is
at best a long way off. There are a lot of useful capabilities along
the way I would think.
This approach seems to have more documented principles than doing the
same with SOAP, WS-*. Although similar ideas could be mapped onto
those, just as you could map them onto other systems such as JMS or
Jabber or SMTP or... The question then is which of those mappings are
worthwhile.
-Patrick
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
