- From: Colin <colin@zebrana.net>
- Date: Tue, 2 Apr 2013 20:05:02 +0200
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>, public-lod <public-lod@w3.org>
- Message-ID: <CAKGUnveF-6qdo2Xotx1ZAtdPQhVLMV68KMxHzQCx6XeO+StSHw@mail.gmail.com>
Hello Stian, Very interesting. I am currently trying to model the documentation objects and properties of my client, and this vocabulary could come handy (I need to read it more in depth). So far I have made an extensive use of the classes and predicates described by the Nepomuk Information Element<http://www.semanticdesktop.org/ontologies/nie/>(nie:) and Nepomuk File Ontology <http://www.semanticdesktop.org/ontologies/nie/> (nfo). Your ontology would probably integrate well, especially for the versioning part. So... thanks! Colin PS: I'm currently working on an Apache Ant script (you double click on a .bat or .sh file) that automates the creation of the different elements that compose a decent kit to publish an ontology (RDF/XML, .htaccess, HTML+RDFa with BootStrap CSS) from a Turtle source (though it could also be RDF/XML), and upload (FTP) it all to the server of your choice. I'll let you know when a beta version is ready, if you want. On Tue, Apr 2, 2013 at 7:32 PM, Kingsley Idehen <kidehen@openlinksw.com>wrote: > On 4/2/13 1:31 PM, Stian Soiland-Reyes wrote: > > As we've gone lightweight with svn hosting on google-code (to avoid > dependence on a server we probably would forget to maintain), we can't do > content negotiation. Sadly purl.org has np content negotiation, which > would have been very helpful here. > > I went with application/xml as a compromise so that I could keep the owl > in rdf/xml, but could add an xslt stylesheet to give browsers something to > display rather than an opaque xml file. (people click those links!). > Browsers should of course recognize +xml, but I don't remember if any of > them did. > > I am open for suggestions though, perhaps an alternative purl which end up > on say pav.owl.rdf with the correct content type? Perhaps the version IRIs > could go there? > > > Why aren't you serving the RDF/XML using Content-Type: application/rdf+xml > ? > > Kingsley > > On Apr 2, 2013 6:05 PM, "Kingsley Idehen" <kidehen@openlinksw.com> wrote: > >> On 4/2/13 12:50 PM, Stian Soiland-Reyes wrote: >> >>> We *) are pleased to announce the release of the PAV (Provenance, >>> Authoring and Versioning) ontology v2.1. >>> >>> http://purl.org/pav/2.1 >>> >> >> Congrats! >> >> BTW -- wondering if you could fix the "Content-Type:" value returned the >> server? It currently returns: >> >> curl -I http://pav-ontology.googlecode.com/svn/tags/2.1.1/pav.owl >> HTTP/1.1 200 OK >> Date: Tue, 02 Apr 2013 16:58:53 GMT >> Server: Apache >> Last-Modified: Tue, 26 Mar 2013 16:12:15 GMT >> ETag: "162//tags/2.1.1/pav.owl" >> Accept-Ranges: bytes >> Expires: Tue, 02 Apr 2013 17:01:53 GMT >> Content-Length: 32172 >> Content-Type: application/xml >> Age: 88 >> Cache-Control: public, max-age=180 >> >> >> -- >> >> Regards, >> >> Kingsley Idehen >> Founder & CEO >> OpenLink Software >> Company Web: http://www.openlinksw.com >> Personal Weblog: http://www.openlinksw.com/blog/~kidehen >> Twitter/Identi.ca handle: @kidehen >> Google+ Profile: https://plus.google.com/112399767740508618350/about >> LinkedIn Profile: http://www.linkedin.com/in/kidehen >> >> >> >> >> >> > > -- > > Regards, > > Kingsley Idehen > Founder & CEO > OpenLink Software > Company Web: http://www.openlinksw.com > Personal Weblog: http://www.openlinksw.com/blog/~kidehen > Twitter/Identi.ca handle: @kidehen > Google+ Profile: https://plus.google.com/112399767740508618350/about > LinkedIn Profile: http://www.linkedin.com/in/kidehen > > > >
Received on Tuesday, 2 April 2013 18:06:03 UTC