bundle install
bundle exec nanoc compile
bundle install
bundle exec guard
https://linkedsoftwaredependencies.org/articles/reproducibility/
Article “Reproducible software experiments through semantic configurations”
Home Page: https://linkedsoftwaredependencies.org/articles/reproducibility/
bundle install
bundle exec nanoc compile
bundle install
bundle exec guard
https://linkedsoftwaredependencies.org/articles/reproducibility/
Components vocabulary
Object Mapping vocabulary
Components JSON-LD context
LDF server JSON-LD context
For instance [](#om-collects-module), [](#om-collects-data) and [](#om-collects-result)
could more conveniently be written as [](#om-collects-module,#om-collects-data,#om-collects-result)
.
It would be great if code snippets can be included.
Both inline code and code imported from external files would be nice.
Markdown codeblock support would be awesome, both `code` and ```code```.
I currently use iframe
's, the only problem with this is that printing to PDF ignores iframe
's.
Instead of having to type [Fig. 4](#config-n3)
, something like [Fig](#config-n3)
with automatic numbering would be more convenient.
Authors should have their foaf profiles linked.
If links like [Components.js](https://github.com/LinkedSoftwareDependencies/Components.js)
are included, they are not included in the PDF-ized paper.
One option could be that footnotes are automatically added for such links.
Or a special tag similar to [Components.js](footnote https://github.com/LinkedSoftwareDependencies/Components.js)
can be added.
Currently, nesting markdown in html is not possible, as can be seen here: https://linkedsoftwaredependencies.github.io/Article-Reproducability/#use-case
If it's not a trivial thing to implement, we need to manually make it so that the mandatory links inside these HTML blocks are included in the paper.
@hvdsomp pointed me to Andreas Rauber's work, which includes relevant publications:
We might want to study and cite them.
Ordered and unordered list support, either with HTML tags (<ol>
, <ul>
) or markdown (*
).
At the end of the introduction, section references are wrong.
An alternative for footnotes would be nice.
Now I use <sidenote>
as a placeholder.
For instance [Inversion of Control](cite:cites DesigningReusableClasses,InversionOfControl)
or [Inversion of Control](cite:cites DesigningReusableClasses, cite:cites InversionOfControl)
Currently, referencing to subsections (<h3>
) results in Unknown x
.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.