RE: Matter of DN and what's possible

Im not reading it much (being far to ignorant).

 

But, I do see folks operating at two different levels/planes. These are never going to mesh.

 

For Kingsley, "deferencing" is not one thing. Its a function pointer. Sometimes it means GET, other times it means describe (and other verbs).its a polymorphic casting operator (that can also mean construct, ill guess).

 

For Henry, it means what he taught me (simply): get a stream, parse it, query it.

 

One is semantic web as conceived; the other is elementary semantic web technology. The latter should be piss simple (but it in fact has its own endless fuss).

 

Im guessing this is the root of the discussion about whether the va should be a linked-data-UA, or a stream/parse/query-UA. The former is a bit like an XRI/XDI client. It envisages an enterprise world of MANAGED data graphs, superimposed over the usual stuff. These goes beyond merely spying on the web for correlations (for policing agencies, over the last 10 years), and one now envisages is DRIVING a new class of application.

 

If I had not seen for my own eyes that the classical, non-enhanced browser can be an effective linked-data-UA, Id be going for stream/parse/query. But, if we want to match internet2 type expectations, its obvious which represents a major leap forward. And again, the real qualifier is: its there working. That the RDFa document is delivering the SSL client is just cute, with objects of class RSAPublicKey "acting to key/arm said client code, once instanced in the js engine".

Received on Tuesday, 10 January 2012 01:49:11 UTC