semantic

The only thing is that the name 'semantic' is not really a winner (it sets people on edge).

With macros, every single semantic property you can imagine is available to you at no cost.

I call the rules of reasoning, that is the rules of manipulation of statements including their lexicon, syntax and semantic, a logic.

But that wouldn't be semantic in that use case either.

Also, if divs have no semantic meaning in the context of the document's structure, it means they serve some other purpose: and that purpose is visual styling (not directly but through a css applied to them).

Also, div's by definition have no semantic meaning, and that's a good thing—those who bothered to care know that tables for layout had their share of accessibility issues.

I want the Web that was originally intended: One source of data, the document, which allows you to be as expressive and semantic as you want.

Some comments I've seen are that it is simply about establishing parity with Clojure 1.7 while keeping the current release strategy (it's not about semantic versioning).

If there was a choice to use CSS properties and values that better conveyed the presentation intent (what you might call its semantic value), they would advocate for that as well.

One of our primary goals is to make knowledge discovery more accessible, contextual, and anticipatory, all driven with the power of machine learning, AI, and the semantic web.

The whole point here is to give this idea a name and clear spec so that I can tell people my software uses Semantic Versioning instead of writing it all out every time.

Another great thing about Python in particular is that it ends to be extremely easy to read other people's code due to semantic whitespace and also by language design of there only being one way to do things.

How else could the term "self-censorship" have any semantic value?

Machines without "subjective experience" or "semantic content" can still fire guns.

The fact that both "style as a table" and "center" attain to the visual aspect doesn't change the fact there is a semantic difference between the two.

But sure, it's a "violation" but web standards do not say "you must only use elements that are essential to the semantic structure of the document." I'd say the guideline is "start with semantic elements, add others as needed for styling, programmatic access, componentization, etc."

Semantic Versioning is very simple and has no intention of solving every possible versioning problem.

Semantic Versioning is also about more than just dependencies.

Semantic networks of particular interest - Content managers (2-4 per religion) We are based in London but there is significant scope for location elsewhere or remote work.