Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Specification

Related Topics

In the News (Fri 22 Mar 19)

  Specification - Wikipedia, the free encyclopedia
Normally, a specification is the specific set of (high level) requirements agreed to by the sponsor/user and the manufacturer/producer of a system.
The specification may also contain both the systems requirements and the test requirements by which it is determined that the systems requirements have been met, known as the acceptance test requirement(s), and a mapping between them.
An official document intended primarily for supporting procurement, which document clearly and accurately describes the essential technical requirements for items, materials, or services, including the procedures by which it will be determined that the requirements have been met.
en.wikipedia.org /wiki/Specification   (202 words)

 Really Simple Syndication: RSS 2.0.1 Specification (revision 6)
Archivist's Note: From 2003 to 2005, the RSS Advisory Board reported revisions to this document with change notes but did not increment the version number in the specification itself.
All date-times in RSS conform to the Date and Time Specification of RFC 822, with the exception that the year may be expressed with two characters or four characters (four preferred).
Prior to RSS 2.0, the specification only allowed http:// and ftp://, however, in practice other URI schemes were in use by content developers and supported by aggregators.
www.rssboard.org /rss-specification   (2232 words)

 Cascading Style Sheets, Level 2   (Site not responding. Last check: 2007-11-07)
It is a stable document and may be used as reference material or cited as a normative reference from another document.
In case of a discrepancy between the various forms of the specification, http://www.w3.org/TR/1998/REC-CSS2-19980512 is considered the definitive version.
The English version of this specification is the only normative version.
www.w3.org /TR/REC-CSS2   (623 words)

 XML Topic Maps (XTM) 1.0   (Site not responding. Last check: 2007-11-07)
This specification provides a model and grammar for representing the structure of information resources used to define topics, and the associations (relationships) between topics.
This version of the XTM specification and its associated materials may be distributed freely, as long as all text and legal notices remain intact.
The syntax for serializing and interchanging topic map documents conforming to this specification is defined by the XML document type definition provided in Annex D: XTM 1.0 Document Type Declaration.
www.topicmaps.org /xtm/1.0   (7677 words)

 Intel Corporation - Extensible Firmware Interface (EFI) Home
The EFI specification is primarily intended for the next generation of IA architecture-based computers, and is an outgrowth of the "Intel® Boot Initiative" (IBI) program that began in 1998.
Using the EFI 1.10 specification as the staring point, this industry group is responsible for developing, managing and promoting the UEFI specification.
The file detailing the changes between the Draft 0.95 of the EFI Specification and the final EFI Specification 1.10 was released.
developer.intel.com /technology/efi   (520 words)

 AtomEnabled / Developers / Syndication / Atom Syndication Format Spec
This specification uses the namespace prefix "atom:" for the Namespace URI identified in Section 1.2, above.
Some sections of this specification are illustrated with fragments of a non-normative RELAX NG Compact schema [RELAX-NG].
This specification does not define a DTD for Atom Documents, and hence does not require them to be valid (in the sense used by XML).
www.atomenabled.org /developers/syndication/atom-format-spec.php   (6990 words)

 WAP Forum Specifications
This page lists the latest WAP Forum conformance release, along with the specifications which are in an Approved state, but not yet included in a release.
The proposed and prototype specifications that were available here in the past have now been moved to a separate documents under review page.
A Proposed Specification is a technical document under active review and validation by the WAP Forum membership, as well as the general public, but which not yet have passed the final approval by the Membership.
www.wapforum.org /what/technical.htm   (979 words)

 OMG Modeling and Metadata Specifications
The purpose of this specification is to add a semantic context to the interchange of metadata in terms of recognized sets of objects or object patterns.
This specification is one of a series related to developing the 2.0 revision of the OMG Meta Object Facility specification, referred to as MOF 2.0.
The problem being addressed by this Specification is to manage the co-existence of multiple versions of metadata in a Meta Object Facility and their inclusion in different configurations (for example a specific version of a PIM, the corresponding version of the derived PSM, and the corresponding version of the generated system).
www.omg.org /technology/documents/modeling_spec_catalog.htm   (1562 words)

 LSB Written Specification   (Site not responding. Last check: 2007-11-07)
The base specification consists of the Core and C++ modules, and is extended with the full LSB set, which is labelled Desktop.
The individual specifications (sometimes called "books") are not released by the LSB project on a standalone basis, only rolled up into the specification modules.
These specifications reflect work in progress and can be commented on, but are not intended to be released as is.
freestandards.org /spec   (280 words)

 [No title]
