Paul Wade

Administrators
  • Content Count

    67
  • Joined

  • Last visited

  • Days Won

    1

Paul Wade last won the day on July 10 2018

Paul Wade had the most liked content!

Community Reputation

1 Neutral

About Paul Wade

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. until
    Location: Sands Expo & Convention Center, Las Vegas, NV Meeting Room: 307
  2. until
    Location: Sands Expo & Convention Center, Las Vegas, NV Meeting Room: 307
  3. Hi Nick, First, just to be clear, this is for the new standard still under development, not the existing LDS. The problem is that we do not have a standardized, universally unique way of identifying things outside of physical lenses. OPC's work for that and while expanding the use of OPC was discussed it's not really feasible for this purpose. So it's really about more than packages. No user of the standard would be forced to create packages in their LPDS catalogs but if they want to we would like to have a single ID methodology that can be applied to those as well. I think your last bullet is on point... I believe that is exactly what the group is trying to develop. Regards, Paul
  4. During the LPDS Committee meeting the working group presented their proposed implementation for concise base cure and range chart definitions. This proposal is outlined in this thread: During discussions at the meeting representatives from Shamir pointed out that this method does not allow the specification of an allowable base curve range for a specific power combination. The group requested this topic be started so further discussion could take place between now and our next meeting at Vision Expo West.
  5. Starter topic for discussion of product ID's to be used in LPDS to include identification of "packages" which may include lenses and various treatments. Please post your thoughts, questions, concerns, etc. If you have any specific proposals on the creation of product identifiers please feel free to share those as well.
  6. Agenda for our 2019 VEE meeting. 2019 VEE - DCS Agenda - FINAL.pdf
  7. https://drive.google.com/file/d/1JJjTVyaq626b9ggYyBP90m8Q4d0o-U8f/view?usp=sharing
  8. Hi there. My name is Paul Wade and I'm a liaison for The Vision Council. I'd like to see if I can help you with this but it might be better if you contact me directly. You can email me at pwade@thevisioncouncil.org. If you could include some more detail about the system you are trying to design I can try and provide you with some documentation that might help with your goal.
  9. The audio from the DCS meeting at VEW 2018 has been uploaded to our Google Drive folder. https://drive.google.com/file/d/1SapKukV1slmkNc3DEKaQQD0IGraaZreT/view?usp=sharing Please let me know if you have any trouble downloading it. Paul
  10. Hi Everyone, The audio from our working group meeting is now available: https://drive.google.com/file/d/1wr30abo1Zib0v-dtwuONCzYBLw7pbRS0/view?usp=sharing Let me know if you have any trouble downloading it. Thanks, Paul
  11. Hi Everyone, The audio for our 2018 VEW meeting is now available: https://drive.google.com/file/d/1jsTOINTa0IwKT9y-xKi0jIGtfqQqsaPI/view?usp=sharing Let me know if you have any trouble downloading it. Thanks, Paul
  12. I apologize for the delay in posting these. Steve provided them several weeks ago and I thought I had already sent them out. I just realized my mistake this morni ng. 2018 VEE - LPDS Meeting Minutes - Final.pdf
  13. Thank you Thomas. This has been added to the agenda.
  14. Dear Colleagues, You can find the agenda for the LPDS Committee meeting at VEW 2018 posted here: https://thevisioncouncil.org/sites/default/files/2018-VEW-LPDS-Agenda-FINAL.pdf If you have any topics you would like added to the agenda please reply to this post or send them to Daniel Simonetta or myself directly. Thanks!
  15. The synopsis would be very brief indeed. We have no such capability at the moment and without specifications it would be hard to predict what changes or additions would be necessary to support such a platform.