Re: Last Call: draft-wilde-text-fragment (URI Fragment Identifiers for the text/plain Media Type) to Proposed Standard
An updated version taking into account the various comments received during Last Call is now available as http://www.ietf.org/internet-drafts/draft-wilde-text-fragment-07.txt. Most Last Call comments were editorial in nature, but one commenter strongly, and in the end convincingly, argued that the spec was too complicated. As a consequence, we have removed two features: 1) Regular expressions 2) The possibility to list several scheme parts in a single fragment identifier. As a result of this, fragments for text/plain can no longer consist of disconnected pieces. While we do not want to exclude bringing the removed functionality back in a future version of the spec if there is clear demand for it, we feel that the reduced set of features is best suited for speedy implementation and deployment, and also matches the fact that text/plain by itself is very simple and straightforward. The area directors in charge (first Ted Hardie, now Chris Newman) have advised us that they don't expect another Last Call for this feature reduction, but that we should announce this change to this list. If you have concerns about this feature reduction, in particular if you already have implemented some of the features we removed, please notify this list. With kind regards, Martin. At 09:40 07/02/15, The IESG wrote: The IESG has received a request from an individual submitter to consider the following document: - 'URI Fragment Identifiers for the text/plain Media Type ' draft-wilde-text-fragment-06.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-03-14. Exceptionally, comments may be sent to [EMAIL PROTECTED] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-wilde-text-fragment-06.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=9149rfc_flag=0 ___ IETF-Announce mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/ietf-announce #-#-# Martin J. Durst, Assoc. Professor, Aoyama Gakuin University #-#-# http://www.sw.it.aoyama.ac.jp mailto:[EMAIL PROTECTED] ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Last Call: draft-wilde-text-fragment (URI Fragment Identifiers for the text/plain Media Type) to Proposed Standard
On Wed, Feb 14, 2007 at 07:40:16PM -0500, The IESG [EMAIL PROTECTED] wrote a message of 24 lines which said: - 'URI Fragment Identifiers for the text/plain Media Type ' draft-wilde-text-fragment-06.txt as a Proposed Standard There are a few problems regarding the ABNF of this draft which have been sent to the author, acknowledged but apparently not fixed in this copy. I suggest another version before a last call. (That's apparently what the author intended, froma private conversation.) ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Last Call: draft-wilde-text-fragment (URI Fragment Identifiers for the text/plain Media Type) to Proposed Standard
On 2/14/07, The IESG [EMAIL PROTECTED] wrote: The IESG has received a request from an individual submitter to consider the following document: - 'URI Fragment Identifiers for the text/plain Media Type ' draft-wilde-text-fragment-06.txt as a Proposed Standard Editorial point: Section 2.2.1 says Character position counting starts with 0, so the character position before the first character of a text/plain MIME entity has the character position 0 but the example in section 5 says http://example.com/text.txt#char=100 This URI identifies the position after the 100th character of the text.txt MIME entity. If character counting starts at 0 I take it that the initial character is the 0th character, thus char=100 is before not after the 100th, right? In fact the spec is perfectly correct according to the normal meaning of 100th but it took me a minute to get that, and I suspect a little clean-up in the example description would be useful. Substantive point: Each of the addressing schemes is easy to understand, but the ways they combine are hard to explain and understand, and I'm unconvinced that being able to identify things like This URI identifies the first line and all occurrences of the regular expression 'searchterm' in the MIME entity. are worth the effort. I'd strongly recommend simplifying the spec by allowing only one scheme, which might turn out to hit a very desirable 80/20 point. -Tim ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Last Call: draft-wilde-text-fragment (URI Fragment Identifiers for the text/plain Media Type) to Proposed Standard
The IESG has received a request from an individual submitter to consider the following document: - 'URI Fragment Identifiers for the text/plain Media Type ' draft-wilde-text-fragment-06.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-03-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-wilde-text-fragment-06.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=9149rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce
