Bislet bad web site

Trying to find information about the Bislet swimming pool. The bisletbad.no site is parked. The bisletbad.com web site is unmaintained (no opening hours, incorrect phone number) but the swimming pool is functionning and isn't that bad !

Looks like the new owners are in some kind of domain dispute with the previous ones...

The whois entry of the .com site contains:

   Domain Name: BISLETBAD.COM

   Registrar: ENOM, INC.

   Whois Server: whois.enom.com

   Referral URL: http://www.enom.com

   Name Server: NS3.NETBOX.NO

   Name Server: NS4.NETBOX.NO

   Name Server: NS5.NETBOX.NO

   Status: clientTransferProhibited

   Updated Date: 23-sep-2010

   Creation Date: 23-sep-2010

   Expiration Date: 23-sep-2011



Domain name: bisletbad.com



Registrant Contact:

   BISLET BAD LIMITED

   Dawson E. Hamilton ()

   

   Fax: 

   Pilestredet 60

   995901099

   Oslo, Oslo 0167

   NO



Administrative Contact:

   BISLET BAD LIMITED

   Dawson E. Hamilton (pt@jamfit.no)

   +47.23333810

   Fax: 

   Pilestredet 60

   995901099

   Oslo, Oslo 0167

   NO



Technical Contact:

   BISLET BAD LIMITED

   Dawson E. Hamilton (pt@jamfit.no)

   +47.23333810

   Fax: 

   Pilestredet 60

   995901099

   Oslo, Oslo 0167

   NO



Status: Locked

   

Creation date: 23 Sep 2010 16:03:00

Expiration date: 23 Sep 2011 11:03:00

The old Norwegian company points to http://w2.brreg.no/enhet/sok/detalj.jsp?orgnr=995901099 and the company is non existant.

This has been ongoing for months. Why don't they set up a temporary site with basic information (phone number, prices, opening hours) until they resolve their dispute.

Trafikanten & open data update - things happened

Following up my post from about 2 months ago, I was announcing good news on the way. As you may already know, the bigs news is finally out there: Trafikanten has opened up their data!

I would like to thank the various people involved in getting this in place, in no particular order, Bent Flyen, Christopher Worren and Jarl Eliassen from Trafikanten, Bjorn Tennøe from Iterate, Marius Mårnes Mathiesen from Shortcut and the numerous people whose name I've forgot along the way.

What's next ?

* I hope that now some people will come up with cool things building upon this free data & API

* yesterday I found farebot for android, and I would love to see the Flexus card data supported by similar applications. I already contacted trafikanten, and will follow up here.

Trafikanten & open data update - things are happening!

I am just back from a meeting with Trafikanten (where I met the Advisor for realtime data and the QA responsible). The meeting has been from my point of view pretty constructive. We've then spent a bit of time to better understand our needs. We've exchanged thoughts around their current data offering, the licensing, etc and came up with ideas that I think will make many people happy. I won't say much more for the moment, as I am waiting for them to actually implement the ideas we talked about, but as soon as I know more, you'll be posted. I would like again to thank Trafikanten for their time and I really wish them good luck with their changes. Exiting times!

Trafikanten: meeting on license and open data next week

A follow up after my last post on the topic of opendata/trafikanten. It seems that being constructive and open to new possibilities has some results. Trafikanten is revising their API license, in oart to be attractive to smaller actors as well. They invited me to a meeting on the 20th of January to present and discuss their new license proposal.

If you have some meaning on the topic, feel free to contact me, publicly or privately.

Opendata @ Trafikanten, answer strategies

Obviously (and unfortunately) Trafikanten isn't willing to cooperate to open up their data.

I have to answer them within about 10 days and I am left with different strategies:

1. abandon
   
2. confrontation
   
3. negotiate
   
4. workaround
   

The first question one has to ask oneself is of course whether to abandon or not. Is this worth our time? I will have to ponder that.

The second option is go on with the confrontation. It's clear to say that now, using lawyers to defend themselves, Trafikanten isn't currently very open for negotiation. Hard to say who caused the situation, and it's not even important. It's just a fact. I am pretty sure I can find arguments to counter their answer, or even find things that as a public company they are obliged to do causing them problems. I am not very interested in that, and I would prefer negotiation/cooperation.

Cooperation, a WIN/WIN solution would have been the best. Making Trafikanten truly a leader in open data in Norway, finding a gradual path that leads for opening their data little by little. It might be possible. But right now I don't know. The tone is set and probably hard to change and they've made it clear they didn't want to help small companies nor their users. But I am optimist by nature, so why not?

As for the last solution, workaround, I am also sure I can find a technical solution that solves my issue independently of them. Trafikanten has a public API, and I can probably build the DB of the interesting data based on it. It might be completely inefficient, maybe illegal, incomplete, but I will sure be able to gather part of this data.

Open Trafikanten data, update

A little update after my latest encouraging post:



It doesn't seem that Trafikanten is ready to open some of its data. They are on the defensive now... I have 3 weeks to answer what I can answer to that mail.

Too bad. I think we could have worked towards an open and better service for Norway.

Open Trafikanten data, a better future ?

Bjørn started a Facebook group to push for open communications from Trafikanten and NSB. I am all for it.

Last year I tried to get access to similar information from Trafikanten and Ruter. I didn't manage to get anything.

Here's a few extract from communications I had with them.

Python Oslo Group

Today we hold our first meeting of the new Oslo Python/Django discussion group. Feel free to join! We will try to meet once a month.