BarCamp Wellington Egovt

Get Started. It's Free
or sign up with your email address
Rocket clouds
BarCamp Wellington Egovt by Mind Map: BarCamp Wellington Egovt

1. Top 10 Things for Government Webmasters

1.1. Validate your page

1.1.1. Use microformats

1.1.2. Why dont we do it now?

1.1.2.1. Not enough time

1.1.2.2. Not enough money

1.1.2.3. No CMS

1.1.2.4. Old CMS

1.1.3. Stop the rot

1.1.4. We need a better way to create, manage and publish content, Open source CMS !

1.2. User-centric

1.2.1. Testing, testing, testing

1.2.1.1. Try to break it

1.2.2. User feedback

1.2.3. Self-service

1.2.4. Usable forms

1.3. Only current information OR put all information!

1.3.1. Put a date in the metadata, to allow better filtering

1.4. Subscription

1.4.1. RSS on way out

1.4.2. ATOM is new standard

1.4.3. Only 2/34 govt websites have RSS icon

1.4.4. Get more granular, allow local news

1.5. Website compression

1.5.1. Analyse your website to see possible performance gains

1.5.1.1. Trademe is compressed

1.5.1.2. Stuff could get 330% improvement

1.5.1.3. newzealand.govt.nz could get 217% improvement

1.5.2. How to do compression

1.6. Visual design - look nice

1.6.1. Aesthetics

1.6.2. Sites still look nice with web standards

1.7. Improve workflow

1.7.1. Collaborate with content people

1.8. Use the .govt.nz namespace

1.8.1. newzealand.govt.nz brand will help with recognition over time

1.9. Review site statistics, metrics

1.9.1. Page views are a bad metric

1.9.1.1. Distribute your information, let others publish it

1.10. Search engine optimisation

1.10.1. Test google search

1.10.2. Fix your website search

1.11. Market your website

1.12. Just follow the web standards

1.12.1. No PDFs only

1.12.2. Multiple style sheets for different mediums

1.12.3. Access keys

1.12.4. Fix your metadata

1.12.4.1. Put Subject first in the Title, not the Organisation name

1.12.5. Richer content is to be encouraged

1.12.5.1. Accessible graphics and information

1.12.5.2. Fewer pictures, more words OR more pictures, less words!

2. Trust

2.1. Reputation

2.1.1. Trademe feedback

2.1.2. Blacklisted

2.1.3. Vendor / Government

2.2. Transparency

2.3. Accountability

2.4. Real-time government Networked government

2.4.1. Nanny government

2.4.1.1. Proving your age at a pub

2.4.2. No more pieces of paper

2.4.3. Prove yourself online, realtime

2.5. Identity

2.5.1. Uniqueness

2.5.1.1. Individuals

2.5.1.1.1. Who?

2.5.1.1.2. How?

2.5.1.2. Organisations

2.5.1.2.1. Who?

2.5.1.2.2. How?

2.5.1.2.3. Issues?

2.5.1.3. Cows

2.5.1.3.1. Who?

2.5.1.3.2. How?

2.5.2. Governments

2.5.2.1. Trusted internationally

2.5.2.2. Authoritative

2.5.2.2.1. Guaranteed?

2.5.3. Seperate identity from authentication

2.5.3.1. Not an identity card!

2.5.3.2. Proof: Share your authentication key

2.5.3.3. Unique to NZ

2.5.3.3.1. NZ context

2.5.3.3.2. We are different, don't copy the rest of the world

2.6. Distributed "The People"

2.7. Security

2.7.1. Authentication

2.7.2. Non-repudiation

2.7.3. Does not guarantee privacy

2.8. Privacy

2.8.1. Silos enhance privacy

2.8.2. Information sharing

2.8.2.1. User in control

2.8.2.1.1. Attribute Assertion

2.8.2.2. Compliance

2.8.2.2.1. Data matching

2.8.2.2.2. Data matching

2.8.2.2.3. User trying to avoid

2.9. Enables society to do more with less knowledge

3. single source publishing

