Re: Reusing "status" property from the health-lifesci extension

Hi Thomas,

The property https://health-lifesci.schema.org/status is planned to be
deprecated because is too broad even in health_and_life science.
It will be superseded by ```studyStatus```.
Therefore I am in favour of having your own specialized property in
legislation vocab.

See also:
https://github.com/schemaorg/schemaorg/issues/1114#issuecomment-212845014

Regards
Marc
________________________________________

On 17 October 2016 at 17:23, Thomas Francart <thomas.francart@sparna.fr>
wrote:

> Hello
>
> In the context of the ongoing proposed legal/legislation extension [1], we
> were suggested to reuse the "status" property instead of our
> "legislationLegalForce" referring to "LegalForceStatus" enumeration.
> We have nothing against the idea of using "status" instead of
> "legislationLegalForce" if we can keep the "LegalForceStatus" enumeration,
> except that *"status" is currently defined in the health-lifesci
> extension* [2]
> This raises some questions :
>
>    - What is the process for reusing terms from another extension ?
>    should they be moved to core first, before being reused ?
>    - Should I go ahead and broaden the definition of "status" and its
>    allowed range in the health-lifesci extension in my proposed pull request ?
>    or should this be done by the responsible of the health-lifesci extension ?
>    - Should I simply open a separate issue to ask to broaden the
>    definition of "status" ?
>
> My questions are really on the process/governance associated to the
> possible reuse of a property across extensions.
>
> Best regards
> Thomas
>
> [1] : https://github.com/schemaorg/schemaorg/issues/1156
> [2] : https://health-lifesci.schema.org/status
>
> --
>
> *Thomas Francart* -* SPARNA*
> Web de *données* | Architecture de l'*information* | Accès aux
> *connaissances*
> blog : blog.sparna.fr, site : sparna.fr, linkedin : fr.linkedin.com/in/
> thomasfrancart
> tel :  +33 (0)6.71.11.25.97, skype : francartthomas
>