matthewmueller / matthewmueller/date
Support of EDTF?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
Is there any interest in extending the date representation used to support EDTF?
As far as I can see there is nothing in the date representation to indicate that any given date represents an approximate date/time. It would be great to retain this aspect of parsed date/time strings.
For example parsing a date like "Tomorrow afternoon" is useful, however to then output this date again without distorting meaning we need to know that the 2pm part of the resulting date object is inferred and approximate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing date representation and the parsing and output behavior described in this issue. Determine how inferred or approximate values are currently represented, then define what EDTF support must preserve when a parsed date is emitted again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100