Leo is a python-based open source outlining tool that allows you to do web snippet or common element sharing. It lets you manage any repeated element in a multiple documents in one place, but the beautiful thing is that it will export the common element *inline*, so that unlike Dreamweaver's lib (if I understand it correctly) you actually have a working HTML file that you can view in a browser.
It's mature, actively developed, cross platform, and quite useful when working with languages that don't have the concept of a subroutine, like XML/HTML, XSL, SQL.
This is a red herring. By open sourcing the.NET runtime with rotor (and ASP.NET to various MVPs), Microsoft has officially ceded the argument that open source is less secure. I can't see them making it any more without looking very bad.
"Not free as in beer or free as in speech, but free as in stolen." - me
I believe this was just a reference to the new indexing support... not native OLAP per se, just better support for implementing those types of apps in an RDBMS
I began working on a project for a consortium of peer-review journals to support online publishing last year, but the effort ran out of funding as we went to alpha. The toolkit we selected (OpenACS) supports the e-commerce and subscriber/anonymous access you describe, multi-journal ASP-style deployment, as well as customizable workflows for peer review.
I've written up a draft design document
here
It's a bit rough, but you should get a sense of what's the projects goals were.
If you'd like the code, I'd be happy to share it with you. I'd love to see it make it into production, and it's possible that the original sponsors might be able to make resources available to see it happen.
Click the mail link on my blog if you want to get in touch.
I agree with Bruce's math, but disagree strongly with his conclusions. I think that facial biometrics are one dimension of a multidimensional problem. A security analytics system must be put in place that knows
1) whether your name is on a list of known or suspected terrorists
2) whether your face is possibly on the list
3) whether you'd recently travelled to a country supporting terrorism
4) whether you'd recently entered the country
5) whether you're paying with cash, have a one-way ticket, etc. etc. etc.
This is the way some crimes are currently solved - facts are put in a crime computer, correlations are made and suspects come out. Any one dimension in this equation may be far less that 99% reliable, but together you have something that is both potentially far less intrusive than a national identity card, and far more reliable than what we have now.
Also, the false positive number you quote is misleading - how hard would it be to incorporate a feedback mechanism so that once an innocent person had struck a falso positive and you're cleared of being on the list (by going on a retinal scan or further standard means of verification), the security system would retain knowledge of that fact? I would strongly suspect that even disregarding algorithmic and hardware improvements, the awful numbers you accurately give for face recognition would fall rapidly.
So I definitely think there's a role for the technology, and the standalone strawman you poke holes in is not a real world scenario that proves otherwise.
Doesn't an open alternative to Passport already exist at www.xns.org? I'm familiar with what they're trying to do, but not why they haven't really gained much traction (besides a mention in the economist.)
Slashdot Mirror
I spent some time looking at it, but I couldn't figure what the advantage was over Yubnub ? ( except maybe the GUI+ the name brand/network effects )
this page has all the open source wiki pages, and this is the front page for the site.
Leo @ Sourceforge
It's mature, actively developed, cross platform, and quite useful when working with languages that don't have the concept of a subroutine, like XML/HTML, XSL, SQL.
This is a red herring. By open sourcing the .NET runtime with rotor (and ASP.NET to various MVPs), Microsoft has officially ceded the argument that open source is less secure. I can't see them making it any more without looking very bad.
"Not free as in beer or free as in speech, but free as in stolen." - me
I believe this was just a reference to the new indexing support... not native OLAP per se, just better support for implementing those types of apps in an RDBMS
If you'd like the code, I'd be happy to share it with you. I'd love to see it make it into production, and it's possible that the original sponsors might be able to make resources available to see it happen. Click the mail link on my blog if you want to get in touch.
John
Look at bitTorrent.
http://bitconjurer.org/BitTorrent/
It's not multicast per se, but seeks to avoid the horrific inefficiencies you've noted.
You could think of it as inspired by mojoNation, but it's a different architecture focusing on a different problem.
I agree with Bruce's math, but disagree strongly with his conclusions. I think that facial biometrics are one dimension of a multidimensional problem. A security analytics system must be put in place that knows
1) whether your name is on a list of known or suspected terrorists
2) whether your face is possibly on the list
3) whether you'd recently travelled to a country supporting terrorism
4) whether you'd recently entered the country
5) whether you're paying with cash, have a one-way ticket, etc. etc. etc.
This is the way some crimes are currently solved - facts are put in a crime computer, correlations are made and suspects come out. Any one dimension in this equation may be far less that 99% reliable, but together you have something that is both potentially far less intrusive than a national identity card, and far more reliable than what we have now.
Also, the false positive number you quote is misleading - how hard would it be to incorporate a feedback mechanism so that once an innocent person had struck a falso positive and you're cleared of being on the list (by going on a retinal scan or further standard means of verification), the security system would retain knowledge of that fact? I would strongly suspect that even disregarding algorithmic and hardware improvements, the awful numbers you accurately give for face recognition would fall rapidly.
So I definitely think there's a role for the technology, and the standalone strawman you poke holes in is not a real world scenario that proves otherwise.
Doesn't an open alternative to Passport already exist at www.xns.org? I'm familiar with what they're trying to do, but not why they haven't really gained much traction (besides a mention in the economist.)
Anyone know enough to compare the two?
Check out http://www.halcyonsoft.com/. They wrote ASP in Java - very portable.
From their home page:
"Are you looking to banish Code Red and Nimda forever by moving your ASP apps to a non-IIS server?
Instant ASP runs on ANY Java-enable platform from a Linux box to an S/390 and has NONE of the security vulnerabilities of IIS..."