TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: SGML [features, attributes, relationships] From:Joyce Flaherty <flahertj -at- SMTPGW -dot- LIEBERT -dot- COM> Date:Sun, 31 Mar 1996 15:17:38 EST
Text item: Text_1
Len Olszewski, Project Manager, SGML Technology Group,
saslpo -at- unx -dot- sas -dot- com
> The point is that if you assign attribute values, then
> group based on the attribute values to assign metadata,
> you are duplicating a function. Unnecessary attribute
> values in a large database for frequent and
> relatively small elements adds size to your data,
> subtracts performance speed from your processing,
> and adds nothing to your application. Better to
> achieve the grouping using a database tool, or
> some other convention, than to muck with attributes.
By George, I think she's got it!
I don't consider myself slow, but this one went right
over my head--light speed! Must be the pizza I slept
with last night, or the TV test pattern finally
getting to me.
Let me restate it: I require the group association in
the application I am using NOW (limitation of the software)
to perform certain meta-functions. In the target environment,
the SGML environment, this is redundant information.
I owe you one,
flahertj -at- smtpgw -dot- liebert -dot- com