-
Notifications
You must be signed in to change notification settings - Fork 1
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
DM-006 Provider Identification #59
Comments
Hi Jim, Thanks, Nancy |
That does not seem to say the same thing as the current sentence. I think what you want to say is closer to: The interfaces and actions in the data model MUST include the ability to identify data published by a specific provider. I used published because I don't know if there is a better SACM verb. What I mean by it is "data collected, processed or assessed". That is data that originated with that provider as oppose to data which it received from elsewhere and relayed on. |
Hi Jim, I think it is the distinction is that when the data is provided, in that encapsulation there must be a means to specify the provider of that data.....that is what I was striving for.....I interpret the "identify data published by a specific provider" as potentially being a separate interface as well?
|
Getting back into the flow of things again. This seems to me to be better stated as an operation requirement than as a data model requirement. The query would say - only get the data from provider X. However it is not clear that I would model this as part of the data when I am doing processing on it. I would not necessary expect to keep this as part of my internal data structures. Data source is already provided as DM-0012 so that would not need to be duplicated here. I would suggest |
Hi Jim, |
Version -09
I am not sure what this statement is actually trying to say. I first read it as referring to a Data Origin source, but then realized that this could refer to a provider in the architecture sense. This should probably be clarified.
The text was updated successfully, but these errors were encountered: