Closed timbot1789 closed 7 months ago
timbot1789
commented
1 year ago This is proving to be more complex than I anticipated. I think we can delay this for now. A better use of time immediately IMO is https://github.com/codeforpdx/PASS/issues/259
timbot1789
commented
7 months ago Closing as not relevant to current designs. Compliance to these specs requires a mobile device, which is not compatible with PASS's current direction
Is your feature request related to a problem? Please describe. One of the early goals of PASS is to be an alternative storage space for drivers' licenses if they get lost. Currently, we're using a largely bespoke system for license verification. However, an international standard for this exists, ISO 18013. Implementing this would make PASS users able to use PASS itself for their drivers' licenses in participating states.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context The spec itself is quite expensive. It's split into 5 parts, each part costing about $200, although not all of them relate to computers. For PASS purposes, we'd at least need:
However, the specs do refer to parts of other specs, so we may not be able to comply with Part 5 if we are unable to read the other parts. It's likely we'll also need:
This is a sizable project, and could take several months to complete (especially with a volunteer staff). I think it could be more manageable if we split it into 2 parts:
If we split up work in this way, PASS could do just part 1, and a separate affiliate project could do Part 2. Realistically, a user could use any app that can process the file format we set up as their mobile driver's license anyway.