Propose new type CreativeWork

[ljgarcia]

Internal reference

No open issue related to this PR

Description

• Creates new type CreativeWork so we can add properties needed for various types of research artifacts, e.g., training resources, software

Motivation and context

Rather than having many types/profiles repeating similar or same properties, we put them at CreativeWork level

Have these been tested?

• Not really tested but based on observations from various hackathons

What should reviewers focus on?

• see if the properties are generic enough and make sense for various types of research artifacts
• see if having named properties nextItem and previousItem works better as extending a second type ListItem. We decided for named properties to add the inverse property feature (which is not in schema.org)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New content (non-breaking change which adds new content)
• Modified content (non-breaking change which modifies existing content)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Future TO-DOs

• Once reviewed, create web page for this new type

[gtsueng]

@ljgarcia @nsjuty @PhilReedData @albangaignard

I think this proposal has to be done at schema.org, no? The schema.org/Dataset will NOT inherit from the bioschemas.org/CreativeWork, nor will existing schema.org classes, unless the goal is to change all inheritance to bioschemas.org/CreativeWork.

E.g. - current inheritance is like this:
schema.org/CreativeWork > schema.org/LearningResource > bioschemas.org/LearningResource profile

With this new proposed type happening on the bioschemas side, you would need to also recreate any downstream types that you would like them to apply to since they won't naturally inherit from the bioschemas parent.
bioschemas.org/CreativeWork > ??? > bioschemas.org/LearningResource profile

I recommend proposing these properties to schema.org. We can ask our community to provide examples of how it would be used and to support its inclusion. These are properties that can sensibly apply to many downstream types such as Dataset, SoftwareApplication, WebSite, WebPage, ScholarlyArticle, Thesis, Manuscript, Guide, in addition to the educational schemas.

[ljgarcia]

@gtsueng no need to create a new hierarchy. It would be enough for any profile/type in Bioschemas which wants to use these properties to add a second type bioschemas:CreativeWork

[ljgarcia]

By the way, moving this to draft as it will be influenced by other research artifacts developed in other groups, e.g., software metadata and AI models metadata.

One of the possibly conflicting properties is applicationDomain, called researchDomain in other efforts.

[gtsueng]

schemaorg/schemaorg#4841 (comment)