3.1. docvert

3.2. doc - > odf -> anything

3.3. unlocking content from word processor tools

3.4. Word as a scratchpad

4. space and place

4.1. passionate places

4.2. zoomin.co.nz

4.3. collaborative stories on places

5. Open Source

5.1. framework

5.1.1. legal

5.1.2. evaluation

5.2. purchasing policy

5.2.1. national framework

5.2.1.1. legislation

5.2.1.2. protection of IP

5.2.2. international policy level

5.2.2.1. eg OOXML

5.2.2.2. we have a role in the world

5.2.2.3. as vaguely independent

5.2.2.4. and thinking deeply

5.2.3. some apps don't have an opensource equivalent

5.2.4. participating without having to join a huge corporate

5.2.5. though shalt consider opensource

5.2.6. DRM policy

5.2.7. G2009

5.2.7.1. will this be run more openly

5.2.7.2. SSC will probably do it this time

5.2.7.3. and SSC can only influence, not compel

5.2.8. syndicated procurement

5.2.8.1. there is one for Novell

5.2.9. auditor generals office has 'gone opensource'

5.3. Intertia is a problem

5.4. arguments

5.4.1. the utility of it, are they equivalent

5.4.2. cost of licencing

5.4.3. ideological

5.4.3.1. this does have traction

5.5. Justice

5.5.1. awareness of ideological issue is a distraction

5.5.2. documenting the objections

5.5.3. economic question is more important

5.5.4. there are some things we have to do ourselves

5.5.5. reliability

5.5.5.1. google runs on it

5.5.6. legal risks

5.5.6.1. is it actually a risk?

5.5.6.2. noone's every been sued as an individual

5.5.7. perception of the user experience being poor

5.5.7.1. has tarnished the perception

5.5.8. so how do we have an open selection process

5.5.9. this changes the nature of a purchasing effort

6. Privacy

6.1. creative commons

6.2. need something similar for user data

6.2.1. identity commons

6.2.2. social networking contract manifesto

6.3. can we do this in the NZ context?

6.3.1. control of user data in the hands of the users

6.3.2. OpenID identify provider

6.3.3. I can see my identity agreements in one place

6.3.4. and shift my data from place to place

6.4. Architecture

6.4.1. security architecture

6.4.2. vs

6.4.3. privacy architecture

6.5. duplication is bad

6.5.1. needs dispute processes

6.5.2. if we could agree on a single source

6.5.2.1. we could link to it

6.5.2.2. halve the cost to the tax payer

6.6. govt looks after your most initimate records

6.6.1. shifting my medical data

6.6.2. convenience vs big brother

6.6.3. who do you want to do this?

6.6.3.1. do people care enough about it

6.6.3.2. for it to become a policy issue

6.6.4. place of birth, date of birth

6.6.5. Mike's URN

6.6.5.1. chooses to publish his address to the world

6.6.6. your address

6.6.7. ACC rape records

6.7. negative identity

6.7.1. verification service

6.8. checks and balances

6.8.1. sovereignty

6.8.1.1. you can take govt to court

6.8.1.2. applies to private sector too

6.8.2. if your data is offshore

6.8.2.1. sovereignty doesn't apply

6.8.2.2. software as a service

6.8.2.2.1. infrastructure and data can be offshore

6.8.2.2.2. can we choose where it's hosted

6.8.2.3. moko on models in Paris

6.8.2.3.1. from pictures on Flickr

6.8.2.3.2. cultural loss not monetary

6.8.3. what other social constructs exist

7. OpenID

7.1. to use mindmeister

7.2. wouldn't have to create an account

7.3. openid.net.nz

7.3.1. open id provider service

7.4. how does it relate to NZGLS?

7.4.1. conceptually could integrate the two

7.4.2. but reputation issue

7.5. webstock

7.5.1. Simon Willison

7.6. sxip.com

7.6.1. dick hardt

7.6.2. is an openid provider

7.6.2.1. that lives on your machine

7.6.2.2. not on the network

7.6.2.3. a password manager on steroids