X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/f3234b5394966c14fb0093c0391334e0149c92a0..6e332956d6c23a97d301a12447ddc462c5e22e78:/blog/index.html diff --git a/blog/index.html b/blog/index.html index b089d0591e..3a33896444 100644 --- a/blog/index.html +++ b/blog/index.html @@ -19,6 +19,66 @@ +
+
Fiksgatami tar form - snart klar for test
+
2011-02-13 21:10
+
+

NUUGs Fiksgatami-tjeneste tar sakte form, og den siste uka har vi +betalt mySociety i England for å tilpasse kildekoden til deres +tjeneste slik at den skal fungere for Norge. I løpet av kommende uke +regner jeg at vi skal i gang med testing.

+ +

For å forberede testing, har jeg tatt en titt på hva slags +informasjon som samles inn av kommuner som har lignende tjeneste for +sin kommune allerede på plass. Jeg har tittet på tjenestene til +Tromsø, +Porsgrunn +og Kongsvinger. Jeg +tittet også på +Askers, +som er litt på siden at det jeg skriver om her

+ +

Om problemet samles alle tjenestene inn plassering, enten som +adresse eller som kartkoordinat. De samler også inn en +oppsummering/overskrift og en lengre beskrivelse, og noen av dem +tillater bilde og vedlegg lagt ved. Alle problemene tildeles en +kategori, og det er stort overlapp i kategoriseringen:

+ + + + + + + + + + + + + +
Tromsø Porsgrunn Kongsvinger
Vei Hull i veg Veg/Vegvedlikehold
Skilt/Trafikksikkerhet
Gatelys Gatelys virker ikke Gatelys
Vann og avløp Vann og avløp Vann/Avløp
Park Park Park/Grønt
Friluftsliv Friluft
Renovasjon Renovasjon Renovasjon/Avfall
Grafitti-Tagging Grafitti/Tagging
Forsøpling
Annet Annet Annet
+ +

Om de som rapporterer inn problemet, blir det samlet inn navn, +epostadresse, et eller to telefonnummer og for Asker postadresse. +Noen vil også vite hvordan tilbakemelding ønskes, dvs. epost, telefon +eller via post.

+ +

Fiksgatami skulle kunne håndtere innsending til disse kommunene +uten større problemer, tror jeg. Kategorier defineres per område, +slik at kommunene kan få meldinger inndelt i de kategoriene de +trenger. Fiksgatami samler i utgangspunktet kun inn navn og +epostadresse for innsender, og det tror jeg vi skal fortsette med.

+
+
+ + + + Tags: fiksgatami, kart, norsk. + +
+
+
+
Bedre kommunegrense for Oslo i OpenStreetmap.org
2011-02-07 10:35
@@ -783,95 +843,6 @@ provided by external plugins like the Flash plugins.

-
-
Chrome plan to drop H.264 support for HTML5 <video>
-
2011-01-12 22:10
-
-

Today I discovered -via -digi.no that the Chrome developers, in a surprising announcement, -yesterday -announced plans to drop H.264 support for HTML5 <video> in -the browser. The argument used is that H.264 is not a "completely -open" codec technology. If you believe H.264 was free for everyone -to use, I recommend having a look at the essay -"H.264 – Not The Kind Of -Free That Matters". It is not free of cost for creators of video -tools, nor those of us that want to publish on the Internet, and the -terms provided by MPEG-LA excludes free software projects from -licensing the patents needed for H.264. Some background information -on the Google announcement is available from -OSnews. -A good read. :)

- -

Personally, I believe it is great that Google is taking a stand to -promote equal terms for everyone when it comes to video publishing on -the Internet. This can only be done by publishing using free and open -standards, which is only possible if the web browsers provide support -for these free and open standards. At the moment there seem to be two -camps in the web browser world when it come to video support. Some -browsers support H.264, and others support -Ogg Theora and -WebM -(Dirac is not really an option -yet), forcing those of us that want to publish video on the Internet -and which can not accept the terms of use presented by MPEG-LA for -H.264 to not reach all potential viewers. -Wikipedia keep an -updated summary of the current browser support.

- -

Not surprising, several people would prefer Google to keep -promoting H.264, and John Gruber -presents -the mind set of these people quite well. His rhetorical questions -provoked a reply from Thom Holwerda with another set of questions -presenting -the issues with H.264. Both are worth a read.

- -

Some argue that if Google is dropping H.264 because it isn't free, -they should also drop support for the Adobe Flash plugin. This -argument was covered by Simon Phipps in -todays -blog post, which I find to put the issue in context. To me it -make perfect sense to drop native H.264 support for HTML5 in the -browser while still allowing plugins.

- -

I suspect the reason this announcement make so many people protest, -is that all the users and promoters of H.264 suddenly get an uneasy -feeling that they might be backing the wrong horse. A lot of TV -broadcasters have been moving to H.264 the last few years, and a lot -of money has been invested in hardware based on the belief that they -could use the same video format for both broadcasting and web -publishing. Suddenly this belief is shaken.

- -

An interesting question is why Google is doing this. While the -presented argument might be true enough, I believe Google would only -present the argument if the change make sense from a business -perspective. One reason might be that they are currently negotiating -with MPEG-LA over royalties or usage terms, and giving MPEG-LA the -feeling that dropping H.264 completely from Chroome, Youtube and -Google Video would improve the negotiation position of Google. -Another reason might be that Google want to save money by not having -to pay the video tax to MPEG-LA at all, and thus want to move to a -video format not requiring royalties at all. A third reason might be -that the Chrome development team simply want to avoid the -Chrome/Chromium split to get more help with the development of Chrome. -I guess time will tell.

- -

Update 2011-01-15: The Google Chrome team provided -more -background and information on the move it a blog post yesterday.

-
-
- - - - Tags: english, standard, video. - -
-
-
-

RSS feed

-Created by Chronicle v3.2 +Created by Chronicle v3.7