OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xml-dev] XML for Video, Pizza Shops & TakeOut




John,

> At the risk of sounding a bit retro, how about some old-fashioned,
> well-proven technology? What's wrong with going for a little walk to find
> one? It worked when I was growing up.

At the risk of sounding a bit progressive, howabout the case where you land 
in a city, jump off a flight and go to your hotel. You're really hungry and 
feel like going to get a bite to eat but you have no idea where the pizza or 
any other food is because you've never been to that city or maybe you can't 
even read the local language.

For a few hundred bucks cost, don't you think it would be really cool to have 
a console in your hotel room to do the ordering from in a language that you 
understand.

I reckon that would be a really cool xml device. It could be revenue 
generating paying for itself earning money for every pizza ordered.

David

On Thursday 18 October 2001 18:31, Anderson, John wrote:
> At the risk of sounding a bit retro, how about some old-fashioned,
> well-proven technology? What's wrong with going for a little walk to find
> one? It worked when I was growing up.
>
> No matter how clever XML can be, it can't tell you whether the pizza is
> going to be good anyway (that would be taking the Sematic Web to it's next
> level. Can an Intelligent Agent taste the pizza? Would SML allow us to
> transmit odors over the internet?)
>
> Mind you, I live in the Netherlands now, and the pizza shops are a lot
> closer together.
>
> John
>
>
> _______________________________________________________
> John Anderson
> CTO BarbadosoftTM
> The XML Management Company
> +31 (0)20 750 7582 / +31 (0)6 65 347 448 / www.barbadosoft.com
>
> - putting the "X" in "XML" -

----------------------------------------
Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1"
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Description: 
----------------------------------------