[EDITORIAL] ListCost: convert normative statement into bullet points

[jpradocueva]

This PR is related to issue #606 and converts normative statements into bullet points.

[kk09v]

This change looks good, but I just wanted to note that this definition could use some review:

• ListUnitPrice is conditional on a price list being published, but ListCost is mandatory and not nullable.
  • There is no guidance for how ListCost should be calculated when ListUnitPrice is not present.
• The first reference to List Unit Price links to the glossary rather than the column.

[ijurica]

This change looks good, but I just wanted to note that this definition could use some review:

• ListUnitPrice is conditional on a price list being published, but ListCost is mandatory and not nullable.

  • There is no guidance for how ListCost should be calculated when ListUnitPrice is not present.

• The first reference to List Unit Price links to the glossary rather than the column.

Adding a couple of notes:

• Guidance for how ListCost should be calculated**

  • ListUnitPrice MUST be null when ChargeCategory is "Tax" and I'm not sure if, in case of tax, we can even describe how this should or could be calculated. (there is so much I don’t know about taxes 😃) The question is: should we rephrase this or attempt to describe it, if possible?
  • By the way, we used a similar phrase in Contracted Cost.

• Link to glossary term

  • The link to the glossary was also used in Contracted Cost. I'm not saying that it was the right decision, but it was intentional 😄. The decision was made to link the glossary term because those unit prices might not always be present.

Overall, I suggest we discuss and address this as part of #557 (copying this comment there).

[jpradocueva]

The group agreed to the work in stages. First is to convert the normative statements into bullet points and then enhance the bullet points according to #557. The PR is approved.