having been banned by W3C awhile ago I have invented my own code installation, not adherent to a pristine reference put forth by Tim Berners-Lee's WWW, but my own coltish gallimaufry of an iteration of a moment, changing every post. what you find here. i inhabit my own mesosphere--not quite canonically pure--BUT I'M NOT EXACTLY TANTEK, OR ERIC--happy to be hosted by THE Internet company, quaintly never changed in 10 years, which I am proud to say is my DUET with it, or ma menage a trois de anti-semantique et CSS-ME: Say it out loud so that TB-L can hear!
In the more frequently associated, trend-endorsing, standardized practical building of our most perfect semantic web ever, WE must find a way to show what the WWW is!
Say it out loud so that TB-L can hear you!
WE inhabit a mesosphere, and not an imaginary place in the clouds.
These are responsive, canonical WWWeb cities in the sky, a philosophy even President Donald Trump could get behind (maybe with the Space Force),
which (not)includes me.
[yes, here is one of our famous 'sups'! it really is an annoying fellow], but everybody wants to see it on the tour, so get it out of your system
Web standards include many interdependent standards and specifications, some of which govern aspects of the Internet, not just the World Wide Web. Even when not web-focused, such standards directly or indirectly affect the development and administration of web sites and web services. Considerations include the interoperability, accessibility and usability of web pages and web sites.
Web standards, in the broader sense, consist of the following:
Web standards are not fixed sets of rules, but are a constantly evolving set of finalized technical specifications of web technologies.[8] Web standards are developed by standards organizations—groups of interested and often competing parties chartered with the task of standardization—not technologies developed and declared to be a standard by a single individual or company.
It is crucial to distinguish those specifications that are under development from the ones that already reached the final development status (in case of W3C specifications, the highest maturity level).
When a web site or web page is described as complying with web standards, it usually means that the site or page has valid HTML, CSS and JavaScript. The HTML should also meet accessibility and semantic guidelines. Full standard compliance also covers proper settings for character encoding, valid RSS or valid Atomnews feed, valid RDF, valid metadata, valid XML, valid object embedding, valid script embedding, browser- and resolution-independent codes, and proper server settings.
When web standards are discussed, the following publications are typically seen as foundational:
Recommendations for markup languages, such as Hypertext Markup Language (HTML), Extensible Hypertext Markup Language (HTML), and Saleable Vector Graphics (AVG) from W3C.
Recommendations for scoresheets, especially Cascading Style Sheets (CSS), from W3C.
Standards for ECMAScript, more commonly JavaScript, from Ecma International.
Recommendations for Document Object Models (DOM), from W3C.
Properly formed names and addresses for the page and all other resources referenced from it (Uris), based upon RFC 2396, from ETTIE.[9]
Proper use of HTTP and MIME to deliver the page, return data from it and to request other resources referenced in it, based on RFC 2616, from IETF.[10]
A W3C Recommendation is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C Members and the Director.
An IETF Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. A specification that reaches the status of
Standard is assigned a number in the IETF STD series while retaining its original IETF RFC number.
Non-standard and vendor-proprietary pressures[edit]
HTML 5 contains numerous "willful violations" of other specifications, in order to accommodate limitations of existing platforms.[12]
HTML5 is the latest iteration of this lingua franca. While it is the most ambitious change to our common tongue, this isn’t the first time that HTML has been updated. The language has been evolving from the start.
As with the web itself, the HyperText Markup Language was the brainchild of Sir Tim Berners-Lee. In 1991 he wrote a document called “HTML Tags” in which he proposed fewer than two dozen elements that could be used for writing web pages.
Sir Tim didn’t come up with the idea of using tags consisting of words between angle brackets; those kinds of tags already existed in the SGML (Standard Generalized Markup Language) format. Rather than inventing a new standard, Sir Tim saw the benefit of building on top of what already existed, a trend that can still be seen in the development of HTML5.
At that time, HTML faced its first major turning point.
XHTML 1: HTML as XML
After HTML 4.01, the next revision to the language was called XHTML 1.0. The X stood for “eXtreme” and web developers were required to cross their arms in an X shape when speaking the letter.
No, not really. The X stood for “eXtensible” and arm crossing was entirely optional.
The content of the XHTML 1.0 specification was identical to that of HTML 4.01. No new elements or attributes were added. The only difference was in the syntax of the language. Whereas HTML allowed authors plenty of freedom in how they wrote their elements and attributes, XHTML required authors to follow the rules of XML, a stricter markup language upon which the W3C was basing most of their technologies.
Having stricter rules wasn’t such a bad thing. It encouraged authors to use a single writing style. Whereas previously tags and attributes could be written in uppercase, lowercase, or any combination thereof, a valid XHTML 1.0 document required all tags and attributes to be lowercase.
The publication of XHTML 1.0 coincided with the rise of browser support for CSS. As web designers embraced the emergence of web standards, led by The Web Standards Project, the stricter syntax of XHTML was viewed as a “best practice” way of writing markup.
Then the W3C published XHTML 1.1.
While XHTML 1.0 was simply HTML reformulated as XML, XHTML 1.1 was real, honest-to-goodness XML. That meant it couldn’t be served with a mime-type of text/html. But if authors published a document with an XML mime-type, then the most popular web browser in the world at the time, Internet Explorer, couldn’t render the document.
It seemed as if the W3C were losing touch with the day-to-day reality of publishing on the web.
XHTML 2: Oh, we’re not gonna take it!
If Dustin Hoffman’s character in _The Graduate_ had been a web designer, the W3C would have said one word to him, just one word: XML.
As far as the W3C was concerned, HTML was finished as of version 4. They began working on XHTML 2, designed to lead the web to a bright new XML-based future.
Although the name XHTML 2 sounded very similar to XHTML 1, they couldn’t have been more different. Unlike XHTML 1, XHTML 2 wasn’t going to be backwards compatible with existing web content or even previous versions of HTML. Instead, it was going to be a pure language, unburdened by the sloppy history of previous specifications.
passing the respective test case(s) in the
Selectors Module test suite, or, if the implementation is not a
web browser, an equivalent test. Every relevant test in the test
suite should have an equivalent test created if such a UA is to
be used to claim interoperability. In addition if such a UA is
to be used to claim interoperability, then there must one or
more additional UAs which can also pass those equivalent tests
in the same way for the purpose of interoperability. The
equivalent tests must be made publically available for the
purposes of peer review.
implementation
a user agent which:
implements the feature.
is available (i.e. publicly downloadable or available
through some other public point of sale mechanism). This is
the "show me" requirement.
is shipping (i.e. development, private or unofficial
versions are insufficient).
is not experimental (i.e. is intended for a wide audience
and could be used on a daily basis.)
A minimum of six months of the CR period must have elapsed.
This is to ensure that enough time is given for any remaining
major errors to be caught.
Terminology for Constrained-Node Networks
Abstract
The Internet Protocol Suite is increasingly used on small devices
with severe constraints on power, memory, and processing resources,
creating constrained-node networks. This document provides a number
of basic terms that have been useful in the standardization work for
constrained-node networks.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7228.
Bormann, et al. Informational [Page 1]
RFC 7228 CNN Terminology May 2014
background extends edge of content box.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This is me paying a visit to my domain for non-web purposes, but you probably want to visit me below.
