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

Timestamps #7

Closed
FeLungs opened this issue Oct 31, 2022 · 7 comments
Closed

Timestamps #7

FeLungs opened this issue Oct 31, 2022 · 7 comments
Assignees
Milestone

Comments

@FeLungs
Copy link
Owner

FeLungs commented Oct 31, 2022

Change Log Item Ids

s19, s20, s22

1.0.3 text -> 9274.1.1 Update

A Timestamp SHOULD* be expressed using the format described in RFC 3339, which is a profile of ISO 8601
->
A Timestamp shall be expressed using the format described in RFC 3339, which is a profile of ISO 8601.

A Timestamp SHOULD* include the time zone.
->
Removed as requirement

The LRS SHOULD* return the Timestamp in UTC timezone.
->
An LRS shall convert Timestamps to UTC rather than rejecting Statements that send Timestamps not in UTC form

Updates to xAPI Profile spec

  • specify datatype (e.g. XSD dateTime vs dateTimeStamp) used for timestamps. What is the RDF type that is closest to RFC 3339?
  • update Profile Server section to describe how it will handle timestamps not in the expected form
@FeLungs FeLungs added this to the Timestamps milestone Oct 31, 2022
@FeLungs
Copy link
Owner Author

FeLungs commented Jan 9, 2023

@FeLungs
Copy link
Owner Author

FeLungs commented Jan 9, 2023

@FeLungs
Copy link
Owner Author

FeLungs commented Jan 9, 2023

@FeLungs
Copy link
Owner Author

FeLungs commented Jan 9, 2023

Overall, I think we should go with dateTimeStamp over dateTime because xAPI doesn't support timestamp without timezone or offset which IMO makes dateTimeStamp more correct than dateTime

dateTime

dateTimeStamp

The dateTimeStamp datatype is ·derived· from dateTime by giving the value required to its explicitTimezone facet. The result is that all values of dateTimeStamp are required to have explicit time zone offsets and the datatype is totally ordered.

Both XSD types have differences from RFC 3339 but that can be accounted for within normative language. (example within explanation section of https://validator.w3.org/feed/docs/error/InvalidRFC3339Date.html)

  • replace dateTime within profile context?
  • informative + normative language for timestamps

https://www.w3.org/2011/rdf-wg/wiki/XSD_Datatypes

@imartinezortiz
Copy link
Collaborator

I rather prefer the dateTimeStamp following your analysis.

@FeLungs
Copy link
Owner Author

FeLungs commented Jan 13, 2023

See check boxes in comment for next steps

@imartinezortiz
Copy link
Collaborator

This issue has been migrated to upstream repo adlnet#269

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants