[atlas-l] knuggets - first up, identity
jer
jeremie at jabber.org
Wed Jul 18 20:09:40 UTC 2007
>> This early knugget spec looks very interesting. I'm curious about
>> provisions for:
>>
>> - HTTPS with minimum cipher specification in URL
> So, since the only thing a Factory is publishing is something that
> is to be indexed and available in a public search engine, I can't
> justify any need for HTTPS. If I try to think about using it as a
> private search engine, well, I just have a hard time understanding
> about how a Factory would have your private data and be sharing/
> trusting it with a Collector/Broker... it just doesn't seem like
> something that is worth it or even hinting at encouraging.
>
> I can think of many compelling uses for a search which integrates
> public and private data. For example, personal medical issue and
> new treatment tracking, personal finance and investment tracking, etc.
>
> Holders/distributors of private information could easily set up
> their own Collectors, so only a Collector/Broker relationship need
> be secure (although the option of secure Factory/Collector data
> exchange can still be useful, as in the case of a trusted 3rd party
> Collector)
Yep, the C/B interaction should definitely have the option to be
secure (and is likely secure by default in most cases).
For Factories and the identity of the knuggets they produce/share,
I'd prefer to use only straight HTTP to build the first working
models. I have a hard time justifying HTTPS this early and until
we've all some real experience with a working model.
> Hacking something like TCP with UDP is quite frowned upon :)
>
> Oops, a TCP/UDP negotiation isn't what I was inferring, but rather
> content-centric networking, who's "founding principle is that a
> communication network should allow an user to focus on the data he
> or she needs, rather than having to reference a specific, physical
> location where that data is to be retrieved from." (quoted from the
> Wikipedia entry; see also Van Jacobson's Google Tech Talks speech
> entitled "A New Way to Look at Networking").
Gotcha! That model is definitely worth aspiring for and if you step
back from Atlas you'll see the entire thing revolves around focusing
on knuggets by their keywords and relationships, that is what
primarily identifies them. Basing the actual unique identifier on a
domain+hash that also happens to function as a retrieval method isn't
about a physical location as much as it is a very simple mechanism
for authority and verification.
Jer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikia.com/pipermail/atlas-l/attachments/20070718/cf8d426d/attachment.html
More information about the Atlas-l
mailing list