Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
schaertl_andreas
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
supervision
schaertl_andreas
Commits
05f78daa
Commit
05f78daa
authored
4 years ago
by
Andreas Schärtl
Browse files
Options
Downloads
Patches
Plain Diff
report: review intro
parent
e7b9fdcc
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/report/introduction.tex
+21
-20
21 additions, 20 deletions
doc/report/introduction.tex
with
21 additions
and
20 deletions
doc/report/introduction.tex
+
21
−
20
View file @
05f78daa
...
...
@@ -9,17 +9,17 @@ is that computerization will yield great improvement to formal
research by making the results of all collected publications readily
available and easy to search.
One research
topic
in this field is the idea of a
\emph
{
tetrapodal
search
}
that combines four distinct areas of mathematical knowledge.
One
topic of
research in this field is the idea of a
\emph
{
tetrapodal
search
}
that combines four distinct areas of mathematical knowledge.
These four kinds being (1)~the actual formulae as
\emph
{
symbolic
knowledge
}
, (2)~examples and concrete objects as
\emph
{
concrete
knowledge
}
,
(3)~names and comments as
\emph
{
narrative knowledge
}
and
finally
(4)~identifiers, references and their relationships, referred
to as
\emph
{
organizational knowledge
}
~
\cite
{
tetra
}
.
knowledge
}
, (2)~examples and concrete objects as
\emph
{
concrete
knowledge
}
,
(3)~names and comments as
\emph
{
narrative knowledge
}
and
finally
(4)~identifiers, references and their relationships, referred
to as
\emph
{
organizational knowledge
}
~
\cite
{
tetra
}
.
Tetrapodal search aims to provide a unified search engine that indexes
each of the four different subsets of mathematical knowledge.
Because
all four kinds of knowledge are inherently
different
in their
each of the
se
four different subsets of mathematical knowledge.
Because
all four kinds of knowledge are inherently
unique
in their
structure, tetrapodal search proposes that each kind of mathematical
knowledge should be made available in a storage backend that fits the
kind of data it is providing. With all four areas available for
...
...
@@ -40,26 +40,27 @@ available~\cite{afpexport, uloisabelle, ulocoq}. The resulting data
set is already quite large, the Isabelle export alone containing more
than 200~million triplets.
Existing exports from Isabelle and Coq result in
a
set of XML~files
Existing exports from Isabelle and Coq result in set
s
of XML~files
that contain RDF~triplets. This is a convenient format for exchange
and easily tracked using version control systems such as
Git~
\cite
{
gitpaper
}
as employed by MathHub~
\cite
{
mh
}
. However,
considering the vast number of triplets, it is impossible to query
easily and efficiently in this state. This is what
\emph
{
ulo-storage
}
is focused on
: M
aking ULO data sets accessible for querying and
is focused on
, that is m
aking ULO data sets accessible for querying and
analysis. We collected RDF files spread over different Git
repositories, imported them into a database and then experimented with
APIs for accessing that data set.
The main contribution of
\emph
{
ulo-storage
}
is twofold. First, (1)~we
built up various infrastructure components for making organizational
knowledge queryable. These components can make up building blocks of
a larger tetrapodal search system. Their design and implementation are
discussed in Section~
\ref
{
sec:implementation
}
. Second, (2)~we ran
sample prototype applications and queries on top of this
interface. While the applications themselves are admittedly not very
useful in itself, they can give us insight about future development of
the upper level ontology. These applications and queries are the focus
of Section~
\ref
{
sec:applications
}
. A summary of encountered problems
and suggestions for next steps concludes this report in
built up various infrastructure components that make organizational
knowledge easy to query. These components can make up building blocks
of a larger tetrapodal search system. Their design and implementation
are discussed in Section~
\ref
{
sec:implementation
}
. Second, (2)~we ran
prototype applications and queries on top of this
infrastructure. While the applications themselves are admittedly not
very useful in itself, they can give us insight about future
development of the upper level ontology and related schemas. These
applications and queries are the focus of
Section~
\ref
{
sec:applications
}
. A summary of encountered problems and
suggestions for next steps concludes this report in
Section~
\ref
{
sec:conclusion
}
.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment