Lists Home |
Date Index |
- From: "Simon St.Laurent" <email@example.com>
- To: David Brownell <firstname.lastname@example.org>
- Date: Wed, 16 Jun 1999 12:35:05 -0400
At 09:21 AM 6/16/99 -0700, David Brownell wrote:
>And one more: you appear to be assuming that the client actually
>has enough horsepower and information to do the transformation (or
>for the FO side of the argument, formatting) ... those are known
>to be false assumptions in many cases. A PDA with a typical speed
>IR link (not measured in megabits), slow CPU, and small fixed size
>storage just doesn't have that kind of resources. For many set-top
Maybe it's just that I'm at JavaOne, where Sun and 3Com keep talking about
what you can do with Java on a Pilot, but I see the bandwidth as more of a
problem than the processing power. It might well make sense to create some
kind of PDA middleware that slims down content before shipping it to the
PDA, but that seems more a matter of consumer-oriented content-negotiation
than producer-determined semantic firewalling.
>Hmm ... do you see them as issues in other contexts? Information
>is transformed routinely, every day. Frankly, I don't want to to be
>getting a complete history of everyone's life every time I deal with
>them; I'm happier to work with the current context (far smaller!).
>That sort of time/history based "semantic firewall" is very useful,
>for all that it's subject to abuse by all parties.
>There are others; if I browse a product description, rarely will I
>want complete technical specs, and if I do then I'll ask for them.
>I may want my technical books at a different level than someone else.
>Those are examples of transformations reducing the information
>that's presented. There are other transformations that can increase
>it; perhaps I want to look at a particular seller's history on an
>auction system before I buy from them, and not otherwise.
>If the semantic content is a "web" then anything short of looking at
>the whole web at once (yeah, right!) is looking through a "firewall".
In all of these cases, I have a very simple question: do you want to be
able to choose the level of semantic information you receive, or do you
want that to be determined by your provider? I have no object to
intelligent content-negotiation. I do have a problem with handing content
producers new tools for creating dumbed-down content with XML, the very
language that was supposed to improve the level of information quality on
XML: A Primer / Building XML Applications
Inside XML DTDs: Scientific and Technical (July)
Sharing Bandwidth / Cookies
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)