Changes between Version 5 and Version 6 of ImplementationBootcamp
- Timestamp:
- 2010/02/10 16:16:33 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ImplementationBootcamp
v5 v6 1 = = Implementation Bootcamp ==1 = Implementation Bootcamp = 2 2 3 == == Participants ====3 == Participants == 4 4 5 5 * Please add your name here 6 * Rutger Vos 6 7 7 == == Last year was largely about concept. This year will be about hairy coding! ====8 == Implementation tips and tricks / FAQ == 8 9 9 If you need to do XXX then you should use/do YYY 10 Here we collect useful tips and tricks so that we don't all have to reinvent the wheel. Please add any answers and/or questions! 10 11 11 * I have to build a triplestore, what tool should I use under what circumstances? 12 === I have to build a triplestore, what tool should I use under what circumstances? === 12 13 13 * I have an analysis tool, how do I expose it as a semantic web resource? 14 Francois Belleau seems to prefer virtuoso, though he assures us he has no commercial interest in them :) 14 15 15 * I have to build an OWL model of my data - how do I go about doing this? 16 === I have an analysis tool, how do I expose it as a semantic web resource? === 16 17 17 * When someone calls GET on my URLs, what should I return in order to be semantic webby? 18 === I have to build an OWL model of my data - how do I go about doing this? === 18 19 19 * What are the similarities and differences between the various shared names proposals? 20 === When someone calls GET on my URLs, what should I return in order to be semantic webby? === 20 21 21 * What XSL processor to use, should you want to convert legacy xml to rdf? 22 === What are the similarities and differences between the various shared names proposals? === 23 24 === What XSL processor to use, should you want to convert legacy xml to rdf? === 25 26 @yokofakun just tweeted using xsltproc for this, but it doesn't seem to be happy about xsl 2.0 features, so @rvosa is using net.sf.saxon.Transform instead.
