semantics

Which of the following is the correct way to structure a page: 1) h1 only in header <header> <h1>Site title</h1> <nav>...</nav> </header> <section> <h2>Page title</h2> </section> If I use h1 exclusively inside header as the site's title, every page will have the same content for the h1 tag. That doesn't seem very informative. 2) h1 in header and section , for both site and page title <header> <h1>Site title</h1> <nav>...</nav> </header> <section> <h1>Page title</h1> </section> I've also seen examples of using h1 more than once, in both header and section tags. However, isn't it wrong to have

In R we all know it is convenient for those times we want to ensure we are dealing with an integer to specify it using the "L" suffix like this: 1L # [1] 1 If we don't explicitly tell R we want an integer it will assume we meant to use a numeric data type... str( 1 * 1 ) # num 1 str( 1L * 1L ) # int 1 Why is "L" the preferred suffix, why not "I" for instance? Is there a historical reason? In addition, why does R allow me to do (with warnings): str(1.0L) # int 1 # Warning message: # integer literal 1.0L contains unnecessary decimal point But not.. str(1.1L) # num 1.1 #Warning message: #integer

I've often wondered about the proper use of a <br> line break. Seems that often they are incorrectly used for positioning or clearing content where CSS should instead be used. W3schoools.org says to use <br> for blank lines, but not for creating or separating paragraphs. Looking over W3C HTML5 spec draft , it's a little clearer that the <br> would be used when content requires a line break such as lines of an address or blank lines in poetry, where intended by the author. But I'm still interested in any further clarification or input anyone else. I often find myself opting not to use <br> tags

Today I've gotten a remark about code considering the way I check whether a variable is true or false in a school assignment. The code which I had written was something like this: var booleanValue = true; function someFunction(){ if(booleanValue === true){ return "something"; } } They said it was better/neater to write it like this: var booleanValue = true; function someFunction(){ if(booleanValue){ return "something"; } } The remark which I have gotten about the "=== true" part was that it was not needed and could create confusion. However my idea is that it is better to check whether the

I'm trying to find some good examples of semantic diff/merge utilities. The traditional paradigm of comparing source code files works by comparing lines and characters.. but are there any utilities out there (for any language) that actually consider the structure of code when comparing files? For example, existing diff programs will report "difference found at character 2 of line 125. File x contains v-o-i-d, where file y contains b-o-o-l". A specialized tool should be able to report "Return type of method doSomething() changed from void to bool". I would argue that this type of semantic