This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068 [33].
Applications that are at least conditionally compliant with this specification SHOULD use an HTTP-Version of "HTTP/1.1" in their messages, and MUST do so for any message that is not compatible with HTTP/1.0.
This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host","abs_path", "rel_path", and "authority" from that specification.
www.ietf.org /rfc/rfc2616.txt   (15391 words)

 specs: Specification Project
The goal of the OpenOffice.org Specification project is to have a home for specifications which are related to OpenOffice.org.
As a small piece of the workflow puzzle for specifications, there's a document describing how to obtain linguistic review for a specification document.
This means that parts of the specification are automatically transferred into the What's New Guide.
specs.openoffice.org   (336 words)

 RDF Site Summary (RSS) 1.0
This is one of the approaches used in this specification: modularization is achieved by using XML Namespaces for partitioning vocabularies.
The specifics of the various intricacies of syndication systems (free vs. subscription, push vs. pull, etc.) is beyond the scope of this specification.
While the later 0.91 specification allowed for a width of 1-144 and height of 1-400, convention (and the 0.9 specification) dictate 88x31.
web.resource.org /rss/1.0/spec   (3025 words)

 What is UNIX ?
Since the introduction of the Single UNIX Specification, there has been a single, open, consensus specification that defines the requirements for a conformant UNIX system.
The Open Group is committed to working with the community to further the development of standards conformant systems by evolving and maintaining the Single UNIX Specification and participation in other related standards efforts.
You can also get involved in the ongoing development and maintenance of the Single UNIX Specification, by joining the Austin Group whose approach to specification development is "write once, adopt everywhere", The Open Group's Base Working Group or get involved in the UNIX Certification program.
www.unix.org /what_is_unix.html   (386 words)

 [No title]
Where possible, references are made to the memo that provides for the specification of these concepts or definitions.
Individual property definitions should be consulted for determining whether a specific property allows multiple values and in which of these two forms.
The specification of globally unique time zone identifiers is not addressed by this document and is left for future study.
www.ietf.org /rfc/rfc2445.txt   (13692 words)

 Intel Corporation - Specification Overview
The EFI 1.10 Specification is a merging of documents of the 1.02 specification and the EFI Driver Model along with additional protocol interfaces that provide access to a richer set of boot devices.
You may download the EFI Specification version 1.10, download a document outlining the changes between the draft 0.95 and the final version, or access related specifications.
There are companion specifications for specific bus and device types.
www.intel.com /technology/efi/main_specification.htm   (892 words)

 The Java Language Specification
The Java Language Specification, Third Edition is now available in a pre-publication PDF release.
Written by the inventors of the technology, The Java Language Specification, Third Edition is the definitive technical reference for the Java programming language.
The Java Language Specification, Second Edition - Written by the inventors of the technology, this book is the definitive technical reference for the Java programming language.
java.sun.com /docs/books/jls   (750 words)

 USB.org - Documents   (Site not responding. Last check: 2007-11-07)
Errata to the USB 2.0 specification as of December 7, 2000
Errata (.pdf file format, size 172k) to the USB 2.0 Specification (As of May 28, 2002) In case you only want to download only the most recent Errata to the USB 2.0 Specification, download it here.
Errata (.pdf file format, size 136k) to the USB 2.0 Specification (As of December 7, 2000) In case you only want to download this Errata to the USB 2.0 Specification, download it here.
www.usb.org /developers/docs   (2075 words)

 OPML 1.0 Specification
Outlines can be used for specifications, legal briefs, product plans, presentations, screenplays, directories, diaries, discussion groups, chat systems and stories.
There is no specific limit on the length of the text attribute.
Further, while these copyright restrictions apply to the written OPML specification, no claim of ownership is made by UserLand to the format it describes.
www.opml.org /spec   (1132 words)

 Object Management Group - UML
OMG is a not-for-profit computer industry specifications consortium; our members define and maintain the UML specification which we publish in the series of documents linked on this page for your free download.
UML 2.0 Diagram Interchange: This specification extends the UML metamodel with a supplementary package for graph-oriented information, allowing models to be exchanged or stored/retrieved and then displayed as they were originally.
In our UML 2.0 Specifications Box, version 1.5 will be labeled "Current" until all four of the 2.0 components have completed their final adoption step.
www.uml.org   (1100 words)

 HTML 4.01 Specification   (Site not responding. Last check: 2007-11-07)
This specification defines HTML 4.01, which is a subversion of HTML 4.
This document specifies HTML 4.01, which is part of the HTML 4 line of specifications.
This specification is the first HTML 4.01 Recommendation.
www.w3.org /TR/html4   (716 words)

 Liberty Alliance Project - Specifications
