Lists Home |
Date Index |
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: north@synopsys.COM, firstname.lastname@example.org
- Date: Wed, 13 Dec 2000 10:43:04 -0600
Umm.. maybe. The issue raised by
Didier about trans/including improper
fragments (eg, content sans ad) is
a fairly old problem. The *content*
has to assert rights with regards
to reuse. That a topic map can
point to a bit of content and include
a traversal rule might enable better
navigation, but the assertion of
right to copy still should be a locally
set policy which the implementor of
the trans/including system must respect
by law. Policy before code; always.
Just because it can be built doesn't
mean it is legal to use. Note the
cases with cable descramblers.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Simon North [mailto:north@synopsys.COM]
Sent: Wednesday, December 13, 2000 10:36 AM
Subject: Re: Didier's lab report
Simon St.Laurent said:
> I wonder if maybe there'd be a way to establish this a little more
> solidly as a means of providing metadata about links and inclusions.
> XLink already provides some metadata, but I suspect we're going to
> find more places where extra information about a link might be useful,
> and where they might be useful across multiple applications.
Isn't this precisely where topic maps come in?