Michael Flanakin
Michael Flanakin
I like this idea. We could introduce a fictitious provider or maybe a couple different types of providers to support this. Let's just make sure the example values are natural...
FYI - We chose camel case because it's more readable and approachable for non-technical people who aren't used to lowercase names with underscores.
nit: Should we rename this to "commitment discount eligibility"?
Absolutely! This is what #315 is all about 🙂 We discussed this leading up to the preview and just weren't able to lock it down. We were in agreement that...
Isn't this covered in supporting content?
I agree the first two references are a bit confusing. The third seems more detailed but could be more explicit. I'm not following the two suggestions, however. Perhaps we should...
I would expect there to be a baseline schema from FOCUS for every customer/product to use when they support the specific schema version. I'd love to see schemas for vendor...
Should this be closed with metadata?
The "SKU" in FOCUS terminology is more than just the size/shape of a VM, as an example. So the SkuName would be something that would represent the entire SKU, which...
The problem I have is that I don't know what a "SKU" is for FOCUS. It's not clear as a provider what I should set the value to. And if...