Can't import new vocabulary

[thanakorn]

I import new vocabulary (ver. 3.0.1)

Label: EXIF

Namespace URI: http://www.w3.org/2003/12/exif/ns
Namespace prefix: exif_
Vocabulary URL: http://www.w3.org/2003/12/exif/ns

The result :

No classes or properties found. Are you sure you used the correct namespace URI?

(I test in Sandbox … it’s OK)

how to fix this, help me please…

[jimsafley]

I can import the vocabulary using the following:

Label: Exif
Namespace URI: https://www.w3.org/2003/12/exif/ns
Namespace prefix: exif
Vocabulary URL: https://www.w3.org/2003/12/exif/ns
File format: [Autodetect]

The label and ns prefix can be anything you want. Perhaps you’re not selecting [Autodetect]?

[jimsafley]

I’m sorry, I meant to write the following:

Namespace URI: http://www.w3.org/2003/12/exif/ns
Vocabulary URL: http://www.w3.org/2003/12/exif/ns

Note that you should use http: not https:

[thanakorn]

Thank you for your kindness ^^

1. Autodetect Selected and I use http:

2. I try to import other vocabulary from https://lov.linkeddata.es/dataset/lov/vocabs
   example:
   The RDF Schema vocabulary (rdfs)
   http://www.w3.org/2000/01/rdf-schema#

The results remain the same.

No classes or properties found. Are you sure you used the correct namespace URI?

[jimsafley]

I can confirm that that these should work:

Exif
Namespace URI: http://www.w3.org/2003/12/exif/ns
Vocabulary URL: http://www.w3.org/2003/12/exif/ns
File format: [Autodetect]

RDFS
Namespace URI: http://www.w3.org/2000/01/rdf-schema#
Vocabulary URL: https://www.w3.org/2000/01/rdf-schema#
File format: [Autodetect]

There are two ways you could be getting the “No classes or properties found” error. First, the Vocabulary URL successfully resolves but is not a RDF file. Second, the Namespace URI differs from the one that’s defined in the RDF file. I can think of no other reason why Omeka would raise that error.