Comments on: Mainframe to mobile http://commonplace.net/2010/02/mainframe-to-mobile/ Library2.0 and beyond Mon, 23 Aug 2010 10:53:17 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jamie Cox http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-18362 Jamie Cox Mon, 23 Aug 2010 10:53:17 +0000 http://commonplace.net/?p=983#comment-18362 During the green-screen era, there was indeed email. That goes back to the 1970s. Also, our local library had the old green-screen computer terminals for client catalog access. It was a bit unusual -- allowing the general public to touch a computing device -- but it worked pretty well. The system worked well enough that it lasted well into the PC era after such terminals were rare anywhere else. During the green-screen era, there was indeed email. That goes back to the 1970s. Also, our local library had the old green-screen computer terminals for client catalog access. It was a bit unusual — allowing the general public to touch a computing device — but it worked pretty well. The system worked well enough that it lasted well into the PC era after such terminals were rare anywhere else.

]]> By: Go Mobile (màj 01/08/2010) « pintiniblog http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-17661 Go Mobile (màj 01/08/2010) « pintiniblog Sun, 01 Aug 2010 21:00:13 +0000 http://commonplace.net/?p=983#comment-17661 [...] 1. Mainframe to mobile (Common Place, 16/02/2010) [...] [...] 1. Mainframe to mobile (Common Place, 16/02/2010) [...]

]]> By: Bruno Hazelwood http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-17654 Bruno Hazelwood Sun, 01 Aug 2010 19:26:02 +0000 http://commonplace.net/?p=983#comment-17654 A lot of people are resorting to many different types of this, as conventional methods have become more complicated and displaying more unwanted side effects. your post explores a few of these different sorts of methods and ways in which the benefit us, thanks! <a href="http://makemusiconlinenow.com" rel="nofollow">thanks</a> A lot of people are resorting to many different types of this, as conventional methods have become more complicated and displaying more unwanted side effects. your post explores a few of these different sorts of methods and ways in which the benefit us, thanks! thanks

]]> By: Go Mobile (màj 14/04/2010) « pintiniblog http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-15319 Go Mobile (màj 14/04/2010) « pintiniblog Wed, 14 Apr 2010 16:00:25 +0000 http://commonplace.net/?p=983#comment-15319 [...] 1. Mainframe to mobile (Common Place, 16/02/2010) [...] [...] 1. Mainframe to mobile (Common Place, 16/02/2010) [...]

]]> By: Things I need to learn more about – Stephen's Lighthouse http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-8978 Things I need to learn more about – Stephen's Lighthouse Wed, 03 Mar 2010 21:42:58 +0000 http://commonplace.net/?p=983#comment-8978 [...] 1: Mainframe to Mobile Part 2: Mobile app or mobile web? Part 3: [...] [...] 1: Mainframe to Mobile Part 2: Mobile app or mobile web? Part 3: [...]

]]> By: Bibliotheken, Google en zoeken in Februari 2010 « Dee'tjes http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-8587 Bibliotheken, Google en zoeken in Februari 2010 « Dee'tjes Sun, 28 Feb 2010 18:37:14 +0000 http://commonplace.net/?p=983#comment-8587 [...] Mainframe to mobile interessante serie op CommonPlace.Net Deel 2:  Mobile app or mobile web? [...] [...] Mainframe to mobile interessante serie op CommonPlace.Net Deel 2:  Mobile app or mobile web? [...]

]]> By: Lukas Koster http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-7938 Lukas Koster Wed, 17 Feb 2010 12:54:38 +0000 http://commonplace.net/?p=983#comment-7938 Till, thanks. And yes: connecting mobile apps and distributed data (linked data/semantic web) will be very prominent in the (planned) third post about Mobile Services. It's good to get confirmation for that approach! I already mentioned this model in a previous post http://commonplace.net/2010/01/mobile-reading/ Lukas Till, thanks. And yes: connecting mobile apps and distributed data (linked data/semantic web) will be very prominent in the (planned) third post about Mobile Services. It’s good to get confirmation for that approach!

I already mentioned this model in a previous post http://commonplace.net/2010/01/mobile-reading/

Lukas

]]> By: till http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-7937 till Wed, 17 Feb 2010 12:50:33 +0000 http://commonplace.net/?p=983#comment-7937 Hmmm, I feel you look at all the technology changes you describe with a static "distribution" model in mind: Disseminate data/content from a central "production/storage point" to distributed consumers. But with the hyperlinked Web(!) there are alternative distribution models... Content providers (newspapers, publishers, music industry...) that base their business on that classic distribution model still struggle hard with the Web. And libraries do, too (I think, at least part of the "library 2.0" hype is related to that). As you write, with those mobile apps, you have that pre-Web client-server model again: One central content repository you access through a one way distribution channel, sometimes offering a limited, controlled back channel, sometimes extended by controlled linking to other ressources. I think, that's why classic content providers (like newspapers) love apps, isn't it? It fits their classic business model. No need to change. I totally agree with @ostephens, who wrote "Apps are not about technology, they are about a business model" that tweet: http://twitter.com/ostephens/status/7982515485. It's like AOL and the Web, different business models. Who is still there? How will libraries deal with that? I am courious, if you will look at these aspects of apps in one of the following parts of this article series. Hmmm, I feel you look at all the technology changes you describe with a static “distribution” model in mind: Disseminate data/content from a central “production/storage point” to distributed consumers. But with the hyperlinked Web(!) there are alternative distribution models…
Content providers (newspapers, publishers, music industry…) that base their business on that classic distribution model still struggle hard with the Web. And libraries do, too (I think, at least part of the “library 2.0″ hype is related to that).
As you write, with those mobile apps, you have that pre-Web client-server model again: One central content repository you access through a one way distribution channel, sometimes offering a limited, controlled back channel, sometimes extended by controlled linking to other ressources.
I think, that’s why classic content providers (like newspapers) love apps, isn’t it? It fits their classic business model. No need to change. I totally agree with @ostephens, who wrote “Apps are not about technology, they are about a business model” that tweet: http://twitter.com/ostephens/status/7982515485. It’s like AOL and the Web, different business models. Who is still there?
How will libraries deal with that?
I am courious, if you will look at these aspects of apps in one of the following parts of this article series.

]]> By: Jakob http://commonplace.net/2010/02/mainframe-to-mobile/comment-page-1/#comment-7907 Jakob Tue, 16 Feb 2010 20:54:17 +0000 http://commonplace.net/?p=983#comment-7907 Thanks for the comprehensive overview! I'd add the invention of stable URLs which most library system vendors have not catched for years. Thanks for the comprehensive overview! I’d add the invention of stable URLs which most library system vendors have not catched for years.

]]>