[
Lists Home |
Date Index |
Thread Index
]
- From: Marcus Carr <mrc@allette.com.au>
- To: xml-dev@ic.ac.uk
- Date: Tue, 28 Sep 1999 12:10:13 +1000
Mark Nutter wrote:
> Ok, but now how about this: You're doing contract work for the government,
> and all of your documentation uses an attribute to indicate security level,
> e.g. <para security="ts"> for paragraphs classified as Top Secret. All is
> well, and you have an entire application written that uses Processing
> Instructions that rely on having the security level defined by an attribute
> in the containing tag. Now the government decides that "ts" (Top Secret)
> is no longer fine-grained enough -- there are a whole new set of "top
> secret" classifications: "ts-ce" (top secret, counter-espionage), ts-snp
> (top secret, security at nuclear power plants), ts-ch (top secret, computer
> "hacking"), and so on, and your paragraphs need to be tagged with all the
> security levels that apply. You are working on a document that discusses
> security measures used to prevent foreign governments from hacking into
> computers at nuclear power plants. What now?
Three things:
a) what Ken Holman said about XPath (onya, Ken)
b) I'm not advocating building applications that make that kind of use of
processing instructions, simply pointing out that I believe attributes provide
an additional degree of certainty
c) the security status of the various fragments would typically require
content expertise, so I'd probably strip all of the attributes out and get the
expert to apply them only where they change, then "normalise" them
programmatically. I imagine that this is the same process you'd use for
elements, isn't it?
--
Regards,
Marcus Carr email: mrc@allette.com.au
___________________________________________________________________
Allette Systems (Australia) www: http://www.allette.com.au
___________________________________________________________________
"Everything should be made as simple as possible, but not simpler."
- Einstein
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
