You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the terminology source requirement to preserve outdated terms but no implementation yet to support that.
If we can agree on a way to have deprecated terms be marked in the sources (either by the source administrators or by us in our queries), we can include the status in the NoT API responses, and optionally the demonstrator.
We have the terminology source requirement to preserve outdated terms but no implementation yet to support that.
If we can agree on a way to have deprecated terms be marked in the sources (either by the source administrators or by us in our queries), we can include the status in the NoT API responses, and optionally the demonstrator.
In the terminology sources
Skosmos models this case as:
@rschalkrce suggested adding:
Other/better ideas to model this?
In our GraphQL API
A proposal (where
reason
could be derived fromchangeNote
):The text was updated successfully, but these errors were encountered: