View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008106 | 10000-003: Address Space | Spec | public | 2022-07-11 21:22 | 2023-05-09 16:01 |
| Reporter | Randy Armstrong | Assigned To | Jeff Harding | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.05.02 RC1 | ||||
| Target Version | 1.05.03 RC1 | ||||
| Summary | 0008106: Need Named Composite Permissions | ||||
| Description | The spec uses the phrase "not visible" to imply "not browseable, readable, writable or callable". This ambiguous to some readers who think that visibility only affects browsing. Propose adding composite permissions to Part 3 that can be referenced as terms in the spec to eliminate ambiguity. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
There is only one use of the phrase "not visible" in Part 3. This one use is used to describe the visibility of structure of structured data. I don't see anything related to the original issue however I do think we need to review what this is saying about structured data. |
|
|
This does not apply to Part 3. No change needed. |
|
|
Submitter agreed to no change required. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-11 21:22 | Randy Armstrong | New Issue | |
| 2022-07-12 15:50 | Jim Luth | Target Version | 1.05.03 => 1.05.03 RC1 |
| 2022-07-12 15:50 | Jim Luth | Assigned To | => Jeff Harding |
| 2022-07-12 15:50 | Jim Luth | Status | new => assigned |
| 2023-05-04 19:23 | Jeff Harding | Note Added: 0019289 | |
| 2023-05-09 16:00 | Jeff Harding | Status | assigned => resolved |
| 2023-05-09 16:00 | Jeff Harding | Resolution | open => no change required |
| 2023-05-09 16:00 | Jeff Harding | Note Added: 0019299 | |
| 2023-05-09 16:01 | Jim Luth | Status | resolved => closed |
| 2023-05-09 16:01 | Jim Luth | Note Added: 0019300 |
