W3C home > Mailing lists > Public > public-lod@w3.org > September 2009

RE: Project idea: cviki (or some better name than that)

From: John Flynn <jflynn@bbn.com>
Date: Wed, 2 Sep 2009 08:19:24 -0400
To: "'Toby Inkster'" <tai@g5n.co.uk>, "'Semantic Web'" <semantic-web@w3.org>, <public-lod@w3.org>
Cc: "'John Flynn'" <jflynn@bbn.com>
Message-ID: <000601ca2bc7$9bece3c0$d3c6ab40$@com>
You might want to consider using the HR-XML Consortium's XML schemas (1) as
a starting point for the templates. 

(1)
http://www.hrxmlconsortium.org/hr-xml/wms/hr-xml-1-org/index.php?id={E00DA03
B685A0DD18FB6A08AF0923DE0|139|2} 

-----Original Message-----
From: semantic-web-request@w3.org [mailto:semantic-web-request@w3.org] On
Behalf Of Toby Inkster
Sent: Wednesday, September 02, 2009 1:34 AM
To: Semantic Web; public-lod@w3.org community
Subject: Project idea: cviki (or some better name than that)

I think this is a great idea for a project, but I don't have time to  
do it myself...

1. Set up a wiki (pref MediaWiki) for people to publish their CVs/ 
Resumés. This might need slightly different access restrictions than  
normal MediaWiki installations to prevent people from negatively  
editing others' CVs.

2. The site would provide a bunch of MediaWiki "templates" which  
would expose the CV data as XHTML+RDFa using the FOAF and DOAC vocabs  
primarily.

3. The site would provide a conformance checking tool for CV authors,  
using RDFS and OWL reasoning, and perhaps in-built knowledge of FOAF  
and DOAC, to look at individual CVs and check them for  
contradictions. (e.g. range/domain conflicts.)

4. The site would provide a "dictionary" of skills, each with a URI,  
for more standardised markup of a person's skillset.

5. A bot would monitor the "recent changes" RSS feed (is this valid  
RSS 1.0 - i.e. RDF? If not, it could maybe be fixed.) finding CVs  
which had recently been changed. Each of these would be parsed as  
RDFa and entered into a big, communal triple store (using the URL of  
the CV page as a graph name for easy maintenance).

6. A SPARQL endpoint would be exposed for the big triple store.

7. People could write various human-friendly forms as a wrapper for  
the SPARQL endpoint. The cviki community would vote on the best of  
these, and the winner would be placed on the Wiki front page.

-- 
Toby A Inkster
<mailto:mail@tobyinkster.co.uk>
<http://tobyinkster.co.uk>
Received on Wednesday, 2 September 2009 12:19:51 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 31 March 2013 14:24:23 UTC