Thank you so much, Jürgen!
The WG decision is to use a single unit and hence to allow scaling below
the chosen unit, we have to deal with float. As much as we thought 1 second
is typically the smallest, from my understanding, some use cases from a
major app developer is already below this. We
I will remove all closed issues and comment further inline.
On Fri, Feb 21, 2020 at 03:54:30PM -0500, Y. Richard Yang wrote:
> > > > - Since you write "SHOULD at least IEEE 754 double-precision floating
> > > > point", does this not make the IEEE 754 reference a normative
> > > > reference?
Dear Jürgen,
Sorry for the late reply, as our lead author is off without a stable
connection.
Please see below.
On Wed, Feb 19, 2020 at 4:38 AM Schönwälder, Jürgen <
j.schoenwael...@jacobs-university.de> wrote:
> Dear authors,
>
> I will comment inline...
>
> On Tue, Feb 18, 2020 at 06:39:04PM
Dear authors,
I will comment inline...
On Tue, Feb 18, 2020 at 06:39:04PM -0500, Y. Richard Yang wrote:
> Dear Jürgen,
>
> Thank you so much for the careful reviews. The lead author of the document
> is Sabine and the response below is formulated by her and then discussed
> among the authors.
Dear Jürgen,
Thank you so much for the careful reviews. The lead author of the document
is Sabine and the response below is formulated by her and then discussed
among the authors. Since she is off this week, so let me send the response
on her behalf to make progress.
Her response for an item
Reviewer: Jürgen Schönwälder
Review result: Has Issues
I am not an ALTO expert so keep this in mind in case some of my
comments have little meaning for ALTO experts.
- If multiple clients retrieve information about costs in the future
and take independent scheduling decisions based on that
