DC: I would like for this section C to have a test case prior to going into effect

17:52:09 [Roy]

NW: would like Dan to send mail to public-xml to that effect

17:54:05 [Roy]

NW: I don't know how to construct a test for CSS, but the introduction of xml:id does not change historical documents and its presence will be ignored by parsers ignorant of xml:id. The CSS spec doesn't need to say anything about that.

17:55:30 [Roy]

VQ: suggest revisiting this after Norm completes action ... is there any other spec beyond CSS that are impacted?

17:55:37 [Roy]

DC: six specs are listed

17:56:11 [Roy]

VQ: let's move on

17:56:24 [Roy]

Topic: Review of XRI documents

17:56:52 [Roy]

VQ; Henry is not here, but can Ed provide his feedback?

17:57:20 [Roy]

Ed: I sent HT some feedback this morning but haven't heard back yet

17:57:37 [Roy]

Ed: (my delay)

17:57:59 [Roy]

VQ: we need to reply to the WG by the end of this month

17:58:17 [Roy]

VQ: and work on a longer document

17:59:19 [Roy]

Ed: HT is working on the longer document ... after feedback, will have a better idea how to proceed toward sending comments to WG

18:00:00 [Roy]

VQ: should we prepare something specific for the XRI team?

18:00:20 [Roy]

Ed: yes, they deserve a direct feedback as opposed to a general reference

18:00:54 [Roy]

RF: agree on direct response (as well as later general document)

18:01:18 [Roy]

VQ: running out of time, do we have time to make a TAG decision?

18:02:10 [Roy]

DC: we already have general feedback in the form of the webarch doc

18:04:38 [Roy]

DO: we need to take a look at the examples given and explain how we can solve those problems using URI, HTTP, etc.

18:05:25 [DanC]

q+ to propose: 1. XRI follows the pattern of an administrative hierarchy of delegation ending with a path, 2. http/dns handle that case, and is ubiquitously deployed 3. new URI schemes should not be introduced when existing schemes handle them 4. ergo XRI should not be introduced.

18:05:40 [Roy]

DO: on my blog, I got comments about change of ownership of a domain and broke it down into examples

18:05:56 [Vincent]

ack DanC

18:05:56 [Zakim]

DanC, you wanted to propose: 1. XRI follows the pattern of an administrative hierarchy of delegation ending with a path, 2. http/dns handle that case, and is ubiquitously deployed

18:05:59 [Zakim]

... 3. new URI schemes should not be introduced when existing schemes handle them 4. ergo XRI should not be introduced.

18:06:00 [Roy]

DO: that show how the points can be responded to

18:06:27 [dorchard]

q+

18:06:40 [Vincent]

ack dorchard

18:07:03 [Roy]

DC: wonder what parts of the argument would fail to convince

18:07:05 [DanC]

DO: what's not established is "http/dns handle that case"

18:08:39 [Roy]

DO: they wrote a document that shows (in their mind) why 2) is not the case. What we need to do is come up with examples that show an alternative interpretation/solution to the examples they provided in the documents.

18:08:57 [Roy]

DC: did their writing convince you?

18:09:17 [Roy]

DO: it did give me pause to wonder about the two scenarios already mentioned

18:10:02 [Roy]

Ed: most cases of domain change can be handled by redirects

18:10:46 [DanC]

dorchard, did you mail something to www-tag on this item?

18:11:36 [Roy]

NM: is it obvious to people on this call that redirect is something that we can point to for longevity of URIs?

18:11:57 [Zakim]

- +1.804.740.aaaa

18:12:02 [Roy]

DC: yes, one of the many reasons why HTTP is better for this type of thing

18:12:37 [Zakim]

+ +1.804.740.aabb

18:12:53 [Roy]

DC: I am willing to try to make that case (am writing a related article)

NM: what about the general concern that they are using something other than URIs for general identity?

18:25:34 [Roy]

NM: what WSA did was remove the distinction that indicated a parameter was being used for identity, but they didn't remove the mechanism itself. Some people still use that feature for the purpose of identification.

18:26:19 [DanC]

q+ to note my struggles reviewing WS-addressing... can anybody sketch a test scenario? how can I tell if a hunk of software is doing ws-addressing right or not?

18:27:06 [Roy]

DC: similar to cookies in that WSA does not prevent the use of those fields for the sake of passing identifying data