We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DPLA MAP doesn't seem very clear about the differentiation between edm:hasType and dcterms:type:
dcterms:type (under heading "type")
Nature or genre of described resource.
edm:hasType (under heading "genre")
Captures categories of described resource in a given field. Does not capture aboutness.
I would propose to use only edm:hasType and rdf:type.
The text was updated successfully, but these errors were encountered:
@azaroth42 DPLA MAP intends dcterms:type to be used only with values for from the DCMI types vocabulary.
dcterms:type
Sorry, something went wrong.
EDM defines the following hierarchy:
edm:type rdfs:subPropertyOf dc:type . dc:type rdfs:subPropertyOf edm:hasType . dc:language rdfs:subPropertyOf edm:hasType . dc:format rdfs:subPropertyOf edm:hasType .
So edm:hasType may end up aggregating a bunch of "types" of different nature, eg
"IMAGE", aat:painting, "image/jpeg", aat:English
(Assuming that AAT concepts are used. Substitute the respective 300xxxx number)
No branches or pull requests
DPLA MAP doesn't seem very clear about the differentiation between edm:hasType and dcterms:type:
dcterms:type (under heading "type")
edm:hasType (under heading "genre")
I would propose to use only edm:hasType and rdf:type.
The text was updated successfully, but these errors were encountered: