Open jorge-cardoso opened 12 years ago
This could be useful since dc is used a lot for service descriptions. As far as I understand, only the dc:type property refers to dc:type?
If we do this, a lot of relations are inherited. I don't understand all consequences.
I did not follow your question: "As far as I understand, only the dc:type property refers to dc:type?"
Looking at the definition I am not clear that DC's understanding of Service is like ours. Notably they consider this a system. Additionally, a quick look up on the usage of this term out there it doesn't seem to be very used so we don't seem to loose much in terms of compatibility or data import: http://stats.lod2.eu/rdf_classes?search=http%3A%2F%2Fpurl.org%2Fdc%2Fdcmitype%2FService
Does it make sense to make the class Service a type of URI: http://purl.org/dc/dcmitype/Service?
Label: Service Definition: A system that provides one or more functions. Comment: Examples include a photocopying service, a banking service, an authentication service, interlibrary loans, a Z39.50 or Web server.