Interoperability Standards Finder
Lookup standards
The Interoperability Standards Finder is an extract of our catalog of interoperability related standards.
Name:: Java Specification Request 362 ()
Description: Java Specification Request 362: Portlet Specification 3.0 equests the creation of the next version of the Portlet Specification. An update is necessary to address progress in Java EE Java technology that has taken place since JSR286 Portlet Specification 2.0 became final in 2008 and also to address new technology themes that have since come into focus.
Name:: Java Specification Request 286 ()
Description: JSR 286: Portlet Specification 2.0 requests the creation of the next version of the Portlet Specification. The main goal of this version is to align the Java Portlet Specification with J2EE 1.4, other JSRs relevant for portlet programming, like JSR 188, the next version of Web Services for Remote Portlets (WSRP).
Name:: NSW Government Data Interoperability Standards ()
Description: Various data standards which support data interoperability and exchange of information by NSW Government agencies. Standards offer a common language enabling agencies to appropriately share or compare data managed across diverse systems. Invliding Standard Approach to Metadata, Standard Approach to Information Architecture, Standard for Customer Reference Data, Standard for Spatially Enabling Information, Standard for Human Services Classification, Standard for Data Quality Reporting
Name:: .NET Framework (.NET)
Description: .NET is a component model from Microsoft. The model is proprietary protected, eventhough some open source projects recreate parts of .NET.
Name:: .NET Messenger Service (.NET Messenger Service)
Description: A proprietary instant messaging protocol from Microsoft. The official clients are Windows Messenger and MSN Messenger, but clients such as Miranda and Gaim can be used as well.
Name:: General encryption algorithms (3DES, AES, Blowfish)
Description: Widely used algorithms, such as DES, AES (Advanced Encryption Standard) and Blowfish can be used for encryption.
Name:: IEEE 802.11b (802.11b)
Description: 802.11b-standard (PDF)
Name:: IEEE 802.11g (802.11g)
Description: Specification: IEEE 802.11g-2003.
Name:: 802.11X(EAP) (802.11X(EAP))
Description: Many implementations have security faults. Security experts should be consulted when planning wireless networks for proper implementation.
Name:: ISO/IEC 8859-1 (8859-1)
Description: ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1: Latin alphabet No. 1, is part of the ISO/IEC 8859 series of ASCII-based standard character encodings, first edition published in 1987. It is generally intended for Western European languages (see below for a list). It is the basis for most popular 8-bit character sets, including Windows-1252 and the first block of characters in Unicode.
Our comments: Use UTF-8.
Name:: Advanced Audio Codec (AAC)
Description: Advanced Audio Codec was originally defined as a replacement for MP3 in MPEG-2, and was further improved for MPEG-4. Normally AAC audio is placed in a MP4 container, but raw AAC files is also an option, although not advised. For AAC license information, go to license information.
Name:: Dolby Digital (AC3)
Description: Dolby digital is the dominating audioformat for digital Movie audio and is among other things used for DVD’s. AC3 is seldom used for audiofiles, but can be placed as raw data in a file. Dolby was involved in the development of AAC, which gives a superior sound quality compared to AC3, at all bit-rates. This link has more information concerning license rules for AC3.
Name:: ActiveX Data Objects (ADO)
Description: ADO is a component from Microsoft, which gives a common interface for accessing databases. ADO has now been replaced by ADO.NET. For external parties it should be possible to access the database via web-services.
Name:: .NET Data Access Architecture (ADO.NET)
Description: ADO.NET is a .NET component. It is an interface for accessing data from various sources, including databases. ADO.NET is replacing ADO. For external parties it should be possible to access the database via web-services. For strictly internal projects ADO.NET can be considered a de facto standard.
Name:: ArchiMate 2.1 Specification (ArchiMate)
Description: ArchiMate, an Open Group Standard, is an open and independent modeling language for Enterprise Architecture that is supported by different tool vendors and consulting firms. The ArchiMate Standard provides instruments to enable enterprise architects to describe, analyze, and visualize the relationships among business domains in an unambiguous way.
Name:: ArchiMate Model Exchange File Format (Archimate Exchange)
Description: The Open Group ArchiMate Model Exchange File Format Standard defines a file format that can be used to exchange data between systems that wish to import and export ArchiMate models. ArchiMate exchange files enable exporting content from one ArchiMate modeling tool or repository and importing it into another while retaining information describing the model in the file and how it is structured, such as a list of model elements and relationships. The Standard focuses on the packaging and transport of ArchiMate models.
Name:: Advanced Systems Format (ASF)
Description: Advanced Systems Format is Microsoft proprietary multimedia container. It is primarily used for the Windows Media Video and Windows Media Audio formats, but can also be used for multimedia compressed with other codecs.
Name:: Atom Publishing Format and Protocol (Atom)
Description: Atom is an XML-based document format that describes lists of related information known as feeds. Feeds are composed of a number of items, known as entries, each with an extensible set of attached metadata. For example, each entry has a title.
The primary use case that Atom addresses is the syndication of Web content such as weblogs and news headlines to Web sites as well as directly to user agents.
Our comments:
Name:: Audio Video Interleave (AVI)
Description: AVI is a proprietary format from Microsoft, designed for containing video with or without sound. The multimedia is normally compressed with a codec. AVI is a specialization of the RIFF format. AVI is an old and limited format, but is still widely used. It does not support streaming.
Name:: Border Gateway Protocol (BGP) v4 (BGPv4)
Description: BGP v4 is the de facto exterior routing protocol of the Internet.
Name:: IEEE 802.15.1 (Bluetooth 1.0)
Description: 802.15.1, also called Bluetooth 1.0. Specification: 802.15.1-2002
Name:: Windows Bitmap (BMP)
Description: A proprietary, but royalty-free, bitmapped graphics format used by Microsoft Windows programs, and the Windows operating system itself. Supported on other platforms too. Lossless compression can be specified, but only uncompressed files can be assumed to be supported.
Name:: Business Process Execution Language for Web Services 2.0 (BPEL)
Description: BPEL is a XML based business process execution language under development by major suppliers.
Our comments: BPEL 2.0 blev godkendt som en OASIS-standard i april 2007.
Den hidtidige version 1.1 understøttes i mange værktøjer, men der er mange gode grunde til at satse på version 2.0, som bl.a. omfatter flere nøgleprocesser end v1.1, og som alle leverandører også har udmeldt de vil satse på i kommende releases af deres løsninger.
OIO-kataloget er ikke opdateret hvad denne standard angår.
Name:: Business Process Modeling Notation 1.1 (BPMN 1.1)
Description:
Our comments: Brug nyere version af BPMN.
Name:: Business Process Modeling Notation Version 1.2 (BPMN 1.2)
Description:
Our comments: Brug hellere BPMN 2.0
Name:: Business Process Model And Notation (BPMN 2.0)
Description: The BPMN specification provides a graphical notation for specifying business processes in a Business Process Diagram. Its goal is to support BPM by providing a standard notation that is comprehensible to business users yet represents complex process semantics for technical users.
Name:: Computer Managed Instruction Guidelines (CMI)
Description: Developed by the Aviation industry CBT Committee (AICC), CMI is considered the oldest eLearning standard in the world orginating from the needs of the aviation industry to create a common CBT system. Subsequently, the standard was shifted to encompass web-based training.
Name:: Component Object Model (COM+)
Description: Microsoft component object model contains an inter process communication mechanism. See http://msdn.microsoft.com
Name:: CORBA/IIOP/IDL (CORBA)
Description: CORBA/IIOP is a language independent disitributed model. The 2.6 specifcation is recommended to exclude the OMG component model implemented in CORBA 3.0. at present time.
Name:: Cross-Origin Resource Sharing (CORS)
Description: This document defines a mechanism to enable client-side cross-origin requests. Specifications that enable an API to make cross-origin requests to resources can use the algorithms defined by this specification. If such an API is used on http://example.org resources, a resource on http://hello-world.example can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: http://example.org as response header), which would allow that resource to be fetched cross-origin from http://example.org.
Name:: Common Procurement Vocabulary (CPV)
Description: European parlament and counsils order (Ef) Nr. 2195/2002, CPV extends the 6 digit Classification of Products by Activity (CPA) coding scheme and the NACE Rev. 1 (General Industrial Classification of Economic Activities within the European Communities) to provide an 8 digit + check digit product type identification scheme. Multilingual tables map the codes to national product vocabularies.
Name:: Creative Commons (Creative Commons)
Description: Creative commons provides a way to specify rights for online content. Using creative commons, the author or responsible party for the work can retain copyright while making exceptions based on desired usage.
Name:: Cascading Style Sheets (CSS)
Description: CSS should be used according to the W3C-specification.
Our comments: CSS er en af kernestandarderne for webben. Specifikt har CSS en fremtrædende rolle omkring Ajax og dynamiske webtjenester.
En af de traditionelle udfordringer med CSS er, at browserunderstøttelsen af selve standarden har været ringe i de fleste gængse webbrowsere. Dette indebærer, at webdesignere har været og er nødsaget til at teste i mange forskellige browsere.
Microsofts browser Internet Explorer har i flere generationer brugt CSS, men gør samtidig brug af mange proprietære CSS-udvidelser i form af de såkaldte conditional comments.
Man kan validere CSS hos W3C.
Name:: Custom Elements (Custom Elements)
Description: This specification describes hot to let authors define their own elements, with new tag names and new script interfaces. by enabling the author to define and use new types of DOM elements in a document.
Custom Elements is a W3C Working Draft 16 December 2014.
Name:: DivX (DivX)
Description: DivX is a proprietary codec from DivXNetworks. DivX stated as an open project, but in September 2001 it was closed. From version 4, DivX is an MPEG-4 codec, but is often used for compressing video in AVI files.
Name:: Domain name services (DNS)
Description: IETF RFC 1035 defines the internet domain system and the protocols used. The official danish guidelines for assigning domain names can be found on dk-hostmaster.dk. Public authorities should avoid using Danish characters in domain names due to interoperability problems for many users as well as to patent issues.
Name:: Microsoft Word Binary File (DOC)
Description: Because the DOC file format was a closed specification for many years, inconsistent handling of the format persists and may cause some loss of formatting information when handling the same file with multiple word processing programs. Some specifications for Microsoft Office 97 binary file formats were published in 1997 under a restrictive license, but these specifications were removed from online download in 1999. Specifications of later versions of Microsoft Office binary file formats were not publicly available. The DOC format specification was available from Microsoft on request since 2006 under restrictive RAND-Z terms until February 2008. Sun Microsystems and OpenOffice.org reverse engineered the file format. On February 15, 2008, Microsoft released a .DOC format specification under the Microsoft Open Specification Promise. However, this specification does not describe all of the features used by DOC format and reverse engineered work remains necessary.[16] Since 2008 the specification was changed several times, the last change was made in October 2014.
Name:: Document Object Model (DOM)
Description: The Document Object Model, DOM, is a W3C-specification. DOM is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents.
DOM Level 1 provided a complete model for an entire HTML or XML document, including means to change any portion of the document.
DOM Level 2 was published in late 2000. It introduced the “getElementById” function as well as an event model and support for XML namespaces and CSS.
DOM Level 3, the current release of the DOM specification, published in April 2004, added support for XPath and keyboard event handling, as well as an interface for serializing documents as XML.
DOM Level 4 is currently being developed.
The W3C WebApps Working Group continues developing standards for web-based applications and service.
Name:: DS484 (DS484)
Description: Deprecated Danish standard DS484 was an adoption of international standards for information security.
Name:: Encryption algorithms for keytransport (DSA, RSA)
Description: Widely used algorithms are RSA and DSA.
Name:: Directory Services Markup Language (DSML)
Description: DSML provides a standard for the expression and exchange of LDAP schemas.
Name:: Document Type Definition (DTD)
Description: Meta language for development of syntaxes in SGML and XML documents. Use should be limited to classic documents. However, forms and data oriented exchange should be described in a W3C XML Schema. DTD exchange should be validated by security control.
Name:: Dublin Core (Dublin Core)
Description: Dublin Core forms a vital starting point for det danish work on a OIO meta data core.
Name:: Electronic Business using eXtensible Markup Language (ebXML)
Description: ebXML is a global effort to standardise the exchange of business data coordinated by business processes. ebXML supports the common business-to-business (B2B) transactions. This includes: Reliable exchange of messages; non rejection; long running transactions; process choreography; explicit / negotiated agreement on processes; choice of connections and business semantics.
Name:: Electronic Business using eXtensible Markup Language (ebXML)
Description: ebXML is a global effort to standardise the exchange of business data coordinated by business processes. ebXML supports the common business-to-business (B2B) transactions. This includes: Reliable exchange of messages; non rejection; long running transactions; process choreography; explicit / negotiated agreement on processes; choice of connections and business semantics.
Name:: New Standardized Material and Service Classification (eClass)
Description: eCl@ss is a 4-level hierarchical classification system with a keyword register of 12,000 words split into over 22 segments, 366 groups, 2725 subgroups and 10190 commodity classes. eCl@ss maps market structure for industrial buyers and supports engineers at development, planning and maintenance. Through the access either via the hierarchy or over the key words both the expert as well as the occasional user can navigate in the classification. An unique feature of eCl@ss is the integration of attribute lists for the description of material and service specifications. (http://www.diffuse.org/semantics.html). Cologne Institute for Business Research.
Name:: x.12 and UN/EDIFACT (EDI)
Description: Many present systems uses EDIFACT, especially for transferring sensitive information, such as financial transactions and data about health issues. Further information can be found on DISA, X12 and UNCEFACT.
Name:: IP encapsulationsecurity with IP Encapsulating Security Payload (ESP)
Description: ESP v3 offers Security functions like IPv4 and IPv6, and work on the IP protocol level with wider facilities for entrusted transportation, use of tunnels etc.
Name:: Macromedia Flash (Flash)
Description: Flash is a proprietary protected format, but widely used and supported. Should only be used when animations are important from a user perspective and should never be the sole option for navigation or any such important interface aspects.
Name:: File transfer protocol (FTP/HTTP)
Description: FTP (RFC 959) (with restart and regeneration) is used to transfer larger files. Smaller files can be transferred by HTTP (RFC 2616) for file transport.
Name:: Graphics Image Format (GIF)
Description: GIF is widely used as an image format for the web. See GIF specification. The GIF format uses the LZW loss-less data compression algorithm. LZW is patented, but known patents have expired. GIF supports transparent areas. The PNG format was created to replace GIF for use as a single-image web format, and should be considered as a superior alternative to GIF-images both concerning functionality and openness.
Name:: Geography Markup Language (GML)
Description: International XML-based language for describing and encoding geospatial information. An application of XML, a specification developed by members of the Open GIS Consortium. GML is an XML encoding for spatial data, a schema-writing language for spatial information. De facto use: GML 2.1.2, future direction:
GML 3.0. Danish Geoforum is working with localising basic specs.
Name:: HyperText Markup Language HTML 4.01 (HTML)
Description: HTML 4.01 it the classic W3C-specification.
Our comments: HTML 4.01 er den oprindelige webstandard. Den understøttes stadig, men har en masse begrænsninger og problemer.
Istedet bør XHTML benyttes.
Name:: HTML Imports (HTML Imports)
Description: HTML Imports are a way to include and reuse HTML documents in other HTML documents.
W3C Working Draft 11 March 2014, so still only for experimental use.
Name:: Hypertext Markup Language HTML5 (HTML5)
Description: HTML5, a work in progress, intends to replace HTML 3.2, HTML 4, and XHTML 1.x.
Our comments: Although HTML5 has been around for a while, and is used for both classic desktop website and mobile apps, the providers of browsers and app frameworks have yet to implement the full standard. For example. multi-threading called Web Workers. iOS did not support Web Workers until version 7.1 (released March 10, 2014) and Android did not support Web Workers until KitKat (released November 12, 2014).
Name:: HyperText Transfer Protocol (HTTP)
Description: The Hypertext-specification (RFC 2616, HTTP v1.1) includes online public services provided on the internet. RFC 2616 contains an upgrading mechanism in HTTP/1.1 to start a Transport Layer Security (TLS) via an existing TCP connection.
Name:: Information and Content Exchange (ICE 2.0)
Description: The ICE specification provides businesses with an XML-based common language and architecture that facilitates automatic exchanging, updating, supplying and controlling of assets in a trusted fashion without manual packaging or knowledge of remote Web site structures. ICE 1.0 is a W3C-Note
Name:: Internet Message Access Protocol (IMAP)
Description: IETF RFC 3501 specifies a method to access public electronic mail or messages, stored on a (possibly shared) mail server. In other words the method allows a client (email program) to access foreign storages as if they where local. For example email, stored on an IMAP server, could be accessed from a home PC, a work station in the office or from a travellers laptop, without the need for sending messages and files between these computers.
Name:: Instant Messaging / Presence Protocol, RFC 2779 (IMPP)
Description: Instant Messaging or ‘chat’, is relatively widely used amongst internet users. The Instant Messaging and Presence Protocol (IMPP) defines a standard protocol for clients using this standard.
Name:: IMS (IMS)
Description: IMS is a widely used standard for e-learning systems. The IMS Global Learning Consortium develops and promotes the adoption of open technical specifications for interoperable learning technology.
Name:: RTF mail (Indlejret via klient, mul)
Description: A number of mail clients, but not all, supports included RTF in email, making it possible for the user to format the contents. Should not be used for communication with external users, as there is a risk that these can not read such mails properly.
Name:: IP-Security with IP Security Protocol (IPSEC)
Description: Security in the transportation level is necessary, but not covering all aspects of Security. IETF standards RFC2402 and 2404 work on the IP transport level. Internet Key Exchange (IKEv2) is an integrated part of of IPsec.
Name:: Standard Internet protocol (IPv4)
Description: IETF RFC 791 specifies the underlying internet protocol.
Name:: Future internet protocol (IPv6)
Description: It is the policy to move to IPv6, whenever there is a competitive urge to do so. When IPv6 is an option, suppliers of operating systems and applications can implement support of this standard. A coexistence of the two standards is recommended IPv4 will sustain a while (5 years or longer) . We recommend however to start planning of IPv6-integration, before this standard is incorporated and scrutinised through IPv4 and IPv6 in actual accusations.
Name:: Internet Relay Chat (IRC)
Description: One of the oldest forms of instant messaging.
Variations in server rules and policies between different IRC networks (e.g. IRCnet and EFnet) and within each network makes IRC a somewhat segmented standard.
Name:: Specification and Standardization of Data Elements (ISO 11179)
Description: ISO/IEC 11179 Information technology — Specification and standardization of data elements:
- Part 1: Framework for the specification and standardization of data elements
- Part 2: Classification for Data Elements
- Part 3: Basic Attributes of Data Elements
- Part 4: Rules and Guidelines for the Formulation of Data Definitions
- Part 5: Naming and Identification Principles for Data Elements
- Part 6: Registration of Data Elements.
Name:: Environmental management systems — Requirements with guidance for use (ISO 14001:2004)
Description: ISO 14001:2004 specifies requirements for an environmental management system to enable an organization to develop and implement a policy and objectives which take into account legal requirements and other requirements to which the organization subscribes, and information about significant environmental aspects. It applies to those environmental aspects that the organization identifies as those which it can control and those which it can influence. It does not itself state specific environmental performance criteria.
ISO14001:2015 is due September 2015.
Our comments: Use ISO14001:2015.
Name:: Environmental Management Systems (ISO 14001:2015)
Description: The revision of ISO 14001, one of ISO’s most widely used standards, has now entered its last stage, with the new version due to be published by tSeptember 2015.
Name:: Compliance management systems – Guidelines (ISO 19600:2014)
Description: ISO 19600:2014 provides guidance for establishing, developing, implementing, evaluating, maintaining and improving an effective and responsive compliance management system within an organization. The guidelines on compliance management systems are applicable to all types of organizations. The extent of the application of these guidelines depends on the size, structure, nature and complexity of the organization. ISO 19600:2014 is based on the principles of good governance, proportionality, transparency and sustainability.
Name:: Occupational health and safety management systems – Requirements (ISO 45001)
Description: This coming standard provides requirements for an effective OH&S management system.
Name:: Quality management (ISO 9000)
Description: The ISO 9000 family addresses various aspects of quality management and contains some of ISO’s best known standards. The standards provide guidance and tools for companies and organizations who want to ensure that their products and services consistently meet customer’s requirements, and that quality is consistently improved.
Standards in the ISO 9000 family include:
ISO 9001 – sets out the requirements of a quality management system
ISO 9000 – covers the basic concepts and language
ISO 9004 – focuses on how to make a quality management system more efficient and effective
ISO 19011 – sets out guidance on internal and external audits of quality management systems.
Name:: Quality management systems — Requirements (ISO 9001:2008)
Description: ISO 9001:2008 specifies requirements for a quality management system where an organization needs to demonstrate its ability to consistently provide product that meets customer and applicable statutory and regulatory requirements, and aims to enhance customer satisfaction through the effective application of the system, including processes for continual improvement of the system and the assurance of conformity to customer and applicable statutory and regulatory requirements. All requirements of ISO 9001:2008 are generic and are intended to be applicable to all organizations, regardless of type, size and product provided.
ISO 9001: 2015 http://www.iso.org/iso/home/standards/management-standards/iso_9000/iso9001_revision.htm
Our comments: Use the 2015 version.
Name:: Quality Management Systems (ISO 9001:2015)
Description: ISO 9001, the world’s leading quality management standard, is under revision, with an updated version due by the end of 2015. A Final Draft is under review.
Name:: ISO base media file format (ISO MF)
Description: Base format for media file formats, designed to contain time-based audio-visual information in a flexible, extensible format that facilitates interchange, management, editing, and presentation of the media. This presentation may be âlocalâ to the system containing the presentation or may be via a network or other stream delivery mechanism. The file structure is object-oriented; a file can be decomposed into constituent objects very simply, and the structure of the objects inferred directly from their type. The file format is designed to be independent of any particular network protocol while enabling efficient support for them in general. Specification is available for purchase only.
Name:: ISO 27000 (ISO27000)
Description: This International Standard provides the overview of information security management systems, and terms and definitions commonly used in the ISMS family of standards. This International Standard is applicable to all types and sizes of organization (e.g. commercial enterprises, government agencies, not-for-profit organizations).
Name:: ISO 27001 (ISO27001)
Description: This International Standard specifies the requirements for establishing, implementing, maintaining and continually improving an information security management system within the context of the organization. This International Standard also includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in this International Standard are generic and are intended to be applicable to all organizations, regardless of type, size or nature.
Name:: Java 2 Platform, Enterprise Edition (J2EE)
Description: J2EE is the Java based component model from Sun. The standard is widely accepted by many suppliers.
Name:: ECMAScript 2015 (JavaScript)
Description: This Ecma Standard defines the ECMAScript 2015 Language. It is the sixth edition of the ECMAScript
Language Specification. Since publication of the first edition in 1997, ECMAScript has grown to be one of the
world’s most widely used general purpose programming languages. It is best known as the language
embedded in web browsers but has also been widely adopted for server and embedded applications. The
sixth edition is the most extensive update to ECMAScript since the publication of the first edition in 1997.
Goals for ECMAScript 2015 include providing better support for large applications, library creation, and for use
of ECMAScript as a compilation target for other languages. Some of its major enhancements include modules,
class declarations, lexical block scoping, iterators and generators, promises for asynchronous programming,
destructuring patterns, and proper tail calls. The ECMAScript library of built-ins has been expanded to support
additional data abstractions including maps, sets, and arrays of binary numeric values as well as additional
support for Unicode supplemental characters in strings and regular expressions. The built-ins are now
extensible via subclassing.
Name:: Java Database Connectivity (JDBC)
Description: JDBC is a part of the Java API designed for accessing databases. JDBC is primarily aimed towards relational databases. The Java 2 Platform also includes support for ODBC, meaning that databases, which only support ODBC, can be accessed via JDBC. For external parties it should be possible to access the database via web-services. For strictly internal projects JDBC can be considered a de facto standard.
Name:: Java Data Objects (JDO)
Description: JDO is a part of the Java API designed for materializing object instances without knowing how they are materialized.
Name:: Joint Photographic Expert Group (JPEG, JPG)
Description: JPEG is a proprietary protected format, but widely used and supported. Also known as ITU-T T.81 and ISO/IEC 10918-1. Further on IETF RFC 2435. JPEG supports both loss-less and lossy compression, but is mostly used for the latter.
Name:: JSON (JSON)
Description: JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard (Javascript). JSON defines a small set of formatting rules for the portable representation of structured data.
JSON became ECMA404 in 2013. Originally, IETF RFC4627, the application/json Media Type for JavaScript Object Notation (JSON) was propsed by D. Crockford in 2006.
Our comments: Use best practices for good javascript.
Name:: JSON-based Serialization for Linked Data (JSON-LD)
Description: Linked Data is a way to create a network of standards-based machine interpretable data across different documents and Web sites. It allows an application to start at one piece of Linked Data, and follow embedded links to other pieces of Linked Data that are hosted on different sites across the Web.
JSON-LD is a lightweight syntax to serialize Linked Data in JSON [RFC4627]. Its design allows existing JSON to be interpreted as Linked Data with minimal changes. JSON-LD is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines. Since JSON-LD is 100% compatible with JSON, the large number of JSON parsers and libraries available today can be reused.
JSON-LD 1.0 became a W3C Recommendation 16 January 2014.
Name:: Java Specification Request 168 (JSR168)
Description: The JSR168 Portlet Specification and API 1.0 is a deprecated portlet standard used by several portal vendors. The spec aims to enable interoperability between Portlets and Portals, by defining a set of Java APIs for Portal computing addressing the areas of aggregation, personalisation, presentation and security. A vendor-neutral reference implementation is done in the Pluto-project.
Name:: Lightweight Directory Access Protocol (LDAP)
Description: LDAP is primarily used for accessing X.500 directories via TCP/IP. For more information concerning the relations between LDAP and X.500, we refer to this whitepaper. LDAP V3 should be used for user access to public user databases.
Name:: Learning Object Metadata (LOM)
Description: Standard that defines the structure of a metadata instance for a learning object. For this standard, a learning object is defined as any entity (digital or non- digital) that may be used for learning, education or training. Maintained by the IEEE LTSC (Learning Technology Standards Committee).
Name:: HTML mail (MIME text/html)
Description: Used for example in email based news letters. Use valid HTML and remember always to offer pure text as an alternative as not all mail clients supports HTML mail.
Name:: MetaObject Facility Specification (MOF)
Description: The MetaObject Facility Specification (MOF) is the foundation of OMG’s industry-standard environment where models can be exported from one application, imported into another, transported across a network, stored in a repository and then retrieved, rendered into different formats (including XMI, OMG’s XML-based standard format for model transmission and storage), transformed, and used to generate application code. These functions are not restricted to structural models, or even to models defined in UML – behavioral models and data models also participate in this environment, and non-UML modeling languages can partake also, as long as they are MOF-based. We’ll explain what this means in a moment. The 2014 OMG MOF 2.4.2 became an ISO standard in 2014: ISO/IEC 19508:2014. OMG released version 2.5 in June 2015.
Name:: Quicktime (Mov)
Description: Quicktime is Apples proprietary format for multimedia. Several elements from this format were used as a basis for MP4. The format supports streaming.
Name:: MPEG-1/2 Audio Layer 3 (MP3)
Description: Streaming and downloading format. Proprietary format, owned by Thomson. Constant or variable bit-rate.
Name:: MPEG-4 (MP4)
Description: MPEG-4 is a term used for all codecs, which complies with the MPEG-4 standard. These codecs normally give a high level of compression in conjunction with a high image quality. A generic MPEG-4 decoder is sufficient for decoding all MPEG-4 video. Got to the following link for license terms.
Name:: MPEG-4 (MP4)
Description: MP4 is the official container for MPEG-4 multimedia. MP4 is primarily used for MPEG-4 video and AAC audio, but can also be used for multimedia in the following formats. Video in: MPEG-2 an MPEG-1, audio in MP3, MP2 and MP1, pictures in JPEG and PNG, and finally subtitles I xmt/bt text. The format can be used for streaming and has support for DRM. For license terms concerning MP4 go to MPEG LA and Via Licensing.
Name:: MPEG-2 (MPEG-2, M2V)
Description: The MPEG-2 standard is designed for video of high quality. It is used among other things for DVDs.
Name:: MPEG-1 (mpg)
Description: MPEG-1 is the first of the MPEG standards. It is among other things used for VideoCDs and small video files of low quality. Gives low image quality. Associated sound must be in MP1, MP2 or the MP3 format.
Name:: Newsgroups with Network News Transfer Protocol (NNTP)
Description: The Internets news groups (called USENET) uses NNTP (RFC 977), and where necessary is subject to security restrictions.
Name:: Public Certificates for Electronic Services (OCES)
Description: The digital signature gives a possibility to identify yourself in the digital world. The system fulfills the basic requirements for citizens, private enterprises and public authorities to exchange confidential and sensitive information via the internet in a secure manner.
The digital signature secures that a message received comes from the person who claims to have sent it. It also secures that the message has not been changed after being sent and if it is also encrypted that nobody unauthorised has been able to read it.
There are three certificate policies for person, employee and enterprise certificates. The OCES certificate policies are based on the ETSI TS 102 042 v 1.1.1. (2002-04) standard and establish a standard for the CA’s handling of certificates and for the content of these. The certificates policies define the security level which as a minimum must be fulfilled if the CA wants to issue OCES certificates. At the moment there is one OCES CA, TDC Certificeringscenter.
The certificate policies can be found at www.signatursekretariatet.dk. More information about the digital signature kan be found at www.digitalsignatur.dk.
Name:: Open Database Connectivity (ODBC)
Description: ODBC is an interface for accessing databases. Originally only supported by Microsoft Windows, but today implementations for UNIX, OS/2 and Macintosh also exist. For external parties it should be possible to access the database via web-services. For strictly internal projects ODBC can be considered a de facto standard.
Name:: OpenOffice Calc Spreadsheet Format (ODS)
Description: OpenOffice Calc spreadsheet format is an open XML based format, submitted to OASIS. It is currently not widely supported.
Name:: Ogg Project (Ogg)
Description: Ogg is a file format designed for containing different forms of multimedia. Ogg is a product of the Xiph.org organisation and is a completely open and free of patents. Ogg is primarily used for the audio formats Vorbis, Speex, and Flac and the video format Theora. The format supports streaming.
Name:: Office Open XML (OOXML, Ecma-376, Open XML)
Description: ISO/IEC 29500-1:2012 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations, based on the Microsoft Office 2008 applications. It specifies requirements for Office Open XML consumers and producers that comply to the strict conformance category.
Our comments:
Name:: OpenDocument Format for Office Applications (OpenDocument. ODF, ISO26300)
Description: ISO/IEC 26300-1:2015 the Open Document Format for Office Applications (OpenDocument) Version 1.2 specification. It defines an XML schema for office documents. Office documents includes text documents, spreadsheets, charts and graphical documents like drawings or presentations, but is not restricted to these kinds of documents. The XML schema for OpenDocument is designed so that documents valid to it can be transformed using XSLT and processing with XML-based tools.
ISO/IEC 26300:2015 was released in June 2015.
Name:: Open System for CommunicAtion in Realtime (OSCAR)
Description: A proprietary instant messaging protocol from AOL. The owners have a policy of deliberate non-interoperability towards other clients than their own. The official client are AIM and ICQ, but clients such as Miranda and Gaim can be used as well.
Important! As the protocol is proprietary, the link refers to an unofficial guide.
Name:: Open Shortest Path First (OSPF)
Description: OSPF is used as an Interior Gateway Routing Protocol.
Name:: OWSA-model T (OWSA-model T)
Description: Danish localization of WS-I Basic Profile 1.1 with specified use of OCES certificates and OIOXML in a P2P integration demanding confidentiality.
Our comments: OWSA-Model T beskriver en meget udbredt form for sikring af Web Services transaktioner nemlig punkt-til-punkt sikring ved hjælp af SSL.
Standarden er også nyttig som inspiration ved udvikling af Web Services der udveksler data standardiseret i OIOXML format.
Name:: Portable Document Format (PDF)
Description: Portable Document Format (PDF) is a file format used to present documents in a manner independent of application software, hardware and operating systems. Each PDF file encapsulates a complete description of a fixed-layout flat document, including the text, fonts, graphics and other information needed to display it.
The following specialized subsets of PDF specification has been standardized as ISO standards (or are in standardization process):
PDF/X (since 2001 – series of ISO 15929 and ISO 15930 standards) – a.k.a. PDF for Exchange
PDF/A (since 2005 – series of ISO 19005 standards) – a.k.a. PDF for Archive
PDF/E (since 2008 – ISO 24517) – a.k.a. PDF for Engineering
PDF/VT (since 2010 – ISO 16612-2) – a.k.a. PDF for exchange of variable data and transactional (VT) printing.
PDF/UA (since 2012 – ISO 14289-1) – a.k.a. PDF for Universal Accessibility
Name:: Portable Network Graphics (PNG)
Description: PNG complies with a W3C-specification. PNG supports loss-less compression and 254 levels of transparency. Further information on W3C’s PNG pages and The PNG Home Site.
Name:: Post Office Protocol – Version 3 (POP)
Description: E-mail products facillitating mail products which as a minimum should correspond to POP3 for access to distant mailboxes. This includes RFC 1939; RFC 1957 and RFC 2449.
Name:: ODBC/JDBC/ADO/JDO (Proprietære databaser)
Description: There is a great number of widely used proprietary, often platform independent, database standards. Integration and interoperability problems in relation to external parties should be expected when using such standards.
Name:: Role-Based Access Control (RBAC, ANSI INCITS 359-2004)
Description: RBAC is a conceptual model for role based access control applicable for a large number of applications. RBAC is published by the InterNational Committee for Information Technology Standards (INCITS) at the American National Standards Institute (ANSI).
Name:: Resource Description Framework (RDF)
Description: RDF is a widely used format for Meta data description.
Name:: Real Audio (Real Audio)
Description: Real Audio is RealNetworks proprietary audioformat. It is possible to obtain the source code to Reals codecs. Implementations that support the format require a license payment to RealNetworks. There exist both a free player for Windows and an open source player for Linux/UNIX. Real Audio is primarily for streaming and supports both lossless and lossy compression.
Name:: Real Video (Real Video)
Description: Real Video is RealNetworks proprietary videoformat. It is possible to obtain the source code to Reals codecs. Implementations that support the format require a license payment to RealNetworks. There exist both a free player for Windows and an open source for playerLinux/UNIX.
Name:: Reliable Secure Profile Version 1.0 (Reliable Secure Profile)
Description: A set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability. It also contains a set of executable test assertions for assessing the conformance to the profile. Final Material 2010-11-09
Name:: Resource Interchange File Format (RIFF)
Description: RIFF (Resource Interchange File Format) is a tagged file structure for multimedia resource files. RIFF is a file structure that defines a class of more specific file formats, including WAVE, AVI, and RMID. The basic building block of a RIFF file is called a chunk. The RIFF structure is the basis for a few important file formats, but has not been used as the wrapper structure for any file formats developed since the mid 1990s.
Name:: Routing Information Protocol (RIP)
Description: Older version of RIP, does not support authentication.
Name:: Routing Information Protocol v2 (RIP2)
Description: RIP 2 is often used in small networks and LANS. RIP does not understand variable length subnet masks. RIP is limited to 15 hops and has no notion of link costs. For these reasons, OSPF is recommended where possible.
Name:: Java Remote Method Invocation (RMI)
Description: Java RMI is a distributed object model from Sun.
Name:: Remote Procedure Call Protocol (RPC, RPC binding og XDR)
Description: Remote Procedure Call is a procedure mechanism for Inter Process Communication. Includes RPC (RFC1831), RPC binding (RFC 1833) and XDR (RFC1832).
Name:: Encryption algorithms for signatures (RSA, DSA)
Description: Widely used algorithms are RSA and DSA.
Name:: RSS 1.0, RDF Site Summary/Rich Site Summary (RSS 1.0)
Description: RSS 1.0 is a more semantic and flexible format for e.g. news syndication. Based on W3C XML/RDF, allowing enlargements with XML namespaces and RDF based modularisaton. A well documented Dublin Core module exists.
Our comments: Brug Atom.
Name:: RSS 2.0, Really Simple Syndication (RSS 2.0)
Description: RSS 2.0 is a simple, XML based format for syndication of web contents such as news. The format is widely used and supported by many services and clients. RSS 2.0 is plublished by Berkman Center for Internet & Society at Harvard Law School under a Attribution/Share Alike Creative Commons licence.
Our comments: RSS bør benyttes ved syndikering af bl.a. netnyheder, pressemeddelelser, og anden kronologisk information.
På sigt bør migreres til Atom.
Name:: Rich Text Format (RTF)
Description: Rich Text Format is a proprietary protected format owned by Microsoft, but widely used and free of royalties.
Name:: E-mailSecurity with S/MIME V3 (S/MIME V3)
Description: S/MIME V3 is used, when it is suitable in e-mail based exchange of messages throughout the public sector, unless security demands dictates another approach. This includes RFC 2630, RFC 2631, RFC 2632 and RFC 2633.
Name:: Security Assertions Markup Language (SAML)
Description: SAML facilitates Single Sign-on by defining a framework for communication of security credentials such as user authentication, entitlement and attributes. SAML standardizes the way the security credentials are represented in XML. OASIS/SSTC SAML version 2.0 is recommended.
Name:: ADL Shareable Content Object Reference Model (SCORM)
Description: Defines a web-based learning ‘Content Aggregation Model’ and ‘Run-Time Environment’ for learning objects. SCORM is a collection of specifications adapted from best practices of various existing eLearning standards to provide a comprehensive suite of eLearning capabilities that enable interoperability, accessibility and reusability of web-based learning content.
Name:: Encryption algorithms for hashfunctions (SHA-1, MD5)
Description: SHA-1 and MD5 are widely used for hashfunctions. It has been established that the security of SHA-1 and MD5 is not a high as initially assumed and the algorithms are therefore not completely future-proof.
Name:: Shadow DOM (Shadow DOM)
Description: This specification describes a method of combining multiple DOM trees into one hierarchy and how these trees interact with each other within a document, thus enabling better composition of the DOM.
W3C Working Draft 17 June 2014, so experimental use only.
Name:: Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)
Description: The SIMPLE Instant Messaging protocol is based on the VoIP SIP protocol. It is under developemnt by the IETF.
Name:: Synchronized Multimedia Integration Language, SMIL 2.0 (SMIL)
Description: V. 2.0 is a deprecated W3C-specifikation, see W3C’s SMIL sider.
Follow Recommendations in W3Cs XHTML+SMIL Profile.
Our comments: Check W3Cs XHTML+SMIL Profile.
Name:: Synchronized Multimedia Integration Language, SMIL 3.0 (SMIL)
Description: The Synchronized Multimedia Integration Language (SMIL, pronounced “smile”) enables simple authoring of interactive audiovisual presentations. SMIL is typically used for “rich media”/multimedia presentations which integrate streaming audio and video with images, text or any other media type. SMIL is an easy-to-learn HTML-like language, and many SMIL presentations are written using a simple text-editor.
W3C’s SMIL pages.
Follow Recommendations in W3Cs XHTML+SMIL Profile.
Name:: E-mailtransport with SMTP/MIME (SMTP/MIME)
Description: E-mail products supporting interfaces in accordance with SMTP/MIME for message transportation. This includes RFC 2821; RFC 2822; RFC 2045; RFC 2046; RFC 2646; RFC 2047; RFC 2231; RFC 2048; RFC 3023 and RFC 2049.
Attached files to e-mails correspond to file types browsers can recognise through this specific channel.
Name:: Web surveillance using Simple Network Management Protocol (SNMP2)
Description: SNMP2 is a protocol for guidance in network control and of governing of devices attached to the net. IETF RFC 3416.
Name:: SOAP 1.1 (SOAP)
Description: Communications protocol, allowing applications to communicate with each other using http with XML based information. This can be used to exchange of structured and automaticly generated information amongst parties in an decentralised and branched environment. Recommended implementation see WS-I Basic Profile 2.0.
Name:: Speex (Speex)
Description: Speex is an advanced audioformat for speech, primarily targeted towards IP telephony. The format is free of patents and requires no license. Speex can be placed in an Ogg container.
Name:: Security Provisioning Mark-up Language (SPML)
Description: SPML is a protocol for exchange of information between Authentication and authorisation systems . Established by OASIS.
Name:: ANSI SQL (SQL)
Description: SQL is the standard language in the IT industry for relational database management systems (RDMS). ANSI X3.135-1992 (SQL-92 and ANSI SQL) is the standard for Database Language SQL.
Name:: TransportSecurity with Transport Layer Security (SSL v3/TLS)
Description: TLS (IETF RFC 2246) specifies a transport protocol for secure transportation on the internet. TLS is based on Netscape’s Secure Socket Layer protocol, SSL Version 3.0.
Name:: SSL v3/TLS IPSec (SSL v3/TLS IPSec)
Description: Strong cryptographic solutions like SSH, SSL, and IPSec were designed to transmit data securely over public channels and have proven resistant to attack over many years, and will almost certainly provide a higher level of security. Use of a tunneling protocol in an approved VPN provides the best security for wireless networks. See Interconnectivity/Security section
Name:: Scalable Vector Graphics, SVG 1.1 (SVG)
Description: SVG complies with a W3C-specification. Further on W3C’s SVG pages
Name:: OpenOffice.org 1.0 file format (SXW)
Description: Open XML-format for OpenOffice.org documents. The format is also used by StarOffice, K-Office and AbiWord. The format was accepted By OASIS and served as the first draft for OASIS Open Document Format for Office Applications to the OASIS Open Document Format for Office Applications TC.
Name:: Transmission Control Protocol (TCP)
Description: Standard transport protocol for internet based communication (RFC 793, from 1981).
Name:: Theora Project (Theora)
Description: Theora is a videocodec developed for the Ogg container. Theora is currently at an alpha stage, and is still under development. The project has a close relation ship with the company On2, whose VP3 codec has been used as a basis. VP3 is patented, but On2 has released an eternal free license.
Name:: Tagged Image File Format (TIFF)
Description: Normally an uncompressed image format. Used in situations where image quality is essential, e.g., X-ray images and DTP-systems. Used extensively for traditional print graphics. Supports both lossy and loss-less compression, as well as many proprietary extensions. Interoperability between various systems might be problematic. Bilateral interoperability-tests are recommended.
Name:: Topic Maps (Topic Maps)
Description: The purpose of topic map is to structure information and knowledge about ressources through a semantic mapping. Topic maps specifies relations between subjects and allows one to work with structured subject information independently of specific implementations. (ISO 13250)
Name:: Widget Interface (TW)
Description: This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget’s metadata and persistently storing data.
Widget Interface became a W3C Recommendation on 31 October 2013.
This specification is part of the Widgets family of specifications, which together standardize widgets as a whole. Also see the list of specifications that make up the Widgets family of specifications.
Name:: Tabulator separated text (txt)
Description: Ordinary text is an open format, supported by all spreadsheets. It is however not possible to transfer formulas with a spreadsheet using the text format, only specific data can be transferred and there is a few other restrictions.
Name:: Ordinary text (txt, mime)
Description: Ordinary text is an open format supported everywhere. The problem with this format is the limited possibilities for formatting documents. IEFT RFC822.
Name:: Universal Business Language (UBL)
Description: UBL is a common XML business document library, developed using guidelines by UN/CEFACT. UBL 0.7 is recommended.
Name:: Universal Business Language (UBL)
Description: UBL is a common XML business document library, developed using guidelines by UN/CEFACT regarding message languages executed in an ebXML context. UBL 0.7 is recommended.
Name:: UDDI v3 (UDDI)
Description: Universal Description, Discovery and Integration is used for describing the service and for discovery of the service in a wider perspective.
Name:: User Datagram Protocol (UDP)
Description: UDP (RFC 768) is an IP-based transport protocol. Can be used when necessary, but under Security regulations.
Name:: Unified Modeling Language (UML)
Description: Unified Modeling Language is a widely used standard for description of data models at the logical level.
The objective of UML is to provide system architects, software engineers, and software developers with tools for analysis, design, and implementation of software-based systems as well as for modeling business and similar processes.
UML specifies Activity Diagram, Class Diagram, Component Diagram, Sequence Diagram, Use Case Diagram and more.
Name:: United Nations Standard Products and Services Code (UN/SPSC)
Description: Taxonomy for the classification and identification of products and services. Defines a five level hierarchical taxonomy for the classification and identification of products and services. Each level contains a two-character numerical value and a textual description. The levels identify Segment, Family, Class, Commodity and Business Function. UNSPSC 7.0401 is recommended.
Name:: Unicode (Unicode)
Description: Unicode is an open standard, supporting XML, Java, ECMAScript (JavaScript), LDAP, CORBA 3.0, WML, etc. It is the recommended way of implementing the Character Set standard ISO/IEC 10646.
Version 8.0 of the Unicode Standard was released in June 2015. It includes 41 new emoji characters (including five modifiers for diversity), 5,771 new ideographs for Chinese, Japanese, and Korean, the new Georgian lari currency symbol, and 86 lowercase Cherokee syllables. It also adds letters to existing scripts to support Arwi (the Tamil language written in the Arabic script), the Ik language in Uganda, Kulango in the Côte d’Ivoire, and other languages of Africa. In total, this version adds 7,716 new characters and six new scripts.
Name:: UCS Transformation Format 8 (UTF-8)
Description: UTF-8 is a character encoding capable of encoding all possible characters, or code points, in Unicode, ISO/IEC 10646:2014 Universal Coded Character Set (UCS) defines UTF-8 and other character sets, in total 110.181 characters from the world’s scripts.
IETF RFC3629 is regarded the UTF-8 “spec”.
Name:: Ogg Vorbis (Vorbis)
Description: Streaming and downloading format. Non-proprietary, public domain format. Variable bit-rate.
Name:: Waveform Audio Format (WAV, WAVE)
Description: Can be compressed with any codec, though PCM is usually used. Results in quite large files. Non-streaming, downloading only. Constant bitrate. Subset of Microsoft’s RIFF specification.
Name:: Waveform Audio File Format (WAV, WAVE)
Description: File format for audio. Wrapper file format that can incorporate an audio bitstream with other data chunks. The default bitstream encoding is the Microsoft Pulse Code Modulation (LPCM) format. WAVE is adopted by the European Broadcast Union as the basis for Broadcast Wave Format (BWF).
Name:: Quattro Pro (wb2)
Description: Proprietary spreadsheet format belonging to Corel and part of the WordPerfect Office package.
Name:: Web Content Accessibility Guidelines 1.0 (WCAG 1.0, WAI)
Description: WAI guidelines on accessibility specified by W3C. See W3. A Danish version of the WAI guidelines can be found at the web page Tilggængelighed for alle.
Name:: Web Content Accessibility Guidelines 2.0 (WCAG 2.0)
Description:
Name:: Word Document Markup Language (WDML)
Description: Word Document ML (WordML) is based on W3C XML. With the Word Document ML specification, anyone can generate, read and process Microsoft Word documents to other formats. Read the specifics in Legal Notice.
Name:: Web services (Web Services)
Description: See category Service architecture.
Name:: Web-based Distributed Authoring and Versioning (WebDAV)
Description: RFC 2518 specifies standards for web based authoring and versioning. Amongst other places used on the Infostructurebase web site. Specifications can be found on WebDAV.org.
Name:: Wireless Equivalent Privacy (WEP)
Description: a security protocol for wireless local area networks (WLANs) defined in the 802.11b standard. Has significant, known vulnerabilities and should be phased out. New installations should not use WEP.
Name:: Windows Media Audio (WMA)
Description: Features DRM mechanisms (Windows Media Rights Manager). Supports variable bit-rates. Proprietary format, owned by Microsoft. Streaming and downloading format.
Name:: Web Map Services 1.1.1. (WMS)
Description: Provides operations protocols in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. Danish Geoforum’s guidelines in Vejledning i anvendelse af Web Map Services.
Name:: Windows Media Video (WMV)
Description: Windows Media Video is a proprietary and closed codec from Microsoft. The codec exists in several versions. From version 7 it has been based on MPEG-4, but it is not an MPEG-4 codec, and cannot be played on a MPEG-4 player. The codec is normally used in Advanced Systems Format filer. Just like Advanced Systems Format, the format is closely connected to the Windows platform. Because the codec contains support for DRM, it is illegal to create unofficial implementations for other platforms.
Name:: WordPerfect files (WPD)
Description: WordPerfects documentformat is proprietary protected and not widely used.
Name:: WS-Addressing (WS-Addressing)
Description: Web Services Addressing (WS-Addressing) provides transport-neutral mechanisms to address Web services and messages. Specifically, this specification defines XML elements to identify Web services endpoints and to secure end-to-end endpoint identification in messages. This specification enables messaging systems to support message transmission through networks that include processing nodes such as endpoint managers, firewalls, and gateways in a transport-neutral manner.
Our comments: WS-Addressing er en vigtig del i integrationer, hvor det er nødvendigt route beskeder mellem forskellige delsystemer.
Ved hjælp af addreseringsmekanismer kan man også indbygge understøttelse af asynkron besked-udvekslinger til brug for længerevarende forretningsprocesser.
Name:: Web Services Atomic Transaction v1.1 (WS-AtomicTransaction)
Description: The WS-AtomicTransaction specification provides the definition of the Atomic Transaction coordination type that is to be used with the extensible coordination framework described in WS-Coordination. This specification defines three specific agreement coordination protocols for the Atomic Transaction coordination type: completion, volatile two-phase commit, and durable two-phase commit. Developers can use any or all of these protocols when building applications that require consistent agreement on the outcome of short-lived distributed activities that have the all-or-nothing property.
Name:: Web Services Business Activity v1.1 (WS-BusinessActivity)
Description: The WS-BusinessActivity specification provides the definition of two Business Activity coordination types: AtomicOutcome or MixedOutcome, that are to be used with the extensible coordination framework described in the WS-Coordination specification. This specification also defines two specific Business Activity agreement coordination protocols for the Business Activity coordination types: BusinessAgreementWithParticipantCompletion, and BusinessAgreementWithCoordinatorCompletion. Developers can use these protocols when building applications that require consistent agreement on the outcome of long-running distributed activities.
Name:: WS-Coordination (WS-Coordination)
Description: Standard for reliability in branched environments using web services.
Name:: WS-I Basic Profile 1.2 (WS-I Basic Profile 1.2)
Description: A set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability.
Name:: WS-I Basic Profile Version 2.0 (WS-I Basic Profile 2.0)
Description: A set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability. Final Material 2010-11-09.
Name:: WS-I Basic Profile 1.1 (WS-I Basic Profile, BP1.1)
Description: The WS-I Basic Profile 1.1 consists of a set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability. Web services meeting BP1.1 conform to specified levels of interoperability.
Name:: WS-I Basic Security Profile 1.0 (WS-I Basic Security Profile)
Description: The deprecated WS-I Basic Security Profile 1.0 consists of a set of non-proprietary Web services security specifications, along with clarifications and amendments to those specifications which promote interoperability.
Name:: WS-Policy (WS-Policy)
Description: The Web Services Policy Framework (WS-Policy) provides a general purpose model and corresponding syntax to describe and communicate the policies of a Web Service. WS-Policy defines a base set of constructs that can be used and extended by other Web Services specifications to describe a broad range of service requirements, preferences, and capabilities.
Our comments: I en SOA-baseret arkitektur, vil policies være det styrende element for hvordan elementer som sikkerhed, pålidelighed og transaktioner pågår mellem forskellige Web Service snitflader.
WS-Policy vil blive et naturligt omdrejningspunkt i denne proces, og bruges allerede nu til definition af WS-Security krav i sikre Web Services.
Name:: WS-Reliability (WS-Reliability)
Description: WS-Reliability 1.1 (WS-R) provides a standard, interoperable way to guarantee message delivery to applications or Web services. This open standard is maintained by the OASIS Web Services Reliable Messaging (WSRM) Technical Committee. Since May 2005, OASIS also advances development of the “competing” WS-ReliableMessaging specifications within the OASIS open standards process. Eventually, these standards will merge into one.
Our comments: Sammen med WS-Reliable Messaging var WS-Reliability et bud på, hvorledes pålidelige Web Services transaktioner kunne specificeres.
Der er nu udbredt konsensus om, at WS-Reliable Messaging er standarden for pålidelig Web Services kommunikation.
Name:: WS-Routing (WS-Routing)
Description: WS-routing describes a standard for direction of SOAP messages between applications. WS-Addressing is recommended as an alternative to WS-Routing.
Our comments: Efterhånden som anvendelsen af Web Services vil tage til og flere vil benytte Web Services til kommunikation mellem flere forskellige noder, f.eks. i form af intermediaries, vil der opstå behov for at kunne specificere routning af Web Services beskeder.
WS-Routing bør dog ikke benyttes, da der ikke længere er aktivitet omkring standarden.
Standarden indeholder dog en række “best practices” som er værd at plukke ud, såfremt man skal skitsere en routnings scenarie med Web Services.
Name:: WS-Security (WS-Security)
Description: WS-Security is used when different organisations and/or geographicly separated addresses are integrated by means of SOAP. WS-security works with XML Encryption and XML Signature. SuppIied by OASIS (IBM; Microsoft, Verisign).
Our comments: Mange benytter i dag sikkerhed på transportniveau til at sikre punkt-til-punkt integrationer, men WS-Security er velegnet til at skabe mellem flere forskellige systemer, der indgår i en forretningsproces.
WS-Security er også en vigtig byggesten i de Web Services standarder der giver mulighed for pålidelige transaktioner samt i trust scenarier mellem forskellige systemer.
Name:: WS-Transaction (WS-TX)
Description: Set of standards for transaction control and error handling for web services.
The Web Services Transaction v1.1 specification consists of three documents: Web Services Coordination (WS-Coordination) v1.1, Web Services Atomic Transaction (WS-AtomicTransaction) v1.1, and
Web Services Business Activity (WS-BusinessActivity) v1.1
Our comments: WS-Transaction eksisterer ikke længere i én samlet form, men er i stedet delt ud i to separate standarder, WS-AtomicTransaction og WS-BusinessActivity.
WS-AtomicTransaction bruges ved kortere transaktioner, mens WS-BusinessActivity bruges ved længere forretningsprocesser.
Begge standarder er beregnet til anvendelse i relation med WS-Coordination specifikationen.
Name:: WSDL 1.1 (WSDL)
Description: Web Service Description Language is used to describe applications or services, i.e. location, functional calls and any other information relevant for the use of them. Recommended implementation see WS-I Basic Profile 1.0a.
Name:: WS Distributed Management Protocol (WSDM)
Description: For WS management using web services architecture and technology to manage distributed resources. The specification is developed under OASIS Web Services Distributed Management Technical Committee (WSDM TC).
Name:: WS-Reliable Messaging (WSRM)
Description: WS-ReliableMessaging and WS-RM Policy provides a standard, interoperable protocol for reliable message exchange using Web services. This open standard is maintained by the OASIS Web Services Reliable Exchange (WS-RX) Technical Committee, formed in May 2005. OASIS already advances development of the “competing” WS-Reliability specification within the OASIS open standards process. Eventually, these standards will merge into one.
Our comments: WS-Reliable Messaging er en konkurrerende standard til WS-Reliability og er nu bredt anerkendt som den foretrukne måde at foretage pålidelige Web Services transaktioner.
WS-Reliable Messaging indgår desuden som vigtigt element i Videnskabsministeriets projekt omkring serviceorienteret infrastruktur, OIOSI.
Name:: OASIS Web Services for Remote Portlets (WSRP)
Description: Integration of remote content and application logic into an End-User presentation has been a task requiring significant custom programming effort. Typically, vendors of aggregating applications, such as a portal, write special adapters for applications and content providers to accommodate the variety of different interfaces and protocols those providers use. The goal of this specification is to enable an application designer or administrator to pick from a rich choice of compliant remote content and application providers, and integrate them with just a few mouse clicks and no programming effort. This revision of the specification adds Consumer managed coordination, additional lifecycle management and a set of related aggregation enhancements.
The Web Services for Remote Portlets Specification v2.0 became an OASIS Standard in April 2008.
Name:: eXtensible Access Control Markup Language (XACML)
Description: XACML is a OASIS standard for exchange of access control in collaborating systems in a identity management scenario for the public sector.
Name:: eXtensible Business Reporting Language (XBRL)
Description: XBRL is an xml-based language designed for exchanging financial data as e.g. accounts. The langue is developed by the non-profit consortium XBRL International consisting of approximately 250 major companies, organisations and government agencies. I addition there is a Danish organisation XBRL Denmark whose objective is to spread the knowledge and use of XBRL in Denmark. A Danish adaptation of XBRL is adopted as an OIOXML standard and can be used in communicating with the Danish Commerce and Companies Agency.
Name:: XForms 1.0 (XForms)
Description: Web based forms processes structured data and Xforms facilitates working with XML. See W3C’s specification. Implementations should conform to W3Cs Xforms Basic Profile.
Name:: Xtensible HyperText Markup Language (XHTML)
Description: XHTML is a variant of HTML that uses the syntax of XML, the Extensible Markup Language. XHTML has all the same elements (for paragraphs, etc.) as the HTML variant, but the syntax is slightly different. Because XHTML is an XML application, you can use other XML tools with it (such as XSLT, a language for transforming XML content).
Name:: XML Key Management Specification with XML-Key Management, where a PKI-environment is used (XKMS 2.0)
Description: XML-Key Management Specification (XKMS 2.0) as defined by W3C.
Name:: Microsoft Excel Spreadsheet Format (XLS)
Description: When Microsoft’s proprietary protected xls format is used for document exchanging, it ought to be in the Excel95 version, as support for this version is widely implemented in most spreadsheets today. This includes OSS implementations such as Gnumeric and OpenOffice’s Calc.
Name:: Office XML regnearksformat (ECMA-376) (XLSX)
Description:
Name:: XML Metadata Interchange (XMI)
Description: The XML Metadata Interchange (XMI) is an Object Management Group (OMG) standard for exchanging metadata information via Extensible Markup Language (XML). XMI is also an ISO standard (ISO/IEC 19509:2014).
The latest OMG version (2.5.1) of XMI was launched in June 2015.
It can be used for any metadata whose metamodel can be expressed in Meta-Object Facility (MOF). The most common use of XMI is as an interchange format for UML models, although it can also be used for serialization of models of other languages (metamodels).
Name:: Extensible Markup Language (XML)
Description: The Extensible Markup Language (XML) is a simple text-based format for representing structured information: documents, data, configuration, books, transactions, invoices, and much more. It was derived from an older standard format called SGML (ISO 8879), in order to be more suitable for Web use.
Name:: XML Encryption with XML-Encryption Syntax and Processing (XMLenc)
Description: XMLenc as defined by W3C. XML Encryption is used to ensure encrypted transportation of contents. Is used, when the level of security in transport (like SSL) is not considered satisfactory.
Name:: XML signature and Encryption with Decryption Transform for XML Signature (xmlenc-decrypt)
Description: Decryption Transform for XML Signature as defined by W3C.
Name:: XML signatures with XML Signature Syntax and Processing (XMLsig)
Description: XMLsig as defined by W3C. XML Signatures ensures origin and integrity in XML messages and standardises the process, where XML contents are signed and put in XML documents. XML Signature Security is used, when different organisations and/or geographicly seperated addresses is integrated by means of XML. Through the use of the signature the receiver of a document can be certain that the contents has not been damaged.
Name:: XMPP Extensible Messaging and Presence Protocol (XMPP)
Description: XMPP is an open XML based protocol for almost real-time communication. Used for example in Jabber Instant Messaging and the Presence technology.
Name:: XML Path Language (XPath)
Description: The primary purpose of XPath is to address the nodes of XML trees. XPath gets its name from its use of a path notation for navigating through the hierarchical structure of an XML document. XPath uses a compact, non-XML syntax to facilitate use of XPath within URIs and XML attribute values.
XPath 3.0 operates on the abstract, logical structure of an XML document, rather than its surface syntax. This logical structure, known as the data model, is defined in [XQuery and XPath Data Model (XDM) 3.0]. XPath is designed to be embedded in a host language such as XSL Transformations (XSLT) Version 3.0 or XQuery 3.0 which is an extension of XPath Version 3.0.
Name:: XML Query Language Version 1.0 (XQuery 1.0)
Description: XQuery is designed to be a human-readable language for retrieving information from an XML source.
Name:: XQuery 3.0: An XML Query Language (XQuery 3.0)
Description: XML is a versatile markup language, capable of labeling the information content of diverse data sources including structured and semi-structured documents, relational databases, and object repositories. A query language that uses the structure of XML intelligently can express queries across all these kinds of data, whether physically stored in XML or viewed as XML via middleware. This specification describes a query language called XQuery, which is designed to be broadly applicable across many types of XML data sources.
W3C Recommendation 08 April 2014.
Name:: eXtensible rights Markup Language (XrML 2.0)
Description: An XML-based language for securely specifying and managing rights and conditions associated with all kinds of resources including digital content as well as services.
Name:: W3C XML Schema (XSD)
Description: This document specifies the XML Schema Definition Language, which offers facilities for describing the structure and constraining the contents of XML documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in an XML vocabulary and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML document type definitions (DTDs). This specification depends on XML Schema Definition Language 1.1 Part 2: Datatypes.
Our comments: W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures
Name:: Extensible Stylesheet Language (XSL-FO)
Description: The Extensible Stylesheet Language was defined by W3C. XSL is a language for expressing stylesheets. Given a class of arbitrarily structured XML documents or data files, designers use an XSL stylesheet to express their intentions about how that structured content should be presented; that is, how the source content should be styled, laid out, and paginated onto some presentation medium, such as a window in a Web browser or a hand-held device, or a set of physical pages in a catalog, report, pamphlet, or book.
XSL Formatting Objects (XSL-FO). an XML vocabulary for specifying formatting semantics.
Name:: XSL Transformation (XSLT)
Description: This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML.
The current version is XSLT 2.0 from 2007.
XSLT 3.0 is under development. The primary purpose of the changes in this version of the language is to enable transformations to be performed in streaming mode, where neither the source document nor the result document is ever held in memory in its entirety. Another important aim is to improve the modularity of large stylesheets, allowing stylesheets to be developed from independently-developed components with a high level of software engineering robustness.
Name:: XviD (XviD)
Description: XviD is a further development of OpenDivX from the point, where it was turned in to the closed DivX. XviD is a MPEG-4 codec, but is often used for compressing video in AVI files. XviD is open source, and is published under the GPL license.
Name:: Yahoo! Messenger (Yahoo! Messenger)
Description: A proprietary instant messaging and VoIP protocol from Yahoo!, primarily aimed at private users. The owners have a policy of deliberate non-interoperability towards other clients than their own. The official client is Yahoo! Messenger, but clients such as Miranda and Gaim can be used as well.
