langreiter.com plain, simple: comments-2002-07-28

LANGREITER.COM plain, simple

START

INDEX

Sonntag, 28. Juli 2002

Did you believe the 0-intermediary lie today?

2002-07-28-iLie

Paul Ford: "A Semantic Web scenario. A short feature from a business magazine published in 2009." [ Ø HNS • ]

2002-07-28-google09

james 8182 days AGO
is anyone worried by the trend of applying standards upon standards upon standards? i.e. TCP/IP->HTTP->XML->RDL or whatever.

surely HTTP isn't the definitive protocl. it's can't be the best there will ever be. but how is anything better ever going to establish itself?

[create _pmode] 8182 days AGO
Nice article which opened my eyes. I saw the Semantic Web with its underlying technologies only as a new technology, but if you think it to the end you need much more privacy, because you probably want to give these information only to friends not to google (or another firm doing this step). At the other side you want better search engines for finding stuff which is more appropriate, e.g. music which fits your interests and so on.

@James: Each standard has its purpose. TCP for transportation, HTTP for delivering/storing things, XML for highly structured content without semantics (there is no link to a central concept taxonomy, e.g. a british gallon has another size as a american gallon i think, but you probably use the same tag-name) and RDF for clearifying relations between subjects and objects.

james 8181 days AGO
yeah, i realise that, but HTTP was not designed for the stuff it is being used for today (all it was really meant for was retrieval of text). I just worry that we're locked in to concepts like URL, HTTP and stuff, when there might be something better possible.

[create _pmode] 8181 days AGO
Okay, that's right. But what other concepts are there?

james 8178 days AGO
well... instead of using a request-based model, why not implement a network protocol based directly on message passing? It seems to me this could be done much more effectively and efficiently directly ontop of TCP, rather than via XML-RPC/SOAP over HTTP and Web Services.

I know we have stuff like RMI, regular RPC and that stuff - but why not provide a network layer for doing that unversally (a-la SOAP/.XML-RPC) but not have to have it piggy back HTTP?

That's just one example i pulled off the top of my head, the important thing is not what I can imagine, but stuff that I cannot imagine. If the world locks in to Web Services and everything running through modules on webservers, the horrendous architectures we'll end up with will be a nightmare, which might have been avoided by abandoning the current "HTTP-is-the-Internet" mentality of corporations and 'breakthroughs' in programming models.

Please log in (you may want to register first) to post comments!