[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Hanging paragraph issue in core spec (OBIX-109)
I’m not sure I understand this one. According to Toby, all hanging paragraph issues in the WebSocket Binding spec are addressed. But I still see things in WD11 like lines 47-49. This looks to be text immediately following a heading.
I’m not pointing this out as wrong in WebSocket, because I think it’s fine. I’m trying to understand what is desired for the core spec. If the requirement is that you cannot have any text after a heading, then this seems to invite a recursive application
of the rule that would prevent you from ever having any text. Is the rule that you cannot have text if and only if you have subheadings? So, this is legal: 2 Section Title 2.1 Subsection Title blah blah blah....... 2.2 Subsection Title blah blah blah....... But this is not: 2 Section Title blah blah blah this is NOT legal here 2.1 Subsection Title blah blah blah....... So, if I have a 2.1.1, 2.1.2, 2.1.3, I cannot have any text directly under 2.1
before the title for 2.1.1, is that correct? |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]