Auth48 changes #264
Auth48 changes #264
Conversation
this wraps the value in <bcp14> for rfcxml
ffv1.md
Outdated
|
|
||
| `YCbCr`: A reference to the method of storing the value of a Pixel by using three numeric values that represent the luma of the Pixel (Y) and the chroma of the Pixel (Cb and Cr). YCbCr word is used for historical reasons and currently references any color space relying on 1 luma Sample and 2 chroma Samples, e.g. YCbCr, YCgCo or ICtCp. The exact meaning of the three numeric values is unspecified. | ||
| YCbCr: | ||
| : A reference to the method of storing the value of a pixel by using three numeric values that represent the luma of the pixel (Y) and the chroma of the pixel (Cb and Cr). The term YCbCr is used for historical reasons and currently references any color space relying on one luma Sample and two chroma Samples, e.g., YCbCr, YCgCo (luma, blue-difference chroma, red-difference chroma), or ICtCp (intensity, blue-yellow, red-green). |
There was a problem hiding this comment.
The explanation of YCgCo is not correct. It’s the one for YCbCr.
There was a problem hiding this comment.
This was corrected upstream in the AUTH48 review.
|
|
||
| This specification describes the valid bitstream and how to decode such valid bitstream. Bitstreams not conforming to this specification or how they are handled is outside this specification. A decoder could reject every invalid bitstream or attempt to perform error concealment or re-download or use a redundant copy of the invalid part or any other action it deems appropriate. | ||
| This specification describes the valid bitstream and how to decode it. Nonconformant bitstreams and the nonconformant handling of bitstreams are outside this specification. A decoder can perform any action that it deems appropriate for an invalid bitstream: reject the bitstream, attempt to perform error concealment, or re-download or use a redundant copy of the invalid part. |
There was a problem hiding this comment.
nit: there are double-spaces in between the sentences
There was a problem hiding this comment.
verified that the double spaces are before and after AUTH48
|
Within this pull request, I'm working according to reducing the diff between the rfc9043.xml draft and the xml make from here. I'll resolve some of the outdated comments, but others are out of scope with the PR and belong in the AUTH48 process. |
I am afraid, I am not sure I understand carefully. Would you prefer that I open an issue for #264 (review)? It’s just the bracket that refers to the previous colour space, not the one to which it belongs. |
|
|
||
| SVGI:!--- | ||
| SVGI: | ||
| SVGI:!--- | ||
| SVGC:rangebinaryvalues7.svg=$$j_{0}=2$$ | ||
| AART:j_(0) = 2 | ||
| Figure: The initial value for "j", the length of the bytestream encoding. {#figureInitializeLength} | ||
| Figure: The initial value for j, the length of the bytestream encoding. {#figureInitializeLength} |
There was a problem hiding this comment.
Should it be
value for `j`, the length
?
There was a problem hiding this comment.
I don't know why this changed within the AUTH48 process. For this PR, my goal was to sync with AUTH48 so that the changes there are available for ongoing work on version 4.
There was a problem hiding this comment.
To me it’s the same change that you made a few lines later with k, therefore I mentioned it for consistency.
also remove collision of section name ("Exception")
This reorders the <reference> nodes but does not edit their content
as discussed on cellar and updated in the AUTH48 review
I filed a related issue at mmarkdown/mmark#137 to support the use of <refcontent>.
|
This PR is updated according to the version of rfc9043.xml provided on June 28th. Apologies for the messy commits, it was a challenge to organize the changes clearly. The xml output of the make process of this repo still differs from the rfc9043.xml version, but in ways ways that the mmark process can not accommodate. |
|
will delete, as this is superseded by #266 |
This is a part one of work to align the xml output of this repository to bring in the corrections of the auth48 process for what will be RFC9043.