This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.


List of prioritizations given through the mailinglist(s):

Voter Membership 1 2 3 4 5 6 7 8 9 10 11 12 13
David Harrison (Tieto) Communications       1   2     3        
Vaibhav Srivastava (IBM) Communications       1         2   3    
Parham Vasaiely (EADS) Communications       1   2     3        
Andy Gurd (IBM) Communications         1     2 3        
Wesley Coelho (Tasktop) Communications       2       3       1  
Robert Myers (IBM) Communications       1     2       3    
Rainer Ersch (Siemens) Steering Committee 3       2       1        
Andreas Keis (EADS) Steering Committee 3     1         2        
David Ingram (Accenture) Steering Committee       1 2   3*            
Mik Kersten (Tasktop) Steering Committee         2     3       1  

* with case studies


  Overall Communications WG Steering Committee
totals 1st 2nd 3rd 1st 2nd 3rd 1st 2nd 3rd
1 0 0 2           2
2 0 0 0            
3 0 0 0            
4 6 1 0 4 1   2    
5 1 3 0 1       3  
6 0 2 0   2        
7 0 1 1   1       1
8 0 1 2   1 1     1
9 1 2 3   1 3 1 1  
10 0 0 0            
11 0 0 2     2      
12 2 0 0 1     1    
13 0 0 0            

Ideas snapshot

Copied from AwarenessRaisingActivities on August 13:

New ideas that have yet to be prioritized (Steering Committee is looking to provide prioritization feedback)

  1. OSLC "Promoter's Toolkit" - centralized place to find canned slides for presentations, presentation templates, graphics, posters, patterns for buttons and t-shirts, and other media
  2. Refresh of the " Case for OSLC" whitepaper, especially with input from multiple sources/companies
  3. Establish a process for getting endorsements and testimonials from Members, get X of them in Y months
  4. Assist workgroups in raising their presence in the technical world: assist them in getting started microbloging, provide interesting decisions and ongoing discussions for inclusion in a periodic community-wide workgroup update blog, broader promotion of upcoming meetings
    1. Help contributors get more "street cred" for their OSLC efforts
    2. Make sure OSLC, and its contributors, are part of the wider conversations on Linked Data, integrations, and $domain
    3. Help make OSLC workgroups "happening" places where other technical leaders feel the need to participate
  5. Get TBL to record a video explaining how OSLC is the leading example of using Linked Data for data creation and modification, not just consumption, and then to expand on how he thinks this will affect the world and to sketch the possibilities of a bi-directionally linked enterprise/supply chain/world
  6. Engage Lyo contributors and users to help promote the Lyo project as a "happening" place for technical all-stars and to catalog the benefits of using Lyo to implement OSLC (and using OSLC to do integrations)
  7. Develop a general ROI model for building integrations using OSLC, validate against the experiences of commercial and internal implementers in the community
  8. Reach out to known influences in the technology industry (especially/starting with bloggers), help them see how OSLC is relevant to their audience/readership, and assist them in becoming a in informed commenter on OSLC
  9. Create an OSLC Summit/Conference, possibly co/pre/post-located with another conference
  10. Host an analysts roundtable (at the summit/conference?)
  11. How about an OSLC Boot Camp?This would be an intense one-day learn everything about OSLC session with 5 minute breaks for running around the room, stretching exercises, bread sandwiches with water,... you get the idea,'- Could be done virtually. Learn the OSLC API sufficiently to write a limited wrapper for their product Workflow precepts for Linked data applications etc. High energy, high value in the time spent. I borrowed this idea from a brilliant software engineer I knew years ago
  12. Write 1-page case studies outlining how organizations are using OSLC and the resulting benefits. These can be anonymous if needed. The case studies can then be promoted via various channels.
  13. Well-formated one-page newsletter sent to mailing lists generated from, webinar registrations etc. Newsletters can feature new integrations, past blog posts, case studies, the whitepaper etc.
Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 13 Aug 2012 - 18:01:36 - SeanKennedy
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback