Changes between Version 27 and Version 28 of InstallationInstructions
- Timestamp:
- 07/09/10 12:38:18 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InstallationInstructions
v27 v28 23 23 24 24 Well, and you MUST have several RDF files for rdfhomepage to work: 25 * a FOAF file specifying yourself and your "friends"and colleagues25 * a FOAF file specifying yourself and your "friends" and colleagues 26 26 * a bibtex files, that is, the text version PLUS the RDF version(!) of your publications 27 27 * an organizational model, that is, your organizational properties and relations (your projects, department(s), roles...) … … 39 39 For all RDF files to be used in rdfhomepage you have to follow the following rules (btw, you should follow these rules for all software using RDF). This holds especially for your FOAF file: 40 40 41 * Resources to be referenced from outside the RDF file need a URI = >Your foaf:Person needs a URI.42 * Blank/anonymous nodes can't be referenced from outside the RDF file. = > Your foaf:Person needs a URI, no blank/anonymous node! So: don't use nodeID="...", but use rdf:about="...".43 * Some (most!) RDF parsers do not like relative URIs (or NodeIDs). = > It is generally better to use ABSOLUTE URIs. So: don't use rdf:about="#me" in your foaf file, better use something like rdf:about="http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me".41 * Resources to be referenced from outside the RDF file need a URI => Your foaf:Person needs a URI. 42 * Blank/anonymous nodes can't be referenced from outside the RDF file. => Your foaf:Person needs a URI, no blank/anonymous node! So: don't use nodeID="...", but use rdf:about="...". 43 * Some (most!) RDF parsers do not like relative URIs (or NodeIDs). => It is generally better to use ABSOLUTE URIs. So: don't use rdf:about="#me" in your foaf file, better use something like rdf:about="http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me". 44 44 * Generally, every thing described in an RDF file, that could be relevant and/or referenced outside the RDF file, should have an absolute URI. However, the foaf:Persons I link with foaf:knows do not have a URI, because so many people out there do not have a URI for their foaf:Person. 45 45 … … 47 47 {{{ 48 48 // The location of your FOAF file on the web (This is also the data source) 49 $MY_FOAF_FILE_URL = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml";49 $MY_FOAF_FILE_URL = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml"; 50 50 51 51 // Your URI in your FOAF file - Look this one up! 52 $MY_FOAF_URI = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me";52 $MY_FOAF_URI = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me"; 53 53 }}} 54 54 … … 69 69 At the END of the bibtex-file there is a rdf:Seq like this 70 70 {{{ 71 <rdf:Seq rdf:about="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList">72 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz05"/>73 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz06"/>74 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#GrimnesSchwarzSauermann06"/>71 <rdf:Seq rdf:about="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList"> 72 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz05"/> 73 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz06"/> 74 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#GrimnesSchwarzSauermann06"/> 75 75 . . . 76 </rdf:Seq>76 </rdf:Seq> 77 77 }}} 78 78 … … 80 80 {{{ 81 81 // The name (not path) of your bibtex.rdf 82 define( "BIBTEX_FILE_NAME", "bib_ss.rdf");82 define("BIBTEX_FILE_NAME", "bib_ss.rdf"); 83 83 84 84 // The URL of your BibTeX file. (real BibTeX format, not RDF!) 85 $MY_BIB_TEX_URL = "http://www.dfki.uni-kl.de/~schwarz/ss.bib";85 $MY_BIB_TEX_URL = "http://www.dfki.uni-kl.de/~schwarz/ss.bib"; 86 86 87 87 // The URI of a sequence of all the articles in your bibtex file 88 $MY_BIB_TEX_SEQ_URI = "http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList";88 $MY_BIB_TEX_SEQ_URI = "http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList"; 89 89 }}} 90 90 … … 94 94 95 95 The !OrgRep models our/your organizational structure, that is, your organizational properties and relations, your projects, project leaders, department, research groups, etc. Especially the relations between people and projects will be used for rdfhomepage. 96 You may have a look at our !OrgRep - > see {{{{rdfhomepage/vocabulary/OrgRepDFKI.*}}} ->best viewed with [http://protege.stanford.edu/ Protege], http://protege.stanford.edu/96 You may have a look at our !OrgRep -> see {{{{rdfhomepage/vocabulary/OrgRepDFKI.*}}} -> best viewed with [http://protege.stanford.edu/ Protege], http://protege.stanford.edu/ 97 97 98 98 There is also a better, nearly-empty Protege-Projekt + RDF + RDFS, which you could use to model your own organizational structure(s): {{{{rdfhomepage/vocabulary/OrgRep.*}}} [[BR]] 99 99 I advise you take the following steps: 100 100 1. Open {{{OrgRep.pprj}}} with Protege 101 2. Save it again (File/Save as), maybe use other filenames like {{{OrgRepACME.*}}} - the important thing here is: choose an OTHER default namespace - > last edit field in the "Save as"dialog (initially, the value will be http://rdfhomepage.opendfki.de/please_choose_another_namespace#).101 2. Save it again (File/Save as), maybe use other filenames like {{{OrgRepACME.*}}} - the important thing here is: choose an OTHER default namespace -> last edit field in the "Save as" dialog (initially, the value will be http://rdfhomepage.opendfki.de/please_choose_another_namespace#). 102 102 3. Open it again (with Protege) and add your people, projects, etc. therein. 103 4. There are some inverse properties, which may need manual care, e.g. between org:Project <-->org:Person103 4. There are some inverse properties, which may need manual care, e.g. between org:Project <--> org:Person 104 104 105 105 I would suggest better URIs than the automatically generated ones by Protege, but as Protege does not provide a GUI component to edit the URI (or does it?), you would have to edit/replace the URIs later using a text editor or shell command or whatever. … … 109 109 // Your URI in the OrgRep ontology 110 110 // If in doubt, look it up in the OrgRep RDF File or ask somebody! 111 $MY_ORGREP_URI = "http://km.dfki.de/model/org#OrganisationalModel_00077";111 $MY_ORGREP_URI = "http://km.dfki.de/model/org#OrganisationalModel_00077"; 112 112 }}} 113 113 … … 125 125 // as it can be found in the rdfhomepage.rdf file. 126 126 // You may commit to the default URI scheme, which is like 127 // http://www.dfki.uni-kl.de/~schwarz <-- note: no trailing slash!!!127 // http://www.dfki.uni-kl.de/~schwarz <-- note: no trailing slash!!! 128 128 // or change this value 129 $MY_HOMEPAGE_URI= "http://www.dfki.uni-kl.de/~schwarz";129 $MY_HOMEPAGE_URI= "http://www.dfki.uni-kl.de/~schwarz"; 130 130 }}} 131 131 132 132 Another important thing in the homepage.rdf is the information about the name that is used in your bibtex. Unfortunately this information should be better stored in config.php, but it is in homepage.rdf for several reasons... ;) 133 133 {{{ 134 <hp:bibtexName>Sven Schwarz</hp:bibtexName>134 <hp:bibtexName>Sven Schwarz</hp:bibtexName> 135 135 }}} 136 136 Edit this to match the name (or abbreviation!) you use IN YOUR BIBTEX FILE. Currently, you have to decide on exactly ONE version! So: do not mix full names with abbreviations in your bibtex file! … … 141 141 There could be a chunk containing short information about yourself: 142 142 {{{ 143 <hp:shortBio>144 <![CDATA[145 <p align="justify">143 <hp:shortBio> 144 <![CDATA[ 145 <p align="justify"> 146 146 My name is Bob. I am a researcher aiming at... 147 </p>148 <p align="justify">147 </p> 148 <p align="justify"> 149 149 I like tennis and swimming... 150 </p>151 ]] >152 </hp:shortBio>150 </p> 151 ]]> 152 </hp:shortBio> 153 153 }}} 154 154 … … 157 157 Most probably, there will be one or more chunks about projects you work for: 158 158 {{{ 159 <hp:inProject>160 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0815">161 <hp:htmlText>162 <![CDATA[163 <p align="justify">164 This is one of two projects I work for. <br/>159 <hp:inProject> 160 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0815"> 161 <hp:htmlText> 162 <![CDATA[ 163 <p align="justify"> 164 This is one of two projects I work for.<br/> 165 165 I took talk hours about this project... 166 </p>167 ]] >168 </hp:htmlText>169 <hp:next rdf:resource="http://orgrep_namespace#OrgRep_0816"/>170 </hp:Project>171 </hp:inProject>172 173 <hp:inProject>174 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0816">175 <hp:htmlText>176 <![CDATA[177 <p align="justify">166 </p> 167 ]]> 168 </hp:htmlText> 169 <hp:next rdf:resource="http://orgrep_namespace#OrgRep_0816"/> 170 </hp:Project> 171 </hp:inProject> 172 173 <hp:inProject> 174 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0816"> 175 <hp:htmlText> 176 <![CDATA[ 177 <p align="justify"> 178 178 And this is the second of the two projects I work for. 179 </p>180 ]] >181 </hp:htmlText>182 <!-- no next project -->183 </hp:Project>184 </hp:inProject>179 </p> 180 ]]> 181 </hp:htmlText> 182 <!-- no next project --> 183 </hp:Project> 184 </hp:inProject> 185 185 }}} 186 186 We see several things here: … … 195 195 196 196 There can be one or more chunks about your (research) interest. 197 As "interests" are quite manifold, each interest belongs to (exactly!) one "section".198 I personally distinguish between "research contributions" and "research applications"(however, you do not have to do so as well):199 {{{ 200 <hp:hasInterest>201 <hp:Interest rdf:about="http://some_namespace#MayorResearch"202 rdfs:label= "Mayor Research Questions">203 <hp:section>204 <hp:Section rdf:about="http://some_namespace#MyContribution"205 hp:htmlText= "My Contribution to Research"/>206 </hp:section>207 <hp:htmlText>208 <![CDATA[209 <p align="justify">197 As "interests" are quite manifold, each interest belongs to (exactly!) one "section". 198 I personally distinguish between "research contributions" and "research applications" (however, you do not have to do so as well): 199 {{{ 200 <hp:hasInterest> 201 <hp:Interest rdf:about="http://some_namespace#MayorResearch" 202 rdfs:label="Mayor Research Questions"> 203 <hp:section> 204 <hp:Section rdf:about="http://some_namespace#MyContribution" 205 hp:htmlText="My Contribution to Research"/> 206 </hp:section> 207 <hp:htmlText> 208 <![CDATA[ 209 <p align="justify"> 210 210 My mayor research questions: 211 <ul>212 <li><b>research in ABC</b>: ABC is my personal dream... </li>213 <li><b>DEF for GHI</b>: In the next 2 months, ... </li>214 </ul>215 </p>216 ]] >217 </hp:htmlText>218 <hp:next rdf:resource="http://some_namespace#MinorResearch"/>219 </hp:Interest>220 </hp:hasInterest>221 <hp:hasInterest>222 <hp:Interest rdf:about="http://some_namespace#MinorResearch"223 rdfs:label= "Minor Research Questions">224 <hp:section rdf:resource="http://some_namespace#MyContribution"/> <!-- same section!!! -->225 <hp:htmlText>226 <![CDATA[227 <p align="justify">211 <ul> 212 <li><b>research in ABC</b>: ABC is my personal dream... </li> 213 <li><b>DEF for GHI</b>: In the next 2 months, ... </li> 214 </ul> 215 </p> 216 ]]> 217 </hp:htmlText> 218 <hp:next rdf:resource="http://some_namespace#MinorResearch"/> 219 </hp:Interest> 220 </hp:hasInterest> 221 <hp:hasInterest> 222 <hp:Interest rdf:about="http://some_namespace#MinorResearch" 223 rdfs:label="Minor Research Questions"> 224 <hp:section rdf:resource="http://some_namespace#MyContribution"/> <!-- same section!!! --> 225 <hp:htmlText> 226 <![CDATA[ 227 <p align="justify"> 228 228 I'm also interested in 229 <ol>230 <li>JKL, and</li>231 <li>MNO</li>232 </ol>233 </p>234 ]] >235 </hp:htmlText>236 <hp:next rdf:resource="http://some_namespace#ResearchApplication1"/>237 </hp:Interest>238 </hp:hasInterest>229 <ol> 230 <li>JKL, and</li> 231 <li>MNO</li> 232 </ol> 233 </p> 234 ]]> 235 </hp:htmlText> 236 <hp:next rdf:resource="http://some_namespace#ResearchApplication1"/> 237 </hp:Interest> 238 </hp:hasInterest> 239 239 240 <hp:hasInterest>241 <hp:Interest rdf:about="http://some_namespace#ResearchApplication1"242 rdfs:label= "Research Application (1)">243 <hp:section>244 <hp:Section rdf:about="http://some_namespace#ResearchApplication"245 hp:htmlText= "Research I Apply"/>246 </hp:section>247 <hp:htmlText>248 <![CDATA[249 <p align="justify">240 <hp:hasInterest> 241 <hp:Interest rdf:about="http://some_namespace#ResearchApplication1" 242 rdfs:label="Research Application (1)"> 243 <hp:section> 244 <hp:Section rdf:about="http://some_namespace#ResearchApplication" 245 hp:htmlText="Research I Apply"/> 246 </hp:section> 247 <hp:htmlText> 248 <![CDATA[ 249 <p align="justify"> 250 250 I'm heavily allying and relying of the following research areas: 251 <ul>252 <li><b>XXX</b>: nobody can't without... </li>253 <li><b>XYY</b>: also very important, because... </li>254 <li><b>XYZ</b>: very interesting, but not yet really applicable... </li>255 </ul>256 </p>257 ]] >258 </hp:htmlText>259 <!-- no hp:next -->260 </hp:Interest>261 </hp:hasInterest>251 <ul> 252 <li><b>XXX</b>: nobody can't without... </li> 253 <li><b>XYY</b>: also very important, because... </li> 254 <li><b>XYZ</b>: very interesting, but not yet really applicable... </li> 255 </ul> 256 </p> 257 ]]> 258 </hp:htmlText> 259 <!-- no hp:next --> 260 </hp:Interest> 261 </hp:hasInterest> 262 262 }}} 263 263 We see several things here: … … 270 270 === nice URLs via htaccess === 271 271 272 This paragraph is about having "nice"URLs, i.e., we want to allow the following TWO possible versions to access rdfhomepage pages:[[BR]]272 This paragraph is about having "nice" URLs, i.e., we want to allow the following TWO possible versions to access rdfhomepage pages:[[BR]] 273 273 {{{old version:}}} http://www.dfki.uni-kl.de/~schwarz/index.php?page=projects [[BR]] 274 274 {{{new version:}}} http://www.dfki.uni-kl.de/~schwarz/projects … … 277 277 278 278 Then for each page you have in rdfhomepage, you have to 279 1. Edit the .htaccess file and add one mappings there. For each index.php?page=xxx, you will have an entry in .htaccess for xxx. Example for pages "projects" and "interests":280 {{{ 281 <Files projects> 279 1. Edit the .htaccess file and add one mappings there. For each index.php?page=xxx, you will have an entry in .htaccess for xxx. Example for pages "projects" and "interests": 280 {{{ 281 <Files projects> 282 282 ForceType application/x-httpd-php 283 </Files> 284 <Files interests> 283 </Files> 284 <Files interests> 285 285 ForceType application/x-httpd-php 286 </Files> 287 }}} 288 2. Create a symbolic link to index.php with the name of the page. Following the example with the "projects"page, you have to execute (unix/linux)286 </Files> 287 }}} 288 2. Create a symbolic link to index.php with the name of the page. Following the example with the "projects" page, you have to execute (unix/linux) 289 289 {{{ 290 290 ln -s index.php projects … … 304 304 In that CSS file you would include the homepage.css of the rdfhomepage package. Example: 305 305 {{{ 306 @import url( "rdfhomepage/homepage.css");306 @import url("rdfhomepage/homepage.css"); 307 307 308 308 a { … … 320 320 * template.css defines the layout for the multi-column layout. [[BR]] 321 321 * color_and_font.css defines the colors and fonts to be used. 322 * homepage.css defines ordering and spacing of the <div>s.322 * homepage.css defines ordering and spacing of the <div>s. 323 323 324 324 If you just like to override the coloring or some fonts, then you could create an own {{{homepage.css}}} in your myrdfhomepage directory containing 325 325 {{{ 326 @import url( "rdfhomepage/homepage.css");327 @import url( "color_and_font.css"); // <--- private color_and_font.css326 @import url("rdfhomepage/homepage.css"); 327 @import url("color_and_font.css"); // <--- private color_and_font.css 328 328 329 329 a { … … 333 333 Then you can also create an own {{{color_and_font.css}}} in that directory containing 334 334 {{{ 335 @import url( "rdfhomepage/color_and_font.css");335 @import url("rdfhomepage/color_and_font.css"); 336 336 337 337 a.menuItem:hover { … … 345 345 Note, that for the examples above it is assumed, that the rdfhomepage package can be found directly inside your myrdfhomepage directory. If you put the rdfhomepage package to let's say {{{/home/share/rdfhomepage}}} to share the rdfhomepage core, then the import statements have to be modified in the code above, i.e., changed to 346 346 {{{ 347 @import url( "/home/share/rdfhomepage/homepage.css");347 @import url("/home/share/rdfhomepage/homepage.css"); 348 348 . . . 349 @import url( "/home/share/rdfhomepage/color_and_font.css");349 @import url("/home/share/rdfhomepage/color_and_font.css"); 350 350 . . . 351 }}} 954633916463351 }}}
