jobdataexchange / Data-Modeling

This repo is intended to contain resources and discussion regarding the JDX data modeling.
Other
8 stars 6 forks source link

Determining which entities are merely referenced vs being described via the JDX model #1

Closed stuartasutton closed 5 years ago

stuartasutton commented 5 years ago

@matthewgee, @jkitchensSIUC

On Wed, Jul 18, 2018 at 5:11 AM Matt Gee mattgee@gmail.com wrote:

This is really helpful Bob. I think the employer-organization extension makes an enormous amount of sense.

One other piece of the standardization work that I’m curious about: since part of the job registry draft architecture is allowing employers, through their ATS and HRIS vendors, to “push to” or publish to their talent sourcing partners (education and training organizations), can we use an existing data standard or catalogue of educational organizations, or will we need to augment an existing standard to be able to enumerate and provide HRIS links to talent sourcing partners for job description distribution?

We need to distinguish between whether entities in the JDX domain model (e.g., job description, job posting) need to be able to reference descriptions of organizations (of different types) where ever located on the Web or whether our intention is to actually maintain such descriptions within the JDX itself. Big difference. If it's the former (reference) then all we need is a list of classes (e.g., schema.org/Organization, ceterms:CredentialOrganization etc. etc.). If it's the latter, then we need to determine if there is a satisfactory public schema to use and whether it needs extension etc. to meet use cases. So, are we talking about referencing or storing (maintaining).