Re: [xml2rfc-dev] Please help review v3 file: draft-ietf-avtcore-rtp-multi-stream-optimisation-12

[Henrik Levkowetz <[e-mail]>]

Hi Martin,

On 2019-08-06 02:03, Martin Thomson wrote:
> https://martinthomson.github.io/i-d-template/sample4.html
> 
> The strange author ordering continues:
> 
> China
> 210012
> JiangsuNanjing,
> 101 Software Avenue, Yuhua District
> Huawei
> Qin Wu
> Email: [e-mail]

Two things:

 - This is actually the correct field order for this Chinese postal
   address, as given by google's i18n address database (except for
   a missing space between Jiangsu and Nanjing, a bug I saw now).

 - In Prague, IETF-104, I discussed the interest of correct rendering of
   addresses from an i18n perspective versus the interest of listing authors
   in a recognizable form with Alice and Sandy, with the outcome that we'd
   change this to always show the author name first, even if not strictly
   correct from an i18n address format point of view.  I thought I'd already
   fixed this, but find that the code changes have not been released.  It
   will be part of the next release, some time later this week.


Regards,

	henrik

   
> 
> 
> On Tue, Aug 6, 2019, at 09:30, Sandy Ginoza wrote:
>> Hi again,
>> 
>> Continuing with our request to review XMLv3 files, we’d appreciate your 
>> input regarding draft-ietf-avtcore-rtp-multi-stream-optimisation-12. 
>> We’re hoping some of you will take the time to review the files and 
>> provide feedback regarding whether the updates are as expected and the 
>> XMLv3 files are considered “good” v3 files. 
>> 
>> NOTEs: 
>> - As previously mentioned, we are aware there is an issue w/ sectionFormat.
>> Example: text is missing from the output (Section 3.1) after this XML
>> <xref target="RFC3550" sectionFormat="comma" section="6.3.7"/>
>> 
>> - Although it gives an error currently, our understanding is that using 
>> xref in this manner (or similar) to create a link to a specific section 
>> of an I-D will be possible (without relying on the target attribute of 
>> the corresponding reference), per discussion with Henrik.
>> <xref target="RTP-STREAMS" sectionFormat="of" section="5.4"/>
>> 
>> - we focused on format only; we did not make editorial updates. 
>> 
>> - the diff files compare the initial v2v3 output with the files we edited.
>> 
>> Please review the following files related to 
>> draft-ietf-avtcore-rtp-multi-stream-optimisation-12:
>> 
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.html
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.pdf
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.txt
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3.xml
>> 
>> Diff files:
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3-xmldiff.html
>> https://www.rfc-editor.org/v3test/draft-ietf-avtcore-rtp-multi-stream-optimisation-12-KC.v2v3-htmlwdiff.html
>> 
>> 
>> Thanks,
>> Sandy 
>> _______________________________________________
>> xml2rfc-dev mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>>
> 
> _______________________________________________
> xml2rfc-dev mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>