View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007298 | 10000-006: Mappings | Spec | public | 2021-09-23 05:23 | 2021-09-24 12:16 |
| Reporter | Zbynek Zahradnik | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0007298: "XML fragment" is confusing in XmlElement binary encoding description | ||||
| Description | (5.2.2.8) XmlElement currently has this text: "An XmlElement is an XML fragment serialized as UTF-8 string and then encoded as ByteString." The word "fragment" should be replaced by "element", as that is what the intention was (Randy), and is also in line with how XmlElement is defined at other places in the specification. There probably are compliance tests (for client, and server) that are based on understanding of "XML fragment" as being a wider concept than "XML element". This issue should be cloned to the Compliance project if this is the case. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
This was discussed on virtual F2F, near the end of Sept 22, 2021 session. |
|
|
Replaced the word “fragment” with the word “element” in 5.3.1.9 in Draft 6. |
|
|
Agreed to changes in 1.05.1 Draft 6. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-09-23 05:23 | Zbynek Zahradnik | New Issue | |
| 2021-09-23 05:24 | Zbynek Zahradnik | Note Added: 0014944 | |
| 2021-09-24 03:26 | Randy Armstrong | Assigned To | => Randy Armstrong |
| 2021-09-24 03:26 | Randy Armstrong | Status | new => resolved |
| 2021-09-24 03:26 | Randy Armstrong | Resolution | open => fixed |
| 2021-09-24 03:26 | Randy Armstrong | Note Added: 0014989 | |
| 2021-09-24 12:16 | Jim Luth | Status | resolved => closed |
| 2021-09-24 12:16 | Jim Luth | Fixed in Version | => 1.05 |
| 2021-09-24 12:16 | Jim Luth | Note Added: 0014998 |
