semantics

How do I semanticly markup the headers in the article as presented in the picture below? I often run into this problem; where I have a header that is visually first, but is a subheading, intro header or less important then the main header. I could put it after the main header and move it above with CSS, but that isn't always a ideal solution. Another question: is there any special way to markup lead paragraphs? Not allowed? <article> <h2>New prodcut</h2> <h1>Launching our new x-series</h1> <p class="lead">Lorem ipsum dolor sit amet...</p> <p>Integer varius, turpis sit amet accumsan...</p> ...

What to use for poem? pre blockquote code something else? unor Don't use code (unless computer code is part of the poem). Don't use blockquote (unless you quote a poem). white space / line breaks: pre or br You may use the pre element . The spec gives an (informative) example: The following shows a contemporary poem that uses the pre element to preserve its unusual formatting, which forms an intrinsic part of the poem itself. <pre> maxling it is with a heart heavy that i admit loss of a feline so loved a friend lost to the unknown (night) ~cdr 11dec07</pre> However, I'd only use the pre

Seems interchangable? UL means "unordered list". OL means "ordered list". UL gets you bullet points. OL gets you numbers. Definitely not interchangable. In math terms (hey, why not?), an <ol> represents a sequence, whereas <ul> represents a set. Rearranging the items in an ordered list changes the list's meaning. Rearranging them in an unordered list does not. This is a good rule-of-thumb for which type of list to use. If changing the order of the items makes the list incorrect, you want to use <ol> . If the order doesn't matter, use <ul> . With <ol> the order of the data is important and will

I would like to implement Latent Semantic Analysis (LSA) in PHP in order to find out topics/tags for texts. Here is what I think I have to do. Is this correct? How can I code it in PHP? How do I determine which words to chose? I don't want to use any external libraries. I've already an implementation for the Singular Value Decomposition (SVD) . Extract all words from the given text. Weight the words/phrases, e.g. with tf–idf . If weighting is too complex, just take the number of occurrences. Build up a matrix: The columns are some documents from the database (the more the better?), the rows

In the Introduction to Swift WWDC session, a read-only property description is demonstrated: class Vehicle { var numberOfWheels = 0 var description: String { return "\(numberOfWheels) wheels" } } let vehicle = Vehicle() println(vehicle.description) Are there any implications to choosing the above approach over using a method instead: class Vehicle { var numberOfWheels = 0 func description() -> String { return "\(numberOfWheels) wheels" } } let vehicle = Vehicle() println(vehicle.description()) It seems to me that the most obvious reasons you would choose a read-only computed property are:

This question already has an answer here: How to compute the similarity between two text documents? 8 answers Are there any libraries for computing semantic similarity scores for a pair of sentences ? I'm aware of WordNet's semantic database, and how I can generate the score for 2 words, but I'm looking for libraries that do all pre-processing tasks like port-stemming, stop word removal, etc, on whole sentences and outputs a score for how related the two sentences are. I found a work in progress that's written using the .NET framework that computes the score using an array of pre-processing

I am looking at messing around with creating a functional reactive framework at some point. I have read quite a lot about it and seen a few examples but I wanted to get a clear idea of what this framework would HAVE to do to be considered an FRP extension/dsl. I'm not really concerned with implementation problems or specifics etc but more as to what would be desired in a perfect world situation. What would be the key operations and qualities of an ideal functional reactive programming language? Conal I'm glad you're starting by asking about a specification rather than implementation first.

Are there some noticeable outcomes in terms of performance or other aspects to follow semantic HTML? Thanks Nathan Long Not about performance Semantic markup isn't about performance, it's about meaning. Let's imagine two parallel universes. In Dumb HTML World , there is only one tag: <thing> . How would you specify where styles should be applied? How would browsers know how to render the page? How would screen readers for the blind differentiate between headlines and text and footnotes and menu items? You'd have to add all kinds of awkward attributes. Meanwhile, in Detailed HTML World , there