Changes between Version 24 and Version 25 of InstallationInstructions
- Timestamp:
- 11/30/06 00:55:27 (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InstallationInstructions
v24 v25 1 1 2 == Short installation overview == 2 3 … … 15 16 16 17 Well, and you MUST have several RDF files for rdfhomepage to work: 17 * a FOAF file specifying yourself and your "friends"and colleagues18 * a FOAF file specifying yourself and your "friends" and colleagues 18 19 * a bibtex files, that is, the text version PLUS the RDF version(!) of your publications 19 20 * an organizational model, that is, your organizational properties and relations (your projects, department(s), roles...) … … 31 32 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: 32 33 33 * Resources to be referenced from outside the RDF file need a URI = >Your foaf:Person needs a URI.34 * 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="...".35 * 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".34 * Resources to be referenced from outside the RDF file need a URI => Your foaf:Person needs a URI. 35 * 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="...". 36 * 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". 36 37 * 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. 37 38 … … 39 40 {{{ 40 41 // The location of your FOAF file on the web (This is also the data source) 41 $MY_FOAF_FILE_URL = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml";42 $MY_FOAF_FILE_URL = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml"; 42 43 43 44 // Your URI in your FOAF file - Look this one up! 44 $MY_FOAF_URI = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me";45 $MY_FOAF_URI = "http://www.dfki.uni-kl.de/~schwarz/foaf.xml#me"; 45 46 }}} 46 47 … … 61 62 At the END of the bibtex-file there is a rdf:Seq like this 62 63 {{{ 63 <rdf:Seq rdf:about="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList">64 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz05"/>65 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz06"/>66 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#GrimnesSchwarzSauermann06"/>64 <rdf:Seq rdf:about="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList"> 65 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz05"/> 66 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#Schwarz06"/> 67 <rdf:li rdf:resource="http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#GrimnesSchwarzSauermann06"/> 67 68 . . . 68 </rdf:Seq>69 </rdf:Seq> 69 70 }}} 70 71 … … 72 73 {{{ 73 74 // The name (not path) of your bibtex.rdf 74 define( "BIBTEX_FILE_NAME", "bib_ss.rdf");75 define("BIBTEX_FILE_NAME", "bib_ss.rdf"); 75 76 76 77 // The URL of your BibTeX file. (real BibTeX format, not RDF!) 77 $MY_BIB_TEX_URL = "http://www.dfki.uni-kl.de/~schwarz/ss.bib";78 $MY_BIB_TEX_URL = "http://www.dfki.uni-kl.de/~schwarz/ss.bib"; 78 79 79 80 // The URI of a sequence of all the articles in your bibtex file 80 $MY_BIB_TEX_SEQ_URI = "http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList";81 $MY_BIB_TEX_SEQ_URI = "http://www.dfki.uni-kl.de/~schwarz/rdf/ss_bib.rdf#referenceList"; 81 82 }}} 82 83 … … 86 87 87 88 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. 88 You may have a look at our !OrgRep - > see {{{{rdfhomepage/vocabulary/OrgRepDFKI.*}}} ->best viewed with [http://protege.stanford.edu/ Protege], http://protege.stanford.edu/89 You may have a look at our !OrgRep -> see {{{{rdfhomepage/vocabulary/OrgRepDFKI.*}}} -> best viewed with [http://protege.stanford.edu/ Protege], http://protege.stanford.edu/ 89 90 90 91 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]] 91 92 I advise you take the following steps: 92 93 1. Open {{{OrgRep.pprj}}} with Protege 93 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#).94 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#). 94 95 3. Open it again (with Protege) and add your people, projects, etc. therein. 95 4. There are some inverse properties, which may need manual care, e.g. between org:Project <-->org:Person96 4. There are some inverse properties, which may need manual care, e.g. between org:Project <--> org:Person 96 97 97 98 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. … … 101 102 // Your URI in the OrgRep ontology 102 103 // If in doubt, look it up in the OrgRep RDF File or ask somebody! 103 $MY_ORGREP_URI = "http://km.dfki.de/model/org#OrganisationalModel_00077";104 $MY_ORGREP_URI = "http://km.dfki.de/model/org#OrganisationalModel_00077"; 104 105 }}} 105 106 … … 117 118 // as it can be found in the rdfhomepage.rdf file. 118 119 // You may commit to the default URI scheme, which is like 119 // http://www.dfki.uni-kl.de/~schwarz <-- note: no trailing slash!!!120 // http://www.dfki.uni-kl.de/~schwarz <-- note: no trailing slash!!! 120 121 // or change this value 121 $MY_HOMEPAGE_URI= "http://www.dfki.uni-kl.de/~schwarz";122 $MY_HOMEPAGE_URI= "http://www.dfki.uni-kl.de/~schwarz"; 122 123 }}} 123 124 124 125 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... ;) 125 126 {{{ 126 <hp:bibtexName>Sven Schwarz</hp:bibtexName>127 <hp:bibtexName>Sven Schwarz</hp:bibtexName> 127 128 }}} 128 129 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! … … 133 134 There could be a chunk containing short information about yourself: 134 135 {{{ 135 <hp:shortBio>136 <![CDATA[137 <p align="justify">136 <hp:shortBio> 137 <![CDATA[ 138 <p align="justify"> 138 139 My name is Bob. I am a researcher aiming at... 139 </p>140 <p align="justify">140 </p> 141 <p align="justify"> 141 142 I like tennis and swimming... 142 </p>143 ]] >144 </hp:shortBio>143 </p> 144 ]]> 145 </hp:shortBio> 145 146 }}} 146 147 … … 149 150 Most probably, there will be one or more chunks about projects you work for: 150 151 {{{ 151 <hp:inProject>152 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0815">153 <hp:htmlText>154 <![CDATA[155 <p align="justify">156 This is one of two projects I work for. <br/>152 <hp:inProject> 153 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0815"> 154 <hp:htmlText> 155 <![CDATA[ 156 <p align="justify"> 157 This is one of two projects I work for.<br/> 157 158 I took talk hours about this project... 158 </p>159 ]] >160 </hp:htmlText>161 <hp:next rdf:resource="http://orgrep_namespace#OrgRep_0816"/>162 </hp:Project>163 </hp:inProject>164 165 <hp:inProject>166 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0816">167 <hp:htmlText>168 <![CDATA[169 <p align="justify">159 </p> 160 ]]> 161 </hp:htmlText> 162 <hp:next rdf:resource="http://orgrep_namespace#OrgRep_0816"/> 163 </hp:Project> 164 </hp:inProject> 165 166 <hp:inProject> 167 <hp:Project rdf:about="http://orgrep_namespace#OrgRep_0816"> 168 <hp:htmlText> 169 <![CDATA[ 170 <p align="justify"> 170 171 And this is the second of the two projects I work for. 171 </p>172 ]] >173 </hp:htmlText>174 <!-- no next project -->175 </hp:Project>176 </hp:inProject>172 </p> 173 ]]> 174 </hp:htmlText> 175 <!-- no next project --> 176 </hp:Project> 177 </hp:inProject> 177 178 }}} 178 179 We see several things here: … … 187 188 188 189 There can be one or more chunks about your (research) interest. 189 As "interests" are quite manifold, each interest belongs to (exactly!) one "section".190 I personally distinguish between "research contributions" and "research applications"(however, you do not have to do so as well):191 {{{ 192 <hp:hasInterest>193 <hp:Interest rdf:about="http://some_namespace#MayorResearch"194 rdfs:label= "Mayor Research Questions">195 <hp:section>196 <hp:Section rdf:about="http://some_namespace#MyContribution"197 hp:htmlText= "My Contribution to Research"/>198 </hp:section>199 <hp:htmlText>200 <![CDATA[201 <p align="justify">190 As "interests" are quite manifold, each interest belongs to (exactly!) one "section". 191 I personally distinguish between "research contributions" and "research applications" (however, you do not have to do so as well): 192 {{{ 193 <hp:hasInterest> 194 <hp:Interest rdf:about="http://some_namespace#MayorResearch" 195 rdfs:label="Mayor Research Questions"> 196 <hp:section> 197 <hp:Section rdf:about="http://some_namespace#MyContribution" 198 hp:htmlText="My Contribution to Research"/> 199 </hp:section> 200 <hp:htmlText> 201 <![CDATA[ 202 <p align="justify"> 202 203 My mayor research questions: 203 <ul>204 <li><b>research in ABC</b>: ABC is my personal dream... </li>205 <li><b>DEF for GHI</b>: In the next 2 months, ... </li>206 </ul>207 </p>208 ]] >209 </hp:htmlText>210 <hp:next rdf:resource="http://some_namespace#MinorResearch"/>211 </hp:Interest>212 </hp:hasInterest>213 <hp:hasInterest>214 <hp:Interest rdf:about="http://some_namespace#MinorResearch"215 rdfs:label= "Minor Research Questions">216 <hp:section rdf:resource="http://some_namespace#MyContribution"/> <!-- same section!!! -->217 <hp:htmlText>218 <![CDATA[219 <p align="justify">204 <ul> 205 <li><b>research in ABC</b>: ABC is my personal dream... </li> 206 <li><b>DEF for GHI</b>: In the next 2 months, ... </li> 207 </ul> 208 </p> 209 ]]> 210 </hp:htmlText> 211 <hp:next rdf:resource="http://some_namespace#MinorResearch"/> 212 </hp:Interest> 213 </hp:hasInterest> 214 <hp:hasInterest> 215 <hp:Interest rdf:about="http://some_namespace#MinorResearch" 216 rdfs:label="Minor Research Questions"> 217 <hp:section rdf:resource="http://some_namespace#MyContribution"/> <!-- same section!!! --> 218 <hp:htmlText> 219 <![CDATA[ 220 <p align="justify"> 220 221 I'm also interested in 221 <ol>222 <li>JKL, and</li>223 <li>MNO</li>224 </ol>225 </p>226 ]] >227 </hp:htmlText>228 <hp:next rdf:resource="http://some_namespace#ResearchApplication1"/>229 </hp:Interest>230 </hp:hasInterest>222 <ol> 223 <li>JKL, and</li> 224 <li>MNO</li> 225 </ol> 226 </p> 227 ]]> 228 </hp:htmlText> 229 <hp:next rdf:resource="http://some_namespace#ResearchApplication1"/> 230 </hp:Interest> 231 </hp:hasInterest> 231 232 232 <hp:hasInterest>233 <hp:Interest rdf:about="http://some_namespace#ResearchApplication1"234 rdfs:label= "Research Application (1)">235 <hp:section>236 <hp:Section rdf:about="http://some_namespace#ResearchApplication"237 hp:htmlText= "Research I Apply"/>238 </hp:section>239 <hp:htmlText>240 <![CDATA[241 <p align="justify">233 <hp:hasInterest> 234 <hp:Interest rdf:about="http://some_namespace#ResearchApplication1" 235 rdfs:label="Research Application (1)"> 236 <hp:section> 237 <hp:Section rdf:about="http://some_namespace#ResearchApplication" 238 hp:htmlText="Research I Apply"/> 239 </hp:section> 240 <hp:htmlText> 241 <![CDATA[ 242 <p align="justify"> 242 243 I'm heavily allying and relying of the following research areas: 243 <ul>244 <li><b>XXX</b>: nobody can't without... </li>245 <li><b>XYY</b>: also very important, because... </li>246 <li><b>XYZ</b>: very interesting, but not yet really applicable... </li>247 </ul>248 </p>249 ]] >250 </hp:htmlText>251 <!-- no hp:next -->252 </hp:Interest>253 </hp:hasInterest>244 <ul> 245 <li><b>XXX</b>: nobody can't without... </li> 246 <li><b>XYY</b>: also very important, because... </li> 247 <li><b>XYZ</b>: very interesting, but not yet really applicable... </li> 248 </ul> 249 </p> 250 ]]> 251 </hp:htmlText> 252 <!-- no hp:next --> 253 </hp:Interest> 254 </hp:hasInterest> 254 255 }}} 255 256 We see several things here: … … 262 263 === nice URLs via htaccess === 263 264 264 This paragraph is about having "nice"URLs, i.e., we want to allow the following TWO possible versions to access rdfhomepage pages:[[BR]]265 This paragraph is about having "nice" URLs, i.e., we want to allow the following TWO possible versions to access rdfhomepage pages:[[BR]] 265 266 {{{old version:}}} http://www.dfki.uni-kl.de/~schwarz/index.php?page=projects [[BR]] 266 267 {{{new version:}}} http://www.dfki.uni-kl.de/~schwarz/projects … … 269 270 270 271 Then for each page you have in rdfhomepage, you have to 271 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":272 {{{ 273 <Files projects> 272 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": 273 {{{ 274 <Files projects> 274 275 ForceType application/x-httpd-php 275 </Files> 276 <Files interests> 276 </Files> 277 <Files interests> 277 278 ForceType application/x-httpd-php 278 </Files> 279 }}} 280 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)279 </Files> 280 }}} 281 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) 281 282 {{{ 282 283 ln -s index.php projects … … 296 297 In that CSS file you would include the homepage.css of the rdfhomepage package. Example: 297 298 {{{ 298 @import url( "rdfhomepage/homepage.css");299 @import url("rdfhomepage/homepage.css"); 299 300 300 301 a { … … 312 313 * template.css defines the layout for the multi-column layout. [[BR]] 313 314 * color_and_font.css defines the colors and fonts to be used. 314 * homepage.css defines ordering and spacing of the <div>s.315 * homepage.css defines ordering and spacing of the <div>s. 315 316 316 317 If you just like to override the coloring or some fonts, then you could create an own {{{homepage.css}}} in your myrdfhomepage directory containing 317 318 {{{ 318 @import url( "rdfhomepage/homepage.css");319 @import url( "color_and_font.css"); // <--- private color_and_font.css319 @import url("rdfhomepage/homepage.css"); 320 @import url("color_and_font.css"); // <--- private color_and_font.css 320 321 321 322 a { … … 325 326 Then you can also create an own {{{color_and_font.css}}} in that directory containing 326 327 {{{ 327 @import url( "rdfhomepage/color_and_font.css");328 @import url("rdfhomepage/color_and_font.css"); 328 329 329 330 a.menuItem:hover { … … 337 338 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 338 339 {{{ 339 @import url( "/home/share/rdfhomepage/homepage.css");340 @import url("/home/share/rdfhomepage/homepage.css"); 340 341 . . . 341 @import url( "/home/share/rdfhomepage/color_and_font.css");342 @import url("/home/share/rdfhomepage/color_and_font.css"); 342 343 . . . 343 }}} 344 }}}954633916463
