Skip to content
New issue

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

Class vs property #35

Open
jiteshjosh8 opened this issue May 8, 2021 · 0 comments
Open

Class vs property #35

jiteshjosh8 opened this issue May 8, 2021 · 0 comments

Comments

@jiteshjosh8
Copy link

I feel that some entities should be data property instead of Class. For example : "official title of clinical trial" is a subclass of "title of clinical trial". It means when we use this ontology to define a RDF graph, we have to create an instance of this class to put value for a specific "study". So does it make sense to create a instance for such properties?
Also I can see lot of properties defined as class in this Ontology. I need to understand if I am wrong here or this is the right way to define Ontology. Interesting fact is that I don't see any "Data Property" in this Ontology.
Another example which is a class and I feel it should be "Data Property": "contact name"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant