Brian J. Miller
Brian J. Miller
I agree that whatever is decided would have to go in a major release. I can understand the softening of the original `SHOULD* NOT`, and potentially flipping it to a...
The other thing that will have to be considered here is `timestamp` in SubStatements particularly in their future tense use case (ref: https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Data.md#substatements). A SubStatement being used to indicate the...
Yep, `stored` is just one possible workaround, seemed worth mentioning. The value outside of a range isn't an *interpretation* of the value as 2 is distinctly not in the range...
I think you're being overly creative in your reading of the spec :-). The intent of that portion was to highlight that the LRS itself has to set the `timestamp`...
Basically, yes. At this time the query parameters requires a pre-constructed TinCan.Agent or TinCan.Group. We can leave this open as a feature enhancement, there are probably other places that could...
Why would the AP be sending to the regional and/or national LRS, why wouldn't the local LRS do it, at which point the id has already been assigned? I think...
@rswetnam I'll reply to you directly since you addressed me but I think the others have captured well the thoughts. I think you are reading it fine, I just wanted...
> what, then is the AP? I think that is the point. Personally I'd like to see us use the first sentence in the original definition of an AP, because...
@rswetnam that's why it is a "SHOULD" requirement, it is considered a best practice and they should do so. But making it a "MUST" may well break some use cases...
Permission does not imply best practice. The vast majority of the current use cases aren't likely to produce a conflict so the spec was left loose in this regards to...