-
Notifications
You must be signed in to change notification settings - Fork 48
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
Profile hardware - Draft Hardware Profile Submission #947
base: profile-hardware
Are you sure you want to change the base?
Conversation
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Need to move to model/Core/Vocabularies/processType.md Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Add new Relationship Types Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Improved clarity Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Improved Clarity. Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Clarity Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Fix coordinateOrientationType Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Moved to model/Core/Vocabularies/processType.md Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
move to /Core/Vocabularies/processType.md Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>
@stevenc-stb You can put this PR out of draft anytime you feel ready, so one of the maintainers can merge it. Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not marking typos, etc. in descriptions; these can be fixed later.
@@ -0,0 +1,36 @@ | |||
SPDX-License-Identifier: Community-Spec-1.0 | |||
|
|||
# Process |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very confusing.
There is a definition of Process, which is a set of tasks (not found elsewhere), and its status is a document State ?
More explanation is needed, in the text, I think.
And why is it in /Core ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FuSa and Hardware profiles in the current discussion will need the class. Where should it go if two profiles need it?
i will put the definition of Process on the to-do list for improvement .
|
||
## Description | ||
|
||
Draft, active, obsolete or other are used to define the state or status of a proceedure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems this uses "state" and "status" interchangeably. Can you standardize in one?
@@ -0,0 +1,17 @@ | |||
SPDX-License-Identifier: Community-Spec-1.0 | |||
|
|||
# typeOfProcess |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our usual naming conventions would have it as processType
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are trying to avoid having the property name and the vocabulary name having the same name.
the following has to hold: | ||
|
||
|
||
1. for every `/Hardware/Hardware` The property listed under the physical are not available if virtualFlag = true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to have different classes, VirtualHardware
and PhysicalHardware
(or whatever you want to name them) and have the corresponding properties in the corresponding classes. You may have an abstract Hardware
superclass for the common properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will discuss this issue with the HBOM group January 10. What is the main reason for your suggestion?
@@ -0,0 +1,17 @@ | |||
SPDX-License-Identifier: Community-Spec-1.0 | |||
|
|||
# informationElementList |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd usually call it simply informationElement
, not adding "List"
|
||
## Description | ||
|
||
This is the name of the OEM organization for a product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be a Relationship between a Product and an Organization ?
The description is not clear what the relationship is: is it the org that conceived, designed, manufactured, sells, buys, uses, ... the product?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the /Core/Artifact is "originatedBy" property. This is a data property.
What is the forward looking standard we should use in relation to property and relationships?
Update Definition-- please advise
Co-authored-by: Alexios Zavras (zvr) <zvr+git@zvr.gr> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Alexios Zavras (zvr) <zvr+git@zvr.gr> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Alexios Zavras (zvr) <zvr+git@zvr.gr> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have put some individual suggestions, please take a look at each of them.
All of them are just suggestions.
The Hardware Profile group may like to discuss this further and may like to put it otherwise -- happy to approve this for now so there can be something on the branch for discussion further.
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
Signed-off-by: stevenc-stb <steven@smarttalkbeacon.com>
This is the draft hardware submission. Please review and advise.