SI
SI
discoversearch

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 (774)4/13/2003 1:59:32 PM
From: E. Charters  Read Replies (1) | Respond to of 16214
 
You are around all the points, and what is more impressive is you have no typos, no bad grammatical errors, and your text is properly paragraphed. I can see no way I could win an argument with that kind of imposing presence.

I take all your distinctions. What I am saying is that we should SHARE documents on the web and in other MEDIA, in common FORMATS. Document sharing as Tim Berners Lee pointed out so artfully by WWWing it, is best achievable by a common display format and some common display software.

Where XML would come in is to build a common mark-up language for displaying text. Why not? I know it is a database language, but try this on. <paragraph> <indent3>
<tabindent2> If the containers can be database they can be format instructions too, can't they? Right now we translate the XML to HTML by CSS which makes rules for the HTMLizatiion or SGMLization of the components that we make in XML.

Personally I prefer .commands as in Roff that are escaped. By this I mean having a character that will turn off or turn on special characters like the dot.
I like them better as they read better, and they do not require containerization or a second command to end them usually.

I am not arguing for word processing across the net in these kind of forums. It would be kool, but that is not what I meant. I mean sending docs to the net or to others, with common formatting in them they can display in their xmlbrowser, that is as good as page typesetting.

The part about changing a site in that format, is that one does not want to be trying to edit a site you are passworded onto by changing a separate document on your computer and then uploading all 75 pages of it to change a comma. You should be able to log on, and change the document in situ, by having a copy that changes at both ends in real time. Saving does a save at both ends. Dangerous? No more than present word processing and file copy management.

HTML is impoverished it is true. It is a tiny and MS-Netscape screwed-up subset of SGML, which is not nearly as good as Tex etc.. It needs to have a facelift for the browser, and the printer.

A word processor of the XML/HTML/Roff type would need to be three incarnations. One would be WYSIWIG drop down/keystroke tool capability, and the other would be, like Word Perfect, the ability to change the mark ups directly in straight text. Images and their manipulation other than sizing, would have to be in another tool. A final capability would be to program in the language a lal Roff scripts, or CSS/XML page building. The rules of XML allow you to build your own containers and then translate. This would be retained, as it allows new datastandards to be interchanged.

What this would do is make the document a data document as well as human readable, and make it indexable as well.

EC<:-}