Wednesday, February 29, 2012

Json name spaces, a big topic currently

The issue is how can Json indicate the namespace where symbol definitions reside for any given transaction. he really boils down to finding the proper table to perform look up., the semantics do to go beyond that. Anything beyond that requires humans to agree on some semantics, I doubt we can avoid that.

Hence the reason I hesitate in jumping in, there has been a of of thought on the problems since 2006 and much of the discussion posted, a lot of issues discussed and I am better off reading the current state of the discussion before proceeding. Here is a good overview of naming.

URLs can uniquely identify a look up list, URLs are unique be we don't all have one. If my bot is roaming and want to look something up in its unique table, then it needs its own unique URL. Actually the best bet here would be for clients to obtain a unique hash which they can keep.

In the local case, he client just manages local name space for bookmarks, files, and names and places. Hence, he does not need prefix his url, the default local namespace is used. Maybe work on that?

1 comment:

Anonymous said...

[img]http://moomin-troll.narod.ru/xrumimages/c3.jpg[/img]


New to this scene, I was very hesitant of ordering but to be honest I got great support and advice on the products I was thinking of using. Had a read and knew what i wanted to gain and what to buy to do it. Really helped and starting to see and feel!

[url=http://yourpharmacydirect.com/at-Laurabolin-drug-profile-.html]laurabolin[/url]

[url=http://yourpharmacydirect.com/raAnastrozole-British-Dragon-.html]anastrozole[/url]

[url=http://yourpharmacydirect.com/raMethandriol-Dipropionate-British-Dragon-.html]methandriol dipropionate[/url]

[url=http://yourpharmacydirect.com/rbMethanabol-BritishDragon-.html]methanabol bd[/url]