Lists Home |
Date Index |
- From: Marc.McDonald@Design-Intelligence.com
- To: firstname.lastname@example.org
- Date: Mon, 21 Jun 1999 15:42:26 -0700
I agree there are times for data to be filtered, which is why I mentioned
the elements and attributes that would not be present. With CSS, I admit
they would be there but a system that removed elements that had no style
attributes added is more of what I'm thinking of.
In the case given, you wouldn't know Joe was an employee or that he was
active. All you would know is that his name is joe and his phone number.
When sensitive data needs to be hidden I would send it out subsetted in the
His salary, review info, and other sensitive material would not be sent out
Marc B McDonald
Principal Software Scientist
Design Intelligence, Inc
From: David Brownell [SMTP:email@example.com]
Sent: Monday, June 21, 1999 3:35 PM
To: Marc McDonald
Subject: Re: XSL and the semantic web
> I think the point was that <H3>Joe</H3> has lost the fact that
>'Joe' was a name (<name>Joe</name>), and similarly with the
> phone number.
I read that just fine. And as I said, you don't have any kind
of entitlement or right to such information, so it's no use to
base any arguments on such an entitlement.
For example, there are risks to society in making it too easy
for people to find out information about other folk. It makes
it easy to perform identity theft, invade privacy, etc. The
very example (a semantic web search) you used to motivate your
desire for this representation came across to me as a powerful
reason to avoid what you're arguing in favor of!
> Looks to me like grasping at straws to justify FO model.
... or to attack it! In fact, I never mentioned FOs, the
points I was making apply to _any_ element vocabulary used
to deliver information. They will be used to filter out data,
and hide it in less accessible forms, since organizations
MUST do that. The more sensitive the data, the more work
will be (or at least should be!) put into filtering it out
or hiding it.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)