Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

replace start and end date of a FIP - include instead FIP status #2

Open
mabablue opened this issue Nov 9, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@mabablue
Copy link
Contributor

mabablue commented Nov 9, 2024

In the metadata chapter of the FIP Questionnaire start and end dates for the FIP is asked. For many the end date at least is a difficult question to answer.

What about adding a FIP status instead with these possible values:

  • in preparation (still not completely finalized, but already published as a nanopub)
  • in review (in review by the community)
  • approved (by the community)

When a FIP is published as a nanopub we have a timestamp for the creation time and we know which status the FIP had at this time.

There are multiple implications to consider:

  • when we create a FIP matrix do we need to filter per year? would this still be possible without a start date? Or should we keep the start date and add the status?
  • how easy is it to include the publication date in a SPARQL query so that we can make use of it when filtering?
  • we might want to discuss about the maturity of a FIP and how long it will persist (but I personally think that a FIP should evolve over time anyway)
  • a FIP status is not the same as a FAIR Implementation Community status (which can be developing, emerging or mature)

Can you please contribute with your thoughts on this possible improvement?

@mabablue mabablue added the enhancement New feature or request label Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant