Open mrpatrickwest opened 9 years ago
Because inLanguage does not have a domain or range it can be associated with anything, such as a publication. But a publication can be translated to many different languages. A manifestation of a publication might be in a particular language, but not the publication itself.
I believe inLanguage was intended to be what we would call the manifestation of the publication, although I'm not sure they thought about it that way.
Note that CrossRef recognizes each new language version as a separate publication eligible for a distinct DOI.
John
On Thu, Sep 3, 2015 at 3:33 PM, Patrick West notifications@github.com wrote:
Because inLanguage does not have a domain or range it can be associated with anything, such as a publication. But a publication can be translated to many different languages. A manifestation of a publication might be in a particular language, but not the publication itself.
— Reply to this email directly or view it on GitHub https://github.com/tetherless-world/dco-ontology/issues/19#issuecomment-137550838 .
John S. Erickson, Ph.D. Director of Operations, The Rensselaer IDEA Deputy Director, Web Science Research Center (RPI) http://tw.rpi.edu olyerickson@gmail.com Twitter & Skype: olyerickson
Looks like we're using dco:inLanguage when we should be using dco:speaksLanguage. Is there a difference? inLanguage doesn't define a domain or range but we're attaching to foaf:Person. I recommend that we change it to dco:speaksLanguage for foaf:Person.