Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 73 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]Code Context
trigger_error($message, E_USER_DEPRECATED);
}
$message = 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 73 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php.' $stackFrame = (int) 1 $trace = [ (int) 0 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ServerRequest.php', 'line' => (int) 2421, 'function' => 'deprecationWarning', 'args' => [ (int) 0 => 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead.' ] ], (int) 1 => [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 73, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) {}, 'type' => '->', 'args' => [ (int) 0 => 'catslug' ] ], (int) 2 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Controller/Controller.php', 'line' => (int) 610, 'function' => 'printArticle', 'class' => 'App\Controller\ArtileDetailController', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 3 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 120, 'function' => 'invokeAction', 'class' => 'Cake\Controller\Controller', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 4 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 94, 'function' => '_invoke', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(App\Controller\ArtileDetailController) {} ] ], (int) 5 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/BaseApplication.php', 'line' => (int) 235, 'function' => 'dispatch', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 6 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Http\BaseApplication', 'object' => object(App\Application) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 7 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/RoutingMiddleware.php', 'line' => (int) 162, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 8 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\RoutingMiddleware', 'object' => object(Cake\Routing\Middleware\RoutingMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 9 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/AssetMiddleware.php', 'line' => (int) 88, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 10 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\AssetMiddleware', 'object' => object(Cake\Routing\Middleware\AssetMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 11 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Middleware/ErrorHandlerMiddleware.php', 'line' => (int) 96, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 12 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Error\Middleware\ErrorHandlerMiddleware', 'object' => object(Cake\Error\Middleware\ErrorHandlerMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 13 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 51, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 14 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Server.php', 'line' => (int) 98, 'function' => 'run', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\MiddlewareQueue) {}, (int) 1 => object(Cake\Http\ServerRequest) {}, (int) 2 => object(Cake\Http\Response) {} ] ], (int) 15 => [ 'file' => '/home/brlfuser/public_html/webroot/index.php', 'line' => (int) 39, 'function' => 'run', 'class' => 'Cake\Http\Server', 'object' => object(Cake\Http\Server) {}, 'type' => '->', 'args' => [] ] ] $frame = [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 73, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) { trustProxy => false [protected] params => [ [maximum depth reached] ] [protected] data => [[maximum depth reached]] [protected] query => [[maximum depth reached]] [protected] cookies => [ [maximum depth reached] ] [protected] _environment => [ [maximum depth reached] ] [protected] url => 'latest-news-updates/failed-number-usha-ramanathan-22912/print' [protected] base => '' [protected] webroot => '/' [protected] here => '/latest-news-updates/failed-number-usha-ramanathan-22912/print' [protected] trustedProxies => [[maximum depth reached]] [protected] _input => null [protected] _detectors => [ [maximum depth reached] ] [protected] _detectorCache => [ [maximum depth reached] ] [protected] stream => object(Zend\Diactoros\PhpInputStream) {} [protected] uri => object(Zend\Diactoros\Uri) {} [protected] session => object(Cake\Http\Session) {} [protected] attributes => [[maximum depth reached]] [protected] emulatedAttributes => [ [maximum depth reached] ] [protected] uploadedFiles => [[maximum depth reached]] [protected] protocol => null [protected] requestTarget => null [private] deprecatedProperties => [ [maximum depth reached] ] }, 'type' => '->', 'args' => [ (int) 0 => 'catslug' ] ]deprecationWarning - CORE/src/Core/functions.php, line 311 Cake\Http\ServerRequest::offsetGet() - CORE/src/Http/ServerRequest.php, line 2421 App\Controller\ArtileDetailController::printArticle() - APP/Controller/ArtileDetailController.php, line 73 Cake\Controller\Controller::invokeAction() - CORE/src/Controller/Controller.php, line 610 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 120 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51 Cake\Http\Server::run() - CORE/src/Http/Server.php, line 98
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 74 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]Code Context
trigger_error($message, E_USER_DEPRECATED);
}
$message = 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 74 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php.' $stackFrame = (int) 1 $trace = [ (int) 0 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ServerRequest.php', 'line' => (int) 2421, 'function' => 'deprecationWarning', 'args' => [ (int) 0 => 'The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead.' ] ], (int) 1 => [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 74, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) {}, 'type' => '->', 'args' => [ (int) 0 => 'artileslug' ] ], (int) 2 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Controller/Controller.php', 'line' => (int) 610, 'function' => 'printArticle', 'class' => 'App\Controller\ArtileDetailController', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 3 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 120, 'function' => 'invokeAction', 'class' => 'Cake\Controller\Controller', 'object' => object(App\Controller\ArtileDetailController) {}, 'type' => '->', 'args' => [] ], (int) 4 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/ActionDispatcher.php', 'line' => (int) 94, 'function' => '_invoke', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(App\Controller\ArtileDetailController) {} ] ], (int) 5 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/BaseApplication.php', 'line' => (int) 235, 'function' => 'dispatch', 'class' => 'Cake\Http\ActionDispatcher', 'object' => object(Cake\Http\ActionDispatcher) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 6 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Http\BaseApplication', 'object' => object(App\Application) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 7 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/RoutingMiddleware.php', 'line' => (int) 162, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 8 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\RoutingMiddleware', 'object' => object(Cake\Routing\Middleware\RoutingMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 9 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Routing/Middleware/AssetMiddleware.php', 'line' => (int) 88, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 10 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Routing\Middleware\AssetMiddleware', 'object' => object(Cake\Routing\Middleware\AssetMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 11 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Middleware/ErrorHandlerMiddleware.php', 'line' => (int) 96, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 12 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 65, 'function' => '__invoke', 'class' => 'Cake\Error\Middleware\ErrorHandlerMiddleware', 'object' => object(Cake\Error\Middleware\ErrorHandlerMiddleware) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {}, (int) 2 => object(Cake\Http\Runner) {} ] ], (int) 13 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Runner.php', 'line' => (int) 51, 'function' => '__invoke', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\ServerRequest) {}, (int) 1 => object(Cake\Http\Response) {} ] ], (int) 14 => [ 'file' => '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Http/Server.php', 'line' => (int) 98, 'function' => 'run', 'class' => 'Cake\Http\Runner', 'object' => object(Cake\Http\Runner) {}, 'type' => '->', 'args' => [ (int) 0 => object(Cake\Http\MiddlewareQueue) {}, (int) 1 => object(Cake\Http\ServerRequest) {}, (int) 2 => object(Cake\Http\Response) {} ] ], (int) 15 => [ 'file' => '/home/brlfuser/public_html/webroot/index.php', 'line' => (int) 39, 'function' => 'run', 'class' => 'Cake\Http\Server', 'object' => object(Cake\Http\Server) {}, 'type' => '->', 'args' => [] ] ] $frame = [ 'file' => '/home/brlfuser/public_html/src/Controller/ArtileDetailController.php', 'line' => (int) 74, 'function' => 'offsetGet', 'class' => 'Cake\Http\ServerRequest', 'object' => object(Cake\Http\ServerRequest) { trustProxy => false [protected] params => [ [maximum depth reached] ] [protected] data => [[maximum depth reached]] [protected] query => [[maximum depth reached]] [protected] cookies => [ [maximum depth reached] ] [protected] _environment => [ [maximum depth reached] ] [protected] url => 'latest-news-updates/failed-number-usha-ramanathan-22912/print' [protected] base => '' [protected] webroot => '/' [protected] here => '/latest-news-updates/failed-number-usha-ramanathan-22912/print' [protected] trustedProxies => [[maximum depth reached]] [protected] _input => null [protected] _detectors => [ [maximum depth reached] ] [protected] _detectorCache => [ [maximum depth reached] ] [protected] stream => object(Zend\Diactoros\PhpInputStream) {} [protected] uri => object(Zend\Diactoros\Uri) {} [protected] session => object(Cake\Http\Session) {} [protected] attributes => [[maximum depth reached]] [protected] emulatedAttributes => [ [maximum depth reached] ] [protected] uploadedFiles => [[maximum depth reached]] [protected] protocol => null [protected] requestTarget => null [private] deprecatedProperties => [ [maximum depth reached] ] }, 'type' => '->', 'args' => [ (int) 0 => 'artileslug' ] ]deprecationWarning - CORE/src/Core/functions.php, line 311 Cake\Http\ServerRequest::offsetGet() - CORE/src/Http/ServerRequest.php, line 2421 App\Controller\ArtileDetailController::printArticle() - APP/Controller/ArtileDetailController.php, line 74 Cake\Controller\Controller::invokeAction() - CORE/src/Controller/Controller.php, line 610 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 120 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51 Cake\Http\Server::run() - CORE/src/Http/Server.php, line 98
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]Code Contextif (Configure::read('debug')) {
trigger_error($message, E_USER_WARNING);
} else {
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-trace').style.display = (document.getElementById('cakeErr680058b4c4f3d-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr680058b4c4f3d-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-code').style.display = (document.getElementById('cakeErr680058b4c4f3d-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-context').style.display = (document.getElementById('cakeErr680058b4c4f3d-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr680058b4c4f3d-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr680058b4c4f3d-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 22758, 'metaTitle' => 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan', 'metaKeywords' => 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer', 'metaDesc' => ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...', 'disp' => '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {}, (int) 2 => object(Cake\ORM\Entity) {}, (int) 3 => object(Cake\ORM\Entity) {}, (int) 4 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 22758 $metaTitle = 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan' $metaKeywords = 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer' $metaDesc = ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...' $disp = '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/failed-number-usha-ramanathan-22912.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | Failed Number -Usha Ramanathan | Im4change.org</title> <meta name="description" content=" -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>Failed Number -Usha Ramanathan</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $maxBufferLength = (int) 8192 $file = '/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php' $line = (int) 853 $message = 'Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853'Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 48 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]Code Context$response->getStatusCode(),
($reasonPhrase ? ' ' . $reasonPhrase : '')
));
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-trace').style.display = (document.getElementById('cakeErr680058b4c4f3d-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr680058b4c4f3d-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-code').style.display = (document.getElementById('cakeErr680058b4c4f3d-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-context').style.display = (document.getElementById('cakeErr680058b4c4f3d-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr680058b4c4f3d-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr680058b4c4f3d-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 22758, 'metaTitle' => 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan', 'metaKeywords' => 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer', 'metaDesc' => ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...', 'disp' => '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {}, (int) 2 => object(Cake\ORM\Entity) {}, (int) 3 => object(Cake\ORM\Entity) {}, (int) 4 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 22758 $metaTitle = 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan' $metaKeywords = 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer' $metaDesc = ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...' $disp = '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/failed-number-usha-ramanathan-22912.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | Failed Number -Usha Ramanathan | Im4change.org</title> <meta name="description" content=" -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>Failed Number -Usha Ramanathan</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $reasonPhrase = 'OK'header - [internal], line ?? Cake\Http\ResponseEmitter::emitStatusLine() - CORE/src/Http/ResponseEmitter.php, line 148 Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 54 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]Notice (8): Undefined variable: urlPrefix [APP/Template/Layout/printlayout.ctp, line 8]Code Context$value
), $first);
$first = false;
$response = object(Cake\Http\Response) { 'status' => (int) 200, 'contentType' => 'text/html', 'headers' => [ 'Content-Type' => [ [maximum depth reached] ] ], 'file' => null, 'fileRange' => [], 'cookies' => object(Cake\Http\Cookie\CookieCollection) {}, 'cacheDirectives' => [], 'body' => '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <link rel="canonical" href="https://im4change.in/<pre class="cake-error"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-trace').style.display = (document.getElementById('cakeErr680058b4c4f3d-trace').style.display == 'none' ? '' : 'none');"><b>Notice</b> (8)</a>: Undefined variable: urlPrefix [<b>APP/Template/Layout/printlayout.ctp</b>, line <b>8</b>]<div id="cakeErr680058b4c4f3d-trace" class="cake-stack-trace" style="display: none;"><a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-code').style.display = (document.getElementById('cakeErr680058b4c4f3d-code').style.display == 'none' ? '' : 'none')">Code</a> <a href="javascript:void(0);" onclick="document.getElementById('cakeErr680058b4c4f3d-context').style.display = (document.getElementById('cakeErr680058b4c4f3d-context').style.display == 'none' ? '' : 'none')">Context</a><pre id="cakeErr680058b4c4f3d-code" class="cake-code-dump" style="display: none;"><code><span style="color: #000000"><span style="color: #0000BB"></span><span style="color: #007700"><</span><span style="color: #0000BB">head</span><span style="color: #007700">> </span></span></code> <span class="code-highlight"><code><span style="color: #000000"> <link rel="canonical" href="<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">Configure</span><span style="color: #007700">::</span><span style="color: #0000BB">read</span><span style="color: #007700">(</span><span style="color: #DD0000">'SITE_URL'</span><span style="color: #007700">); </span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$urlPrefix</span><span style="color: #007700">;</span><span style="color: #0000BB">?><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">category</span><span style="color: #007700">-></span><span style="color: #0000BB">slug</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>/<span style="color: #0000BB"><?php </span><span style="color: #007700">echo </span><span style="color: #0000BB">$article_current</span><span style="color: #007700">-></span><span style="color: #0000BB">seo_url</span><span style="color: #007700">; </span><span style="color: #0000BB">?></span>.html"/> </span></code></span> <code><span style="color: #000000"><span style="color: #0000BB"> </span><span style="color: #007700"><</span><span style="color: #0000BB">meta http</span><span style="color: #007700">-</span><span style="color: #0000BB">equiv</span><span style="color: #007700">=</span><span style="color: #DD0000">"Content-Type" </span><span style="color: #0000BB">content</span><span style="color: #007700">=</span><span style="color: #DD0000">"text/html; charset=utf-8"</span><span style="color: #007700">/> </span></span></code></pre><pre id="cakeErr680058b4c4f3d-context" class="cake-context" style="display: none;">$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 22758, 'metaTitle' => 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan', 'metaKeywords' => 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer', 'metaDesc' => ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...', 'disp' => '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {}, (int) 2 => object(Cake\ORM\Entity) {}, (int) 3 => object(Cake\ORM\Entity) {}, (int) 4 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 22758 $metaTitle = 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan' $metaKeywords = 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer' $metaDesc = ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...' $disp = '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be &lsquo;seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to &lsquo;de-duplicate' the whole population? In a &lsquo;notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: &quot;there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The &lsquo;quality' assessment of fingerprint data (in the UIDAI's &lsquo;preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy.&quot; Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would &lsquo;own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that &quot;no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory&quot;. That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of &lsquo;consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'</pre><pre class="stack-trace">include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51</pre></div></pre>latest-news-updates/failed-number-usha-ramanathan-22912.html"/> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link href="https://im4change.in/css/control.css" rel="stylesheet" type="text/css" media="all"/> <title>LATEST NEWS UPDATES | Failed Number -Usha Ramanathan | Im4change.org</title> <meta name="description" content=" -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three..."/> <script src="https://im4change.in/js/jquery-1.10.2.js"></script> <script type="text/javascript" src="https://im4change.in/js/jquery-migrate.min.js"></script> <script language="javascript" type="text/javascript"> $(document).ready(function () { var img = $("img")[0]; // Get my img elem var pic_real_width, pic_real_height; $("<img/>") // Make in memory copy of image to avoid css issues .attr("src", $(img).attr("src")) .load(function () { pic_real_width = this.width; // Note: $(this).width() will not pic_real_height = this.height; // work for in memory images. }); }); </script> <style type="text/css"> @media screen { div.divFooter { display: block; } } @media print { .printbutton { display: none !important; } } </style> </head> <body> <table cellpadding="0" cellspacing="0" border="0" width="98%" align="center"> <tr> <td class="top_bg"> <div class="divFooter"> <img src="https://im4change.in/images/logo1.jpg" height="59" border="0" alt="Resource centre on India's rural distress" style="padding-top:14px;"/> </div> </td> </tr> <tr> <td id="topspace"> </td> </tr> <tr id="topspace"> <td> </td> </tr> <tr> <td height="50" style="border-bottom:1px solid #000; padding-top:10px;" class="printbutton"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> <tr> <td width="100%"> <h1 class="news_headlines" style="font-style:normal"> <strong>Failed Number -Usha Ramanathan</strong></h1> </td> </tr> <tr> <td width="100%" style="font-family:Arial, 'Segoe Script', 'Segoe UI', sans-serif, serif"><font size="3"> <div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p> </font> </td> </tr> <tr> <td> </td> </tr> <tr> <td height="50" style="border-top:1px solid #000; border-bottom:1px solid #000;padding-top:10px;"> <form><input type="button" value=" Print this page " onclick="window.print();return false;"/></form> </td> </tr> </table></body> </html>' } $cookies = [] $values = [ (int) 0 => 'text/html; charset=UTF-8' ] $name = 'Content-Type' $first = true $value = 'text/html; charset=UTF-8'header - [internal], line ?? Cake\Http\ResponseEmitter::emitHeaders() - CORE/src/Http/ResponseEmitter.php, line 181 Cake\Http\ResponseEmitter::emit() - CORE/src/Http/ResponseEmitter.php, line 55 Cake\Http\Server::emit() - CORE/src/Http/Server.php, line 141 [main] - ROOT/webroot/index.php, line 39
<head>
<link rel="canonical" href="<?php echo Configure::read('SITE_URL'); ?><?php echo $urlPrefix;?><?php echo $article_current->category->slug; ?>/<?php echo $article_current->seo_url; ?>.html"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
$viewFile = '/home/brlfuser/public_html/src/Template/Layout/printlayout.ctp' $dataForView = [ 'article_current' => object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ [maximum depth reached] ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ [maximum depth reached] ], '[dirty]' => [[maximum depth reached]], '[original]' => [[maximum depth reached]], '[virtual]' => [[maximum depth reached]], '[hasErrors]' => false, '[errors]' => [[maximum depth reached]], '[invalid]' => [[maximum depth reached]], '[repository]' => 'Articles' }, 'articleid' => (int) 22758, 'metaTitle' => 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan', 'metaKeywords' => 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer', 'metaDesc' => ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...', 'disp' => '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>', 'lang' => 'English', 'SITE_URL' => 'https://im4change.in/', 'site_title' => 'im4change', 'adminprix' => 'admin' ] $article_current = object(App\Model\Entity\Article) { 'id' => (int) 22758, 'title' => 'Failed Number -Usha Ramanathan', 'subheading' => '', 'description' => '<div align="justify"> -The Hindu </div> <p align="justify"> <br /> The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. </p> <p align="justify"> Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. </p> <p align="justify"> Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. </p> <p align="justify"> <em>No responsibility</em> </p> <p align="justify"> The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. </p> <p align="justify"> In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. </p> <p align="justify"> January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory. </p> <p align="justify"> The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. </p> <p align="justify"> And this is where the concerns about the project are currently poised. </p> <p align="justify"> <em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em> </p>', 'credit_writer' => 'The Hindu, 5 October, 2013, http://www.thehindu.com/opinion/lead/failed-number/article5204937.ece?homepage=true', 'article_img' => '', 'article_img_thumb' => '', 'status' => (int) 1, 'show_on_home' => (int) 1, 'lang' => 'EN', 'category_id' => (int) 16, 'tag_keyword' => '', 'seo_url' => 'failed-number-usha-ramanathan-22912', 'meta_title' => null, 'meta_keywords' => null, 'meta_description' => null, 'noindex' => (int) 0, 'publish_date' => object(Cake\I18n\FrozenDate) {}, 'most_visit_section_id' => null, 'article_big_img' => null, 'liveid' => (int) 22912, 'created' => object(Cake\I18n\FrozenTime) {}, 'modified' => object(Cake\I18n\FrozenTime) {}, 'edate' => '', 'tags' => [ (int) 0 => object(Cake\ORM\Entity) {}, (int) 1 => object(Cake\ORM\Entity) {}, (int) 2 => object(Cake\ORM\Entity) {}, (int) 3 => object(Cake\ORM\Entity) {}, (int) 4 => object(Cake\ORM\Entity) {} ], 'category' => object(App\Model\Entity\Category) {}, '[new]' => false, '[accessible]' => [ '*' => true, 'id' => false ], '[dirty]' => [], '[original]' => [], '[virtual]' => [], '[hasErrors]' => false, '[errors]' => [], '[invalid]' => [], '[repository]' => 'Articles' } $articleid = (int) 22758 $metaTitle = 'LATEST NEWS UPDATES | Failed Number -Usha Ramanathan' $metaKeywords = 'aadhaar,uid,UIDAI,Supreme Court,Direct Benefit Transfer' $metaDesc = ' -The Hindu The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns. Unique, universal, ubiquitous: three...' $disp = '<div align="justify">-The Hindu</div><p align="justify"><br />The Supreme Court's Interim order defining Aadhaar from subsidies has left the Centre grappling with the future of the Unique Identification programme. It must now provide a clear roadmap to citizens and address their genuine concerns.</p><p align="justify">Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions.</p><p align="justify">Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence.</p><p align="justify"><em>No responsibility</em></p><p align="justify">The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both.</p><p align="justify">In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush.</p><p align="justify">January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory.</p><p align="justify">The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population.</p><p align="justify">And this is where the concerns about the project are currently poised.</p><p align="justify"><em>(Usha Ramanathan works on the jurisprudence of law, poverty and rights.) </em></p>' $lang = 'English' $SITE_URL = 'https://im4change.in/' $site_title = 'im4change' $adminprix = 'admin'
include - APP/Template/Layout/printlayout.ctp, line 8 Cake\View\View::_evaluate() - CORE/src/View/View.php, line 1413 Cake\View\View::_render() - CORE/src/View/View.php, line 1374 Cake\View\View::renderLayout() - CORE/src/View/View.php, line 927 Cake\View\View::render() - CORE/src/View/View.php, line 885 Cake\Controller\Controller::render() - CORE/src/Controller/Controller.php, line 791 Cake\Http\ActionDispatcher::_invoke() - CORE/src/Http/ActionDispatcher.php, line 126 Cake\Http\ActionDispatcher::dispatch() - CORE/src/Http/ActionDispatcher.php, line 94 Cake\Http\BaseApplication::__invoke() - CORE/src/Http/BaseApplication.php, line 235 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\RoutingMiddleware::__invoke() - CORE/src/Routing/Middleware/RoutingMiddleware.php, line 162 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Routing\Middleware\AssetMiddleware::__invoke() - CORE/src/Routing/Middleware/AssetMiddleware.php, line 88 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Error\Middleware\ErrorHandlerMiddleware::__invoke() - CORE/src/Error/Middleware/ErrorHandlerMiddleware.php, line 96 Cake\Http\Runner::__invoke() - CORE/src/Http/Runner.php, line 65 Cake\Http\Runner::run() - CORE/src/Http/Runner.php, line 51
![]() |
Failed Number -Usha Ramanathan |
-The Hindu
Unique, universal, ubiquitous: three words that Mr Nandan Nilekani used to describe the ambitions of the UID project. Every person across the population of over 1.2 billion was to be uniquely identified. Every person was to be enrolled. The number was to be ‘seeded' in every data base, and the system re-engineered, making the UID number indispensable to every individual and every system. The UID project is based on these ambitions. Biometrics was the UIDAI's route to uniqueness. Except that very little, or nothing, was known about biometrics when the project started. How much did the UIDAI know about the efficacy of biometrics when it made its decision to capture fingerprints and iris scans, and to use biometrics to ‘de-duplicate' the whole population? In a ‘notice' inviting a biometrics consultant, the UIDAI was saying, in January-February 2010: "there is a lack of a sound study that documents the accuracy achievable on Indian demographics (that is, larger percentage of rural population) and in Indian environmental conditions (that is, extremely hot and humid climates and facilities without air-conditioning). In fact, we do not have any credible study assessing the achievable accuracy in any of the developing countries.... The ‘quality' assessment of fingerprint data (in the UIDAI's ‘preliminary assessment') is not sufficient to fully understand the achievable de-duplication accuracy." Yet, the decision had already been made, that the fingerprints and iris scan of the entire population be stored on the UIDAI database. Later reports on enrolment, and fingerprint and iris authentication, revealed deep flaws in the system, and escalating costs; but no one seems to have been paying attention to the emerging evidence. No responsibility The UID project has been weak on respect for the law. Despite the potential for surveillance, tracking, tagging, profiling and even exclusion that the project holds - say, migrant workers develop calluses in their hands that makes matching their fingerprint to that on the UID database a hard task - there has been no law protecting the rights of people, or detailing the liability of agencies that handle personal data. Through the years since the project was launched, there has only been the executive notification by which the UIDAI was set up in January 2009; which, among other things, says that the UIDAI would ‘own' the data. It was December 2010 when, bowing to pressure from civil society activists, a law was tabled in the Rajya Sabha, which was then referred to the Standing Committee. In December 2011, the Standing Committee delivered a scathing report which asked that the project, and the law, be taken back to the drawing board; there were too many problems with both. In response, the government did nothing; the report passed by them like an idle wind, which Shakespeare had taught them to respect not. From then, until now, the law is non-existent. This has allowed the UIDAI to expand the fields of data it collects, aggressively push for making enrolment mandatory to access any service or legal right, enter into data sharing agreements, and shrug off the idea of responsibility when there is identity fraud, or where authentication failures occur. The fait accompli is being created in a rush. January 2013, and anyone not enrolled for a UID began to be threatened with consequences that included not receiving subsidies more recently for LPG gas, scholarships, wages, and marriage registration. From being a facility, it had become mandatory. Yet, as recently as August 2013 in Parliament, and in September, 2013 in the Supreme Court, the government was saying that the UID was voluntary - because when one went to enrol, they were giving their consent! On September 23, 2013, the Supreme Court stepped in to direct that "no person should suffer for not getting the Aadhaar card in spite of the fact that some authority had issued a circular making it mandatory". That is, the UID is not to be mandatory. The government's response has blown away the fig leaf of ‘consent' and voluntariness. On October 4, 2013, the government was back in court asking that it be heard urgently on making the UID mandatory. The implication: that the government is asking that its authority to coerce enrolment on pain of exclusion be recognised. Given that even such acts as registering a will, or a lease deed, or drawing a salary have been made dependent on being enrolled in states such as Delhi and Maharashtra, this could spell bullying by the state, as detractors of the project warn. Even if it were to be made mandatory just for, say, LPG, that would help achieve the UIDAI's proximate purpose of databasing everybody. Once universality is achieved, ubiquity could follow with greater ease. These are two admitted ambitions of the project. In the meantime, the project is experimenting with biometrics and uniqueness, on the entire population. And this is where the concerns about the project are currently poised. (Usha Ramanathan works on the jurisprudence of law, poverty and rights.) |