-
Notifications
You must be signed in to change notification settings - Fork 811
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
billingPeriod of type Duration, but represents an Interval #2210
Comments
I agree the documentation is a little confusing here. I believe the property is there to capture [from an invoice] the standard payment terms messages such as "Payment within 30 days" . To that end I think it should be correctly defined as a Duration eg "P30D". Equally I believe validFor should for a Duration "P1Y", as different to validThrough. |
Added invoiceDate property Updated examples to reflect changes Fixes #2210
Whilst reviewing the issue, also noted the obvious omission of an invoiceDate property. |
@tmarshbing @nicolastorzec @scor @tilid any opinion on this? /cc #2648 |
The changes look good to me. @danbri , I agree with your comment on the grammar of the edit to the description. Once that is fixed, it looks good to go to me. |
The billing period for an individual invoice is an The standard terms for a set/class of invoices is typically specified in terms of a standard duration for the interval that will be associated with the individual invoice, whose individual start-time will be tied to that individual invoice. |
Bringing @dr-shorthair 's comment from the pull request in here for visibility:
|
This issue is being tagged as Stale due to inactivity. |
Are you waiting for a proposal? |
We have a similar issue; linking here to bring-into-view: #2689 (comment) |
According to the documentation fo billingPeriod, it represents a time interval, such as
2014-12-21/P30D
. However, the range of billingPeriod includes Duration, which should be of the formP[n]Y[n]M[n]DT[n]H[n]M[n]S
(such asP30D
). The value used would be a Time interval, so really, there should be a datatype Interval which represents this. Or (less correct IMHO), Duration should include values from IS8601 Duration along with Time interval.See also validFor.
See for examples do-invoice-examples.txt:39.
The text was updated successfully, but these errors were encountered: