Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Software standard
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{more citations needed|date=July 2010}} A '''software standard''' is a [[technical standard|standard]], [[Communications protocol|protocol]], or other common format of a document, file, or data transfer accepted and used by one or more [[software developers]] while working on one or more than one computer programs. Software standards enable interoperability between different programs created by different developers. ==How it is used and applied== Software standards consist of certain terms, concepts, data formats, document styles and techniques agreed upon by software creators so that their software can understand the files and data created by a different computer program. To be considered a standard, a certain protocol needs to be accepted and incorporated by a group of developers who contribute to the definition and maintenance of the standard. Some developers prefer using standards for software development because of the efficiencies it provides for code development<ref>{{cite web|url=http://users.cecs.anu.edu.au/~kambara/old_site/software/software_standards.html|title=Software Standards|publisher=|accessdate=22 March 2016}}</ref> and wider user acceptance and use of the resulting application.<ref>{{cite web|url=http://www.comptechdoc.org/independent/programming/programming-standards/|title=Software Standards Specification|publisher=|accessdate=22 March 2016}}</ref> The protocols [[HTML]], [[TCP/IP]], [[SMTP]], [[Post Office Protocol|POP]] and [[FTP]] are examples of software standards that application designers must understand and follow if their software expects to interface with these standards. For instance, in order for an email sent using [[Microsoft Outlook]] to be read by someone using [[Yahoo! Mail]], the email must be sent using the [[Simple Mail Transfer Protocol|SMTP]] so that the recipient's software can understand and correctly parse and display the email. Without such a standardized protocol, two different software applications would be unable to accurately share and display the information delivered between each other. Some other widely used data formats, while understood and used by a variety of computer programs, are not considered a software standard. [[Microsoft Office]] file formats, such as .doc and .xls, are commonly converted by other computer programs to use, but are still owned and controlled by [[Microsoft]], unlike text files ([[Text file|TXT]] or [[Rich Text Format|RTF]].<ref>{{cite web|url=http://www.biblioscape.com/rtf15_spec.htm|title=Rich Text Format (RTF) Version 1.5 Specification|publisher=|accessdate=22 March 2016}}</ref>) ==Creation of a software standard== Representatives from [[standards organization]]s, like [[W3C]]<ref>{{cite web|url=http://www.w3.org/|title=World Wide Web Consortium (W3C)|publisher=|accessdate=22 March 2016}}</ref> and [[Internet Society|ISOC]],<ref>{{cite web|url=http://www.isoc.org/standards/ |title= ISOC's Standards and Technology Activities: Open Standards |access-date=March 30, 2012 |url-status=dead |archive-url=https://web.archive.org/web/20111213013231/https://www.isoc.org/standards/ |archive-date=December 13, 2011 }}</ref> collaborate on how to make a unified software standard to ensure seamless communication between software applications. These organisations consist of groups of larger software companies like [[Microsoft]] and [[Apple Inc.]] The complexity of a standard varies based on the specific problem it aims to address but it needs to remain simple, maintainable and understandable. The standard document must comprehensively outline various conditions, types, and elements to ensure practicality and fulfill its intended purpose. For instance, although both [[File Transfer Protocol|FTP (File Transfer Protocol)]] and [[Simple Mail Transfer Protocol|SMTP (Simple Mail Transfer Protocol)]] facilitate computer-to-computer communication, [[File Transfer Protocol|FTP]] specifically handles the exchange of files, while [[Simple Mail Transfer Protocol|SMTP]] focuses on the transmission of emails. ==Open versus closed standards== A standard can be a closed standard or an [[open standard]]. The documentation for an open standard is open to the public and anyone can create a software that implements and uses the standard. The documentation and specification for closed standards are not available to the public, enabling its developer to sell and license the code to manage their data format to other interested software developers. While this process increases the revenue potential for a useful file format, it may limit acceptance and drive the adoption of a similar, open standard instead.<ref>{{cite web|url=http://www.opensource.org/osr-rationale|title=Open Standards Requirements for Software - Rationale|date=24 July 2006 |publisher=|accessdate=22 March 2016}}</ref> ==See also== * [[List of computer standards]] * [[List of file formats]] ==References== {{Reflist}} <!-- '''Safety reason''' for software standard to-do: '''Economic reason''' for software standard to-do: put economic reasons here '''Social reason''' for software standard to-do: put social reasons here Incorrect implementation of standards or specifications by multiple organizations result in a requirement for implementation specific code and special case exceptions as a necessity for cross-platform interoperability. Notable modern examples include web browser compatibility and web-services interoperability. The arbitrariness of most software concepts, which is related to historical hardware and software implementation, lack of common standards worldwide, and economic pressures. Sometimes software standards are controlled by private corporations (the [[Microsoft Windows|Windows]] GUI interface is owned by [[Microsoft]]). Sometimes software standards are controlled by open, public, or non-profit organizations (the Secure Shell 2 protocol is 'owned' by the [[IETF]]). * [[Programming language]] syntax and semantics. *Packet layout for Internet protocols. ** Secure Shell 2 ** [[HTML]] ** ... *Software protocols ** Client-Server interaction *Platform ** [[API]]s --> {{DEFAULTSORT:Standard (Software)}} [[Category:Computer standards| ]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Cite web
(
edit
)
Template:More citations needed
(
edit
)
Template:Reflist
(
edit
)