|
5 | 5 | \usepackage[english]{babel} |
6 | 6 | \usepackage[T1]{fontenc} |
7 | 7 |
|
| 8 | +\usepackage{tcolorbox} |
8 | 9 | \usepackage{relsize} |
9 | 10 | %\usepackage[breaklinks=true]{hyperref}% hyperref links are displaced with baposter because of the font scale |
10 | 11 | \usepackage{url} |
|
175 | 176 | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
176 | 177 | \begin{posterbox}[name=results,column=1]{Results} |
177 | 178 | SNIK v0.8 contains \num{4729} classes, \num{329} properties, \num{713} interlinks and \num{112747} triples and is available under the CC BY-NC-SA 4.0 as: |
| 179 | +\iffalse |
178 | 180 | \begin{tabulary}{\columnwidth}{lL} |
179 | 181 | \toprule |
180 | 182 | %URL &\url{http://www.snik.eu/ontology}\\ |
|
185 | 187 | %RDF Dump &\url{https://github.com/IMISE/snik-ontology/releases/download/0.8.0/snik-0.8.zip}\\ |
186 | 188 | \bottomrule |
187 | 189 | \end{tabulary}%The source code for the services is available at \url{https://github.com/imise} |
188 | | - |
| 190 | +\fi |
189 | 191 | %The \emph{RDF dump} is available at \url{https://github.com/IMISE/snik-ontology/releases/download/0.8.0/snik-0.8.zip} and contains all triples of SNIK in Turtle syntax, such as: |
| 192 | + |
| 193 | +%\begin{tcolorbox}[colback=white,colframe=mediblue,title=RDF Dump\\\url{https://github.com/IMISE/snik-ontology/releases/download/0.8.0/snik-0.8.zip}] |
| 194 | +\begin{tcolorbox}[colback=white,colframe=mediblue,title=RDF Dump~~\url{http://www.snik.eu/download/snik-0.8.zip}] |
190 | 195 | The \emph{RDF dump} contains all triples of SNIK in Turtle syntax, such as: |
191 | 196 | \begin{lstlisting}[basicstyle=\ttfamily] |
192 | 197 | bb:InformationSystem |
|
196 | 201 | meta:supports bb:Documentation. |
197 | 202 | \end{lstlisting} |
198 | 203 | %offers several interfaces that are useful for researchers practitioners and students, depending on their objectives and their semantic web skills. |
199 | | -Users can open a SNIK class URL in a web browser using \emph{LodLive}~\cite{lodlive}: |
| 204 | +\vspace{-1.0em} |
| 205 | +\end{tcolorbox} |
| 206 | +\vspace{-0.5em} |
| 207 | + |
| 208 | +\begin{tcolorbox}[colback=white,colframe=mediblue,title=LodLive RDF Browser~~~~~~~~~~~~~\url{http://www.snik.eu/ontology}] |
| 209 | +%Users can open a SNIK class URL in a web browser using \emph{LodLive}~\cite{lodlive}: |
200 | 210 | \includegraphics[width=\textwidth]{img/lodlive.png} |
| 211 | +\vspace{-1.0em} |
| 212 | +\end{tcolorbox} |
| 213 | +\vspace{-0.5em} |
| 214 | + |
| 215 | +\begin{tcolorbox}[colback=white,colframe=mediblue,title=SNIK Graph~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\url{http://www.snik.eu/graph}] |
201 | 216 | \emph{SNIK Graph} visualizes the structure of SNIK by modelling each class as a node and each RDF triple and OWL restriction as an edge: |
202 | 217 | \includegraphics[width=\textwidth]{img/snikgraph.png} |
203 | 218 | %SNIK Graph queries the list of classes and their relations from the SPARQL endpoint and transforms them into nodes and edges of the graph. |
204 | 219 | %Exploration options like the “spider worm”, which consists of the shortest path between a start node and an end node together with the end node’s neighbourhood, illustrate the context of a concept. |
205 | 220 | %The meta model and the subontologies can be freely accessed via SPARQL queries: |
| 221 | +\vspace{-1.0em} |
| 222 | +\end{tcolorbox} |
| 223 | +\vspace{-0.5em} |
| 224 | + |
| 225 | +\begin{tcolorbox}[colback=white,colframe=mediblue,title=SPARQL Endpoint~~~~~~~~~~~~~~~~\url{http://www.snik.eu/sparql}] |
206 | 226 | The SPARQL endpoint is the most expressive interface to SNIK but requires knowledge of both the SPARQL syntax and the SNIK meta model. |
207 | 227 | %Read access is publicly available at \url{http://www.snik.eu/sparql} |
208 | | -It can be used both as an API and directly. |
209 | | -Example queries:\\ |
210 | | -Which components of a healthcare network are not healthcare institutions? |
| 228 | +It can be used both as an API and directly. Examples:\\ |
| 229 | + |
| 230 | +Which healthcare network components are not healthcare institutions? |
211 | 231 | \begin{lstlisting} |
212 | 232 | SELECT ?x {bb:HealthCareNetwork meta:entityTypeComponent ?x. |
213 | 233 | MINUS {?x rdfs:subClassOf* bb:HealthCareInstitution.}} |
|
216 | 236 | \begin{lstlisting} |
217 | 237 | SELECT COUNT(?f) {bb:ChiefInformationOfficer meta:isResponsibleForFunction ?f.} |
218 | 238 | \end{lstlisting} |
219 | | - |
220 | | -Do transinstitutional health information systems support telemicroscopy? |
221 | | -\begin{lstlisting} |
222 | | -ASK {bb:TransinstitutionalHealthInformationSystem meta:supports bb:Telemicroscopy.} |
223 | | -\end{lstlisting} |
224 | | -\vspace{0.0em} |
| 239 | +% |
| 240 | +%Do transinstitutional health information systems support telemicroscopy? |
| 241 | +%\begin{lstlisting} |
| 242 | +%ASK {bb:TransinstitutionalHealthInformationSystem meta:supports bb:Telemicroscopy.} |
| 243 | +%\end{lstlisting} |
| 244 | +\vspace{-1.0em} |
| 245 | +\end{tcolorbox} |
| 246 | +\vspace{-0.5em} |
225 | 247 |
|
226 | 248 | \end{posterbox} |
227 | 249 | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
|
0 commit comments