Issues changed or updated on

I just realized that updates to issues in the tracker are being sent to the working group mailing list, but aren't actually being distributed (probably because the tracker isn't a member of the group and that's required.)

Anyway, here are some recent updates to issues in the tracker on 3987bis.

If we've closed something and you're unhappy with the result, please re-open the issue.

Larry
--
http://larry.masinter.net

Forwarded message 1

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 15:05:03 -0700
  • Subject: Re: [iri] #93: Private-use chars are allowed?
  • To: "draft-ietf-iri-3987bis@tools.ietf.org" <draft-ietf-iri-3987bis@tools.ietf.org>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>, "evnikita2@gmail.com" <evnikita2@gmail.com>
  • Message-ID: <075.5d2efd305eb223376c1535708753be74@trac.tools.ietf.org> 
#93: Private-use chars are allowed?

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 iprivate characters are only allowed in query components; the introduction
 of Section 6 is clear, viz:

 "This section provides a list of the groups of characters and code
 points that are allowed in some contexts but are not allowed in IRIs or
 are
 allowed in IRIs only in the query part. "

 We changed the name of section 6 to ""Characters Disallowed or Not
 Recommended in IRIs"

-- 
-------------------------+---------------------------------------
 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  defect       |      Status:  closed
 Priority:  minor        |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/93#comment:1>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 2

  • From: iri issue tracker <trac+iri@trac.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:58:41 -0700
  • Subject: Re: [iri] #95: Update reference to UCS standard (ISO 10646)
  • To: "draft-ietf-iri-3987bis@tools.ietf.org" <draft-ietf-iri-3987bis@tools.ietf.org>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>, "evnikita2@gmail.com" <evnikita2@gmail.com>
  • Message-ID: <075.fd40b1a2ec8ce91543c127c98afa68a3@trac.tools.ietf.org> 
#95: Update reference to UCS standard (ISO 10646)

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Updated reference (since this is available now from ISO web site, added
 URI reference to spec as well).

-- 
-------------------------+---------------------------------------
 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  defect       |      Status:  closed
 Priority:  minor        |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/95#comment:1>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 3

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:46:00 -0700
  • Subject: Re: [iri] #9: "URL" can be used in "formal" documents
  • To: Larry Masinter <masinter@adobe.com>, "stpeter@stpeter.im" <stpeter@stpeter.im>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <067.135ea938bacd66a08b34376fcdeb7996@trac.tools.ietf.org> 
#9: "URL" can be used in "formal" documents

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 This wording is no longer in the document, and so there is no longer an
 issue.

-- 
---------------------+---------------------
 Reporter:  lmm@…    |       Owner:
     Type:  defect   |      Status:  closed
 Priority:  trivial  |   Milestone:
Component:  3987bis  |     Version:
 Severity:  -        |  Resolution:  fixed
 Keywords:           |
---------------------+---------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/9#comment:2>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 4

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:40:45 -0700
  • Subject: Re: [iri] #80: Point to particular schemes' specs in the text
  • To: Larry Masinter <masinter@adobe.com>, "stpeter@stpeter.im" <stpeter@stpeter.im>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.f96bdf70aac3021cb7e10f8e5b57a9db@trac.tools.ietf.org> 
#80: Point to particular schemes' specs in the text

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 There doesn't seem to be any mention in the document of 'mid', 'ftp', or
 'telnet' as schemes, so it's not clear what is wanted here.

 The situation with regard to ftp as a URI scheme and its
 internationalization (as well as file:, for that matter) is pretty murky,
 and needs to be addressed, but doing so is not in scope for this document.

 I wouldn't want to point to 1738, in any case.

-- 
-------------------------+----------------------
 Reporter:  evnikita2@…  |       Owner:
     Type:  defect       |      Status:  closed
 Priority:  trivial      |   Milestone:
Component:  4395bis      |     Version:
 Severity:  -            |  Resolution:  wontfix
 Keywords:               |
-------------------------+----------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/80#comment:2>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 5

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:34:15 -0700
  • Subject: Re: [iri] #87: Mention that octets in <> are denoted in hex
  • To: "draft-ietf-iri-3987bis@tools.ietf.org" <draft-ietf-iri-3987bis@tools.ietf.org>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>, "evnikita2@gmail.com" <evnikita2@gmail.com>
  • Message-ID: <075.ad783cd1e3bca8c6c73f64117b62196d@trac.tools.ietf.org> 
#87: Mention that octets in <> are denoted in hex

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 "the two hex digits denoting the octets..." already says they're in hex.

-- 
-------------------------+---------------------------------------
 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  defect       |      Status:  closed
 Priority:  trivial      |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:  invalid
 Keywords:               |
-------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/87#comment:1>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 6

  • From: iri issue tracker <trac+iri@trac.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:26:43 -0700
  • Subject: Re: [iri] #92: Sections 3.4 & 3.5 should be moved into Section 3.6 of 3987bis
  • To: "draft-ietf-iri-3987bis@tools.ietf.org" <draft-ietf-iri-3987bis@tools.ietf.org>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.6ba75b96be93dbccfbe4a635cbc70acd@trac.tools.ietf.org> 
#92: Sections 3.4 & 3.5 should be moved into Section 3.6 of 3987bis


