SKU Price Details

[jpradocueva]

Description

This issue was created to host the following action item:

• TF2-#497: Karl, Andrew: Draft SKU price details, ensuring they align with SKU price ID.
  Branch: sku-details_sku-price-details by Karl

Proposed approach

Describe the approach that your group is proposing

Github issue or Reference

If the topic is related to a particular work item, reference the Github issue. If its a specification-wide topic, indicate that.

Context

Add any context that may help the community think through this and provide useful feedback

[jpradocueva]

New set of action items:

• TF2-#497: Karl to incorporate the discussion points into a revised document and prepare a Pull Request (PR) by next week.
• TF2-#497: Shawn to provide notes and feedback to Karl for the PR.
  Review and approve changes to column names and issue templates in upcoming meetings.

[jpradocueva]

Action items from TF-2, Jul 17 call:

• TF2-#497 Karl to upload the structured JSON data to the shared drive.
• Members to review the shared documents and provide feedback.
• TF2-#497 Irena, Karl to continue working on collecting data from Google and other providers.

Action items from Maintainers, Jul 22 call:

• Maintainers-#497: Karl to finalize the supporting documentation for SKU details.
  Aim to reach TF consensus by August 12.

Action items from TF-2 call on July 24:

• Review and Refine SKU Price Details:
  Team members were tasked with reviewing the list of properties included in SKU price details. This includes determining what should be included and ensuring that the attributes are accurately defined and relevant to pricing data.
• Provide Examples and Mock Data:
  The team was instructed to provide more examples and mock data, using real-world scenarios where possible, to help illustrate the intended structure and content of SKU price details. This includes utilizing sanitized data samples for clarity.
• Create Guidelines for Including Data:
  Develop guidelines for what type of information should be included in SKU price details versus SKU details. This involves distinguishing between properties that should be classified under each category and establishing criteria for consistency across different cloud providers.

Action Items from TF-2 call on July 31st:

• TF2-#497 Karl to clarify the phrasing regarding the inclusion of properties in SKU details and SKU price details, allowing for flexibility based on provider decisions.
• TF2-#497 A summary of the discussions, open issues, and decisions will be added to the supporting content of the pull request.