1 From - Tue Jul 1 11:00:58 2003
2 X-UIDL: 3f014dc900000006
4 X-Mozilla-Status2: 00000000
5 Envelope-to: adam@indexdata.dk
6 Received: from frink.w3.org ([18.29.1.71])
7 by bagel.index with esmtp (Exim 3.35 #1 (Debian))
8 id 19XGUC-0002xp-00; Tue, 01 Jul 2003 10:27:37 +0200
9 Received: from frink.w3.org (localhost [127.0.0.1])
10 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h618RZSn002707;
11 Tue, 1 Jul 2003 04:27:35 -0400 (EDT)
12 Received: (from lists@localhost)
13 by frink.w3.org (8.12.9/8.12.9/Submit) id h618QkDn002527;
14 Tue, 1 Jul 2003 04:26:46 -0400 (EDT)
15 Resent-Date: Tue, 1 Jul 2003 04:26:46 -0400 (EDT)
16 Resent-Message-Id: <200307010826.h618QkDn002527@frink.w3.org>
17 Received: from dr-nick.w3.org (dr-nick.w3.org [18.29.1.73])
18 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h618QhSn002466
19 for <www-zig@frink.w3.org>; Tue, 1 Jul 2003 04:26:43 -0400 (EDT)
20 Received: from auntie.miketaylor.org.uk (pc-62-30-152-189-hr.blueyonder.co.uk [62.30.152.189])
21 by dr-nick.w3.org (8.12.3/8.12.3/Debian-6.4) with ESMTP id h618Qgvx030432
22 for <www-zig@w3.org>; Tue, 1 Jul 2003 04:26:43 -0400
23 Received: from mike by auntie.miketaylor.org.uk with local (Exim 3.35 #1 (Debian))
25 for <www-zig@w3.org>; Tue, 01 Jul 2003 09:26:28 +0100
26 From: Mike Taylor <mike@indexdata.com>
28 Message-Id: <E19XGT6-00016e-00@auntie.miketaylor.org.uk>
29 Date: Tue, 01 Jul 2003 09:26:28 +0100
30 Subject: Revised XML Proposal
31 X-Archived-At: http://www.w3.org/mid/E19XGT6-00016e-00@auntie.miketaylor.org.uk
32 Resent-From: www-zig@w3.org
33 X-Mailing-List: <www-zig@w3.org> archive/latest/1324
34 X-Loop: www-zig@w3.org
35 Sender: www-zig-request@w3.org
36 Resent-Sender: www-zig-request@w3.org
38 List-Id: <www-zig.w3.org>
39 List-Help: <http://www.w3.org/Mail/>
40 List-Unsubscribe: <mailto:www-zig-request@w3.org?subject=unsubscribe>
47 Regarding the revised _Requesting XML Record_ proposal at
48 http://www.loc.gov/z3950/agency/proposals/request-xml.html
50 The technical content looks good to me. I have a few quibbles with
51 the wording, but they are not important.
53 The globally unique identifier may but need not be a
54 URI. If a URI, it may, but need not be the locator of
55 an XML schema definition or DTD. (And if a URI, it
56 need not be an HTTP URI.)
58 The phrase "may be need not be" feels awkward to me, and would read
59 better as "may be, but need not be,". And the last of these three
60 sentences should use the same phrasing as the first two:
62 The globally unique identifier may be, but need not
63 be, a URI. If it is a URI it may be, but need not be,
64 the locator of an XML schema definition or DTD. (And
65 if a URI, it may be, but need not be, an HTTP URI.)
69 Example 3. The identifier:
70 "http://www.editeur.org/onix/ReferenceNames" would be
71 used as the element set name to indicate the dtd at
72 http://www.editeur.org/onix/2.0/reference/onix-international.dtd.
74 "DTD" is an acronym and so should be all-caps.
78 Example 4. The identifier:
79 "http://www.kb.nl/persons/theo/dcx/" would be used as
80 the element set name to indicate that records are to
81 be composed according to the definition at that URI
82 (http://www.kb.nl/persons/theo/dcx).
84 It would be more explicitly exemplify what's going on if this said
85 "... composed according to the prose definition at ..."
87 Sorry to be picky. (But not so sorry that I won't :-)
89 _/|_ _______________________________________________________________
90 /o ) \/ Mike Taylor <mike@indexdata.com> http://www.miketaylor.org.uk
91 )_v__/\ "Ho ho ho ... Very witty, Wilde! Very, very witty!" --
92 Monty Python's Flying Circus.
95 Listen to my wife's new CD of kids' music, _Child's Play_, at
96 http://www.pipedreaming.org.uk/childsplay/
99 From - Wed Jul 2 00:57:47 2003
100 X-UIDL: 3f0211ea00000001
101 X-Mozilla-Status: 0011
102 X-Mozilla-Status2: 00000000
103 Envelope-to: adam@indexdata.dk
104 Received: from frink.w3.org ([18.29.1.71])
105 by bagel.index with esmtp (Exim 3.35 #1 (Debian))
106 id 19XU3R-0000o8-00; Wed, 02 Jul 2003 00:56:53 +0200
107 Received: from frink.w3.org (localhost [127.0.0.1])
108 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h61Mn1Sn023384;
109 Tue, 1 Jul 2003 18:49:01 -0400 (EDT)
110 Received: (from lists@localhost)
111 by frink.w3.org (8.12.9/8.12.9/Submit) id h61MmH7B022195;
112 Tue, 1 Jul 2003 18:48:17 -0400 (EDT)
113 Resent-Date: Tue, 1 Jul 2003 18:48:17 -0400 (EDT)
114 Resent-Message-Id: <200307012248.h61MmH7B022195@frink.w3.org>
115 Received: from dr-nick.w3.org (dr-nick.w3.org [18.29.1.73])
116 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h61MmESn022042
117 for <www-zig@frink.w3.org>; Tue, 1 Jul 2003 18:48:14 -0400 (EDT)
118 Received: from io.mds.rmit.edu.au (io.mds.rmit.edu.au [131.170.70.10])
119 by dr-nick.w3.org (8.12.3/8.12.3/Debian-6.4) with ESMTP id h61MmDvx015709
120 for <www-zig@w3.org>; Tue, 1 Jul 2003 18:48:14 -0400
121 Received: by io.mds.rmit.edu.au (Postfix, from userid 301)
122 id 3B6A649B70; Wed, 2 Jul 2003 08:48:06 +1000 (EST)
123 Date: Wed, 2 Jul 2003 08:48:06 +1000
124 From: Alan Kent <ajk@mds.rmit.edu.au>
126 Message-ID: <20030702084805.B20964@io.mds.rmit.edu.au>
127 References: <Law12-F268jRACYiFsH000230b4@hotmail.com> <3F005826.B395FDF4@loc.gov>
129 Content-Type: text/plain; charset=us-ascii
131 In-Reply-To: <3F005826.B395FDF4@loc.gov>; from Ray Denenberg on Mon, Jun 30, 2003 at 11:32:54AM -0400
132 Subject: Re: Proposal: requesting XML records
133 X-Archived-At: http://www.w3.org/mid/20030702084805.B20964@io.mds.rmit.edu.au
134 Resent-From: www-zig@w3.org
135 X-Mailing-List: <www-zig@w3.org> archive/latest/1325
136 X-Loop: www-zig@w3.org
137 Sender: www-zig-request@w3.org
138 Resent-Sender: www-zig-request@w3.org
140 List-Id: <www-zig.w3.org>
141 List-Help: <http://www.w3.org/Mail/>
142 List-Unsubscribe: <mailto:www-zig-request@w3.org?subject=unsubscribe>
147 On Mon, Jun 30, 2003 at 11:32:54AM -0400, Ray Denenberg wrote:
148 > Thanks for the comments on this proposal. It's been updated. See:
149 > http://www.loc.gov/z3950/agency/proposals/request-xml.html
152 I may have been out of things for a bit, but was there some reason
153 why Comp-spec was explicitly excluded?
155 "If Comp-spec is used, this agreement does not apply."
157 Is the purpose to say Comp-spec is out of scope (not defined) or that
158 it is recommended that Comp-spec *should not* support these set names.
159 I can understand Comp-spec being undefined/out of scope. But it would
160 seem wrong to disallow it.
162 Another observation (not a problem, just an observation), from memory
163 element set names are not case sensitive (in a quick skim of standard
164 I could not find this just now, but I recall seeing it previously).
165 URIs on the other hand are case sensitive. I guess there is no issue
166 as long as clients are told to always supply the URI with the correct
167 case. (If they don't, should it still work - maybe just undefined).
168 But as I said, probably not an issue in practice so not worth mentioning.
173 From - Wed Jul 2 22:13:36 2003
174 X-UIDL: 3f033cee00000006
175 X-Mozilla-Status: 0011
176 X-Mozilla-Status2: 00000000
177 Envelope-to: adam@indexdata.dk
178 Received: from frink.w3.org ([18.29.1.71])
179 by bagel.index with esmtp (Exim 3.35 #1 (Debian))
180 id 19XnuF-0007jb-00; Wed, 02 Jul 2003 22:08:43 +0200
181 Received: from frink.w3.org (localhost [127.0.0.1])
182 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h62JxFSn024233;
183 Wed, 2 Jul 2003 15:59:15 -0400 (EDT)
184 Received: (from lists@localhost)
185 by frink.w3.org (8.12.9/8.12.9/Submit) id h62JwYov024041;
186 Wed, 2 Jul 2003 15:58:34 -0400 (EDT)
187 Resent-Date: Wed, 2 Jul 2003 15:58:34 -0400 (EDT)
188 Resent-Message-Id: <200307021958.h62JwYov024041@frink.w3.org>
189 Received: from dr-nick.w3.org (dr-nick.w3.org [18.29.1.73])
190 by frink.w3.org (8.12.9/8.12.9) with ESMTP id h62JwXSn024006
191 for <www-zig@frink.w3.org>; Wed, 2 Jul 2003 15:58:33 -0400 (EDT)
192 Received: from sun8.loc.gov (sun8.loc.gov [140.147.249.48])
193 by dr-nick.w3.org (8.12.3/8.12.3/Debian-6.4) with ESMTP id h62JwWvx008936
194 for <www-zig@w3.org>; Wed, 2 Jul 2003 15:58:32 -0400
195 Received: from loc.gov (LSWRKC.dhcp.loc.gov [140.147.156.132])
196 by sun8.loc.gov with ESMTP id h62JwWqc015205
197 for <www-zig@w3.org>; Wed, 2 Jul 2003 15:58:32 -0400 (EDT)
198 Message-ID: <3F033967.67747812@loc.gov>
199 Date: Wed, 02 Jul 2003 15:58:32 -0400
200 From: Ray Denenberg <rden@loc.gov>
201 Organization: Library Of Congress
202 X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
203 X-Accept-Language: en
205 To: zig <www-zig@w3.org>
206 References: <Law12-F268jRACYiFsH000230b4@hotmail.com> <3F005826.B395FDF4@loc.gov> <20030702084805.B20964@io.mds.rmit.edu.au>
207 Content-Type: text/plain; charset=us-ascii
208 Content-Transfer-Encoding: 7bit
209 Subject: Re: Proposal: requesting XML records
210 X-Archived-At: http://www.w3.org/mid/3F033967.67747812@loc.gov
211 Resent-From: www-zig@w3.org
212 X-Mailing-List: <www-zig@w3.org> archive/latest/1326
213 X-Loop: www-zig@w3.org
214 Sender: www-zig-request@w3.org
215 Resent-Sender: www-zig-request@w3.org
217 List-Id: <www-zig.w3.org>
218 List-Help: <http://www.w3.org/Mail/>
219 List-Unsubscribe: <mailto:www-zig-request@w3.org?subject=unsubscribe>
226 > "If Comp-spec is used, this agreement does not apply."
228 > Is the purpose to say Comp-spec is out of scope (not defined) or that
229 > it is recommended that Comp-spec *should not* support these set names.
231 "Out-of-scope". The proposed agreement simply would not apply to compSpec
232 and there is no intent to suggest that compSpec should or should not support
236 > Another observation (not a problem, just an observation), from memory
237 > element set names are not case sensitive (in a quick skim of standard
238 > I could not find this just now, but I recall seeing it previously).
239 > URIs on the other hand are case sensitive. I guess there is no issue
240 > as long as clients are told to always supply the URI with the correct
241 > case. (If they don't, should it still work - maybe just undefined).
242 > But as I said, probably not an issue in practice so not worth mentioning.
244 Yes, ESNs are case insensitive and URIs are case sensitive.
246 So, suppose "http://www. ........... xyz" and "http://www. ........... XYZ"
247 identify two different schemas. Suppose a server knows the first, and the
248 client sends the second. The server will treat it as the first. The only
249 reasonable answer to this problem is that this never should have happened to
250 begin with (these two names identifying different things). But how do you
251 prevent that from happening?
253 I think the practical answer is this: I think that the domain-name part of
254 an http uri is case insensitive, at least in practice. For example,
255 HTTP://WWW.LOC.GOV resolves to http://www.loc.gov, whereas
256 HTTP://WWW.LOC.GOV/Z3950 does not resolves to http://www.loc.gov/z3950.
259 (1) the naming authority part of a uri is, in practice, case insensitive; and
261 (2) a single naming authority has enough sense not to assign conflicting
263 then I think the problem should not arise.