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

Decide on "object" or "component", and use throughout #186

Open
emiltin opened this issue Oct 9, 2024 · 3 comments
Open

Decide on "object" or "component", and use throughout #186

emiltin opened this issue Oct 9, 2024 · 3 comments
Labels
Milestone

Comments

@emiltin
Copy link
Contributor

emiltin commented Oct 9, 2024

Let's decide which terminlogy to use, and use it consistently.

@emiltin emiltin changed the title Device on object or component, and use throughout Decide on "object" or "component", and use throughout Oct 9, 2024
@emiltin
Copy link
Contributor Author

emiltin commented Oct 31, 2024

I think we can include this in 3.3?

@emiltin emiltin added this to the 3.3 milestone Oct 31, 2024
@marcgarba
Copy link

We could have "Component Id" for RSMP core/messages (we have "cId" JSON tag to adress the component), actually used in majority cases.

And we could perhaps keep "object" (and "object type") for abstract part (with link for signals) if wanted (SCADA, objects, type of objects, ...)

In first terms, we have the definition to understand the link :
"An object is identified using component id. Please note that an object is not necessarily the same thing as an NTS object."

Enough?

@emiltin
Copy link
Contributor Author

emiltin commented Nov 15, 2024

My suggestion was to use one or the the other throughout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants