W3C home > Mailing lists > Public > www-xml-fragment-comments@w3.org > April 1999

RE: Changing fragbodyref to be an URL

From: Joel A. Nava <jnava@Adobe.COM>
Date: Mon, 26 Apr 1999 14:49:30 -0700
To: <Daniel.Veillard@w3.org>
Cc: <www-xml-fragment-comments@w3.org>
Message-ID: <000301be902e$a9f2ce70$8c9f2099@corp.adobe.com>
From: Daniel Veillard [mailto:Daniel.Veillard@w3.org]
>   Restricting it to a known kind of reference allow to anticipate
> on the processing needed to handle the fragment on the receiving side.
> In the case one use a packaging mechanism, having a strutured
> naming scheme is important for the evolution of the specification.
> Expressing fragbodyref references as URIs allows to bypass the
> packaging mechanism, and provide a standard way to use Fragment
> in the absence of a Packaging format. This is useful when the server
> has no idea on the client capacity to decode say Mime
> multipart messages.

Okay, I am convinced. URI reference it is then.

Joel A. Nava                  (408)536-6209
Adobe Systems, Inc.         jnava@adobe.com
Received on Monday, 26 April 1999 17:49:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:52:38 UTC