Off topic: .data domain

I ran across this cool idea and thought if adopted may help the performance end of the program. I didn't have a clue as to what was the proper forum for this sort of thing so, here it is in general. If you would like to contribute your insights, follow this link and let us know what you think. http://tcrn.ch/zTLVvR

Find more posts tagged with

Comments

Mike Binks

I ran across this cool idea and thought if adopted may help the performance end of the program. I didn't have a clue as to what was the proper forum for this sort of thing so, here it is in general. If you would like to contribute your insights, follow this link and let us know what you think. http://tcrn.ch/zTLVvR

I'm sure the good folks at Logos will have noticed this and given it consideration. I, though, don't really see the point.

Beloved Amodeo

https://community.logos.com/discussion/comment/324691#Comment_324691

I'm sure the good folks at Logos will have noticed this and given it consideration. I, though, don't really see the point.

Hi Mike,

Some times my reach exceeds my grasp. [:$] As originally conceived, I hoped to stimulate discussion among those who really are equipped to understand the implications of such an idea. I was curious and hoped to learn from the experience of others better able to vote up or down. Thanks for your comment. Peace be with you.

JimTowler

https://community.logos.com/discussion/comment/324840#Comment_324840

I took a quick peek at the link above. Its an interesting idea, but its important to get a clear idea of what the question is, to which that might be the answer.

In the case of the Logos web sites, it would be up to Logos to define what data is on offer, and for what purposes. There is no need to define a new logos.data domain etc. Any data could be offered within some pageurl.xml within the current main Logos.com site, or any of the other Logos sites.

The real issue is not the WHERE (someplace.data), but instead the WHAT.

Its easy to say that data should be offered in .RSS or more generally, in .XML. But thats a bit like saying text should be writtin in ASCII. Its only the first step. What matters is the whole schema for any data formats that might need to be read/written by computer, rather than human.

I have the Wolrfam Alpha app on my iPad, and it can of course be accessed on the web. Its also one of the lookup engines that support Siri on the Apple iPhone 4S. Their goal of wanting to support all "facts" is great, and already the tools are amazing, and very useful. Also pretty neat for being "free". Its the shema ideas behind the .data concept that will drive the sharing of this kind of data. Its not clear to me that a specific top level domain adds anything of value, that can not be coded within the structures on exisiting sites.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/324840#Comment_324840

I'm sure the good folks at Logos will have noticed this and given it consideration. I, though, don't really see the point.

Hi Mike,

Some times my reach exceeds my grasp. As originally conceived, I hoped to stimulate discussion among those who really are equipped to understand the implications of such an idea. I was curious and hoped to learn from the experience of others better able to vote up or down. Thanks for your comment. Peace be with you.

Observation: Logos developers tend to not frequent General forum for discussion.

Apologies: personally do not follow shortened URL links since not know where the links go.

Searching internet for Data Domain found a company web site, which shows ownership by one of the primary enterprise storage vendors, who would be present at many developer conferences to advertise their capabilities.

The amount of storage that can be reused depends on the amount of data duplication (e.g. same email sent to many recipients could be stored once on a mail server instead of one copy for each user).

For resource files, suspect Logos already implements one form of data duplication since a master copy on Logos servers is downloaded by many users on a variety of devices. Logos does not need to have a copy of every resource file for every user. Notes and Highlighting are bit different since imagine most Logos users have different notes and highlighting so would anticipate smallish amount of data duplication. For Proclaim, suspect Logos has one copy of presentation that is collaboratively updated by various group members, which would be simplier than having a presentation copy for every group member. Logos wiki has history for each page, which could be stored as differences between pages vis storing full copies of each history version (storing delta differences is one way to implement data de-duplication).

One technical challenge for data de-duplication is accurately tracking all references to shared data. Only delete data when not being used by anyone anymore.

Keep Smiling [:)]