The decision has fallen to
PostgreSQL because of the XML capabilities.
Next will follow the
installation and the research into the
XML syntax.
http://virtuoso.openlinksw.com/wiki/main/, http://www.firebirdsql.org/, http://www.myqsl.com, http://www-306.ibm.com/software/data/db2/,
http://www.rpbourret.com/xmldbms/, http://www.postgresql.org/,
RDFa is a standard that allows to add meta data to html2 code.
check http://rdfa.info/ or http://www.w3.org/TR/xhtml-rdfa-primer/ for more details.
Swoogle is a semantic web search engine. Search for ontologies.
WordNet® is an online lexical reference system whose design is inspired by current psycholinguistic theories of human lexical memory. English nouns, verbs, adjectives and adverbs are organized into synonym sets, each representing one underlying lexical concept. Different relations link the synonym sets.
Wordnet of Princeton University, USA
pro xml:
- flexible
- redable
- compatible with many interfaces/apps
- commonly used/well understood
con xml:
- bloated
- slow
pro N3:
- small
- fast
con N3:
- inflexible
- hard to read
- not yet very common (yet)
Decision: XML/RDF
... and the xml parsing functionalities have been tested out. The next step is to define the xml schema with a XSD, DTD and do more research in RDF/Notation3
I have installed successfully php5 on my mac os x ppc server. It works fine and smoothly under port 8080.
I am not beginning to research the whole xml setup of php5 and how i should implement my project to make it successful
Yesterday I was in
Brick Lane with a good friend. As usual, the waiters stood in front of the door and tried to convince us that the restaurant we're standing in front of is just the right restaurant to go. And not only because of the free first drinks and the 20% discount. What none of the waiters knew is, I
checked google on my phone beforehand to check out
what the ratings of the restaurants are.
I explained, we had already decided on which restaurant we will visit. And we relied on the internet to the internet take this decision.
They then argued that they are aware that the others may have a better internet site but the curry is supposed to be better in their place.
What they didn't realize is that I was not talking about the website but about what *comments* former customers actually left on the respective restaurants. This has nothing to do with the restaurant's website nor with any city or restaurant guide. It's simply recommondations from former customers. Good
vs. not so good experiences written down on a seemingly independent website.
This finally made the waiters rethinking their strategy... or at least they stopped trying to convince us with specious arguments...