Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Consider removing ceasn:inLanguage from ceasn:Competency #604
Since all of the properties in a competency that are language-dependent are already language strings, is it redundant to have an inLanguage property on the competency itself? This property already exists on the Framework.
It may be useful as a way of summarizing the language of all of the fields in the competency. We need to discuss it.