At 11:31 AM 10/5/2001 -0700, Mike Dierken wrote:
> -----Original
Message-----
> From: Noah_Mendelsohn@lotus.com
[mailto:Noah_Mendelsohn@lotus.com]
> I would love to find some way to unify these models to
the point where
> applications that didn't care wouldn't be very
dependent on the
> differences, but there would also
> be complexitities in trying to achieve such
transparency.
> In any case, I think we need to seriously consider
supporting both
> conventions.
Unifying the two - internal embedding or external - means
making the location transparent to applications.
Since XML is a single-document format, linking to
information outside of that document requires more than (basic) XML
technology - XLink, etc.
? This is a simple matter of software design, not something that
involves
XLink. Whether a resource is embedded, attached or external can be
easily
encapsulated with a function that takes a URL and returns an interface
to
an representation of a resource. That's what the U in URL is
for.
Is there something more complex here?
______________________________________________________
John J. Barton
email: John_Barton@hpl.hp.com
MS 1U-17 Hewlett-Packard
Labs
1501 Page Mill
Road
phone: (650)-236-2888
Palo Alto CA
94304-1126
FAX: (650)-857-5100