Added references to DOAP and schema.org

sc-principles/software-citation-principles.bib

@@ -4,6 +4,12 @@ @misc{APA-guidelines
 	Howpublished = {\url{http://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html}}
 }
 
+@misc{DOAP
+	Author = {{Edd Dumbill}},
+	Title  = {{DOAP}: Description of a Project}
+	Howpublished = {\url{https://github.com/edumbill/doap/}},
+	Note = {Accessed: 2016-03-31}}
+
 @misc{F1000,
 	Author = {{F1000Research}},
 	Howpublished = {\url{http://f1000research.com/for-authors/article-guidelines/software-tool-articles}},

sc-principles/software-citation-principles.tex

@@ -90,8 +90,8 @@ \section{Software citation principles}
 
 \begin{enumerate}
 \item \textbf{Importance}: \label{principle:importance}
-Software should be considered a legitimate, citable product of research. 
-Software citations should be accorded the same importance in the scholarly record as citations of other research products, such as publications and data; they should be part of the standard reference list for that research product and should not be separated. 
+Software should be considered a legitimate, citable product of research.
+Software citations should be accorded the same importance in the scholarly record as citations of other research products, such as publications and data; they should be part of the standard reference list for that research product and should not be separated.
 Software should be cited on the same basis as any other research product such as a paper or book; that is, authors should cite the appropriate set of software products just as they cite the appropriate set of papers.
 \item \textbf{Credit and Attribution}: \label{principle:credit}
 Software citations should facilitate giving scholarly credit and normative
@@ -113,8 +113,8 @@ \section{Software citation principles}
 \end{enumerate}
 
 These software citation principles were originally based on an adaptation of the FORCE11 Data Citation Principles~\cite{data-citation-principles}, and then were modified based on working group discussions and the information from the use cases and the related work.
-The adaptations and modifications have been made because software, while similar to data in terms of not traditionally having been cited in publications, is also different than data in that it can be used to express or explain concepts, it is updated more frequently, and it is executable. 
-% \katznote{are there any other difference between software and data that should be stated here?}  
+The adaptations and modifications have been made because software, while similar to data in terms of not traditionally having been cited in publications, is also different than data in that it can be used to express or explain concepts, it is updated more frequently, and it is executable.
+% \katznote{are there any other difference between software and data that should be stated here?}
 Also, while software can be considered a type of data, the converse is not generally true.
 
 
@@ -347,7 +347,7 @@ \subsection{Existing efforts around metadata standards}
 
 Producing detailed specifications and recommendations for possible metadata standards to support software citation was not within the scope of this working group. However some discussion on the topic did occur and there is significant interest in the wider community to produce standards for describing research software.
 
-Notable examples of community efforts around metadata include the AAS workshop~\cite{aas-software-index}, Project CRediT~\cite{casrai-credit}, Ontosoft~\cite{ontosoft}, CodeMeta~\cite{codemeta}.
+Notable examples around metadata include DOAP~\cite{DOAP}, an early metadata term set used by the Open Source Community, as well as more recent community efforts like the AAS workshop~\cite{aas-software-index}, Project CRediT~\cite{casrai-credit}, Ontosoft~\cite{ontosoft}, CodeMeta~\cite{codemeta}, or the terms and classes defined at \url{schema.org} related to the \url{https://schema.org/SoftwareApplication} class.
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \section{Discussion}
@@ -387,7 +387,7 @@ \subsection{Software papers} \label{sec:software_papers}
 itself should also be cited if it is directly used and was important to the work}.
 If a software paper exists and it contains results (performance, validation, etc.) that are
 important to the work, then the software paper should also be cited.
-In addition, if the software authors ask that a paper should be cited, that should typically be respected and the paper cited in addition to the software. 
+In addition, if the software authors ask that a paper should be cited, that should typically be respected and the paper cited in addition to the software.
 However, the software itself should still be cited.
 Note that there are situations where it is appropriate to cite the software, the software paper, or both.