Skip to content
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

Open
gkellogg opened this issue Apr 11, 2019 · 9 comments · May be fixed by #2688
Open

billingPeriod of type Duration, but represents an Interval #2210

gkellogg opened this issue Apr 11, 2019 · 9 comments · May be fixed by #2688
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@gkellogg
Copy link
Contributor

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 form P[n]Y[n]M[n]DT[n]H[n]M[n]S (such as P30D). 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.

@RichardWallis
Copy link
Contributor

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.

@RichardWallis RichardWallis added the Move to /suggestions-questions-brainstorming Queued for moving to suggestions-questions-brainstorming repo label Jul 2, 2020
@RichardWallis RichardWallis removed the Move to /suggestions-questions-brainstorming Queued for moving to suggestions-questions-brainstorming repo label Jul 14, 2020
@RichardWallis RichardWallis self-assigned this Jul 14, 2020
RichardWallis pushed a commit that referenced this issue Aug 13, 2020
Added invoiceDate property
Updated examples to reflect changes
Fixes #2210
@RichardWallis
Copy link
Contributor

Whilst reviewing the issue, also noted the obvious omission of an invoiceDate property.

@RichardWallis RichardWallis linked a pull request Aug 13, 2020 that will close this issue
@danbri
Copy link
Contributor

danbri commented Aug 18, 2020

@tmarshbing @nicolastorzec @scor @tilid any opinion on this?

/cc #2648

@tmarshbing
Copy link

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.

@dr-shorthair
Copy link

The billing period for an individual invoice is an interval.
An interval has a duration, and in many cases the interval for an individual invoice is described as 'the interval starting {now} with duration {30 days}' etc. I.e. an interval, parameterised by its start position and duration.

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.

@danbri
Copy link
Contributor

danbri commented Aug 25, 2020

Bringing @dr-shorthair 's comment from the pull request in here for visibility:

Terminology is still jumbled here.

time-interval = an interval on the time-line with a beginning and end
duration = distance or amount of time between two instants or temporal positions
period = usually synonym for time-interval
So I would suggest that either the property name or the range needs to be changed:

billingPeriodDuration could have range Duration
billingPeriod should have range Interval or Period, which in 
turn should have a intervalDuration or periodDuration property whose range is Duration
But the proposed state is not coherent.

@github-actions
Copy link

This issue is being tagged as Stale due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Oct 25, 2020
@dr-shorthair
Copy link

Are you waiting for a proposal?

@jaygray0919
Copy link

We have a similar issue; linking here to bring-into-view: #2689 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants