This specification defines features to be supported in a date/time string, features considered useful for a wide variety of applications. It takes the form of a profile of / extension to ISO 8601, the International Standard for the representation of dates and times. ISO 8601 describes a large number of date/time formats. On one hand some of these formats are redundant and/or not very useful; to reduce the scope for error and the complexity of software, it seems worthwhile to restrict the supported formats to a smaller set. On the other hand, there are a number of date and time format conventions in common use that are not included in ISO 8601; it seems worthwhile to normalize these.

This wiki on geo-standards is an initiative of the Dutch national stimulation program on SDI (in Dutch Ruimte voor Geo-Informatie, RGI). One of the projects within this stimulation program, RGI-116, had the task to explore innovations in geo-standards. Within this initiative a world-wide survey was made to appraise the need and wishes of the geo-community to have an active forum of participants that can contribute to sharing a broad spectrum of knowhow concerning the developments related to geo-standards. As a result of the overwhelming positive response by the geo-community, this wiki was developed as a kick-off to host these needs and wishes. Many thanks goes out to the pioneer participants who have come from a number of educational, public and commercial GIS oriented working bodies.

Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.

MARC formatting conventions and US practice put romanized forms in the ”regular” MARC fields, with parallel fields for the original scripts to support systems with the capability to handle one or both scripts. However, most library systems still cannot accept the entire Unicode “repertoire” of characters for all scripts and some still cannot accept any non-Latin scripts.

Standardization is one of the defining aspects of modern life, its presence so pervasive that it is usually taken for granted. However cumbersome, onerous, or simply puzzling certain standards may be, their fundamental purpose in streamlining procedures, regulating behaviors, and predicting results is rarely questioned. Indeed, the invisibility of infrastructure and the imperative of standardizing processes signify their absolute necessity. Increasingly, however, social scientists are beginning to examine the origins and effects of the standards that underpin the technology and practices of everyday life. Standards and Their Stories explores how we interact with the network of standards that shape our lives in ways both obvious and invisible. The main chapters analyze standardization in biomedical research, government bureaucracies, the insurance industry, labor markets, and computer technology, providing detailed accounts of the invention of "standard humans" for medical testing and life insurance actuarial tables, the imposition of chronological age as a biographical determinant, the accepted means of determining labor productivity, the creation of international standards for the preservation and access of metadata, and the global consequences of "ASCII imperialism" and the use of English as the lingua franca of the Internet. Accompanying these in-depth critiques are a series of examples that depict an almost infinite variety of standards, from the controversies surrounding the European Union's supposed regulation of banana curvature to the minimum health requirements for immigrants at Ellis Island, conflicting (and ever-increasing) food portion sizes, and the impact of standardized punishment metrics like "Three Strikes" laws. The volume begins with a pioneering essay from Susan Leigh Star and Martha Lampland on the nature of standards in everyday life that brings together strands from the several fields represented in the book. In an appendix, the editors provide a guide for teaching courses in this emerging interdisciplinary field, which they term "infrastructure studies," making Standards and Their Stories ideal for scholars, students, and those curious about why coffins are becoming wider, for instance, or why the Financial Accounting Standards Board refused to classify September 11 as an "extraordinary" event.

The following guidelines are designed to help departments and faculty members implement effective evaluation procedures for hiring, reappointment, tenure, and promotion. They apply to scholars working with digital media as their subject matter and to those who use digital methods or whose work takes digital form.

This document provides guidelines about best practices in writing specifications, so that the risk of having interoperability (or portability) failures between implementations is reduced. The target audience is primarily specification writers and TC members.

The biggest difference here is that element sets are available for all items, while item type elements are available only to those items that belong to that item type. So, if you need a standardized set of elements that is available across all item types, an element set is the way to go.

It also seems to me that we have everything to gain by beginning our work on a data format with no particular serialization in mind. We could go from RDA to RDA-as-data and then on to RDA-as-RDF. I see some dangers in skipping the middle step, mainly that we could end up making some decisions that fit RDA into RDF but that are problematic for other serializations.

The syntax of HTML, along with rules for how to parse content using those syntaxes.

A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF.

Ian Hickson's post in which he announces (kind of) the formation of the WHATWG and the break from the "out of touch" W3C.

Microformats, RDFa and microdata all enable consumers to extract data from HTML pages. This data may be embedded within enhanced search engine results, exposed to users through browser extensions, aggregated across websites or used by scripts running within those HTML pages.

This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.

The classic "geological time scale" is a hierarchical ordinal system, in which the eras are ranked: "stages" nest within "series" within "systems" within "eras" within "eons" (in the most common version of the ranking system).

The time positions of the start and end points or geological eras are not known precisely, except for most of the Precambrian, where the boundaries are defined chronometrically. Typically there will be a number of estimates available, based on dating specimens retrieved from particular localities believed to correspond to the boundary of interest. A locality ratified by ICS is known as a "Global Boundary Stratotype Section and Point (GSSP)" and is indicated by a "golden spike" on the chart.

The complete definition of a geological time scale requires a description of the hierarchical structure of named eras the temporal positions of the boundaries between the eras.

We need a general purpose media type, which extends JSON, that can be used as a standard way to represent a resource and its relations to other resources on the Web.

It’s very important, particularly because we are talking about JSON, that this media type be simple in its design. There are only three essential capabilities for representing resources that this media type needs deliver:

1. Representing resource state
2. Linking to other resources
3. ‘Framing’ of embedded resources

HAL (application/hal+json) is a media type designed for this purpose.

Collection+JSON is a JSON-based read/write hypermedia-type designed to support management and querying of simple collections.

This document describes N-Quads, a format that extends N-Triples with context. Each triple in an N-Quads document can have an optional context value.

The Before and After Demonstration is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG).

Microformats, RDFa and microdata all enable consumers to extract data from HTML pages. This data may be embedded within enhanced search engine results, exposed to users through browser extensions, aggregated across websites or used by scripts running within those HTML pages.

This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.

URLs can be used to identify abstract concepts or other things that do not exist directly on the Web.  This is sensible, but it means that the same URL might be used in conjunction with four different (but related) things: a name, a concept, a Web location or a document instance.  Somehow, we need conventions for denoting these four different uses.  Two approaches are available: different names or different context.  The "different names" approach requires new URI schemes or conventions; the "different context" approach requires syntactic conventions for indicating the intended context.

This document analyzes the definition of "resource" in RFC2396 [1] in an attempt to understand it.  It notes ten questions or points of confusion (labeled QUESTION1 - QUESTION10) that I encountered.
 
WARNING: This analysis is painfully detailed, and somewhat rambling (sorry!), reflecting my thought process as I (honestly) attempted to understand the definition.  It is only recommended to those who believe that the definition is clear, and want to see evidence to the contrary.

The subjects covered in this document are large and complex, and there is a risk of growing to become unwieldy. The scope of the document is limited, though: to summarize the design considerations important for creating W3C specifications that enable stable standards for the Web, in a way that the Web standards community can discuss issues and altenatives with a common framework, and the evolution of the Web not hindered by interoperability concerns.

One of the important aspects of the Web that is, unlike many other communication applications, there is a broad community of Web developers: designers, programmers, individuals, software engineers, who create instances or strings intended for use in the languages of the Web. Because of the breadth of users as well as large numbers of implementations, the evolution and standadization of the Web has been different from the evolution of most previous communication standards. The history of the evolution of the web is messy: "browser wars", "best viewed by", widespread misunderstanding, slow standards. If we understand better the way in which the Web evolves, we can facilitate the development of useful standards.

The fundamental motivation for this course is that anyone responsible for digital collections will have to understand and be conversant in various aspects of the associated information technologies, in order to evaluate the work of developers, delegate tasks, write appropriate requests for proposals (RFPs), and establish reasonable management and preservation policies.

Discogs uses the Goldmine Standard for grading the condition of items listed in the Marketplace. These standards have been expanded by our community of sellers to include definitions of CD specific gradings.

This paper looks at the reality of implementation of e-commerce standards in the book and journal supply chains, and at where the barriers are to more widespread implementation. It compares this with the situation in other media, and looks at some of the challenges of convergence and divergence. Although the challenges identified are considerable, it finishes by discussing why there may be reasons for optimism about the future.

Standardization is a poorly understood discipline in practice. While there are excellent studies of standardization as an economic phenomenon, or as technical a phenomenon, or as a policy initiative, most of these are ex post facto and written from a dispassionate academic view. They are of little help to practitioners who actually are using and creating standards. The person actually creating the standards is working in an area of imperfect knowledge, high economic incentives, changing relationships, and often, short-range planning. The ostensible failure of a standard has to be examined not so much from the focus of whether the standard or specification was written or even implemented (the usual metric), but rather from the viewpoint of whether the participants achieved their goals from their participation in the standardization process. To achieve this, various examples are used to illustrate how expectations from a standardization process may vary, so that what is perceived as a market failure may very well be a signal success for some of the participants. The paper is experientially, not empirically based, and relies on my observations as an empowered, embedded, and occasionally neutral observer in the Information Technology standardization arena. Because of my background, the paper does have a focus on computing standards, rather than publishing standards. However, from what I have observed, the lessons learned apply equally to all standardization activities, from heavy machinery to quality to publishing. Standards names may vary; human nature doesn’t.

CitationStyles.org is the home of the Citation Style Language (CSL), an open XML-based language to describe the formatting of citations and bibliographies.

the recently published RFC 5988 (Web Linking) specifies relation types for web links more generally, and defines a registry for them. it also defines the use of such links in HTTP headers using the Link header field. this means that from now on, links for RESTful application do not (necessarily) have to be embedded in representations anymore. instead, if they pertain to the requested resource, they can be communicated in a Link header field, which is specifically mentioned to be semantically equivalent to HTML's <link> element and Atom's feed-level <link> element.

the immediate advantage of this approach is that links can now be used for resources where the representation does not define a place to put them, and that resources do not have to be parsed to find links connecting them to other resources. in fact, by using HEAD requests, resources do not even have to be retrieved to find the links that link them to other resources, which means that Link-aware clients can traverse RESTful services in a much more efficient way, as long as all they need are resource-level links.

INSCRIPTION is a collection of 'wordlists' maintained or recommended by the Forum on Information Standards in Heritage (FISH). It provides tools for comprehensive and consistent indexing of different aspects of the built and buried heritage. It includes, for example, standards for how to record the age and nature of a site. This in turn will help to answer both specific questions such as 'What is this site?', 'How old is it?' and more general enquiries such as 'What do we know about Roman villas?' INSCRIPTION thus complements the definitions of individual facts or 'units of information' about a site, event or resource that are recommended by FISH in 'MIDAS - a manual and data standard for monument inventories'.

Julian day is used in the Julian date (JD) system of time measurement for scientific use by the astronomy community, presenting the interval of time in days and fractions of a day since January 1, 4713 BC Greenwich noon.

"HTTP has been successfully conflating names and addresses since 1989."

