Re: XLink 1.1: Security Considerations

/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
| * Norman Walsh wrote:
|>/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say:
|>| No, RFC 1738 is obviously very outdated, I would instead expect that the
|>| security considerations of RFC 3987 apply, a clear description on which
|>| considerations are out of scope, which are in scope, implications of
|>| user agents implementing e.g. XLink and XHTML where the same link might
|>| go to multiple destinations, probably that UTR #36 applies, that XLink
|>| in XML documents is subject to the security considerations of XML and
|>| XML media types where applicable, and so on, depending on what is con-
|>| sidered in scope and out of scope. It might of course be possible that
|>| some of the items above are considered out of scope, but certainly not
|>| all of them.
|>
|>While the WG recognizes that adding more detailed information about
|>security considerations would be valuable, it does not consider such
|>additions to be within the narrow scope of its charter for XLink 1.1.
|>Consequently, the WG does not expect to make any changes with respect
|>to security considerations for XLink 1.1.
|
| That's a pity; do you think it'd be best if I register formal objection
| to this response so the issue can be looked at by the Director? Maybe
| there is a way for the XML Core Working Group to make the changes it'd
| like to make here and it's just been missed so far? I'd imagine there is
| always some room in charters to make a good specification, even if not
| all relevant details are explicitly mentioned.

If you do not indicate that you are satisfied, then this issue will be
discussed at the transition call. Any specific objection that you'd
like to make will be presented at that call.

                                        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.