Have ever thought of having .data domain quite equivalent to the .com, .gov and .org domains? If you think it’s an effort not worth trying then you might as well like to know what Wolfram, the Computer scientist has to say about it,
My concept for the .data domain is to use it to create the “data web”—in a sense a parallel construct to the ordinary web, but oriented toward structured data intended for computational use. The notion is that alongside a website like wolfram.com, there’d be wolfram.data.
If a human went to wolfram.data, there’d be a structured summary of what data the organization behind it wanted to expose. And if a computational system went there, it’d find just what it needs to ingest the data, and begin computing with it.
Weeding data from sites is not a big deal but it has to be sifted from complex hodgepodge of data files, feeds & database dumps. So ain’t it be good if there happens to be a way through which systems could retrieve data in a prearranged way?
As humans roll back to .com domain on their browsers, at the same time computers can visit the .data domains. It would be parallel to the ordinary web but oriented toward structured data intended for computational use.
Now some would argue that “/datamap.xml” file in root of web domains might solve the problem. But having a .data TLD would give a kick that is required to initiate the wave of ‘data web world’ – making it huge like the present web world – it needs a kind of momentum which is picked up by creating a separate set of .data site.
As a concept, it seems useful but what about the navigation part, I mean how would the spider (search engine) crawl o’er it is the thing that am wondering about.