The Unicode Consortium provides four standard normalization forms (see Unicode Normalization Forms [UTR #15]). These forms differ in 1) whether they normalize towards decomposed characters (NFD, NFKD) or precomposed characters (NFC, NFKC) and 2) whether they normalize away compatibility distinctions (NFKD, NFKC) or not (NFD, NFC).

For use on the Web, it is important not to lose the so-called compatibility distinctions, which may be important (see [UXML] Chapter 4 for a discussion). The NFKD and NFKC normalization forms are therefore excluded. Among the remaining two forms, NFC has the advantage that almost all legacy data (if transcoded trivially, one-to-one) as well as data created by current software is already in this form; NFC also has a slight compactness advantage and a better match to user expectations with respect to the character vs. grapheme issue. This document therefore chooses NFC as the base for Web-related text normalization.

NOTE: Roughly speaking, NFC is defined such that each combining character sequence (a base character followed by one or more combining characters) is replaced, as far as possible, by a canonically equivalent precomposed character. Text in a Unicode encoding form is said to be in NFC if it doesn't contain any combining sequence that could be replaced and if any remaining combining sequence is in canonical order.

Thanks to @samruby for a fascinating presentation to #inls520 about the messy business of #standards development! #sils

A simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.

DSPL is the Dataset Publishing Language, a representation language for the data and metadata of datasets. Datasets described in this format can be processed by Google and visualized in the Google Public Data Explorer.

The MADS/RDF (Metadata Authority Description Schema in RDF) vocabulary, a data model for authority and vocabulary data used within the library and information science (LIS) community, which is inclusive of museums, archives, and other cultural institutions.

Periodization standards for World History for Grades 5-12.

The development of the History Standards was administered by the National Center for History in the Schools at the University of California, Los Angeles under the guidance of the National Council for History Standards. The standards were developed with funding from the National Endowment for the Humanities and the U.S. Department of Education.

I fear that the digital humanities is becoming dominated by purely technical concerns of implementation, I suspect in no small measure under pressure to assist the other disciplines survive their crises of confidence and funding — as well as to avoid the severe challenges computing presents to all disciplines. One sign of this industrialization is the spread of technological orthodoxy under the banner of technical standards.

oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly.

It must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Document Object Model Application Programming Interface (RDFa DOM API) that allows simple extraction and usage of structured information from a Web document.

The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.

Standards (and their maintenance efforts) should be judged for their ability to catalyze stable polishing activities around the contact surface rather than for the qualities of the surface they were meant to describe. A good polishing process with a rough surface will always end up more polished that a well polished surface with a poor polishing process around it.

GeoJSON is a format for encoding a variety of geographic data structures. A GeoJSON object may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.

This specification adds mechanisms to the Atom Syndication Format

SPIN is a collection of RDF vocabularies enabling the use of SPARQL to define constraints and inference rules on Semantic Web models. SPIN also provides meta-modeling capabilities that allow users to define their own SPARQL functions and query templates. Finally, SPIN includes a ready to use library of common functions.

The mission of the Media Fragments Working Group, part of the Video in the Web Activity, is to address temporal and spatial media fragments in the Web using Uniform Resource Identifiers (URI).

The mission of the Media Annotations Working Group, part of the Video in the Web Activity, is to provide an ontology and API designed to facilitate cross-community data integration of information related to media objects in the Web, such as video, audio and images.

Talk given at the 2nd Linked Data on the Web workshop (LDOW) co located with WWW 2009, Madrid.

This service will attempt to download a given ORE Resource Map, either from the aggregation URI (if it resolves correctly to a resource map) or from the resource map's URI.

This file maps Internet media types to unique file extension(s).

Short URL auto-discovery is a simple way to link a long URL with a short URL. The following code should be placed in the <head> section of the HTML page: <link rel="shorturl" href="http://short.com/1234" />

RevCanonical is url shortening with a twist. Instead of creating its own super short versions of links, it checks to see if the link owner has published a shortened version of the given page using HTML link element. If not, we just return the original URL. And you should bug the link owner about providing a better alternative.

This specification contains a framework for representing pointers - entities that permit identifying a portion or segment of a piece of content - making use of the Resource Description Framework (RDF). It will also describe a number of specific types of pointers that permit portions of a document to be referred to in different ways.

We need to partition the idea of extensibility into two parts: extending the platform vs. extending the language.

This document describes an extension to the Sitemap protocol targeted at the efficient discovery and use of RDF data. The extension allows Data publishers to state where documents containing RDF data are located, and to advertise alternative means to access it, such as data dumps and SPARQL endpoints.

This module implements ISO 8601 date, time and duration parsing.

Compatibility tables for features in HTML5, CSS3, SVG and other upcoming web technologies.

The premise behind dynamic bindings is that any search engine, even one that existed prior to development of the standard, need only to provide a dynamic binding - a self-description. It need make no other changes in order to be accessible. A client will be able to access any search engine that provides a description, if only it implements the capability to read and interpret the description and use it to formulate a request (including a query) and interpret the response.

The OASIS Search Web Services Technical Committee is developing search and retrieval web services, integrating various approaches under a unifying model, an Abstract Protocol Definition.

Links to documentation for various styles of OCR output.

Specs for EventsML-G2.

Specs for NewsML-G2.

LCCN Permalinks are persistent URLs for bibliographic records in the Library of Congress Online Catalog.

The Kernel vocabulary, based on a subset of the Dublin Core (DC) metadata element set, aims to describe objects of any form or category, but its reach is limited to a small number of fundamental questions such as who, what, when, and where.

This ontology can be used as a citation ontology, as a document classification ontology, or simply as a way to describe any kind of document in RDF.

A request to any web server in existence can be modeled in the simplest of terms: what, who, where, why, when, and how.

How to link to COPAC via OpenURL.

The DjVuXML DTD is a simplification of the HTML DTD. Each of the specified pages of a DjVu document are represented as OBJECT elements within the BODY element of the XML file.

This site describes a number of ways to encode location in RSS and Atom feeds.

A ruby/python based HTML parser/tokenizer based on the WHATWG HTML5 specification for maximum compatibility with major desktop web browsers.

COinS (ContextObjects in Spans) is a simple, ad hoc community specification for publishing OpenURL references in HTML.

AtomOwl is a project to create an official ontology for the atom syndication format.

Open Text Mining Interface (OTMI) is an initiative from Nature Publishing Group (NPG). It aims to enable scholarly publishers, among others, to disclose their full text for indexing and text-mining purposes but without giving it away in a form that is rea

OWL is suited to detailed modeling and reasoning; SKOS is suited to modeling intuitive conceptual structures, used for retrieval, navigation and browsing.

The Search web service is a means of opening a database to external enquiry in a standardized manner that facilitates discovery of query and response possibilities and makes it possible for heterogeneous databases to be queried simultaneously with the sam

The FRBRoo is a formal ontology intended to capture and represent the underlying semantics of bibliographic information and to facilitate the integration, mediation, and interchange of bibliographic and museum information.

A a comprehensive framework for recording descriptions of named geographic places, including the core elements of toponyms (and their history), spatial location (in various representations), and classification (according to referenced typing schemes), and

The ADL Gazetteer Protocol is a lightweight, stateless, XML- and HTTP-based protocol for accessing gazetteers: dictionaries of geographic placenames.