Whether to couch the presentation as an imperative protocol instead of declarative "is a nominal URI documentation carrier". IRI - which to use in the document?ĭisposition: JAR agrees it needs addressing, will defer to TAG. If removed, introduce wa:instanceURI so that there's a common way to talk about generic resources.ĭisposition: This doesn't directly have to do with ISSUE-57, but JAR intends to prepare change proposals during upcoming www-tag discussion (but may run out of time - in the meantime see "either strengthen or retract httpRange-14(a)"). Needs to be either strengthened to "the representation is an instance of the resource", or removed so that 200 can be used instead of 303 for all resources, not just information resources. "Is an information resource" is useless, because the Flickr / Jamendo confusion is not addressed. Raised by: Harry Halpin, Manu Sporny, Ian Davis, Pat Hayes, et al.ĭisposition: Grouped with performance concerns, previous issue. ģ03 is hard to deploy on commodity hosting platforms, and hash is allegedly an unacceptable alternative. The editor's say is not final the content of the document is up to the TAG.Ĭertain names occur repeatedly, so they will be abbreviated by initials: JAR = Jonathan Rees, TimBL = Tim Berners-Lee, DB = David Booth.ģ03 has performance problems (2 round trips, first one not cached by some clients), and hash is allegedly an unacceptable alternative.ĭisposition: This is TAG ISSUE-57. "editorial" classification is whether a change to the document on the given issue is likely to lead to different behavior on someone's part in some situation. I know this is a wiki but I would prefer if you ask me (Jonathan Rees, rees at ) to make changes to this page rather than just editing directly - that will make it much easier for me to keep track of the current state of play for each issue. Jonathan's notes on issues raised with the document at - both substantive and editorial.
0 kommentar(er)
