[OASIS Issue Tracker] (EMERGENCY-96) TEP 1.1 - TAB-1331: Lack of sectioning

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EMERGENCY-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61403#comment-61403 ] 

Patti Aymond commented on EMERGENCY-96:
---------------------------------------

Reporter: Patrick Durusau

> TEP 1.1 - TAB-1331: Lack of sectioning
> --------------------------------------
>
>                 Key: EMERGENCY-96
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-96
>             Project: OASIS Emergency Management TC
>          Issue Type: Bug
>          Components: TEP
>         Environment: Style
>            Reporter: Patti Aymond
>            Assignee: Patti Aymond
>            Priority: Minor
>
> Sections 4.2 (4 possible sections), 4.3 (27 possible sections), 4.4 (10 possible sections), 4.5 (11 possible sections), 4.6 (5 possible sections), 4.7 (7 possible sections), 4.8 (30 possible sections), 4.9 (5 possible sections), 4.10 (3 possible sections), 4.11 (5 possible sections), 4.12 (5 possible sections). 
> By my count, the number of potential sections in the listed parts of section 4 range from 4 to 30. 
> You are well familiar with the text and have no difficulty in finding the material you need. However, consider someone writing an implementation guide who wants to point to a particular element in 4.8. Do they simply point at 4.8 and let the reader wander along until they encounter the element in question? 
> The better course would be to create sections, with headers (may I suggest the element name?) for each of the potential sections. 
> That will enable implementers and people writing guidance for implementers to point directly to elements of concern for their implementations and to use as documentation. 
> More effort on your part but think how that will be multiplied by all the implementers and others whose time you will save by making more precise references available.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)