Re: Specifying all biz rules in relational data

From: Anne & Lynn Wheeler <lynn_at_garlic.com>
Date: Mon, 04 Oct 2004 18:32:49 -0600
Message-ID: <uacv2xavi.fsf_at_mail.comcast.net>


"Dawn M. Wolthuis" <dwolt_at_tincat-group.comREMOVE> writes:
> Good info. I could google around myself, but do you happen to know if Tex
> fits into this anywhere? Did it arise separately or is it related to cms
> script and runoff? Thanks. --dawn

references has knuth doing it circa '78 for typesetting ... i.e. controlling format of the presentation. this is in the same genre as runoff/script which was controlling the format. gml in '69 as generalized markup language ... comes from the initials of the last name of the three inventors at science center (aka "g", "m", and "l"). try search engine for combinations of things like tex, knuth, history. fairly representative version:
http://www.earlham.edu/~thompsk/final_project/latex/node4.html

however, gml was evolving into generalized description of the information, not the specification of the format of the display .... i.e. separate the description of the information and the specification for the display of the information. having self-describing information then enables features other than just dictating how that information might be displayed.

so some other random lore, the chair of x9a10 ... working group for x9.59 standard
http://www.garlic.com/~lynn/index.html#x959

had been one of the edi/x12 standards authors. one of the things focused on with edi/x12 was canonical format conversion for transport to allow different operations to exchange information.

another player in the interoperable transport conversion sphere has been ASN.1

by contrast, the sgml/xml scenario has the information in its "native" form be self-describing and that all applications (regardless of the location or operation) be able to utilize the information (self describing is not just for display purposes). this promotes COTS application interoperability .... as opposed to every operation developing roll-your-own applications and data formats (which then requires things like edi format conversation processes for transport and interoperability). in that sense there is some common objectives for both sgml/xml and various dbms with achieving common use of the same information by a variety of different applications.

so other folklore ... interaction between cluster dbms scale-up mentioned in prior post
http://www.garlic.com/~lynn/2004m.html#0

and electronic commerce
http://www.garlic.com/~lynn/aadsm5.htm#asrn2 http://www.garlic.com/~lynn/aadsm5.htm#asrn3

-- 
Anne & Lynn Wheeler | http://www.garlic.com/~lynn/
Received on Tue Oct 05 2004 - 02:32:49 CEST

Original text of this message