Cart
[Home] [By Thread] [By Date] [Recent Entries]
Len > > Reliability and behavioral fidelity are twins. > This sort of thing really outs in real time > 3D rendering systems. The abstract idea of > namespaced composite vocabularies is great; > I am wondering if it is a concept that works > fine for data systems that do the sort of thing > relational dbs do with tables, but falls apart > the closer one gets to the renderer in the > pipeline. > Optimization and caching. That is the job of the renderer. I assume a renderer would not download a plugin each time a namespace qualified element were encountered. At least I know that my browser does not download the PDF or Flash plugin each time a document is encountered. Heck a really smart renderer might even optimize across downloaded plugins. I just want to create a level playing field in which namespace names can be used as URIs and in which any inefficiencies so created can be optimized away when something is demonstrated to be an actual rather than theoretical bottleneck (remember that Ma Bell said the Internet would never work on theoretical basis, perhaps it doesn't but nonetheless here we are.) Jonathan
|
