Add connective properties to Occupation and Job

[siuc-nate]

We have some use cases where a partner wants to connect from an Occupation and/or a Job to a Credential or set of Credentials.

Currently, the Occupation and Job classes only have the ceterms:requires property, limiting options for cases where, for example, a credential provides preparation or advanced standing (or is recommended for) a job or occupation.

We should consider adding the following properties to ceterms:Occupation and ceterms:Job:

• ceterms:recommends
• preparationFrom
• advancedStandingFrom
• isRequiredFor
• isRecommendedFor
• isAdvancedStandingFor
• isPreparationFor

[philbarker]

For Occupation, who owns these? Does any Credential Organization that wants to get to own their own version of an Occupation for which they can say that their Credentials are preparation? If so how do you link between all the different views of each real-world occupation? This seems like it would create bigger islands rather than linking data. If Occupations are owned by some Organization other than the one with the Credential they want to link to it, then that's a different problem.

In RDF/Graph terms it is enough to have the the links from Credentials to an Occupation and then query to find all the Occupations that have that link.

[siuc-nate]

Re-adding the action needed tag since @jeannekitchens wants to address this in the next release.