HIMSIG20081218
Liberty Alliance Project
VPI SIG
Teleconference Meeting Notes
December 18, 2008
1:00pm-2:05pm EDT
Author: Kurt Kolok
Attendance:
Joe Andrieu, Switchbook
Bill Washburn, XDI
Eve Maler, Sun
Brett McDowell, Liberty Staff
Joni Brennan, Liberty Staff
Kurt Kolok, Liberty Staff
Agenda:
Review Iain’s use case template re: car buying process.
- build out a few more use cases over and above the car buying one, and Bill's vacation one.
- discuss the extent to which the issues and areas of guess work and waste are common across all products and services, or where the splits would be.
- focus most on building out the user description version of 'the tools i'd need to improve things'.
It would be helpful to put out best practices documents for buyers.
We should look at Iain’s document; he specified things that should be ‘must haves’ and others that are ‘nice to haves’. We should prioritize the ‘must haves’ initially.
What things are available in new cars that I might not know about until I start researching cars? Financial piece would be a separate item altogether.
Brett: Boolean operator and priority could be another attribute bound to the attributes in the use case. There is logic and there are attributes and then how it is to be controlled. There are things that you know in the beginning and things you learn along the way. If we go through Iain’s 10 points they appear to be implied architecture but they could be subject to debate (page 6/7 ‘key elements’). There will be a repository of those attributes. There could be multiple ways of getting there but the user needs to be able to prioritize them. An interesting area: his preferences & requirements emerged after he started to get information back.
Bill: Re: Meta questions re: purchasing behavior (there would be other kinds of assumptions). Are all cars equally desirable? In some cases there will be buyers that think that price is the deciding factor. Lifestyle is something that consumers and sellers might consider. From the perspective of the seller: are there best matches between a product and a buyer (certain buyers are ideal buyers for a particular car)?
What are the incentives that the seller is going to offer to the buyer? If they know some of the criteria in my data store (not available for this transaction) maybe the operator has a deal to broker information between the supplier and the user. It could be a fruitful domain of knowledge if it could be appropriately shared (the buyer would need to feel safe in sharing and the seller would benefit greatly). This has a strong bearing on the architecture. What is the deal they’re offering, maybe a late stage deal? “X product matches your needs”. There is personal information that might be so valuable to sellers that they would be inclined to offer great deals and other incentives just to have access to certain buyers.
It needs to somehow describe my personal RFP. There could be services offered around buyers best practices.
Brett: Skipper (personal data store) learns through community (learns how to fill forms out when community members add attributes). If templates need new meta data tags there has to be a way to grow the template.
With a VPI notion of the world we are not talking about pre-existing forms; we are talking about meta data on a product.
Are there standards around describing products that we should be investigating/doing gap analysis on? We should identify what does already exist.
How do you describe variations of a product? Variance is what is acceptable to me.
Would it be in CNET’s interest to be involved in these product insights? Aggregation sites are in a position to provide a lot of value. How products relate to each other is going to be critical. Bill knows someone at CNET that could potentially introduce us to possible CNET participants.
Government procurement is ripe for reinvention in the US. They may have a lot of schema and the people who play in that game might have interest. They have a sophisticated system, so it would be worth investigating.
AARP represents an enormous group of consumers.
Bill: I have a son who belongs to a virtual car community (25-30,000 people) made up of people talking about their cars. They are interested in and well informed about certain kinds of products. Key element #9. It probably applies to things outside of automobiles as well and already exists so it would be more a matter of plugging into Twitter for example. We need to figure out how to leverage existing communities/networks.
Joe: We could create a document that stores keywords and an auto-generated view of search history. If you find a product you’re looking for and it matches something on your list you can drag and drop it from your long term searches. Having standards around what that document is would be a good idea. We want anyone to be able to create and search a search map.
Something that is missing from Iain’s document is a set of policies around data use.
Meeting Adjourned
