In a message dated 6/5/00 2:50:13 PM Eastern Daylight Time, [EMAIL PROTECTED]
writes:
> CC: [EMAIL PROTECTED]
In a message dated 6/5/00 2:34:41 PM Eastern Daylight Time, [EMAIL PROTECTED]
writes:
> CC: [EMAIL PROTECTED]
"The theme" of my reports has been thus:
Since I had a LOT of coding to do, which required lots of keen analysis,
ordering, recording, typing even, which would generate the work of lots of
upkeep, which would generate the work of lots of documentation, which would
generate lots of upkeep ad infinitum! A truly endless loop that so often
seemed a true deadly embrace. I realized I might ought "capture" as much of
all of the analysis and realization as I could/should/would, but instead of
using the in vogue log files, journals, directory hierarchies, tree data
structures, etc., of sooo many forms and functions of programming, etc., what
the HECK! (obviously not a reference to satan). Why did I buy the
(t)re(e)lational dB?
It exists to be used for just that sort of thing.
EDI specifications of differing document formats was so lacking difference in
so many ways. There was so much that could so obviously be reused.
And in normalized data, anything that repeats gets its own file for some cool
reasons.
The literature NEVER said you had to use it for traditional things like
transaction record data processing utility only (say that one time fast).
VIOLA!
Regrids,
JIm Cunningham
P.S. (not PS as AOL, and a few not so inanimate and soulless "others" I might
add, spell/style checkers colloquialize)
I had 12 years of "English by nuns", which included 2 years of Classical
Latin, as opposed to Ecllesiastic/Church Latin. Caesar dixit, veni, vedi,
vici. Remember, they had no "w", "v" was pronounced AS "w", and all "c"s
were "hard"; KYZAR DEEKS-IT, WAY-NEE, WEEDY, WEEKY. WOW.
When I "create" hyphenated words and quoted terms, I do it the "old way" from
habit, and I try to resist promoting a verb to a noun (or vice versa, as I
have seen lately), and I place commas to impart the pauses I would use in
speaking the words, like everyone used to or was supposed to. This is likely
an effect of reading the essay by Orwell, at an early age (6th grade),
wherein he relates the slow painful death of society caused by the
"colloquialization" as "particularized" in journalism (things like "the icy
heat the artist ..."), icy heat. Say what? Me and that one, having had not
had ever metaphor. I'm not even! gonna complain about "irregardless" here.
Oh, the folly of the flurry of the fury of the prefixes and suffixes
fluctuating in the flow of fluff; like way double plus good, huh?
That could be why, on first inspection, I was so relieved that EDI had been
crafted, and so thoroughly on the first implementations. "Business" seems so
firm on such unwavering exactness of meaning being "held" unchanging over
time, via the written word, when it comes to exchanging money for "stuff".
No, it wasn't the lawyers who wanted that so much. They get called back in at
all changes of meaning. It was the guys who hired and paid the lawyers, due
to the arguments made to (re)interpret the words that meant one thing when
agreements were made, yet seemed to change over the life of a contract. OK
so it was failure to reach a "meeting of the minds"; that was a failure to
"intimidate all parties into doing what they agreed to do, to the point that
they were so intimidated, they did". XML will allow me to put "the legals"
of the small print on the back of the transaction document where it needs to
be so as to have the same very important effect it has on paper documents, to
don't get it in their face to the point you scare them away from the
transaction data and the opportunity it represents to both parties.
Thus, my written words may seem quite strange to "kids" and colloquialists.
I look forward to forward lookers who will use XML to stand on the shoulders
of EDI giants and see further than others.
P.P.S.
I use P(P)Ss to respect the rights of the reader to "bail" and to thus
respect the serious nature this forum deserves and requires. I just meet
those requirements in a more traditional manner. Don't read'em, or
"lose'em". I reserve as much of the humor as I can to them, yet I try always
to see that they too, speak of/to EDI/XML. issues I have experienced. And I
could never abide prohibiting authors here from presentations intended to
also inspire some of the audience re: same.
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
