RE: A "Sensible Defaults" Approach to an ELReq Recommendation

Selam Daniel,

This sound a great solution to break the stalemate on this project.
Let me know how I can help.

Thanks,
Elias


Elias Wondimu
Publisher & Editorial Director

Tsehai Publishers
Loyola Marymount University
One LMU Drive, UH 3012
Los Angeles, CA 90045

Cell: 323.533.7626 | Office: 310.258.5460  |  Fax: 310.338.5193
URL: www.tsehaipublishers.com

Imprints: Marymount Institute Press and African Academic Press
________________________________
From: Daniel Yacob [yacob@geez.org]
Sent: Sunday, February 04, 2018 9:15 PM
To: public-i18n-ethiopic@w3.org
Subject: A "Sensible Defaults" Approach to an ELReq Recommendation

Greetings All,

I've been thinking about ways forward for the ELReq document and have a thought to share.  The initial approach was to identified areas to be addressed, then arrive at a recommendation from stakeholder feedback.

Finding and engaging willing industry stakeholders to acquire feedback then became an unexpected obstacle. I still subscribe to this approach but appreciate now that it will take significant time to get through.  Until then, I propose that we review the questions raised for each topic in the ELReq document and determine the most "sensible defaults" to form the basis of a recommendation.

>From there, test cases can be developed to help developers implement the recommendations.  Thoughts?

thanks,

-Daniel