[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Mechanism, not policy

• From: Rick Jelliffe <rjelliffe@allette.com.au>
• To: "Roger L. Costello" <costello@mitre.org>
• Date: Mon, 15 Jun 2015 16:41:28 +1000

And separating content from presentation is just an example of the more general pattern of separating data  from application, which is one of the rationales for databases (and indeed most multi tier systems).  What Goldfarb et al realized in the 70s at IBM was not really a new pattern, but that documents also fitted into the emerging two(+) tier  architectures (and, indeed, that document longevity forced, to some extent, a virtual single-input/multiple-application architecture-- even if only one application was active in any given period there would still need to be a succession of applications as technology moved onwards, and marking up documents to make this succession as easy as possible would be an investment and a risk reduction.)

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: Mechanism, not policy
    • From: Tei <oscar.vives@gmail.com>

• References:
  • Mechanism, not policy
    • From: "Costello, Roger L." <costello@mitre.org>