Asset manager tracks nitrogen model changes to assess impact on related apps

[graybeal]

As a...

semantic assets manager

I want to...

track changes to the model for describing the nitrogen parameter

So that...

I can tell whether my software implementing or using the model needs to be changed.

Domain(s)

Any domain, nitrogen is an example

[jonquet]

I join on that use case too.
A generalization is : being able to track change and update data annotations when ontologies and vocabularies used to annotate are evolving (concept and terms added and removed).

@graybeal Issue title does not match the template ;)

[graybeal]

@jonquet I tried to fix the title, see if it seems better.

I think your 'generalization' is actually a different use case, or even two of them.

I think the task of "updating data annotations in external apps (e.g., deprecating old ones and replacing them with new ones)" is important but mostly an external concern.

Whereas "managing changes to the model in a best practices way, that doesn't disappear any old concepts but makes it clear they are deprecated and points to any replacements" is very much a requirement. Maybe it isn't a separate use case but is a requirement driven by my use case.

Of course, all of this is a bit 'meta', it isn't exactly a use case for using nitrogen terms. But hopefully still useful.

[mabablue]

Dear @graybeal could you please check whether the assigned labels fit as use cases for your user story? Please check this table to find a better or additional use case which matches better your user story.

[graybeal]

Confirmed