Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Gold/Mining/Energy : Canadian Diamond Play Cafi -- Ignore unavailable to you. Want to Upgrade?

To: WhatsUpWithThat who wrote (778)	4/14/2003 2:26:32 AM
From: E. Charters	Respond to of 16214

Right now XML passes through all containers anyway, So mixing the containers or mark-up code with it, is no never mind. If one exchanges xml with another browser, the xml containers that are not recognized are passed through.. except to netscape from microsoft.. as in here..<font color=purple> <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> <font color=black> Mixing mark up code with CSS is right now a problem. It is either one or the other. CSS just HTMLizes your XML anyway. The idea of CSS (style sheets) is to allow your data to be widely changeable in many pages by changing the style sheet once.. Or changing the XML for that page once, and possibly adding a new container rule to the style sheet. Right now good tools for working in style sheets so that you can do them WYSIWYG are not "out there". The pass throught concept allows one to send stuff off willy nilly, and allows later indexing action.. of course there should be some kind of mark-up really. Without a style sheet, you do not know how to display it. The Arena browser pioneered stylesheets, but was very buggy. The Amaya browser was/is fully XML compliant. Search the WWW3 consortium. http://www,google.ca Amaya works but is very slow. If one exchanges the rules for database, and display of your XML "standards" that you make up, either mutually or unilaterally, or the standards are exchanged automatically (your browser has a request to download a 100MB document of garbage.. do you want to accept it? yes, no, cancel) a-la diffie-Hellman key exchanges or some such process, then a fully XML compliant browser, such as the Jumbo Chemical Browser -- could really do neat things. The Jumbo browser will display, query, rotate a molecule, and its chemical properties and combinations in 3D. It is fully XML compliant. <font color=green> Display rules are a tad complex, so XML display standards or style sheets are not exchanged willy nilly. On the other hand, let's say we were geologists exchanging map data, mag data, and a core log. We would have a browser with all the data base standards set by the CIM and FGAC with style sheets for display of standard data. All we have to send it the data properly XML containerized, and it gets zapped up into our browser with the orebody in 3d, and the what-if's for metal prices and interest rates in a spread-sheet and/or chart below. Already, the Gnumeric spreadsheet is in XML. This is today. It just takes someone writing it and the display rules. Amaya or perhaps Netscape 7 would display it. <font color=black> I guess there has to be a merging between XML building tools and CSS or XML translators. What is needed is a tool that allows one to select the categories for XML you want, and to also set the CSS for the pagination and/or "typesetting" of the document, for either a new or a modified Style Sheet, at the same time as you semi-WYSIWYG edit. The idea that there could be a shareable typesetting language or formatting language that is written in XML is not that crazy. In a way, a document is a database of text. Where the text goes is free form, in that content is semi-removed from how the document is formatted. But the layer of formatting is just another database.. the style sheet is fixed, or semi-fixed for all fields or "instructions".. In other words, the HTML container <p> which means paragraph or line feed, is really just an XML content container stating that a data element of a paragraph follows. Saying there is a separation of content from formatting is just a convenient human abstraction. McCluhan would say the message and how it is conveyed are the same thing. My idea of an XML that allowed free form database and embedded formatting, as well as style sheets might work. The only problem is where the CSS might conflict with any embedded format. You could have a checker that looked at the construction of the data and let you know if the embedded formatting of then document conflicted with the style sheet. It probably would not unless the end product did bad nesting which is a no-no in XML. On the other hand if you had a XML container whose CSS called for a table, and you included my Roff command .table. then it would simply put one table inside the other, which is legal. It may not work, so merging CSS, with embedded formatting in an XML document would have to be worked out within the tool itself. EC<:-}