this is for holding javascript data
Linh edited untitled.tex
about 8 years ago
Commit id: 3f9369fb6a297876e912f8d7a8e2e3a02a2afb49
deletions | additions
diff --git a/untitled.tex b/untitled.tex
index 45646b4..6aa60ec 100644
--- a/untitled.tex
+++ b/untitled.tex
...
%Wir sollten uns auf Wikidata konzentrieren und nicht so sehr über Wikipedia abschweifen:
Once added to Wikipedia, a formula usually doesn't change frequently due to being proved by scientist beforehand and checked by certain Wikipedia users afterwards.
Because of the limited scope of targets, the data type will only be relevant for a small portion of Wikipedia.
Mathematical formulae do offer a broader use case as an own data
type. type though. Unlike chemical formulae, mathematical ones have variables and are used for
calculations. %TODO: den Satz verstehe ich nicht:
These calculations would calculations, which can be
implementable in added to the data
type\footnote{\url{http://www.wolframalpha.com/} enables queries resulting type in
complex information about the future. Something similar is already possible with WolframAlpha\footnote{\url{http://www.wolframalpha.com/}}, a computational knowledge engine which allows the user to enter a formula and
returns information such as a graph or zero. It is also
able possible to
calculate use WolframAlpha as a calculator with TeX
string String as
input}. input, a feature we also see in our future work with our data type. While it might be also possible in the add-on idea, it would create a huge overhead for every other use
case There is no free accessible database containing all kinds of mathematical formulae yet. A separate data type where meta data is stored additionally to the formula enables that. Especially computers can look up all kind or formula way easier. case.
\section{Implementation choices}
...
\subsection{Math formula as property type}
Implementing the data type as property type with string as value type would have changed nothing in regards of the output. Instead of storing the information separately in a tuple though, all the information would be in the TeX-string. For the example from above, a possible notation would be\\
\verb!f(x) = \sum\limits_{i = 0}^{n} #a_i|coefficient# x^i,!\\ \verb!n \in \mathds{N}, a_n \neq 0!\\ On the one hand, we wanted our data type to easily handle complex tasks like easy calculation and linking variables and sub formulae to their respective items, on the other hand we had to make sure that our data type will be usable for Wikipedia users. After a discussion with Lydia
Pintscher, the product manager of WikiData, and
Daniel Daniel, a developer from Wikimedia Foundation,
who works on data types in WikiData, we decided to choose the property type version. Maintenance by outsiders is way easier this way and we did not found enough features to justify the overhead the value type implementation would bring.
Before we could start to implement the data type though, we needed something to see, how its going to look like when deployed in Wikipedia.
\section{Test environment}