From: Joost Helberg <joost@snow.nl>
To: billw@wolfram.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Elsevier's "Executable Paper Grand Challenge"
Date: Thu, 09 Dec 2010 10:24:28 +0100 (CET) [thread overview]
Message-ID: <20101209.102428.49159777.joost@snow.nl> (raw)
In-Reply-To: <87lj41pepi.fsf_-_@wolfram.com>
[-- Attachment #1: Type: Text/Plain, Size: 2157 bytes --]
Bill,
An org-file instance on a virtual machine based on GNU/Linux and other
open source stuff doesn't limit any redistribution and will always run
on the right host. The host architecture is the only limitation then.
One issue with org-mode and babel is the necessary availability of all
tools called by the babel-lines. Publishing a VM File with all tools
installed as the container of a scientific document solves this.
January 15th is a bit close though.
regards,
Joost
>>>>> "Bill" == Bill White <billw@wolfram.com> writes:
> Subject: [Orgmode] Elsevier's "Executable Paper Grand Challenge"
> From: Bill White <billw@wolfram.com>
> To: emacs-orgmode@gnu.org
> Date: Tue, 07 Dec 2010 13:26:01 -0600
> In light of recent paper by Davison, Dominik, Dye and Schulte, this
> sounds like something org-mode could address:
> http://www.executablepapers.com
> There is a USD 10000 first-place award.
> Executable Paper Grand Challenge is a contest created to improve the
> way scientific information is communicated and used.
> It asks:
> How can we develop a model for executable files that is compatible
> with the user’s operating system and architecture and adaptable to
> future systems?
> How do we manage very large file sizes?
> How do we validate data and code, and decrease the reviewer’s
> workload?
> How to support registering and tracking of actions taken on the
> ‘executable paper?’
> The purpose of the Executable Paper Challenge is to invite scientists
> to put forth their ideas pertaining to these pressing and unsolved
> questions.
> See http://www.executablepapers.com for more information, deadlines, etc.
> Cheers -
> bw
> --
> Bill White . billw@wolfram.com . http://members.wolfram.com/billw
> "No ma'am, we're musicians."
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
Snow B.V. http://snow.nl
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-12-09 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 7:54 Multi Todo state Chao LU
2010-12-07 8:02 ` suvayu ali
2010-12-07 15:22 ` Eric S Fraga
2010-12-07 19:26 ` Elsevier's "Executable Paper Grand Challenge" Bill White
2010-12-07 21:02 ` Thomas S. Dye
2010-12-07 21:09 ` Erik Iverson
2010-12-09 9:24 ` Joost Helberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101209.102428.49159777.joost@snow.nl \
--to=joost@snow.nl \
--cc=billw@wolfram.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).