[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Naming and reference

• From: "Rob Schoening" <rschoening@u...>
• To: "XML" <xml-dev@i...>
• Date: Mon, 18 Jan 1999 16:03:14 -0800

  I am hoping that someone more knowledgeable than I am might be able to
answer this question:

  Is there a convenient way to identify a document by name?  For transient
documents, it occurs to me that it might be very difficult to maintain an
audit trail of documents without using application and domain specific
tools.  For e-commerce applications, this could be a serious shortcoming.
It seems to me that signing and encryption would necessarily be involved in
this scenario.


As a document passes between systems a->b->c->d, more than likely systems b
and c will have little interest in the contents of the document.  However,
it seems very likely that they would want to log a unique name for the
document (perhaps with its credentials) in order to cross reference it in
their system with some kind of annotation.  This is important if only to
preserve the integrity of the contents of the document.  Presumably, we
would like to know that the document at point A is the same document as the
one arriving at point d.  But if the only way we can refer to documents is
through a URL, I do not see how this will be possible since the URL is a
reference, not a name.

It seems to me that this will be absolutely critical for XML in EC
applications.  Any suggestions on where to look?


Rob Schoening





xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: XML Component API
• Next by Date: re Naming and reference
• Previous by thread: Second Call for Articles - Crossroads Magazine
• Next by thread: re Naming and reference
• Index(es):
  • Date
  • Thread