Create a data model in Omeka-S

[Franck Dupont]

Hi there,

I must add a data model for my project : I want to add specific (non DC, Bibo or FOAF) input fields in the admin form.

I wonder how I should do that.

Should I add a specific (non-standardize) vocabulary ?

Thanks.

Franck.

[Jim Safley]

Hi Franck,

You'll need to import a vocabulary that includes the properties you want. We highly recommend that you use an existing vocabulary---there are many from a wide range of domains. Some are hosted at the Open Knowledge Foundation: http://lov.okfn.org/dataset/lov/.

However, we recognize that a few users work in an underrepresented domain and need to create their own. We haven't written documentation about this yet, but you can find examples of the RDF vocabulary syntax online. Some of the more technical resources are W3C's "RDF Schema 1.1" https://www.w3.org/TR/rdf-schema/ and "Best Practice Recipes for Publishing RDF Vocabularies" https://www.w3.org/TR/swbp-vocab-pub/. You can find the RDF/XML files that we use to import the default vocabularies at omeka-s/data/vocabularies/.

Jim

[Franck]

Hi Jim,

Thanks for your reply.

I intend to use existants vocabs to the extent possible, and complete with new properties for specific values.

My actual problem is that I'm unable to create classes within my new vocabulary.

For example, if I delete the FOAF vocab from Omeka-S and use /data/vocabularies/foaf.rdf to recreate it, it doesn't work : the vocab is added but with 0 classe and 0 property (see attachment).

I tried to add other vocabs, but every time the vocab is added whitout classes & properties.

An idea ?

Thanks.

Franck.

--
You received this message because you are subscribed to the Google Groups "Omeka Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omeka-dev+...@googlegroups.com.
To post to this group, send email to omek...@googlegroups.com.
Visit this group at https://groups.google.com/group/omeka-dev.
For more options, visit https://groups.google.com/d/optout.

[John Flatness]

I believe the specific issue with your FOAF attempt is that the actual namespace URI for FOAF is http://xmlns.com/foaf/0.1/ whereas you provided the URI to the spec document.

The importer needs to receive the exact correct namespace URI, because it uses the URI to tell which properties and classes are actually "in" the vocab being imported.

The same issue could be to blame for your problems when attempting to use other vocabs as well.

-John

[Franck Dupont]

The FOAF URI was the problem, thanks. It's because the browser redirect from http://xmlns.com/foaf/0.1/ to the specs :/

So, if I want to add my own vocabulary (to complete existants), I must write a .rdf file (based on the /data/vocabularies files), but how do I proceed for the namespace ?

Franck.

[Jim Safley]

If you want to be thorough, follow the recommendations outlined in "Best Practice Recipes for Publishing RDF Vocabularies" https://www.w3.org/TR/swbp-vocab-pub/

Otherwise, the namespace can be any unique URI, preferably one under your control.

-Jim

[Patrick Murray-John]

It might be too heavy for your needs (and I haven't used it in a while), but Protege is a good tool to guide building vocabularies http://protege.stanford.edu

Patrick

[Franck]

Many thanks to Omeka team for your help. 

Indeed, Protege can be very helpfull.

Lastly, a final question: 

Is this sementic approach (with search of existants vocabs / writing new vocabs) will be the only way to modifify the data model in Omeka-S ?

[Jim Safley]

Yes, the only way to add classes and properties is to import vocabularies. We strongly encourage the use of existing vocabularies to promote interoperability with other systems and to avoid polluting the Semantic Web with informal domain models. We do offer "resource templates" in which you can clarify the extent and meaning of existing properties for your specific purpose.

-Jim