Lists Home |
Date Index |
- From: Marc.McDonald@Design-Intelligence.com
- To: email@example.com
- Date: Mon, 21 Jun 1999 15:46:34 -0700
(forgot to put in previous reply)
Basically, don't use rendering as an means of filtering (maybe I read too
much into the use of H3 and P elements).
It is certainly valid to filter the XML elements sent out, though that might
be done on the production side, i.e. the application that produces the XML
form in the first place rather than passing it through XSLT.
Marc B McDonald
Principal Software Scientist
Design Intelligence, Inc
From: David Brownell [SMTP:firstname.lastname@example.org]
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:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)