# [rkward-cvs] SF.net SVN: rkward:[3381] branches/jss_dec_10/FINAL_JSS_TEX

tfry at users.sourceforge.net tfry at users.sourceforge.net
Sat Jan 22 13:02:43 UTC 2011

Revision: 3381
http://rkward.svn.sourceforge.net/rkward/?rev=3381&view=rev
Author:   tfry
Date:     2011-01-22 13:02:43 +0000 (Sat, 22 Jan 2011)

Log Message:
-----------
Add more text to the revision notes

Modified Paths:
--------------
branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex
branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt

Modified: branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2011-01-22 12:42:56 UTC (rev 3380)
+++ branches/jss_dec_10/FINAL_JSS_TEX/RKWard_paper.tex	2011-01-22 13:02:43 UTC (rev 3381)
@@ -43,9 +43,9 @@
\item$^{\ddag}$Equal contribution, $^{\S}$Corresponding authors
%%
}
-\Keywords{GUI, IDE, \proglang{R}, plugin, cross-platform}
+\Keywords{GUI, integrated development environment, \proglang{R}, plugin, cross-platform}

-\Plainkeywords{GUI, IDE, R, plugin, cross-platform} %% without formatting
+\Plainkeywords{GUI, integrated development environment, R, plugin, cross-platform} %% without formatting
%% at \leftarrowst one keyword must be supplied

%% publication information

Modified: branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt
===================================================================
--- branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-22 12:42:56 UTC (rev 3380)
+++ branches/jss_dec_10/FINAL_JSS_TEX/revision_notes.txt	2011-01-22 13:02:43 UTC (rev 3381)
@@ -1,4 +1,13 @@
+--- TODO ---
+- Check, whether we are really following our lists (markup, abbreviations), consistently.
+  - Also check, whether we introduce all abbreviations, properly.
+- Second check figure placement
+
+I've tried to write the remainder of these notes in a way that we can simply
+attach it to the revision, and send it to the editors. Please check wording / spelling, etc.
+
+
+--- Requests that we have addressed ---
o In all cases, text/tables/figures\equations must fit within the normal
textwidth of the manuscript.
o Pages: 1,32
@@ -17,7 +26,7 @@
References
- Java (not: JAVA, java)

---- Notes from JSS that we have addressed, but which we are not entirely sure about ---
+--- Requests that we have addressed, but questions remain ---

Code:
Please include a standalone replication script of all code/examples
@@ -40,21 +49,26 @@
Source code for RKWard 0.5.4 can be obtained from

---- Notes from JSS that we have not addressed, yet ---
-
Manuscript:
o As a reminder, please make sure that:
- \proglang, \pkg and \code have been used for highlighting throughout
the paper (including titles and references), except where explicitly escaped.
-  - see our notes below

+We have checked our usage of these macros, and esp. added appropriate highlighting
+in titles and references. Note that for several terms we are not entirely sure,
+whether it is considered appropriate to use the \proglang macro or not. We have added
+a corresponding list near the end of this text file.
+
o Abbreviation expansions should only be introduced in the abstract if they
are needed again within the abstract. If an expansion is introduced within
the abstract it needs to be introduced again within the manuscript the
first time it is used.
o  KDE
-	- see our notes below

+We have removed the abbreviation "IDE" in the abstract. We have decided
+to consider KDE (and several other acronyms) as a proper name, and we do not
+provide an expansion, deliberately (see below).
+
o Abbreviations should be spelled in upper-case letters without additional
formatting (i.e., without periods, without small caps, italics, etc.). All
abbreviations should be introduced with their expansion where the expansion
@@ -63,8 +77,15 @@
Examples would include "support vector machine (SVM)" or "MCMC (Markov
chain Monte Carlo)" etc.
-	- see our notes below

+We have checked our usage of abbreviations and their introduction, and have
+corrected several occurences. For several terms which are derived from
+abbreviations, can be read as acronyms, or contain portions of abbreviations or
+acronyms, we have decided to treat these as proper names, which are not
+introduced with an expansion. A list terms that we have / have not treated as
+an abbreviation is included near the end of this text file. Naturally we will
+be happy to adjust our treatment of these terms per your request.
+
--- Items that we are not sure about ---
---- Use of the \proglang macro ----
In several cases, we are not entirely sure, whether the use of the \proglang macro is called for or not.
@@ -91,8 +112,6 @@
libraries.
* HTML, XML: We are not entirely sure, whether these markup languages are to be considered
"programmable", but have decided to use the \proglang macro for these.
--- TODO --
-- Complete?

----- We have not used the \proglang macro on these items -----
* PNG, JPEG: Binary file formats.
@@ -111,8 +130,6 @@
* R Commander: For similar reasons, we marked up only the "R" in R Commander with the
\proglang macro (the corresponding package Rcmdr is marked up using the \pkg macro).
* Red-R:  Not marked as \proglang, for the same reason as "RKWard".
--- TODO --
-- Complete?

---- Expansion of acronyms or partial abbreviations ----
We have decided to treat the following items as proper names that do not need to be
@@ -137,7 +154,8 @@
Further, we refrained from expanding the names of R packages such as "JGR", and any terms
marked up as \code.

-The following abbreviations are introduced in the article (page number of introduction):
+The following items are treated as abbreviations, and are introduced in the
+article (page number of introduction is given in parentheses):
* GUI (1 & 2)
* IDE (2)
* GPL (3)
@@ -155,12 +173,3 @@
* XML (22)
* IRT (24)
* ECDF (25)
--- TODO --
-- Complete?
-
--- Generic TODO list --
-- Check, whether we are really following the above lists (markup, abbreviations), consistently.
-  - Also check, whether we introduce all abbreviations, properly.
-- Second check figure placement
-
-

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.