Repository navigation
Remove the requirement labels from meta-inf file intro descriptions - #3111
Conversation
|
I agree. However, while we are it: this intro section is fairly far away from the sections that really describe/define them normatively. Sections 4.2.2-4.2.5 are entirely devoted to the gory details of file systems, base URLs etc. These sections are also very long. One would expect 4.2.6 to follow the introductory section, and it is not the case. I wonder whether a restructuring of the sections would make sense: something about file system and base URL details in 4.2 and the META-INF directory (with the sections you just changed). I guess this PR should be merged but it may be worth thinking about reordering. |
|
Ya, most of the abstract container intro reads as an intro to the meta-inf directory. We could take all of that text and make it an intro under 4.2.6, or possibly even merge it normatively into 4.2.6.1 But then what's left of the intro would need some additions to flesh it out. I'll merge this since it's pretty non-controversial and take a stab at fixing the section ups some more. |
This is more of a minor nit on my part, but since we're doing some cleanup in these sections...
Having [required] and [optional] labels after each file name in the introduction makes the section look like our normative content models. The paragraph under the descriptions already says to refer to the file descriptions for usage info and each file's description normatively states whether it is required or optional. Nothing is lost by removing these labels except the appearance that they are normative.
Preview | Diff