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

Range of programmingLanguage: Language instead of Thing? #341

Closed
unor opened this issue Feb 17, 2015 · 3 comments
Closed

Range of programmingLanguage: Language instead of Thing? #341

unor opened this issue Feb 17, 2015 · 3 comments
Assignees
Labels
schema.org vocab General top level tag for issues on the vocabulary status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:bug A mistake or malfunction whose remedy should be straightforward technical work type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc

Comments

@unor
Copy link
Contributor

unor commented Feb 17, 2015

The programmingLanguage property currently has a range of Thing.

Its definition ("The computer programming language.") suggests that it could/should be Language instead:

Natural languages such as Spanish, Tamil, Hindi, English, etc. and programming languages such as Scheme and Lisp.

@danbri
Copy link
Contributor

danbri commented Feb 18, 2015

Thanks. Yes this could do with more care (as could 'Language' itself). We don't want to include lists of actual languages (human, computer or hybrid) as part of the schema.org core, but we should document ways of using external enumerations e.g. Wikipedia/Wikidata and it might make sense to break out subtypes of Language.

@danbri danbri added type:bug A mistake or malfunction whose remedy should be straightforward technical work schema.org vocab General top level tag for issues on the vocabulary status:needs review status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc labels Apr 17, 2015
@danbri danbri added this to the sdo-gozer release milestone Apr 17, 2015
@danbri
Copy link
Contributor

danbri commented Apr 17, 2015

While there are other issues here (Code has a problematic name, see also unrelated 'code' property), writing Language rather than Thing seems a harmless improvement. I'll do that now and close out this specific issue. Thanks again!

danbri added a commit that referenced this issue Apr 17, 2015
@danbri danbri self-assigned this Apr 17, 2015
@danbri
Copy link
Contributor

danbri commented Apr 17, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
schema.org vocab General top level tag for issues on the vocabulary status:work expected We are likely to, or would like to, or probably should try, ... to do something in this area. type:bug A mistake or malfunction whose remedy should be straightforward technical work type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc
Projects
None yet
Development

No branches or pull requests

2 participants