Another rdf example

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:contact="http://www.w3.org/2000/10/swap/pim/contact#">

<contact:Person rdf:about="http://www.w3.org/People/EM/contact#me">
<contact:fullName>Eric Miller</contact:fullName>
<contact:mailbox rdf:resource="mailto:em@w3.org"/>
<contact:personalTitle>Dr.</contact:personalTitle>
</contact:Person>

</rdf:RDF>

OK, the format is going to be hidden, and the user gets something like:

sendto:(about.person,some text right here)

I mean, all software is designed to get simplicity to the client, rdf no exception. All of their xml markup is under the covers. But marking up with xml still won't scale, Entity Attribute Value only makes matters worse.

So, we apply binary speed, recursive convolution, spin tables in and out at very high speeds, chip speeds if we can. XML won't cut it, binary nested order, vertical tables, serialized tables; whatever. These tables with integer formatted pointers, matchable links, fixed width overload identifiers, tight sqlite3 integration, open source, huffman encoded templates and pattern matching ==>> blazing fast ontology spinner.