- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2023 14:30:10 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == `validFrom` and `validTo` fields specification of `dateTime` format == ## Proposed comment Validity Period https://www.w3.org/TR/vc-data-model-2.0/#validity-period > validFrom > A [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) MUST have an validFrom [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property). The value of the validFrom [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property) MUST be a string value of an [[XMLSCHEMA11-2](https://www.w3.org/TR/xmlschema11-2/#dateTime)] combined date-time string representing the date and time the [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) becomes valid, which could be a date and time in the future. Note that this value represents the earliest point in time at which the information associated with the credentialSubject [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property) becomes valid. The text says a "combined date-time string", but this is not actually a type in XMLSchema 1.1. The type that is being referred to is `dateTime`. A challenge of this data type is that it allows values both with (`2023-06-15T00:00:00Z` or `2023-06-15T00:00:00-08:00`) and without (`2023-06-15T00:00:00`) time zone offsets. Since `validFrom` and `validTo` need to be interpreted as timestamp values, the spec should probably require that values without zone offsets be treated as being in the UTC time zone. I would suggest writing this as: > validFrom > A [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) MUST have an validFrom [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property). The value of the validFrom [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property) MUST be a string value of an [[XMLSCHEMA11-2](https://www.w3.org/TR/xmlschema11-2/#dateTime)] dateTime string representing the date, time and timezone offset the [credential](https://www.w3.org/TR/vc-data-model-2.0/#dfn-credential) becomes valid, which could be a date and time in the future. Note that this value represents the earliest point in time at which the information associated with the credentialSubject [property](https://www.w3.org/TR/vc-data-model-2.0/#dfn-property) becomes valid. Values without a timezone offset MUST be treated as being in the UTC time zone. (Note that the quotes/suggestions above are about `validFrom`: the same comments/edits apply to `validTo`) ## Instructions: This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html 1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** 2. **Add one or more t:... labels. These should use ids from specdev establish a link to that doc.** 2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help. 3. Ask the i18n WG to review your comment. 4. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s). 5. Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use \[...](...) notation – you need to delete the placeholder, then paste the URL. 6. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. 7. If you added an \*lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:. 8. Edit this issue to **REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT**, ie. the line below that is '---' and all the text before it to the very start of the issue. --- **This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:** § url_for_the_issue_raised Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1729 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 June 2023 14:30:12 UTC