Re: XLink 1.1: XPointer reference

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>| Assuming this is meant to formally address the issue, I don't think this
|>| is acceptable, draft-murata-kohn-lilley-xml-01.txt expired about two
|>| weeks ago and it clearly noted that
|>|
|>|   If [XPointerFramework] and [XPointerElement] are inappropriate for 
|>|   some XML-based media type, it SHOULD NOT follow the naming convention
|>|   '+xml'.
|>|
|>| which means it is possible that for some "XML resources" the "format of
|>| the fragment identifier" is not specified by XPointer. In fact, XPointer
|>| only defines a framework, for e.g. image/svg+xml the concrete format of
|>| fragment identifiers is specified in the SVG specifications.
|>
|>Does the following proposal seem satisfactory?
|
|>  For locators into XML resources, the format of the fragment
|>  identifier (if any) used within the URI reference is specified by
|>  [RFC xxxx].
|
| You assume that there is and will be one format for all XML resources.
| As I pointed out, this is currently unwarrented. So no, neither text
| would address my concern. Text that would acknowledge that fragment
| identifiers are defined for each individual media type would be more
| appropriate.

I see your point. Would the following change address your concern:

Replace:

   For locators into XML resources, the format of the fragment
   identifier (if any) used within the URI reference is specified by
   the XPointer specification [XPTR].

With:

   If a locator includes a fragment identifer, the syntax of the
   fragment identifier is defined by the media type of the
   representation returned when the locator is dereferenced. For
   locators into XML resources (that is, resources with the media type
   "application/xml" or media types that defer to the fragment
   identifier syntax of "application/xml" media), the syntax of the
   fragment identifier is expected to be defined by the successor to
   RFC 3023. Technically, there is no fragment identifier syntax for
   XML resources at the time of this writing, though the XPointer
   framework and element schemes are explicitly supported by several
   XML vocabularies.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.