profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Aklakan/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Claus Stadler Aklakan University of Leipzig Leipzig

Aklakan/libnss-json 5

JSON bindings for the Name Service Switch (NSS)

Aklakan/DarkSouls-GlovePIE 3

GlovePIE Script for Dark Souls (Wiimote + Nunchuck)

Aklakan/japanese-word-forms-trainer 2

A little japanese trainer app for practicing different word forms

Aklakan/MyTools 2

A collection of some scripts I wrote

Aklakan/aksw-commons.gwt 1

Automatically exported from code.google.com/p/aksw-commons.gwt

Aklakan/aksw-commons.preconfigured 1

Automatically exported from code.google.com/p/aksw-commons.preconfigured

Aklakan/dataId 1

The DBpedia Data ID Unit is a DBpedia Group with the goal of describing LOD datasets via RDF files, to host and deliver these metadata files together with the dataset in a uniform way, create and validate such files and deploy the results for the DBpedia and its local chapters.

push eventScaseco/jenax

Claus Stadler

commit sha a959d999ce416e5b5bec3178888bfeb957dc292e

Project now compiles and tests succeed

view details

push time in 4 hours

push eventSmartDataAnalytics/aksw-commons

Claus Stadler

commit sha a74fa03c44f112180d5c2a2f63dc41ffaf6998a8

Added a small list utility

view details

push time in 4 hours

push eventScaseco/jenax

Claus Stadler

commit sha 2f5f2af9adac934f2f358d4da1a284123d3d5a5c

data access module migrated

view details

push time in 4 hours

push eventScaseco/jenax

Claus Stadler

commit sha 4ea4903c6d0f0e5141c066a90f96e9612dad1504

more work

view details

push time in 21 hours

push eventScaseco/jenax

Claus Stadler

commit sha 1a11b9bd086e6b2b61af5ef22b2e73113f2297ce

datashapes module compiling

view details

push time in 21 hours

push eventScaseco/jenax

Claus Stadler

commit sha 59cc5280a55e22233a77d6892c8e3140418d0cd2

jpa module also compiles; dataaccess not yet building

view details

push time in 21 hours

push eventScaseco/jenax

Claus Stadler

commit sha bb445beede7a5ac4e49ead691e529bd5b6f9c430

path finder module should now compile

view details

push time in 21 hours

push eventScaseco/jenax

Claus Stadler

commit sha ef242b8c712742deec59c5fff12e1d54131995af

more work... the path module makes extensive use of Pair; probably need to migrate that class too

view details

push time in 21 hours

push eventScaseco/jenax

Claus Stadler

commit sha 9c193974b9897498487f0271e6afdc23a17156af

more work for migrating jsa-core to jenax-dataaccess

view details

push time in a day

push eventSmartDataAnalytics/aksw-commons

Claus Stadler

commit sha 533991ff93679cb2c3d058c76d4d2fa51cd1661f

Added the triplet utility classes from jsa utils to this utils module

view details

push time in a day

push eventScaseco/jenax

Claus Stadler

commit sha 390237bec4540c0f2acaa72b672086be81fc1f84

Added jsa-core to jsa-rx-dataaccess for now (not ideal because large parts independent of rx; may be split further)

view details

push time in a day

push eventSmartDataAnalytics/aksw-commons

Claus Stadler

commit sha e7545ae7f3ec362790d98d996f0d904d46972392

Moved the data provider api (lookup / list / map service) from jsa to the rx module

view details

push time in 2 days

push eventhobbit-project/facete3

Claus Stadler

commit sha 6fec81a222b9afe25613e0d2bf2e1a81da4d6df4

wip to upgrade to jena/x 4.3.0 (not yet building)

view details

push time in 2 days

push eventScaseco/jenax

Claus Stadler

commit sha bf1450bf7855c84e8391a08bcfa28cd5df90c861

Turns out there are some parts in use in modules I wanted to retire; towards migrating those (build broken for now)

view details

push time in 2 days

push eventhobbit-project/facete3

Claus Stadler

commit sha b58d2114365b8d2b3ffb20f2cdc65f56a8585728

Upgrade to jena 4.3.0-SNAPSHOT (not yet building)

view details

push time in 3 days

push eventScaseco/jenax

Claus Stadler

commit sha 2b3e08bb0439aa8790871bdd2b22ef9e7af0298e

jenax now building with all modules (though one conjure test case disabled because of hard to track NPE)

view details

push time in 3 days

push eventGeoKnow/LinkedGeoData

Claus Stadler

commit sha 1048e4d5d0f7d5f2c2713c6dce9ea42e26671f52

Added missing restart entries

view details

push time in 3 days

create barnchAKSW/LSQ

branch : jena-4.3.0

created branch time in 3 days

issue commentAKSW/LSQ

Instructions not clear

The reason why there is benchmark create and prepare is to provide context for the benchmarking; espacially about the thresholds that were in place (timeouts / result set limits). The generated config files are RDF and can be put into the same dataset / triple store as the benchmark result. From the same benchmark configuration (create) it is possible to prepare and execute multiple runs at different points in time. While results obtained with different configurations may not be directly comparable, those runs prepared from the same setting should typically be.

vemonet

comment created time in 6 days

issue commentAKSW/LSQ

Instructions not clear

Thanks for your efforts in explaining the process of lsq in clarity. I suppose you are fine with it if I eventually I copied (at least partially) your instruction back into the docs? ;)

vemonet

comment created time in 6 days

issue commentAKSW/LSQ

Make it available as a Docker container

I totally agree that there should be a docker container. One reason this hasn't happened yet that for the past months i wanted to transition the rdfize/analyze part of the processing to apache spark - but I only got around to do it one or two weeks ago. Also the reason why the 'old' lsq is not cross-platform is because if its depondency on /usr/bin/sort - with spark lsq should be fully cross platform - in any case, a docker container certainly makes things alot easier.

vemonet

comment created time in 6 days

issue openedAKSW/LSQ

Add option to rdfize only a sample from the input

LSQ commands for reading in data should support limit/offset parameters to make testing easier

created time in 6 days

push eventSANSA-Stack/SANSA-Stack

Claus Stadler

commit sha d34f9be4ac7a97f20592fa0fed0915995fbfc402

upgraded the lower levels to jena 4.3.0-SNAPSHOT (requires jena to be built from git!)

view details

push time in 6 days

push eventScaseco/r2rml-api-jena

Claus Stadler

commit sha 5bf0647795e6a1c83d8eb9e4a32f5218fe9b4424

Upgrade to jena and jenax 4.3.0-SNAPSHOT

view details

push time in 6 days

push eventSANSA-Stack/SANSA-Stack

Claus Stadler

commit sha 41665eabe790edf4b2214f20cdd19532c72d63e3

Fixed compile errors due to api changes in the rdf reader

view details

push time in 7 days

startedAKSW/sante

started time in 7 days

startedAKSW/sante

started time in 7 days

push eventScaseco/jenax

Claus Stadler

commit sha 91de02858c68e151d46f570b10bd6d9c110c6d5a

Partly migrated to the RDFLink api - but needs more cleanup and removal of the RDFConnection-based utils

view details

push time in 8 days

push eventScaseco/jenax

Claus Stadler

commit sha e01fe1ed0013bfc8b0bf814e80815341b793e4f9

towards migrating the query transform preprocessor...

view details

push time in 8 days

push eventScaseco/jenax

Claus Stadler

commit sha d6d62f45d90f555f56138f576416a40f5447af61

Migrated the core of the connection / query execution builder framework

view details

push time in 8 days