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

Thoughts on "Data Origin" #41

Closed
adammontville opened this issue Jul 17, 2017 · 4 comments
Closed

Thoughts on "Data Origin" #41

adammontville opened this issue Jul 17, 2017 · 4 comments
Assignees

Comments

@adammontville
Copy link
Contributor

The way our definition for data origin is written makes it seem like the origin of data is a set of endpoint attributes (while creating a synonym for endpoint attributes in "properties"). This does not feel accurate. The data origin is the SACM component that initially acquired or produced data about an endpoint. We may call that SACM component the originating SACM component. Then we an use the last sentence of the existing definition: Data Origin can be expressed by an endpoint label information element. Although, that feels more complicated than is necessary and we may instead want to say something like: Data Origin is represented by one or more endpoint attributes intended to identify the originating SACM Component.

@henkbirkholz
Copy link
Member

If there are no objections, I will include the proposed change.

@adammontville
Copy link
Contributor Author

Thanks, Henk. There is a similar circumstance for Data Source which is also written in a manner suggesting that the source is a set of endpoint attributes. Can we add that fix to this issue also?

@henkbirkholz
Copy link
Member

No objections here also.

@djhaynes
Copy link
Contributor

Both updates seem reasonable to me.

Thanks,

Danny

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants