Re: FW: XML Core expects to publish a WG Note "Extending XLink 1.0"

/ Paul Grosso <pgrosso@arbortext.com> was heard to say:
| FYI.
|
| -----Original Message-----
| From: Martin Duerst [mailto:duerst@w3.org] 
| Sent: Friday, 14 January, 2005 5:30
| To: Paul Grosso; chairs@w3.org
| Cc: w3t-comm@w3.org; webreq@w3.org; timbl@w3.org; Steve Bratt
| Subject: Re: XML Core expects to publish a WG Note "Extending XLink 1.0"
|
| Hello Paul,
|
| I have had a short look at the document. In general, it looks
| very good, but I have some small comments, about proposal 3,
| "Allow IRIs.".
|
| First, the title of this proposal should be changed to something
| like "Allow IRIs for XLink properties, such as role and arc types.".
| This would make it much clearer that this is only one aspec related
| to IRIs.

For something as informal as WG Note, I'm inclined to leave it as is.
But it wouldn't be hard to change before 27 Jan.

| Second, there is the issue of upgrading xlink:href to use IRIs
| more directly. The current spec for the value of the xlink:href
| attribute is a very circumscript but simplified description of
| what is essentially an IRI. Ideally, this would just be replaced
| with a reference to the IRI spec (which should be issued as an
| RFC very soon), but there are a few differences that have to
| be carefully considered.
|
| Independent of whether these changes can be made in the actual
| document (with an apparent publication date of January 27, this
| may be feasible or not), I hope that in particular the second
| issue will noted for future work. I personally expect the
| I18N Core WG to contact chairs when the IRI spec is published
| to look at updating issues across specs.

In light of the fact that I18N may wish us to do more with respect
to IRIs, I'm even more inclined to leave point 3 in the general
form "Allow IRIs".

                                        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.