www.MarioStevenson.com

As many of you have read my last post on UPPF-RXSHTML, it appears the format has gained more ground. If any Programmer, Web Designer, or Web Programmer has reviewed W3C lately, they would have read some interesting updates on XHTML 5. It was so interesting that I had to review some of the content again to discover how much change was going to occur!

As it pertains to my current project UPPF-RXSHTML, wonderfully the new developments had involved XHTML. What wasn't expected was the transformation of UPPF-RXSHTML to something else. The new project exposes that with XHTML, the web can have uniformity in design. The new project falls under the codename: EUMMOD, and under this new project; It was also discovered that both PERL, and JAVA can, and would be used. The metadatabase design launches a new era of application intercapability.

Initially, when I had reviewed the SQL language for possible compatibility, the SQL language (as it is structured) appeared rather weak. EUMMOD in theory provides a new approach to information management. The first approach is that EUMMOD transforms the average in-home computer user into a database administrator. The second is that “websites” could start to disappear! However, in foresight, is there an application that would not re-write the mess that Microsoft went through with the IE monopoly?

EUMMOD also takes file sharing to another level, in the way that information is managed along with CRM. It brings into reality the truth about information access, management, responsibility, and assurance. EUMMOD changes the way that we think, and how we use information, by understanding how information is an asset to businesses, and the people who operate them. The every day person that you see, and meet on the street may have no clue or use of the knowledge in understanding information technology. But, when this knowledge is taught as an asset, EUMMOD without the use of SQL or other similar databases is even more powerful! With EUMMOD the every day person that you see, and meet on the street is not only a database administrator, but, also a database architect, and engineer.

Finally in written production is the Uniform Pseudo-Processor Format (UPPF) - Reserve Extensible SHTML (RXSHTML). It's the first uniform design for web-programming using HTML, or SHTML. First, I would like to state that the structure now presents a more defined use of standard HTML, and written in the perspective allowing for security to enter the web through Web Programming. While there are not many users that have the responsibility of managing, or implementing the code for websites. For the individuals that do, can now have a standard format for writing SHTML code for web pages, and web files.

The new code is being published under the EQEACT | Affiliate Consortium Publications Trust copyright, and is expected to make use of the code by pushing its relationship with other languages. The use of the format also explains in contrast XML was not needed as a language, and how UPPF-RXSHTML can be used as relational databases in a similar way that XML holds data. One of the many points that had brought Web Programming to surface was the need to serve many web pages, or web files. This was a form of organization that earned a certification (as a Web Programmer) at a tome when there was no large platforms such as Joomla, Drupal, Wordpress, nor B2evolution. Web pages, and web files were designed, and published as an "art." Still today, many web designers are busy at work creating new themes, or art for websites. However, websites generally contained limited amounts of data, and very rarely served data extending across domains. UPPF-RXSHTML had made relevant changes to much of the idea that XML is a needed platform.

XML versus UPPF-RXSHTML is not a competition, but rather two different relationships where both are coded to control the serving of massive amounts of information. XML has very limited use except where the passing of data is used, and implemented by applications. In an opposing light, XML has no standardized format as where in comparison, graphic programming languages try to maintain similar publishing formats with each program; A format like header, body, footer. Although, XML contains those features, they are translated, and later confused by another schema, making it difficult to follow-through. This is both the advantage, and disadvantage of XML.

UPPF-RXSHTML falls short in the similar manner to XML. It relies heavily on inherent technology. Both languages are front-end gateway mark-up languages. W3C allowed XML to have its own parser allowing for intimate communications to take place using XML. As long as the XML service can be executed in the background, or run silent. There's no interference, nor any needing to launch the browser to activate a remote procedure. We are also moving to create an UPPF-RXSHTML parser, and protocol in which the protocol is now codenamed: UPPF-RXSHTML Remote Procedure Call (UPPF-RRPC). The RPC will also make use of the internet to initiate intimate communications with applications.

Now tingling in my head is where UPPF-RXSHTML technologies are headed! At first creation, UPPF-RXSHTML was to be joined with PERL. However, to ensure UPPF-RXSHTML remains proprietary control over the technologies, it must be joined with JAVA in the creations of applications, and APIs. It demonstrates how far in remote communication technologies EQEACT™ is ready to move! Most of the EQEACT™ technologies are under the control of EQEACT™ | Hermetic Order of the Nano (EHON). Only in the future may we be able to discern the outcome.