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: E. Charters who wrote (775)	4/14/2003 12:53:22 AM
From: WhatsUpWithThat	Read Replies (1) \| Respond to of 16214

I can see no way I could win an argument with that kind of imposing presence Yet you go on in a vain attempt to do so! Foolish mortal... Tell you what: I'll format and spell-check your stuff, and you vet my too-often poor gold and diamond investment decisions; deal? Your second para is right, but one of a) a pinko socialist commie plot to take away our right to choose competing and incidentally incompatible applications and proprietary file formats, b) a perfect world where open standards would be quickly and efficiently developed and managed by a co-operative and creative international standards body, c) what Bill Gates is striving for, the hegemony of Microsoft. I can't see forcing a data description language to do dual duty as a page description language as well. Imagine how ugly it would get, putting multi-level data description tags AND mult-level format description tags around the same poor little piece of text! Say you were formatting a company address, with the company name bold, in Verdana 14 small caps, and the address in Arial 12 italic, indenting, absolute placement of each address on the page, and so on. You'd have a lot of data description tags for all the address entities and a lot of format and description tags; you'd almost lose the actual data in all this. 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. I don't quite understand. The value to XML is three-fold: you exchange data and the description of the data in one document, that document is straight text so it is easy to send/read/use (no proprietary file formats), and - by far the most important - it represents an agreement on the coding of a specific element (ie. the name). You can't make an entirely new data element, put it in a file and send it to another party and expect that just because they have an XML-compliant application they can work with it. If you send me an address and use as your elements <company><address1><address2><city><province><country><postalcode> and I have an XML-compliant database that expects incoming XML client data will be tagged <co><addr1><burg><state><ctry><zip> we're not going to get very far. We have to have an agreement in advance on the data element names (or an ability to have someone manually map them the first time of course). Or maybe I misunderstood and you were just saying that we can agree on a new data element and then begin using it with no change in file formats or application code. indexable as well Aw, I expected you to solve my issues with indexing! I think that's the most interesting and the hardest to work through of what you were suggesting. Cheers WUWT