Construction industry knowledge standard - Revision history

Designing Buildings: Redirected page to Discoverable construction knowledge specification

2020-08-26T08:58:39Z

Redirected page to Discoverable construction knowledge specification

← Older revision		Revision as of 08:58, 26 August 2020
Line 1:		Line 1:
−	~~Guidelines for the preparation of~~ knowledge ~~to make it easy to publish, find and use.~~	+	#redirect:[[Discoverable_construction_knowledge_specification\|Discoverable construction knowledge specification]]

−	~~-----~~	+	[[Category:DCN_Standard]] [[Category:Do_not_autolink]] [[Category:Standards_/_measurements]] [[Category:Site_Information]]
−	~~This document is a draft for consultation. To suggest changes, you can click 'Add a comment' at the bottom of the page or you can email info@designingbuildings.co.uk.~~	+
−		+
−	~~= Introduction =~~	+
−		+
−	Construction is a knowledge-based industry. We disseminate much of our knowledge electronically, sharing it across an array of different software applications, operating systems and devices. However, we generally prepare it as if it is going to be printed, often in pdf format, with all the limitations of hard-copy documents and exploiting few of the inherent benefits of electronic media. This makes knowledge unnecessarily difficult to prepare, publish, find, understand and use.	+
−		+
−	~~In the age of digital media, it is important that we prepare knowledge very simply and clearly so we do not inadvertently limit the ways it can be used by others.~~	+
−		+
−	~~This short document provides guidance for the preparation of knowledge to ensure that:~~	+
−		+
−	* It is easier for software to index, so people can find it.	+
−	* It is easier for authors to collaborate in its preparation.	+
−	* It is easier to publish knowledge on different platforms and in different formats without having to reprocess it every time.	+
−	* It is easier for readers to understand.	+
−	* It is properly attributed, and the terms for its use are clear.	+
−		+
−	~~= File format =~~	+
−		+
−	This guide does not place any restrictions on the type of software that can be used to prepare knowledge. If the approach set out in this document is followed, it should be relatively straight forward to transfer content between different applications and operating systems, irrespective of how it was created.	+
−		+
−	~~= Accessibility =~~	+
−		+
−	* Use plain language titles which enable readers and indexing software to understand the content of the document. Titles should not include symbols (such as / or ?) as they can cause errors in URL's.	+
−	* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.	+
−	* Explain acronyms when they are first used, but also repeat the full phrase throughout the body of the document as people may start reading it part way through.	+
−	* Only capitalise text when it is absolutely necessary, and then only capitalise the first letter of words. Capitalised text is more difficult to read.	+
−	* Provide links to other sources of information that may help explain concepts that are referred to.	+
−	* Links should include the full URL, ie including the http:// part.	+
−		+
−	~~= Design =~~	+
−		+
−	~~Documents should be very simple so they can be re-used on different platforms and in different page layouts without needing to be re-processed:~~	+
−		+
−	* Do not use unusual fonts.	+
−	* Do not use coloured fonts or backgrounds.	+
−	* Do not include hard page breaks.	+
−	* Do not format documents into columns.	+
−	* Do not add page numbers.	+
−	* Do not hyphenate long words between lines.	+
−	* Do not include headers or footers.	+
−	* Do not convert words into pictures, for example in title blocks.	+
−		+
−	~~= Formatting =~~	+
−		+
−	~~Document formatting should be very simple. Complex formatting may not be readable on all platforms:~~	+
−		+
−	* Bulleted and numbered lists should only have one level. Avoid lists within lists.	+
−	* Numbered lists should have simple numbers only. Complex numbering, such as clause numbers should be entered manually.	+
−	* Headings should be applied as proper heading styles, not as formatted normal text. This allows publishers and viewing software to automatically apply their own heading styles and automatically create tables of contents.	+
−	* There should not be more than three levels of headings.	+
−	* Body text should be un-styled or 'normal' style.	+
−	* Spacing between paragraphs should be introduced through paragraph styling (padding above or below the paragraph), not double line breaks.	+
−	* Paragraphs should not be indented or have hanging indents.	+
−	* Tables should not include complex formatting, images or complex cell divisions.	+
−	* Where tables are referred to in the body of the text, the text should refer to the actual table title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.	+
−		+
−	~~= Images =~~	+
−		+
−	* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.	+
−	* Image captions should include a plain language title describing the content of the image.	+
−	* Image files should have plain language file names which enable readers and indexing software to understand the content of the image. They should not include symbols as these can cause errors in URL's.	+
−	* Where images are referred to in the body of the text, the text should refer to the actual image title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.	+
−		+
−	~~= References =~~	+
−		+
−	* References should adopt the [[~~Parenthetical_referencing\|Harvard referencing system~~]]~~, with author and date included in the text, and the full references listed alphabetically at the end of the document (not at the end of pages or sections).~~	+
−		+
−	~~= Notes =~~	+
−		+
−	* Footnotes should be inserted manually, indicated in the text as numbers in brackets (1), with the footnotes listed at the end of the document. Automated footnote systems may not translate between different software applications.	+
−		+
−	~~= Graphs =~~	+
−		+
−	* Where graphs are included, the source data should be attached to allow proper interrogation by readers.	+
−		+
−	~~= Equations =~~	+
−		+
−	* Equations should be written as plain text, or if they are complex, should be inserted as images.	+
−		+
−	~~= Time-dependent information =~~	+
−		+
−	* Where documents refer to time-dependent information, such as an event which will happen or has recently happened, the text should refer to the actual date rather than using time-dependent phrases such as 'recently', 'soon' or 'will' as these phrases give the document an unnecessary 'expiry' date.	+
−		+
−	~~= Complex content =~~	+
−		+
−	* Where complex content, such as video is included, it should be uploaded to a suitable platform such as YouTube or Vimeo, and a link provided in the document. Not all software applications are able to show complex embedded content.	+
−	* Captions should include a plain language title describing the content.	+
−	* Captions should include information about the source of the content and any licensing restrictions where these are different to the rest of the document.	+
−		+
−	~~= Indexing information =~~	+
−		+
−	~~Documents should include indexing information at the beginning:~~	+
−		+
−	* Plain language title.	+
−	* Author details (including organisations and location, and identifying the lead author where there are multiple authors). This may be linked to existing online author profiles, such as Linkedin profiles.	+
−	* Short plain language description.	+
−	* Date of publication (this is very important but often forgotten).	+
−	* Licence restrictions (see below).	+
−		+
−	~~= Licence =~~	+
−		+
−	Documents should adopt licences that reflect the intended purpose of the document. For example, if the purpose for creating a document is the dissemination of knowledge, then adding a copyright symbol that restricts its use may not be the best option.	+
−		+
−	If it is important that the document must not be copied, shared or altered in any way then it may be appropriate for it to be copyright protected. However, there are a number of freely available [http://www.creativecommons.org/choose/ Creative Commons licenses] that give greater flexibility for use. These can be associated with a document by inserting a link to the relevant license:	+
−		+
−	* Attribution: Allows others to distribute, remix, tweak, and build upon the work, even commercially, as long as they credit the author for the original creation.	+
−	* Attribution-NoDerivs: Allows for commercial and non-commercial redistribution, as long as it is passed along unchanged, with credit to the author.	+
−	* Attribution-NonCommercial-ShareAlike: Allows others to remix, tweak, and build upon the work non-commercially, as long as they credit the original author and license their new creations under the identical terms.	+
−	* Attribution-ShareAlike: Allows others to remix, tweak, and build upon the work even for commercial purposes, as long as they credit the original author and license their new creations under identical terms.	+
−	* Attribution-NonCommercial: Allows others to remix, tweak, and build upon the work non-commercially, and although their new works must acknowledge the original author and be non-commercial, they don't have to license their derivative works on the same terms.	+
−	* Attribution-NonCommercial-NoDerivs: Allows others to download the work and share it with others as long as they credit the original author, but they cannot change it in any way or use it commercially.	+
−		+
−	[[Category:Do_not_autolink]] [[Category:Standards_/_measurements~~]] [[Category:DCN_Standard~~]] [[Category:Site_Information]]	+

Designing Buildings at 13:35, 8 March 2018

2018-03-08T13:35:43Z

← Older revision		Revision as of 13:35, 8 March 2018
Line 2:		Line 2:

	-----		-----
−	This document is a draft for consultation. To suggest changes, you can click 'Add a comment' at the bottom of the page ~~and add your thoughts to the discussion page,~~ or you can ~~click 'Send us feedback' or~~ email info@designingbuildings.co.uk.	+	This document is a draft for consultation. To suggest changes, you can click 'Add a comment' at the bottom of the page or you can email info@designingbuildings.co.uk.

	= Introduction =		= Introduction =
Line 14:		Line 14:
	* It is easier for software to index, so people can find it.		* It is easier for software to index, so people can find it.
	* It is easier for authors to collaborate in its preparation.		* It is easier for authors to collaborate in its preparation.
−	* It is easier to publish knowledge on different platforms and in different formats without ~~the need for reprocessing~~.	+	* It is easier to publish knowledge on different platforms and in different formats without having to reprocess it every time.
	* It is easier for readers to understand.		* It is easier for readers to understand.
	* It is properly attributed, and the terms for its use are clear.		* It is properly attributed, and the terms for its use are clear.
Line 20:		Line 20:
	= File format =		= File format =

−	This guide does not place any restrictions to the type of software that can be used to prepare knowledge. If the approach set out in this document is followed, it should be relatively straight forward to transfer content between different applications and operating systems, irrespective of how it was created.	+	This guide does not place any restrictions on the type of software that can be used to prepare knowledge. If the approach set out in this document is followed, it should be relatively straight forward to transfer content between different applications and operating systems, irrespective of how it was created.

	= Accessibility =		= Accessibility =

−	* Use plain language titles which enable readers and indexing software to understand the content of the document. ~~These~~ should not include symbols (such as / or ?) as they can cause errors in URL's.	+	* Use plain language titles which enable readers and indexing software to understand the content of the document. Titles should not include symbols (such as / or ?) as they can cause errors in URL's.
−	* Use UK English.	+
	* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.		* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.
	* Explain acronyms when they are first used, but also repeat the full phrase throughout the body of the document as people may start reading it part way through.		* Explain acronyms when they are first used, but also repeat the full phrase throughout the body of the document as people may start reading it part way through.
Line 34:		Line 33:
	= Design =		= Design =

−	~~Document design~~ should be very simple so ~~that it~~ can be re-used on different platforms and in different page layouts without needing to be re-processed:	+	Documents should be very simple so they can be re-used on different platforms and in different page layouts without needing to be re-processed:

	* Do not use unusual fonts.		* Do not use unusual fonts.
Line 43:		Line 42:
	* Do not hyphenate long words between lines.		* Do not hyphenate long words between lines.
	* Do not include headers or footers.		* Do not include headers or footers.
−	* Do not change page orientation to accommodate images or tables.
	* Do not convert words into pictures, for example in title blocks.		* Do not convert words into pictures, for example in title blocks.

Line 62:		Line 60:
	= Images =		= Images =

−	* All appropriate rights and permissions should be acquired for images and other material.
	* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.		* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.
	* Image captions should include a plain language title describing the content of the image.		* Image captions should include a plain language title describing the content of the image.
Line 91:		Line 88:

	* Where complex content, such as video is included, it should be uploaded to a suitable platform such as YouTube or Vimeo, and a link provided in the document. Not all software applications are able to show complex embedded content.		* Where complex content, such as video is included, it should be uploaded to a suitable platform such as YouTube or Vimeo, and a link provided in the document. Not all software applications are able to show complex embedded content.
−	* Captions should include information about the source of the content and any licensing restrictions where these are different to the rest of the document.
	* Captions should include a plain language title describing the content.		* Captions should include a plain language title describing the content.
		+	* Captions should include information about the source of the content and any licensing restrictions where these are different to the rest of the document.

	= Indexing information =		= Indexing information =
Line 117:		Line 114:
	* Attribution-NonCommercial-NoDerivs: Allows others to download the work and share it with others as long as they credit the original author, but they cannot change it in any way or use it commercially.		* Attribution-NonCommercial-NoDerivs: Allows others to download the work and share it with others as long as they credit the original author, but they cannot change it in any way or use it commercially.

−	[[Category:Do_not_autolink]] [[Category:Standards_/_measurements]] [[Category:Site_Information]]	+	[[Category:Do_not_autolink]] [[Category:Standards_/_measurements]] [[Category:DCN_Standard]] [[Category:Site_Information]]

Designing Buildings at 15:26, 7 March 2018

2018-03-07T15:26:57Z

← Older revision		Revision as of 15:26, 7 March 2018
Line 24:		Line 24:
	= Accessibility =		= Accessibility =

−	* Use plain language titles which enable readers and indexing software to understand the content of the document.	+	* Use plain language titles which enable readers and indexing software to understand the content of the document. These should not include symbols (such as / or ?) as they can cause errors in URL's.
	* Use UK English.		* Use UK English.
	* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.		* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.
Line 30:		Line 30:
	* Only capitalise text when it is absolutely necessary, and then only capitalise the first letter of words. Capitalised text is more difficult to read.		* Only capitalise text when it is absolutely necessary, and then only capitalise the first letter of words. Capitalised text is more difficult to read.
	* Provide links to other sources of information that may help explain concepts that are referred to.		* Provide links to other sources of information that may help explain concepts that are referred to.
		+	* Links should include the full URL, ie including the http:// part.

	= Design =		= Design =
Line 57:		Line 58:
	* Paragraphs should not be indented or have hanging indents.		* Paragraphs should not be indented or have hanging indents.
	* Tables should not include complex formatting, images or complex cell divisions.		* Tables should not include complex formatting, images or complex cell divisions.
		+	* Where tables are referred to in the body of the text, the text should refer to the actual table title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.

	= Images =		= Images =
Line 63:		Line 65:
	* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.		* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.
	* Image captions should include a plain language title describing the content of the image.		* Image captions should include a plain language title describing the content of the image.
−	* Image files should have plain language file names which enable readers and indexing software to understand the content of the image.	+	* Image files should have plain language file names which enable readers and indexing software to understand the content of the image. They should not include symbols as these can cause errors in URL's.
	* Where images are referred to in the body of the text, the text should refer to the actual image title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.		* Where images are referred to in the body of the text, the text should refer to the actual image title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.

Designing Buildings at 15:17, 7 March 2018

2018-03-07T15:17:33Z

← Older revision		Revision as of 15:17, 7 March 2018
Line 64:		Line 64:
	* Image captions should include a plain language title describing the content of the image.		* Image captions should include a plain language title describing the content of the image.
	* Image files should have plain language file names which enable readers and indexing software to understand the content of the image.		* Image files should have plain language file names which enable readers and indexing software to understand the content of the image.
		+	* Where images are referred to in the body of the text, the text should refer to the actual image title (or figure number if it has one), rather than using phrases such as 'below', 'left', 'overleaf' and so on.

	= References =		= References =

Designing Buildings at 14:57, 7 March 2018

2018-03-07T14:57:35Z

← Older revision		Revision as of 14:57, 7 March 2018
Line 2:		Line 2:

	-----		-----
−	This document is a draft for consultation. ~~We want to hear your thoughts and ideas about how it could be improved.~~	+	This document is a draft for consultation. To suggest changes, you can click 'Add a comment' at the bottom of the page and add your thoughts to the discussion page, or you can click 'Send us feedback' or email info@designingbuildings.co.uk.
−		+
−	To suggest changes, you can click 'Add a comment' at the bottom of the page and add your thoughts to the discussion page, or you can click 'Send us feedback' or email info@designingbuildings.co.uk.	+
−		+
−	For more information about this standard, see: [[Proposal_for_a_standard_method_for_the_preparation_of_construction_industry_knowledge\|Proposal for a standard method for the preparation of construction industry knowledge]].	+

	= Introduction =		= Introduction =
Line 30:		Line 26:
	* Use plain language titles which enable readers and indexing software to understand the content of the document.		* Use plain language titles which enable readers and indexing software to understand the content of the document.
	* Use UK English.		* Use UK English.
−	* Summarise findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.	+	* Summarise useable findings at the beginning. If readers do not find what they are looking for quickly, they will look somewhere else.
−	* Explain acronyms when they are first used~~. Repeat~~ the full phrase throughout the body of the document as people may start reading it part way through.	+	* Explain acronyms when they are first used, but also repeat the full phrase throughout the body of the document as people may start reading it part way through.
	* Only capitalise text when it is absolutely necessary, and then only capitalise the first letter of words. Capitalised text is more difficult to read.		* Only capitalise text when it is absolutely necessary, and then only capitalise the first letter of words. Capitalised text is more difficult to read.
−	* Provide links to other sources of information.	+	* Provide links to other sources of information that may help explain concepts that are referred to.

	= Design =		= Design =
Line 64:		Line 60:
	= Images =		= Images =

−	* All appropriate rights and permissions ~~must have been~~ acquired for images and other material.	+	* All appropriate rights and permissions should be acquired for images and other material.
	* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.		* Image captions should include information about the source of images and any licensing restrictions where these are different to the rest of the document.
	* Image captions should include a plain language title describing the content of the image.		* Image captions should include a plain language title describing the content of the image.
Line 102:		Line 98:
	* Author details (including organisations and location, and identifying the lead author where there are multiple authors). This may be linked to existing online author profiles, such as Linkedin profiles.		* Author details (including organisations and location, and identifying the lead author where there are multiple authors). This may be linked to existing online author profiles, such as Linkedin profiles.
	* Short plain language description.		* Short plain language description.
−	* Date of publication.	+	* Date of publication (this is very important but often forgotten).
−	* Licence (see below).	+	* Licence restrictions (see below).

	= Licence =		= Licence =

Designing Buildings at 15:51, 4 October 2017

2017-10-04T15:51:29Z

← Older revision		Revision as of 15:51, 4 October 2017
Line 4:		Line 4:
	This document is a draft for consultation. We want to hear your thoughts and ideas about how it could be improved.		This document is a draft for consultation. We want to hear your thoughts and ideas about how it could be improved.

−	To suggest changes, you can click '~~Discuss~~' ~~above~~ and add your thoughts to the discussion page, or click '~~Submit Comment~~' ~~at the bottom of the page to send us a comment,~~ or email ~~us at~~ info@designingbuildings.co.uk.	+	To suggest changes, you can click 'Add a comment' at the bottom of the page and add your thoughts to the discussion page, or you can click 'Send us feedback' or email info@designingbuildings.co.uk.

	For more information about this standard, see: [[Proposal_for_a_standard_method_for_the_preparation_of_construction_industry_knowledge\|Proposal for a standard method for the preparation of construction industry knowledge]].		For more information about this standard, see: [[Proposal_for_a_standard_method_for_the_preparation_of_construction_industry_knowledge\|Proposal for a standard method for the preparation of construction industry knowledge]].

Designing Buildings at 15:47, 4 October 2017

2017-10-04T15:47:56Z

← Older revision		Revision as of 15:47, 4 October 2017
Line 2:		Line 2:

	-----		-----
−	This document is a draft for consultation ~~v3 27/10/2014~~. We want to hear your thoughts and ideas about how it could be improved.	+	This document is a draft for consultation. We want to hear your thoughts and ideas about how it could be improved.

	To suggest changes, you can click 'Discuss' above and add your thoughts to the discussion page, or click 'Submit Comment' at the bottom of the page to send us a comment, or email us at info@designingbuildings.co.uk.		To suggest changes, you can click 'Discuss' above and add your thoughts to the discussion page, or click 'Submit Comment' at the bottom of the page to send us a comment, or email us at info@designingbuildings.co.uk.

Designing Buildings at 16:30, 7 February 2017

2017-02-07T16:30:55Z

← Older revision		Revision as of 16:30, 7 February 2017
Line 4:		Line 4:
	This document is a draft for consultation v3 27/10/2014. We want to hear your thoughts and ideas about how it could be improved.		This document is a draft for consultation v3 27/10/2014. We want to hear your thoughts and ideas about how it could be improved.

−	To suggest changes, you can click 'Discuss' above and add your thoughts to the discussion page, or click 'Submit Comment' at the bottom of the page to send us a comment, or email us at ~~[mailto:~~info@designingbuildings.co.uk. ~~info@designingbuildings.co.uk.]~~	+	To suggest changes, you can click 'Discuss' above and add your thoughts to the discussion page, or click 'Submit Comment' at the bottom of the page to send us a comment, or email us at info@designingbuildings.co.uk.

	For more information about this standard, see: [[Proposal_for_a_standard_method_for_the_preparation_of_construction_industry_knowledge\|Proposal for a standard method for the preparation of construction industry knowledge]].		For more information about this standard, see: [[Proposal_for_a_standard_method_for_the_preparation_of_construction_industry_knowledge\|Proposal for a standard method for the preparation of construction industry knowledge]].

Designing Buildings at 11:09, 5 July 2016

2016-07-05T11:09:38Z

Designing Buildings at 10:11, 14 January 2016

2016-01-14T10:11:23Z

Show changes

← Older revision		Revision as of 11:09, 5 July 2016
Line 57:		Line 57:
	* Headings should be applied as proper heading styles, not as formatted normal text. This allows publishers and viewing software to automatically apply their own heading styles and automatically create tables of contents.		* Headings should be applied as proper heading styles, not as formatted normal text. This allows publishers and viewing software to automatically apply their own heading styles and automatically create tables of contents.
	* There should not be more than three levels of headings.		* There should not be more than three levels of headings.
−	* Body text should be un-styled or ~~‘normal’~~ style.	+	* Body text should be un-styled or 'normal' style.
	* Spacing between paragraphs should be introduced through paragraph styling (padding above or below the paragraph), not double line breaks.		* Spacing between paragraphs should be introduced through paragraph styling (padding above or below the paragraph), not double line breaks.
	* Paragraphs should not be indented or have hanging indents.		* Paragraphs should not be indented or have hanging indents.
Line 87:		Line 87:
	= Time-dependent information =		= Time-dependent information =

−	* Where documents refer to time-dependent information, such as an event which will happen or has recently happened, the text should refer to the actual date rather than using time-dependent phrases such as ~~‘recently’~~, ~~‘soon’~~ or ~~‘will’~~ as these phrases give the document an unnecessary ~~‘expiry’~~ date.	+	* Where documents refer to time-dependent information, such as an event which will happen or has recently happened, the text should refer to the actual date rather than using time-dependent phrases such as 'recently', 'soon' or 'will' as these phrases give the document an unnecessary 'expiry' date.

	= Complex content =		= Complex content =
Line 115:		Line 115:
	* Attribution-NonCommercial-ShareAlike: Allows others to remix, tweak, and build upon the work non-commercially, as long as they credit the original author and license their new creations under the identical terms.		* Attribution-NonCommercial-ShareAlike: Allows others to remix, tweak, and build upon the work non-commercially, as long as they credit the original author and license their new creations under the identical terms.
	* Attribution-ShareAlike: Allows others to remix, tweak, and build upon the work even for commercial purposes, as long as they credit the original author and license their new creations under identical terms.		* Attribution-ShareAlike: Allows others to remix, tweak, and build upon the work even for commercial purposes, as long as they credit the original author and license their new creations under identical terms.
−	* Attribution-NonCommercial: Allows others to remix, tweak, and build upon the work non-commercially, and although their new works must acknowledge the original author and be non-commercial, they ~~don’t~~ have to license their derivative works on the same terms.	+	* Attribution-NonCommercial: Allows others to remix, tweak, and build upon the work non-commercially, and although their new works must acknowledge the original author and be non-commercial, they don't have to license their derivative works on the same terms.
	* Attribution-NonCommercial-NoDerivs: Allows others to download the work and share it with others as long as they credit the original author, but they cannot change it in any way or use it commercially.		* Attribution-NonCommercial-NoDerivs: Allows others to download the work and share it with others as long as they credit the original author, but they cannot change it in any way or use it commercially.

	[[Category:Do_not_autolink]] [[Category:Standards_/_measurements]] [[Category:Site_Information]]		[[Category:Do_not_autolink]] [[Category:Standards_/_measurements]] [[Category:Site_Information]]