W3C home > Mailing lists > Public > public-egov-ig@w3.org > December 2010

Re: Proposal to structure new eGov IG

From: Tom M. van Engers <vanengers@uva.nl>
Date: Fri, 17 Dec 2010 15:53:02 +0100
Message-ID: <4D0B794E.8080400@uva.nl>
To: daniel@citizencontact.com
CC: chris@e-beer.net.au, Michael Hausenblas <michael.hausenblas@deri.org>, Ed Summers <ehs@pobox.com>, Sandro Hawke <sandro@w3.org>, W3C eGov IG <public-egov-ig@w3.org>, team-egov@w3.org, Brian Gryth <briangryth@gmail.com>
  Dear all,

I agree with Daniel we should address these eGov themes. If we'd 
organize ourselves too much along technical topics we will certainly 
loose interest of many governmental institutions.

Cheers,

Tom

Prof. dr. Tom M. van Engers
Professor in Legal Knowledge Management
University of Amsterdam/Faculty of Law
Leibniz Center for Law
Kloveniersburgwal 48
Postbus 1030
1000BA Amsterdam
+31 20 525 3494
+31 20 525 2179
www.LeibnizCenter.org
vanEngers@uva.nl


On 12/17/10 3:27 PM, daniel@citizencontact.com wrote:
> I am worried that we are becoming tech oriented rather than policy oriented. I would start out with a list of things governments do, especially that differ from commercial interests. My list would include:
> * Publishing documents especially laws and regulations that can be used and cited.
> * Publishing data in ways that the public and value add entities can use.
> * Maintaining private documents securely.
> * Establish and enhance communication between citizens and government.
> * Receive forms from the regulated citizens and entities.
> * Establishing rules of the road for online identity as needed.
> * Outlining the roles of governments in eCommerce.
>
> And there are many more. I think we will find that cloud computing (catch phrase of the day), accessibility, standards adoptions, social media tech, and other technology issues fit into each of these items in my list. I know our audience may be mainly the tech folks in government agencies, but their ability to do their jobs is based on meeting policy directives and shaping government policies.
>
> Perhaps to bring more people in who are tech oriented we need to have some structure that is convenient to them, but I think it is a mistake to not at least have a horizontal policy group that helps focus on the policy implications. This is especially important since different countries have different notions of citizen participation, privacy, regulatory structures, cultures, etc.
>
> One example is the use of HTML5. The ability to use downloaded fonts is important for non-Latin alphabets. There are accessibility advantages. There are digital rights management implications for government cost and oversight.
>
> And there is the issue of producing W3C documents that are human friendly. Which is not to say that there can also be geeked out tech manuals too. But can we address what I think is an important need that will also help with the access to our work by policy folks.
>
> Thanks,
> Daniel Bennett
>
> -----Original Message-----
> From: "Chris Beer"<chris@e-beer.net.au>
> Sent: Friday, December 17, 2010 6:04am
> To: "Michael Hausenblas"<michael.hausenblas@deri.org>
> Cc: "Ed Summers"<ehs@pobox.com>, "Sandro Hawke"<sandro@w3.org>, "W3C eGov IG"<public-egov-ig@w3.org>, team-egov@w3.org, "Brian Gryth"<briangryth@gmail.com>
> Subject: Re: Proposal to structure new eGov IG
>
> Not a bad approach Michael.
>
> If it is taken up, then:
>
> While always tempted by SM - I nominate Brian Gryth as he was handling
> the original SM TF.
>
> I would like to put myself forward as a Chair candidate for the
> Accessibility TF. I'm on the WCAG working group and will be on a joint
> WAI-PF/WAI-WCAG TF in the new year, working on HTML 5. I have a good
> understanding of 508 in the US, and the various legislative requirements
> pertaining to accessibility for most countries as well. Working in web
> publishing and content delivery, I'm also keenly aware of accessibility
> issues as they relate to government, and was accepted to WCAG with this
> as my primary expertise.
>
> Cheers
>
Received on Friday, 17 December 2010 14:53:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 December 2010 14:53:36 GMT