Hi all,
Maybe that structWSF, conStruct & some extensions to conStruct developed
by the community could meet these needs. I would suggest you to take a
look at the two systems here:
http://openstructs.org/structwsf/ (structWSF)
http://constructscs.com (conStruct)
Here are some observations:
Security would be managed by structWSF (the current security is basic,
but will be extended in middle term to certificates). Otherwise, any CV
& dictionaries of skills can already be loaded within structWSF to let
the current tools being aware (and leveraging in term of inference,
display, etc) of this kind of structure.
Templates can be developed for conStruct (based on Smarty & a special
Smarty API to leverage structured data).
So, all the structured data management (and access & security) is
handled by one or multiple structWSF instance(s). Then the UI is handled
by conStruct/Drupal or anything else that you see fits.
What would be needed to be developed is anything that is not generic:
some special searches capabilities, special display stuff, etc. But all
these extensions would getany data from structWSF.
Just my two cents to this conversation. I think this is something that
can be considered for such a project.
Thanks!
Take care,
Fred
It is a great idea. But how can you handle the security issue as your
data are sensitive. Currently, I am not aware of the security
implementation for RDF and SPARQL. Glad to hear other's opinion on the
security problem of SW.
thanks
ying
Toby Inkster wrote:
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.
