Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001881 |
[1003.1(2024)/Issue8] Base Definitions and Headers |
Objection |
Error |
2024-11-28 15:27 |
2024-11-28 15:27 |
|
Reporter |
geoffclare |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Open |
|
Status |
New |
|
|
|
|
Name |
Geoff Clare |
Organization |
The Open Group |
User Reference |
|
Section |
3.10 Alias Name |
Page Number |
32 |
Line Number |
1064 |
Interp Status |
--- |
Final Accepted Text |
|
|
Summary |
0001881: Alias names should not be allowed to contain <slash> |
Description |
XRAT C.2.3.1 says "The definition of ``alias name'' precludes an alias name containing a <slash> character".
However, the definition of "Alias Name" actually says implementations may allow other characters within alias names as an extension and doesn't say anything about <slash> being disallowed.
The affected text is being moved out of the definition by bug 0001874, so the desired action is a change to be applied to the new location in XCU.
|
Desired Action |
On page 2477 line 80277 section 2.3.1 Alias Substitution, after applying bug 1874 change:Implementations may allow other characters within alias names as an extension. to:Implementations may allow other characters, except for <slash>, within alias names as an extension.
On page 3872 line 134187 section C.2.3.1 Alias Substitution, change:The definition of ``alias name'' precludes an alias name containing a <slash> character. to:A valid alias name cannot contain a <slash> character.
|
Tags |
No tags attached. |
|
Attached Files |
|
|