Comment (by masinter@…):

 I think the problem is that all of section 3, except 3.7, leads to the
 conversion of IRIs to URIs, and 3.6 only briefly describes the reassembly
 of parsed IRI components (as converted to URI components).

 We might want to change the title of 3.6 (from "Mapping IRIs to URIs" to
 "Reassembling results of IRI processing into a URI") and beef up the
 introduction of section 3 to be clearer that the whole section 3 covers
 Mapping IRIs to URIs. (We would move 3.7 to be section 4 instead and
 renumber subsequent sections.)

-- 
-------------------------+---------------------------------------
 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  enhancement  |      Status:  new
 Priority:  trivial      |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/92#comment:1>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 7

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Thu, 20 Oct 2011 14:10:48 -0700
  • Subject: Re: [iri] #94: Add reference to RFC 6082
  • To: "draft-ietf-iri-3987bis@tools.ietf.org" <draft-ietf-iri-3987bis@tools.ietf.org>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.8bc4685e036006d68cde9af158ad9e0a@trac.tools.ietf.org> 
#94: Add reference to RFC 6082

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Tags (U+E0000-E0FFF): These characters were intended to provide a way to
 language tag in Unicode plain text. They are now deprecated <xref
 target="RFC6082" />. In any case, they would not be appropriate for IRIs
 because language information in identifiers cannot reliably be input,
 transmitted (e.g. on a visual medium such as paper), or
 recognized.

-- 
-------------------------+---------------------------------------
 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  enhancement  |      Status:  closed
 Priority:  trivial      |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:  fixed
 Keywords:               |
-------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/94#comment:1>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 8

  • From: iri issue tracker <trac+iri@trac.tools.ietf.org>
  • Date: Wed, 5 Oct 2011 09:02:33 -0700
  • Subject: Re: [iri] #70: RFC 2119 language in Section 3.1 of 4395bis
  • To: "chris@lookout.net" <chris@lookout.net>, "evnikita2@gmail.com" <evnikita2@gmail.com>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.2dadacf3d1e99a763514b7f02de0a8c8@trac.tools.ietf.org> 
#70: RFC 2119 language in Section 3.1 of 4395bis


Comment (by chris@…):

 WG consensus seems to be keeping this a "SHOULD".  See:

 http://lists.w3.org/Archives/Public/public-iri/2011Aug/0055.html


 Based on this the issue can be closed.

-- 
-------------------------+------------------
 Reporter:  evnikita2@…  |       Owner:
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  4395bis      |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/70#comment:3>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 9

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Wed, 5 Oct 2011 08:56:47 -0700
  • Subject: Re: [iri] #73: Decide on organization-specific schemes
  • To: "chris@lookout.net" <chris@lookout.net>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.8677e4848a8f48a1131c37ea8f4f9c60@trac.tools.ietf.org> 
#73: Decide on organization-specific schemes


Comment (by chris@…):

 WG consensus is to remove this statement from the text.  See:

 http://lists.w3.org/Archives/Public/public-iri/2011Aug/0058.html


-- 
-------------------------+------------------
 Reporter:  evnikita2@…  |       Owner:
     Type:  defect       |      Status:  new
 Priority:  minor        |   Milestone:
Component:  4395bis      |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+------------------

Ticket URL: <https://svn.tools.ietf.org/wg/iri/trac/ticket/73#comment:2>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 10

  • From: iri issue tracker <trac+iri@gamay.tools.ietf.org>
  • Date: Wed, 5 Oct 2011 08:58:28 -0700
  • Subject: Re: [iri] #64: Disallow registration of URI schemes with generic names 'uri', 'url', etc.
  • To: "chris@lookout.net" <chris@lookout.net>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <075.f70b3f1a8af996da5cf58a1ab0f09bd7@trac.tools.ietf.org> 
#64: Disallow registration of URI schemes with generic names 'uri', 'url', etc.


Comment (by chris@…):

 WG consensus is to add some text like the following here.

 "(e.g. url, uri, iri)."

 See:

 http://lists.w3.org/Archives/Public/public-iri/2011Aug/0057.html


-- 
-------------------------+------------------
 Reporter:  evnikita2@…  |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  minor        |   Milestone:
Component:  4395bis      |     Version:
 Severity:  -            |  Resolution:
 Keywords:               |
-------------------------+------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/64#comment:2>
iri <http://tools.ietf.org/wg/iri/>

Forwarded message 11

  • From: iri issue tracker <trac+iri@trac.tools.ietf.org>
  • Date: Wed, 5 Oct 2011 08:55:22 -0700
  • Subject: Re: [iri] #60: Should we recommend using different ABNF rule names to clarify escaping?
  • To: "chris@lookout.net" <chris@lookout.net>, Larry Masinter <masinter@adobe.com>
  • CC: "public-iri@w3.org" <public-iri@w3.org>
  • Message-ID: <078.dab49a24bdcf82af38a1e2390e12a9e5@trac.tools.ietf.org> 
#60: Should we recommend using different ABNF rule names to clarify escaping?


Comment (by chris@…):

 WG consensus is to close this as "won't fix". See:

 http://lists.w3.org/Archives/Public/public-iri/2011Aug/0059.html


-- 
----------------------+------------------
 Reporter:  duerst@…  |       Owner:
     Type:  defect    |      Status:  new
 Priority:  minor     |   Milestone:
Component:  4395bis   |     Version:
 Severity:  -         |  Resolution:
 Keywords:            |
----------------------+------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/60#comment:2>
iri <http://tools.ietf.org/wg/iri/>

Received on Friday, 21 October 2011 20:16:03 UTC