Friday, July 30, 2004
Disambiguating People in Search
Semantic Negotiation: Coidentifying objects across data sources
Lyrics-For.com The lyrics archive
XML Development
Re: Semantic Web Hackings from Dan Brickley on 2000-12-29 (www-rdf-interest@w3.org from December 2000)
Semantic Web Naming and Reference
uname is a proposal by Sandro Hawke to add a predicate with domain of resource and range of string with semantics that the string unabiguously names the object.
Thursday, July 29, 2004
Object Coidentification on the Semantic Web
A System for integrating Web Services into a Global Knowledge Base
Reference By Description
Slashdot: News for nerds, stuff that matters
alphaWorks : IBM Semantics Toolkit
Magic Quadrant for Enterprise Firewalls, 2H03
Using Diffie-Hellman or other asymetric public/private key pair and encryption technique with JavaScript
In the JavaScript tutorial the authors make the following statements:
"Encrypting data before it is sent to you
Normally, this CANNOT be done with JavaScript using the internet alone. You can encrypt text at the user's end and unencrypt it at your end. The problem is that the user has to encrypt it with a password that you know so that you can unencrypt it. They would have to tell you by telephone or post. Alternatively, you could put the password in the source of the page and get the function to encrypt using that key. But this password would have to be sent over the internet in plain text. Even if you did encode it, it would not be too much work for a snooper to crack it. In fact, the encryption could even be broken with brute force techniques. So what do you do?
The best possible technique would be to create a symmetric encryption key using a twin public/private key pair as with techniques such as Diffie-Hellman or SSL, or use an asymetric public/private key pair and encryption technique as with PGP or RSA. The problem is that in order to prevent brute force cracking techniques, these require the browser to handle numbers as high as 2x10600 or higher. JavaScript is just not natively capable of working with numbers as high as this. As yet, I have found no solution to this, although on http://shop-js.sourceforge.net/ there is an algorithm for emulating large number handling, and an example of JavaScript powered RSA. The technique seems to work and takes only a few seconds to create keys, by using complex mathematics and algorithms (look at the source of crypto.js) to emulate large number handling.
Even so, if doing the equivalent of RSA (etc.), it is still not possible for the user to verify your identity as with SSL certificates, so it would be possible for a third party to inject their own code and have the information sent to them instead, without the user's knowledge. For the best security, stick to real SSL."
"Encrypting data before it is sent to you
Normally, this CANNOT be done with JavaScript using the internet alone. You can encrypt text at the user's end and unencrypt it at your end. The problem is that the user has to encrypt it with a password that you know so that you can unencrypt it. They would have to tell you by telephone or post. Alternatively, you could put the password in the source of the page and get the function to encrypt using that key. But this password would have to be sent over the internet in plain text. Even if you did encode it, it would not be too much work for a snooper to crack it. In fact, the encryption could even be broken with brute force techniques. So what do you do?
The best possible technique would be to create a symmetric encryption key using a twin public/private key pair as with techniques such as Diffie-Hellman or SSL, or use an asymetric public/private key pair and encryption technique as with PGP or RSA. The problem is that in order to prevent brute force cracking techniques, these require the browser to handle numbers as high as 2x10600 or higher. JavaScript is just not natively capable of working with numbers as high as this. As yet, I have found no solution to this, although on http://shop-js.sourceforge.net/ there is an algorithm for emulating large number handling, and an example of JavaScript powered RSA. The technique seems to work and takes only a few seconds to create keys, by using complex mathematics and algorithms (look at the source of crypto.js) to emulate large number handling.
Even so, if doing the equivalent of RSA (etc.), it is still not possible for the user to verify your identity as with SSL certificates, so it would be possible for a third party to inject their own code and have the information sent to them instead, without the user's knowledge. For the best security, stick to real SSL."
Why URLs are good URIs, and why they are not
Wednesday, July 28, 2004
Semantic World and Cyberspace - Principles of Boundaries in the Semantic Web
Gnowsis - SemanticDesktop.ChattyCBD
Joseki - The Jena RDF Server
SIMILE Project
Scalability Report on Triple Store Applications
Semantic Web enabled Web Services (SWWS)
Semantic Web Agents
Semantic Web Services Presentations
The Process Specification Language
The Process Specification Language: Around the World in 80 Axioms.
Preparing for Semantic Web Services
DIP Integrated Project
SEKT: Semantically Enabled Knowledge Technologies
SDK Project Cluster :: Welcome
WSML - Web Service Modeling Language
KnowledgeWeb (FP6-507482). Powered by ODESeW
Web Service Modeling Ontology
Install xfig on MS Windows
www.ps2pdf.com Postscript to Portable Document format converter
ILRT - Code Club - software quality assurance and staff development through software review meetings
ILRT - Code Club - software quality assurance and staff development through software review meetings
Tuesday, July 27, 2004
AtomEnabled.org
SharedID : Web Authentication Service
OWL-S 1.1 DRAFT Release
TeX2Word Software
The Not So Short Introduction to LATEX2e
The Not So Short Introduction to LATEX2e is a 143 page PDF introduction to LaTeX2e.
TexPoint - A Latex add-in for Powerpoint
OWL-S 1.1 Beta Release
