Re: Right way to propose changes to the current schema?

I would suggest making a pull request against https://github.com/BioSchemas
and initiating the discussion (which I think you just did ;-)

Not sure which repo to edit.

Can you motivate the changes?

On 12 September 2017 at 06:14, ljgarcia <ljgarcia@ebi.ac.uk> wrote:

> Hi Dan,
>
> We would like to propose moving hasPart/isPartOf from CreativeWork to
> Thing. We would also like to propose a reverse property for isBasedOn (it
> would be isBasisFor) that would go to CreativeWork.
>
> What would be the right way to do so? Should we include a schema for Thing
> and CreativeWork including those changes? And they, if approved, would be
> later merged?
>
> Regards,
>
>