liberty-metadata-v1.1.xsd: The XSD Schema that accompanies the Liberty Metadata Specification.
liberty-metadata-v2.0.xsd: The XSD Schema that accompanies the draft Liberty Metadata Specification.
Utility XSD schemata are provided for common type definitions and elements that are used in several of the Liberty specifications.
www.projectliberty.org /resources/specifications.php   (2047 words)

 IMS Global Learning Consortium: IMS Learning Resource Meta-data Specification
IMS Meta-Data v1.2.2 specification is is the public draft of an errata update to correct minor discrepancies in the schema.
Version 1.2 Final Specification of the IMS Meta-data Specification was released to the public in June 2001.
The IMS Meta-data Specification was approved unanimously by the IMS Technical Board, which is comprised of one representative from each of the IMS Contributing Member organizations.
www.imsproject.org /metadata   (756 words)

 Web Applications 1.0
In terms of applications, this specification is targetted specifically at applications that would be expected to be used by users on an occasional basis, or regularly but from disparate locations.
For the parts of this specification that are defined in terms of an events model or in terms of the DOM, such user agents must still act as if events and the DOM were supported.
Other specifications may also allow elements in their namespaces to be labelled as being in specific classes.
www.whatwg.org /specs/web-apps/current-work   (9275 words)

 FOAF Vocabulary Specification
The specific contents of the FOAF vocabulary are detailed in this FOAF namespace document.
See the Code of the Geeks specification for details of the code, which provides a somewhat frivolous and willfully obscure mechanism for characterising technical expertise, interests and habits.
Further, there is probably a degree of cultural specificity implicit in the assumptions made by many questionaire-based MBTI tools; the MBTI system may not make sense in cultural settings beyond those it was created for.
xmlns.com /foaf/0.1   (8984 words)

 RELAX NG Specification
This is the definitive specification of RELAX NG, a simple schema language for XML, based on [RELAX] and [TREX].
This Committee Specification was approved for publication by the OASIS RELAX NG technical committee.
This specification was prepared and approved for publication by the RELAX NG TC.
www.oasis-open.org /committees/relax-ng/spec-20011203.html   (4969 words)

 Pingback 1.0
Note that how the client is told of the source and target URIs is out of the scope of this specification.
To claim conformance to this specification a pingback server MUST be able to receive pingback XML-RPC calls and MUST always return results that conform to the allowed return values.
For example, a pingback gateway server could be standalone, and other pages would then use the link element to link to this gateway server instead of providing a server of their own.
www.hixie.ch /specs/pingback/pingback   (2114 words)

 IMS Global Learning Consortium: IMS Question & Test Interoperability Specification
Therefore, the specification enables the exchange of this item, test and results data between authoring tools, item banks, test constructional tools, learning systems and assessment delivery systems.
This v2.1 Public Draft specification is a draft and liable to change before the completion of the Final specification.
Version 1.0 of the IMS Question and Test Interoperability Specification was released to the public in June 2000.
www.imsproject.org /question   (1177 words)

 OASIS Security Services (SAML) TC
It is expected that such specifications will adhere to guidelines set forth in the relevant SAML specification.
If you are an OASIS member and wish to contribute a SAML profile or other SAML-based specification to the SSTC for consideration in future work on SAML, please refer to the OASIS TC process for the proper way to make a contribution.
This is a portion of the XACML 2.0 OASIS Standard from the XACML TC, and includes a core Specification Document, a SAML 2.0 Assertion Extension Schema, and a SAML 2.0 Protocol Extension Schema.
www.oasis-open.org /committees/tc_home.php?wg_abbrev=security   (1400 words)

 International Color Consortium specification
Specification ICC.1:2004-10 (Profile version Image technology colour management — Architecture, profile format, and data structure
These past versions of the ICC Specification are archived here for the convenience of the standards community.
Other ANSI and ISO standards may reference past versions of the ICC specification and they are maintained here for the easy reference of readers of those standards.
www.color.org /icc_specs2.html   (117 words)

 Client Side State - HTTP Cookies
When sending cookies to a server, all cookies with a more specific path mapping should be sent before cookies with less specific path mappings.
For example, a cookie "name1=foo" with a path mapping of "/" should be sent after a cookie "name1=foo2" with a path mapping of "/bar" if they are both to be sent.
This is a specification of the minimum number of cookies that a client should be prepared to receive and store.
wp.netscape.com /newsref/std/cookie_spec.html   (1405 words)

Try your search on: Qwika (all wikis)

  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.