https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&user=John7334&feedformat=atomProject VRM - User contributions [en]2024-03-29T12:51:57ZUser contributionsMediaWiki 1.39.5https://cyber.harvard.edu/projectvrm/?title=VRM_Workshop_2008&diff=5238VRM Workshop 20082011-09-16T19:58:08Z<p>John7334: </p>
<hr />
<div>The first ProjectVRM Workshop (tag [http://technorati.com/tag/vrm2008 vrm2008]) will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] at Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 14-15 July. The event will go from 9AM to 5:30 on both days.<br />
<br />
The purpose of the workshop is to bring people together and make progress on any number of VRM topics and projects. The workshop will be run as an "unconference" on the open space model, which means session topics will be chosen by participants. <span class="plainlinks">[http://www.thechiropractorsanfrancisco.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">san francisco chiropractor</span>] <br />
<br />
<br />
In open space there are no speakers or panels -- just participants, gathered to get work done and enjoy doing it. Participation includes contributing to the [[VRM Workshop 2008]] wiki.<br />
<br />
== Agenda/Session topics ==<br />
''This is a live agenda. The canonical copy is on the wall at Pound Hall, at the workshop.''<br />
<br />
'''''Session 1'''''<br />
* '''B:''' [[Open Social]]<br />
* '''D:''' [[VRM - Public Media]]<br />
<br />
'''''Session 2'''''<br />
* '''A:''' [[Volunteered Personal Information]]<br />
* '''B:''' [[Adoption Ambasadors]]<br />
* '''C:''' [[VRM - Health Care]]<br />
* '''D:''' [[Trust Service as VRM Foundation]]<br />
<br />
'''''Session 3'''''<br />
* '''A:''' [[VRM Organizational Issues]]<br />
* '''B:''' [[Government Relationship Management]]<br />
* '''C:''' [[Info Portability]] "The enemy of good is better." OAuth and OpenID Enterprise (non)adoption?<br />
* '''D:''' [[Intra-Enterprise VRM]] ([http://www.socialcustomer.com/2008/07/vrm-workshop-tr.html session notes])<br />
<br />
'''''Session 4'''''<br />
* '''A:''' [[VRM + Enterprises]]<br />
* '''B:''' Personal Address Manager [[PAM One night Stands]]<br />
* '''C:''' [[Employability + Recruitment]]<br />
* '''D:''' Relationships in Network [[The Mine!]]<br />
<br />
'''Day 2'''<br />
<br />
'''''Session 5'''''<br />
* '''A:''' [[VRM Compliance]]<br />
* '''B:''' [[R-Cards]] The Devil is in the Details<br />
* '''C:''' [[VRM as Disruptive Innovation]] Vendor Adoption and Best Fit Markets<br />
* '''D:''' [[IDFutures]] Interactive Community Future Mapping/Scenario Planning<br />
<br />
'''''Session 6'''''<br />
* '''A:''' Request to Give [[VRM + Charity]] <br />
* '''B:''' [[Customer Driven Markets]]<br />
<br />
'''''Session 7'''''<br />
* '''A:''' [[Product Representation]]<br />
* '''B:''' [[Rel Button + Media]]<br />
<br />
'''''Session 8'''''<br />
* '''B:''' [[Rel Button Standardization]]<br />
<br />
'''''Session 9:'''''<br />
* '''A:''' [[User-Driven Search]]<br />
<br />
== Registration ==<br />
<br />
The workshop is free. You can register through [http://vrmjuly2008workshop.eventbrite.com/ this EventBrite link]. Feel free to also add your name to the [[VRMWorkshop Attendees]] list.<br />
<br />
As of Sunday afternoon, it looks like we have about 50 attendees. I figure we might have a few more showing up from Berkman and other corners of Harvard and beyond. Looks like it's going to be a great group. - Doc<br />
<br />
== Schedule ==<br />
<br />
=== Sunday ===<br />
'''Non-hosted Dinner'''<br />
* Location: [http://www.google.com/search?hl=en&safe=off&pwst=1&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=changsho+cambridge&spell=1 Changsho Restaurant], on Mass Ave, up the street from Harvard.<br />
* Time: 7:30 (reservation made for 20 people - Doc)<br />
* Attendees (please add your name here):<br />
#[http://www.keithhopper.com Keith Hopper]<br />
#Iain Henderson<br />
<br />
#Chris Reynolds<br />
#Jan Searls<br />
#Brett McDowell<br />
#Adriana Lukas<br />
#Bart Stevens (TBC)<br />
#Maarten Smolders (TBC)<br />
#Stephen Lewis<br />
#Mary Ruddy<br />
#Rachel Schiff<br />
#Dean Landsman <br />
#Luk Vervenne<br />
#Davor Meersman<br />
#Britt Blaser<br />
#Kaliya Hamlin<br />
#Bob Frankston<br />
#[http://www.behavioraleconomics.net Sara Wedeman]<br />
<br />
* Social networking for those who come early at [http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=cambridge+common+restaurant Cambridge Common restaurant & bar], across the street on Massachusetts Avenue.<br />
* For help call Doc's cell: +1-805-705-9666.<br />
<br />
=== Monday ===<br />
<br />
Room: Pound 101<br />
<br />
Morning Refreshments - 8:30<br />
<br />
Opening 9-11 <br />
* Overview<br />
** Introductory remarks by Doc Searls and Phil Malone (of the Berkman Center and Harvard Law School), and a technology review by Joe Andrieu<br />
** Project reports (5 min each)<br />
* Marketplace of Ideas for specific projects (1.5 min each)<br />
* Personal introductions by everybody<br />
<br />
Sessions 11-4:30<br />
* 11-11:30 Agenda Making<br />
* 11:30-11:45 Lunch, which will be brought in<br />
* 11:45 - 12:45 - Session 1<br />
* 1:00-2:00 Session 2<br />
* 2:15-3:15 Session 3<br />
* 3:30-4:30 Session 4<br />
<br />
Sessions reporting to the group, 4:30-5:30<br />
<br />
In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large "spreadsheet" of times and session locations, a blackboard in the front of Pound 101, which will be our main room.<br />
[http://www.chenkrahman.com/ TV Online] [http://sakeena.net/ TV Online Indonesia] [http://www.anehuniklucu.com/ Berita Unik] [http://www.musikdahsyat.info/ Free Download Mp3] [http://www.gadgetsnew.us/ Gadgets New] [http://trendsandroid.com/ Trends Android] [http://63newstrends.com/ News Trends] [http://seo.zianka.com/ Media Online News] [http://www.zianka.com/ Bordir Tasikmalaya] [http://www.anggabatik.com/ Batik Tasikmalaya] [http://blog-rahman.blogspot.com/ Mivo TV] [http://63cell.blogspot.com/ Handphone Terbaru] [http://sakee-na.blogspot.com/ Berita Terkini] [http://cr-zianka.blogspot.com/ CR-ZiaNka] [http://ismagianti.blogspot.com/ Blogger Tasik] [http://chenk-rahman.blogspot.com/ Free Download Software] [http://zianka4art.blogspot.com/ Bordir Tasik] [http://s4keena.blogspot.com/ ZiaNka] [http://chenkrahman.blogdetik.com/ Dunia Maya] <br />
One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group.<br />
<br />
7:00PM:<br />
'''Non-hosted Dinner'''<br />
* Location: TBD<br />
* Time: TBD<br />
* Attendees (please add your name here if you plan to attend so we can get reservations):<br />
** [http://blog.joeandrieu.com Joe Andrieu]<br />
** Iain Henderson<br />
** Stephen Lewis<br />
** Bart Stevens<br />
** Maarten Smolders<br />
** [http://twitter.com/ekivemark Mark Scrimshire]<br />
** [http://searls.com Doc Searls]<br />
** Mary Ruddy<br />
** Eve Maler<br />
** Luk Vervenne<br />
** Davor Meersman<br />
** Gerald Beuchelt<br />
** [http://www.socialcustomer.com Christopher Carfi]<br />
** [http://www.openliberty.org Asa Hardcastle]<br />
** [http://xri.net/=paul.trevithick =paul.trevithick]<br />
** [http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO]<br />
** [http://www.finca-portugal.de Portugal]<br />
<br />
=== Tuesday ===<br />
<br />
Morning Refreshments - 8:15<br />
<br />
Opening group gathering (adding or moving sessions, reports of insights from yesterday) - 8:30-9:00<br />
<br />
Sessions: 9am-4pm<br />
* 9:00-10:00 Session 5<br />
* 10:10-11:10 Session 6<br />
* 11:20-12:30 Session 7<br />
* 12:30-1:45 LUNCH - Groups go off to local eateries<br />
* 1:45-2:45 Session 7<br />
* 3:00-4:00 Session 8<br />
<br />
Closing session, summarizing both days, personal comments, more - 4:00-5:30<br />
<br />
==Space==<br />
<br />
We have three classrooms booked, all in Pound Hall. Two rooms have a power outlet at every seat. The third has wall outlets. In each the seating is arranged in a horseshoe shape, so everybody can face everybody else. <br />
<br />
If we need additional small session spaces, there are plenty of those out on the lawns and in the halls and public seating areas amongst nearby buildings at the Law School. We'll make room on the session "spreadsheet" for these, so we're ready if the need arises.<br />
<br />
== Possible Topics ==<br />
<br />
There are many. Here is a list to get us started. Add or subtract whatever you like...<br />
<br />
* The Mine! (Adriana Lukas)<br />
* Volunteered Personal Information (Iain Henderson)<br />
* RelButton -- and first use challenge: a biz model for public media (Doc Searls)<br />
* User-driven Search (Joe Andrieu)<br />
* r-cards (Paul Trevithick) <br />
* VRM and health care<br />
* VRM and employability (Luk Vervenne)<br />
* VRM and social web stuff (Kevin Marks)<br />
* VRM standards, policies and practices (Brett McDowell)<br />
* VRM and TiddlyWiki<br />
* VRM + (rather than vs.)CRM (VRM<>CRM dialogue, digital conversations: next step in the maturity cycle?)<br />
* VRM and legal openings, hurdles, models and precedents (Renee Lloyd)<br />
* Trust architecture for securely shared services involving personal information (www.tas3.eu, Luk Vervenne)<br />
* VRM and the reaction/acceptancce in European Enterprise (Bart Stevens)<br />
* VRM Perception by BigBiz in the USA (Deb Schultz)<br />
* VRM Vendor Adoption, market "best fit", and disruption (Keith Hopper)<br />
* VRM and multi-channel opportunities for manufacturers [Amazon - Sony use case], (Mike Kirkwood)<br />
* VRM and product representation (Davor Meersman)<br />
<br />
== Getting There ==<br />
<br />
Pound Hall is located on the Harvard campus at 1563 Massachusetts Avenue, within the Law School. Some resources --<br />
<br />
* [http://www.law.harvard.edu/about/contact/images/law_map.jpg Harvard Law map] <br />
* [http://www.portlanddentistdds.com portland dentist]<br />
* [http://www.capricejewellery.com/ ювелирный интернет магазин]<br />
* [http://www.injurylawyer-sanfrancisco.com san francisco personal injury lawyer]<br />
<br />
Parking is a hassle, so we highly recommend taking public transportation. Fortunately, the Boston Area has some of the best public transportation in the U.S. The Harvard Campus is adjacent to Harvard Square, which is a stop on the Red Line of the "T", Boston's subway system. The Red Line is the best of all the "T" lines. Trains roll through every stop only few minutes apart, and the trains are fast. If you can find accommodations near a Red Line stop, you'll be in great shape. Cambridge area stops are Alewife, Davis, Porter, Harvard, Central and Kendall. In Boston the near ones are Charles/MGH, Park, Government Center and South Station.<br />
<br />
Getting to Pound Hall:<br />
<br />
From the Harvard "T" station go up the stairs to "Church Street." At the top of the stairs, turn right to walk across Church (and past the church itself), then up "Mass Ave" past Cambridge Common (the large park on the left). At the next light (Waterhouse Street), cross over to the Harvard side of Mass Ave, then turn left to continue north. Pound Hall will come up on your right, just before a big construction project. A granite sign says "HARRVARD LAW SCHOOL." Look for the workshop in the center of the ground floor. If you walk fast you can make it in 5 minutes from the "T".<br />
<br />
== Participation over the Net ==<br />
<br />
We have a [http://direct2dell.com/one2one/archive/tags/IdeaStorm_3A00_+Ideas+in+Action/default.aspx video stream].<br />
<br />
We also have an IRC channel via Freenode, at #VRM.<br />
<br />
== Materials ==<br />
<br />
[http://searls.com/doc/vrm/2008_07_15_vrm.ppt Doc's VRM slides on Day 2 (.ppt)]<br />
<br />
[http://searls.com/doc/vrm/2008_07_15_doc_vrm_talk/ Doc's VRM slides on Day 2 (.html gallery)]<br />
<br />
[http://www.socialcustomer.com/2008/07/vrm-workshop-tr.html VRM Workshop Trip Report] by [http://socialcustomer.com Christopher Carfi]<br />
<br />
[http://ekive.blogspot.com/2008/07/vrm-retrospective-making-adoption-easy.html VRM - A retrospective and some thoughts on making adoption easy] by Mark Scrimshire (@[http://twitter.com/ekivemark ekivemark])<br />
<br />
==Sponsors==<br />
[http://www.thesanfranciscolocksmith.com/ locksmith san francisco] <br />
[http://www.sanfranciscodentistdds.com/ dentist san francisco] <br />
[http://www.yoursanfranciscoplumber.com/ plumber san francisco] <br />
[http://www.bayarea-fishing.com/ Bay area fishing charter]<br />
[http://www.spas-sanfrancisco.com/ spa san francisco] <br />
[http://www.thesanfranciscomovers.com/ movers san francisco] <br />
[http://www.sanfrancisco-weddingphotographers.com/ wedding photographer san francisco]<br />
[http://www.oaklanddentistdds.com/ dentists oakland]<br />
[http://www.sanjosedentist.com/ dentist san jose]<br />
[http://www.thehouston-plumbers.com/ plumber houston]<br />
[http://www.arabaoyunlarimiz.gen.tr/ araba oyunları]<br />
[http://www.torontoraiders.com/ Sports]<br />
[http://www.outdoorlightsgalore.com/outdoor-security-lighting Outdoor Security Lighting]<br />
[http://www.outdoorlightsgalore.com/landscape-lighting/outdoor-garden-lights Outdoor Garden Lights]<br />
[http://www.outdoorlightsgalore.com/ Landscape Lighting]<br />
[http://bestpelletstoves.blogspot.com/ Best Pellet Stoves]</div>John7334https://cyber.harvard.edu/projectvrm/?title=ListenLog&diff=5120ListenLog2011-09-03T17:09:07Z<p>John7334: </p>
<hr />
<div>[[Category:Media Logging]]<br />
<br />
== Overview ==<br />
<br />
The VRM ListenLog is a proposed method for integrating simple user-driven functionality into an online audio player device or application. A ListenLog is a consolidated and documented history of an individual's online listening activity. It is simply a recorded activity log, in a standard and open format, capturing an individual's listening actions from multiple online applications. The ListenLog is unique in that its aim is to give the user the ability to accumulate and control the use of their listener activity data. The data is the user's. It does not belong to any vendor or intermediary. The user alone should have control over where the data lives, what applications write to it, what gets logged, who to share it with, and how it can be used. The ListenLog concept was devised in part for the [http://publicradiotuner.com Public Radio Tuner iPhone project], where it is first being introduced. Plans are to put it on other handhelds as well. (And, as an open source project, there is nothing to prevent others from doing what they like with it.)<br />
<br />
== Purpose & Deployment ==<br />
ListenLog, or [[Listen Log]] is a form of [[Media Logging]]. It is required for [[EmanciPay]] to work. EmanciPay is a new business model for otherwise free media goods -- one that sharply reduces the frictions involved in paying for media. By increasing the number of people who pay for free media, PayChoice also helps stigmatize non-payment for those goods.<br />
<br />
Logging of listening is required to answer all these common questions:<br />
#What was that (program, segment, piece of music)?<br />
#Who was that (host, guest)?<br />
#Who produced that (program, segment, piece of music)?<br />
#When and where did I listen to that?<br />
#How often did I (listen to, watch or read) that in the past?<br />
#Do I have a relationship with the source? (Such as membership, or past transactions.)<br />
<br />
ListenLog is a simple utility that does nothing more than record listening data for the user. It will store it in a form that can be crunched in many ways and for many purposes -- all by the user's choice and at the user's discretion. It will be data that can go in any database or spreadsheet. It can also be shared in a selectively disclosed way. (See [[VRM Principles]].) This will make possible a marketplace for third-party services that help both listeners and the institutions with which they relate. (Starting with stations, but also including program producers, artists and others.)<br />
<br />
With ListenLog data, listeners can make fully informed choices about how they support streams, podcasts and on-demand sources of programming.<br />
<br />
Listeners can also form better relationships with stations and program sources. Membership can come to mean far more than serving as a future target for pitches and billing.<br />
<br />
Both Media Logging and EmanciPay are being pioneered with the Public Radio Tuner, which is currently being developed by [[http://prx.org PRX]] and other partners, including NPR and ProjectVRM at the [[http://cyber.law.harvard.edu Berkman Center]]. Neither, however, are to be limited to the iPhone, or any other platform. But the iPhone and the Public Radio Tuner are where we are starting.<br />
<br />
There are challenges posed both by the pioneering nature of the work and the limitations of the iPhone.<br />
<br />
For example, the iPhone has a tiny memory for data and no persistent and user- (or program-) accessible data store on the host computer with which it syncs through iTunes. But iPhone does provide means for that data to be stored remotely, in a trusted "cloud." For this purpose, PRX has created ListenLog.org as a site/service for storing each user's data and making it available through standard web service interfaces.<br />
<br />
Because this distances the user's data from the user's devices, and requires trust in PRX (or any host), questions of trust are naturally raised. These are the same issues raised by any cloud service, including Gmail and Amazon S3. Establishing trust mechanisms -- both technical and contractual -- are non-trivial. But they are also essential for laying the groundwork required for this new business model to work.<br />
<br />
== History ==<br />
While tracking listener behavior data is not a new concept, the ListenLog is a novel approach to deploying early VRM functionality. While a simple activity log might not appear as the killer app, it succeeds by putting in place a small piece of user-driven infrastructure into a larger application - one with a promise of relatively wide distribution. Since this infrastructure component will write, store, and share listener activity in an open and standard format, we hope that such a log will become significantly more useful as other devices and tools leverage the standard to increase what an individual can do with their ListenLog data. This type of sideways approach holds the promise of planting the seeds of VRM onto lots of devices without requiring the primary application functionality (i.e. audio listening) be purely user-driven.<br />
<br />
A user-driven activity log works well for an application that pulls together audio streams and files from a number of different sources. Of course, online audio providers (vendors in the VRM model) can already track and aggregate listening behavior data, but only for the audio they control. When the user acts as the sole point of integration, pulling together audio from multiple sources, their own consolidated log becomes uniquely powerful. Only when the listener is the point of integration does such an approach yield a new type of value.<br />
<br />
== Specifics ==<br />
<br />
Initially, the ListenLog will capture online audio stream and file listening behavior occurring through a specific application and device in a standard format (see the [[ListenLog XDI]] page for an example). At minimum, the log will capture audio stream/file identification, user agent, listen start time, listen duration and device location information. Extending this data to incorporate unique device IDs, audio meta data, rating (e.g. thumbs-up/down), referral, or other application behavior data is under consideration.<br />
<br />
The application supporting ListenLog recording capability will host the minimum of user-facing functionality. Specifically, the individual user will be able to choose a digital identity(s) with which to associate their listening data, and can also choose where the data is stored, as it will be dynamically written by the device application to any ListenLog standards compliant service provider (host).<br />
<br />
A separate ListenLog Service interface, perhaps integrated with the ListenLog storage provider, will enable the user to choose if and how to share their ListenLog data, either anonymously or as associated with digital identities. For example, an individual may choose to share all data publicly and anonymously. All users selecting this option would, in aggregate, create a single, public "firehose" feed of all listening activity. It is our hope that third-party developers will offer user-driven functionality based on your ListenLog functionality, helping you share selected data conditionally with vendors for example, or providing agnostic recommendations based on your listening habits.<br />
<br />
== Enabled Functionality ==<br />
<br />
The power of ListenLog is not in the log itself, but what the activity history might enable. As an open standard, the ListenLog format will enable third-party relationship services to be developed for users to interact with. Possible examples include:<br />
<br />
==== [[EmanciPay]] ====<br />
By keeping track of what files, tracks and programs are listened to, users can more easily allocate voluntary payments across properties without resorting to the transaction burden of micropayments.<br />
<br />
==== Detached Recommendations ====<br />
<br />
Audio recommendation systems are typically integrated into a single vendor offering and based on your (and your peer's) internal listening behavior. A third party recommendation system could avoid lock-in of data and stimulate competition from pure-play recommendation systems. Additionally, listening behavior would be aggregated across devices, applications, and formats to provide a greater depth and breadth of material to work from.<br />
<br />
==== Personal History Search ====<br />
<br />
The ability to apply an "I've listened to this" filter when you perform an audio search.<br />
<br />
<br />
== More ==<br />
* [[ListenLog Meeting Notes]]<br />
* [[ListenLog Identity]]<br />
* [[ListenLog XDI]]<br />
* [[Listen Log]] (a higher-level more general page on this topic)<br />
[http://www.sanfrancisco-weddingphotographers.com/ wedding photographer san francisco]<br />
[http://phonyphonecalls.blogspot.com/ reverse cell phone lookup]<br />
[http://www.bayarea-fishing.com/ Bay area fishing]<br />
[http://www.spas-sanfrancisco.com/ spa san francisco] <br />
[http://www.thesanfranciscolocksmith.com/ locksmith san francisco]<br />
[http://www.thehouston-plumbers.com/ plumber houston] <br />
[http://boilswiki.com/ what is boil]<br />
[http://www.yoursanfranciscoplumber.com/ plumber san francisco] <br />
[http://www.sanjosedentist.com/ dentist san jose]<br />
[http://gynecomastiawiki.com/ gynecomastia]<br />
[http://www.thesanfranciscomovers.com/ movers san francisco] <br />
[http://www.theseattleplumbers.com/ seattle plumber]<br />
[http://www.yourseattlelocksmiths.com seattle locksmith]<br />
[http://www.cnatrainingsuccess.com cna training online]<br />
[http://www.findacellphoneuser.com/ reverse cell phone lookup]<br />
[http://www.outdoorlightsgalore.com/ Landscape Lighting]</div>John7334https://cyber.harvard.edu/projectvrm/?title=ListenLog&diff=5103ListenLog2011-09-01T17:44:11Z<p>John7334: </p>
<hr />
<div>[[Category:Media Logging]]<br />
<br />
== Overview ==<br />
<br />
The VRM ListenLog is a proposed method for integrating simple user-driven functionality into an online audio player device or application. The ListenLog is a consolidated and documented history of an individual's online listening activity[http://www.chenkrahman.com/ .] It is simply a recorded activity log, in a standard and open format, capturing an individual's listening actions from multiple online applications[http://sakeena.net/ .] The ListenLog is unique in that its aim is to give the user the ability to accumulate and control the use of their listener activity data. The data is the user's. It does not belong to any vendor or intermediary[http://www.musikdahsyat.info/ .] The user alone should have control over where the data lives, what applications write to it, what gets logged, who to share it with, and how it can be used[http://blog-rahman.blogspot.com/ .] The ListenLog concept was devised in part for the [http://publicradiotuner.com Public Radio Tuner iPhone project], where it is first being introduced[http://63cell.blogspot.com/ .] Plans are to put it on other handhelds as well. (And, as an open source project, there is nothing to prevent others from doing what they like with it.)<br />
<br />
== Purpose & Deployment ==<br />
ListenLog, or [[Listen Log]] is a form of [[Media Logging]]. It is required for [[EmanciPay]] to work. EmanciPay is a new business model for otherwise free media goods -- one that sharply reduces the frictions involved in paying for media. By increasing the number of people who pay for free media, PayChoice also helps stigmatize non-payment for those goods.<br />
<br />
Logging of listening is required to answer all these common questions:<br />
#What was that (program, segment, piece of music)?<br />
#Who was that (host, guest)?<br />
#Who produced that (program, segment, piece of music)?<br />
#When and where did I listen to that?<br />
#How often did I (listen to, watch or read) that in the past?<br />
#Do I have a relationship with the source? (Such as membership, or past transactions.)<br />
<br />
ListenLog is a simple utility that does nothing more than record listening data for the user. It will store it in a form that can be crunched in many ways and for many purposes -- all by the user's choice and at the user's discretion. It will be data that can go in any database or spreadsheet. It can also be shared in a selectively disclosed way. (See [[VRM Principles]].) This will make possible a marketplace for third-party services that help both listeners and the institutions with which they relate. (Starting with stations, but also including program producers, artists and others.)<br />
<br />
With ListenLog data, listeners can make fully informed choices about how they support streams, podcasts and on-demand sources of programming.<br />
<br />
Listeners can also form better relationships with stations and program sources. Membership can come to mean far more than serving as a future target for pitches and billing.<br />
<br />
Both Media Logging and EmanciPay are being pioneered with the Public Radio Tuner, which is currently being developed by [[http://prx.org PRX]] and other partners, including NPR and ProjectVRM at the [[http://cyber.law.harvard.edu Berkman Center]]. Neither, however, are to be limited to the iPhone, or any other platform. But the iPhone and the Public Radio Tuner are where we are starting.<br />
<br />
There are challenges posed both by the pioneering nature of the work and the limitations of the iPhone.<br />
<br />
For example, the iPhone has a tiny memory for data and no persistent and user- (or program-) accessible data store on the host computer with which it syncs through iTunes. But iPhone does provide means for that data to be stored remotely, in a trusted "cloud." For this purpose, PRX has created ListenLog.org as a site/service for storing each user's data and making it available through standard web service interfaces.<br />
<br />
Because this distances the user's data from the user's devices, and requires trust in PRX (or any host), questions of trust are naturally raised. These are the same issues raised by any cloud service, including Gmail and Amazon S3. Establishing trust mechanisms -- both technical and contractual -- are non-trivial. But they are also essential for laying the groundwork required for this new business model to work.<br />
<br />
== History ==<br />
While tracking listener behavior data is not a new concept, the ListenLog is a novel approach to deploying early VRM functionality. While a simple activity log might not appear as the killer app, it succeeds by putting in place a small piece of user-driven infrastructure into a larger application - one with a promise of relatively wide distribution. Since this infrastructure component will write, store, and share listener activity in an open and standard format, we hope that such a log will become significantly more useful as other devices and tools leverage the standard to increase what an individual can do with their ListenLog data. This type of sideways approach holds the promise of planting the seeds of VRM onto lots of devices without requiring the primary application functionality (i.e. audio listening) be purely user-driven.<br />
<br />
A user-driven activity log works well for an application that pulls together audio streams and files from a number of different sources. Of course, online audio providers (vendors in the VRM model) can already track and aggregate listening behavior data, but only for the audio they control. When the user acts as the sole point of integration, pulling together audio from multiple sources, their own consolidated log becomes uniquely powerful. Only when the listener is the point of integration does such an approach yield a new type of value.<br />
<br />
== Specifics ==<br />
<br />
Initially, the ListenLog will capture online audio stream and file listening behavior occurring through a specific application and device in a standard format (see the [[ListenLog XDI]] page for an example). At minimum, the log will capture audio stream/file identification, user agent, listen start time, listen duration and device location information. Extending this data to incorporate unique device IDs, audio meta data, rating (e.g. thumbs-up/down), referral, or other application behavior data is under consideration.<br />
<br />
The application supporting ListenLog recording capability will host the minimum of user-facing functionality. Specifically, the individual user will be able to choose a digital identity(s) with which to associate their listening data, and can also choose where the data is stored, as it will be dynamically written by the device application to any ListenLog standards compliant service provider (host).<br />
<br />
A separate ListenLog Service interface, perhaps integrated with the ListenLog storage provider, will enable the user to choose if and how to share their ListenLog data, either anonymously or as associated with digital identities. For example, an individual may choose to share all data publicly and anonymously. All users selecting this option would, in aggregate, create a single, public "firehose" feed of all listening activity. It is our hope that third-party developers will offer user-driven functionality based on your ListenLog functionality, helping you share selected data conditionally with vendors for example, or providing agnostic recommendations based on your listening habits.<br />
<br />
== Enabled Functionality ==<br />
<br />
The power of ListenLog is not in the log itself, but what the activity history might enable. As an open standard, the ListenLog format will enable third-party relationship services to be developed for users to interact with. Possible examples include:<br />
Jewellery: [http://www.capricejewellery.com/ ювелирный интернет магазин]<br />
<br />
==== [[EmanciPay]] ====<br />
By keeping track of what files, tracks and programs are listened to, users can more easily allocate voluntary payments across properties without resorting to the transaction burden of micropayments.<br />
<br />
==== Detached Recommendations ====<br />
<br />
Audio recommendation systems are typically integrated into a single vendor offering and based on your (and your peer's) internal listening behavior. A third party recommendation system could avoid lock-in of data and stimulate competition from pure-play recommendation systems. Additionally, listening behavior would be aggregated across devices, applications, and formats to provide a greater depth and breadth of material to work from.<br />
<br />
==== Personal History Search ====<br />
<br />
The ability to apply an "I've listened to this" filter when you perform an audio search.<br />
<br />
<br />
== More ==<br />
* [[ListenLog Meeting Notes]]<br />
* [[ListenLog Identity]]<br />
* [[ListenLog XDI]]<br />
* [[Listen Log]] (a higher-level more general page on this topic)<br />
[http://www.sanfrancisco-weddingphotographers.com/ wedding photographer san francisco]<br />
[http://phonyphonecalls.blogspot.com/ reverse cell phone lookup]<br />
[http://www.bayarea-fishing.com/ Bay area fishing]<br />
[http://www.spas-sanfrancisco.com/ spa san francisco] <br />
[http://www.thesanfranciscolocksmith.com/ locksmith san francisco]<br />
[http://www.digitalproductsavenue.com ebooks with resale rights]<br />
[http://www.coppervalleycustomhomes.com custom home builders]<br />
[http://www.thehouston-plumbers.com/ plumber houston] <br />
[http://boilswiki.com/ what is boil]<br />
[http://www.yoursanfranciscoplumber.com/ plumber san francisco] <br />
[http://www.sanjosedentist.com/ dentist san jose]<br />
[http://gynecomastiawiki.com/ gynecomastia]<br />
[http://www.thesanfranciscomovers.com/ movers san francisco] <br />
[http://www.theseattleplumbers.com/ seattle plumber]<br />
[http://www.yourseattlelocksmiths.com seattle locksmith]<br />
[http://www.findacellphoneuser.com/ reverse cell phone lookup]<br />
[http://www.outdoorlightsgalore.com/outdoor-security-lighting Outdoor Security Lights]<br />
[http://www.outdoorlightsgalore.com/landscape-lighting-ideas landscape lighting ideas]</div>John7334