• Like
  • Save
Attention Profiling Markup Language Presentation For Xtech08
Upcoming SlideShare
Loading in...5
×
 

Attention Profiling Markup Language Presentation For Xtech08

on

  • 2,574 views

 

Statistics

Views

Total Views
2,574
Views on SlideShare
2,574
Embed Views
0

Actions

Likes
2
Downloads
34
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Attention Profiling Markup Language Presentation For Xtech08 Attention Profiling Markup Language Presentation For Xtech08 Presentation Transcript

    • apml attention profiling mark­up language
    • How it started
    • Attention.xml “Attention.xml is a new technology standard that's being proselytized by influencers like Steve Gillmor, David Sifry, Robert Scoble and Jeremy Zawodny. Basically it is metadata that records and shares information on the quot;attentionquot; users give to their RSS feeds and blogs. Scoble said that by the end of 2005 we'll all know what attention.xml is and why it's important for the services we choose to support it. ” Steve Rubel of Micro Persuasion, Why Attention.xml Could Change PR Forever
    • Attention.xml problems • Ownership problems • Little adoption • It was complex • Lots of baggage • Hyped up? • Misunderstood • Too early?
    • Touchstone/particls
    • Rank your RSS feeds
    • Made use of plain text files
    • Almost everything was transformable
    • Feed lists stored in plain opml
    • Config stored in plain xml
    • Attention stored in plain xml (apml)
    • What is apml? • Attention Profiling Markup Language (APML) is an  open standard that encapsulates a summary of  your interests (across multiple profiles) in a simple,  portable way.
    • Apml in a nutshell • Attention Profiling Markup Language (APML) is an  open standard that encapsulates a summary of  your interests (across multiple profiles) in a simple,  portable way.
    • Apml in a nutshell
    • The purpose of apml • Attention Profiling Mark­up Language is a plain xml  format to compress all forms of Attention Data into  a portable and transformable file format containing  a description of a persons interests (likes and  dislikes) • Its a portability format which allows people to share  their own personal attention profile in much the  same way that opml is used for sharing subscription  lists
    • The current state of apml • Its licensed under creative commons  attribution/share­a­like licence • There are no patents involved in apml • It will be submitted to standards groups soon • currently on version 0.6 • version 1.0 is being openly debated • discussion of other related formats such as, • apml­rdf, apml­json (xsl already exists) and apml­lite  (microformat)
    • Attention data “attention data is comprised of the  websites you visit, the things you  might write about in your blog, the  music you listen to through such  services as Last.fm, the websites  you bookmark using social  bookmarking tools like del.icio.us,  the photos and videos you share  with services like Flickr and  YouTube, and so on.”
    • Attention cloud Your interest cloud is a  combination of your  attention data ranked,  sorted and  normalised. This  should be done with  computer intervention.
    • Attention profile “APML is a way of collecting and  aggregating all of your attention  data together into a single  quot;attention profilequot;. This profile  exists in the form of an XML file ­  which is the same open language  behind RSS and OPML”
    • The elements of apml (head) <APML version=quot;0.6quot;> <Head> <Title>Particls APML File</Title> <DateCreated>2007­04­16T23:00:00Z</DateCreated> <Generator>Particls</Generator> <UserEmail>Ian Forrester</UserEmail> </Head> <Body> <Profile/> <Applications>       <Application/> </Applications> </Body> </APML>
    • The elements of apml (profiles) <Body defaultprofile=quot;homequot;>     <Profile name=quot;homequot;>      <ImplicitData>          <Concepts/>            <Sources/>        </ImplicitData>        <ExplicitData>          <Concepts/>          <Sources/>        </ExplicitData>     </Profile> </Body> It is possible to have many different named profiles in one apml file
    • The elements of apml (data) <ImplicitData/> <ExplicitData/> Explicit data is for items that are explicitly added by a user to represent  something. So for example, a user could edit their own APML file and add  items they know they're interested in. That's why the updated tag isn't  needed on items in ExplicitData, because it's a manual process. Implicit data, it is added by machines/computers that try to make some  informed guesses about the things that you are interested in. This stuff will  change over time and are added with a certain degree of confidence that  may have a decay in certain applications. That's why it is important to keep  a track of when things were added/modified.
    • The elements of apml (concepts) <ImplicitData>     <Concepts/> <Sources/> </ImplicitData> <ExplicitData>     <Concepts/>  <Sources/> </ExplicitData> Concepts mean quot;ideasquot; basically. General quot;thingsquot; you may be interested in.  Sources are specific sources of information that you are interested in. Like  a particular website or rss feed or something. Authors can be authors of a  source, or just plain old authors. It is worth noting that the idea of an  author/people is under review for APML Version 1.0)
    • The elements of apml (concept) <ExplicitData> <Concepts>      <Concept key=quot;xtechquot; value=quot;1.0quot; /> <Concept key=quot;xsl2quot; value=quot;0.90quot; /> <Concept key=quot;golfquot; value=quot;­0.99quot; />     </Concepts> <Sources>      <Source key=quot;http://news.google.com/news? svnum=10&amp;as_scoring=r&amp;as_drrb=q&amp;as_qdr=d&amp;as_mi nd=13&amp;as_minm=1&amp;as_maxd=12&amp;as_maxm=2&amp;q= %22xtech%22&amp;ie=UTF­8&amp;output=rssquot; value=quot;0.25quot; />     </Sources> </ExplicitData>
    • The elements of apml (concept) <ImplicitData>     <Concepts> <Concept key=quot;canon powershotquot; value=quot;0.71quot;  updated=quot;2007­08­21T08:32:38Zquot; from=quot;Particlsquot;/> <Concept key=quot;londonquot; value=quot;0.76quot; updated=quot;2007­08­21T08:32:38Zquot;  from=quot;Particlsquot;/> <Concept key=quot;manchesterquot; value=quot;1.00quot;  updated=quot;2008­04­27T11:41:11Zquot; from=quot;cubicgarden.comquot;> </Concepts> </ImplicitData> The Key is the “concept” in question, the attached value is always a decimal  between ­1.0 and 1.0. The updated is required on implicit but not explicit.
    • The elements of apml (sources) <ImplicitData>    <Sources>           <Source key=quot;http:www.stoweboyd.commessageatom.xmlquot; value=quot;0.85quot;  name=quot;Messagequot; type=quot;application/atom+xmlquot;  updated=quot;2007­05­03T00:01:13Zquot; from=quot;Particlsquot;/>           <Source key=quot;http://feeds.feedburner.com/horsepigcowLifeUncommonquot;  value=quot;0.82quot; name=quot;::HorsePigCow:: marketing uncommonquot;  type=quot;application/atom+xmlquot; updated=quot;2007­05­03T00:01:13Zquot;  from=quot;Particlsquot;>         </Sources> </ImplicitData> Its good practice to use a xml source for the key. The type attribute is optional  right now, although that may change
    • The elements of apml (author) <ImplicitData> <Source key=quot;http://www.darknet.com/atom.xmlquot; value=quot;0.00quot;  name=quot;Darknetquot; type=quot;application/atom+xmlquot;  updated=quot;2007­05­03T00:01:13Zquot; from=quot;Particlsquot;> <Author key=quot;Jd Lasicaquot; value=quot;0.00quot; updated=quot;2007­05­03T00:18:50Zquot;  from=quot;Particlsquot;/> </Source> <Source key=quot;http://www.schneier.com/blog/index.rdfquot; value=quot;0.00quot;  name=quot;Schneier on Securityquot; type=quot;application/rdf+xmlquot;  updated=quot;2007­05­03T00:01:13Zquot; from=quot;Particlsquot;> <Author key=quot;Schneierquot; value=quot;0.00quot; updated=quot;2007­05­03T00:18:53Zquot;  from=quot;Particlsquot;/> </Source> </ImplicitData>
    • The elements of apml (authors) <ImplicitData> <Source key=quot;http://feeds.feedburner.com/zdnetuk/news/20quot; value=quot;0.00quot;  name=quot;ZDNet UK Newsquot; type=quot;application/rss+xmlquot;  updated=quot;2007­05­03T00:01:13Zquot; from=quot;Particlsquot;>             <Author key=quot;Mailroomuk@Zdnet.Com (Will Sturgeon)quot; value=quot;0.34quot;  updated=quot;2007­05­03T00:18:42Zquot; from=quot;Particlsquot;/>             <Author key=quot;Mailroomuk@Zdnet.Com (Tom Espiner)quot; value=quot;0.21quot;  updated=quot;2007­05­03T00:18:42Zquot; from=quot;Particlsquot;/>             <Author key=quot;Mailroomuk@Zdnet.Com (Gemma Simpson)quot;  value=quot;0.23quot; updated=quot;2007­05­03T10:20:42Zquot; from=quot;Particlsquot;/> </Source> </ImplicitData> Its possible to group authors under one source
    • The elements of apml (applications) <Applications> <Application Name=quot;Particlsquot;> <OutputThresholds Key=quot;newstickerquot; NotUnder=quot;­1quot; NotOver=quot;1quot;  Enabled=quot;Yesquot;/> <OutputThresholds Key=quot;pop­up alertsquot; NotUnder=quot;0.4quot; NotOver=quot;1quot;  Enabled=quot;Yesquot;/> <OutputThresholds Key=quot;pebblesquot; NotUnder=quot;0.2quot; NotOver=quot;1quot;  Enabled=quot;Yesquot;/> <OutputThresholds Key=quot;particls.sidebarquot; NotUnder=quot;0quot; NotOver=quot;0quot;  Enabled=quot;Yesquot;/> </Application> </Applications> Inside Application, any type of mark­up is allowed, parsers skip this
    • Apml­json quot;implicitDataquot;: {     quot;sourcesquot;:   {     quot;conceptsquot;: {   quot;http://feeds.feedburner.com/apmlspecquot;: {         quot;attentionquot;: {     quot;namequot;: quot;APML.orgquot;,             quot;valuequot;: quot;1.0quot;,     quot;valuequot;: quot;1.00quot;,             quot;fromquot;: quot;quot;,     quot;typequot;:  quot;application/rss+xmlquot;,             quot;updatedquot;: quot;2007­03­11T01:55:00Zquot;     quot;valuequot;: quot;0.4quot;         },     quot;authorquot;: {         quot;content distributionquot;: {             quot;keyquot;: quot;Samplequot;,             quot;valuequot;: quot;1.0quot;,             quot;valuequot;: quot;0.5quot;,             quot;fromquot;: quot;GatheringTool.comquot;,             quot;fromquot;: quot;GatheringTool.comquot;,             quot;updatedquot;: quot;2007­03­11T01:55:00Zquot;             quot;updatedquot;: quot;2007­03­11T01:55:00Zquot;         }     }     }, }
    • Apml­RDF
    • Other apml avenues • Apml lite • apml in xhtml markup, using rdf/a or as a microformat • Apml+Skos • Apml + simple knowledge organisation systems
    • Linking apml in xhtml <link rel=quot;metaquot; type=quot;application/xml+apmlquot;  title=quot;APMLquot;  href=quot;https://apml.engagd.com/apml/www.cubicgarden .com%2Fblojsom%2Fblog%2Fcubicgarden %2F.apmlquot;/>
    • Apml libraries • Engagd lib ­ Engagd API PHP5 client library • http://code.google.com/p/apml­library/ • Apml parser v2 ­ 2.0 PHP APML parser • http://code.google.com/p/apml­library/ • Apml Stream – Java library • http://apml­ library.googlecode.com/svn/trunk/Java/APMLStream/APMLStream­0.1/ • Engagd – Webservice • http://engagd.com/ • PyAPML – Python library • http://apml­library.googlecode.com/svn/trunk/Python/
    • The bigger picture
    • Apml is part of something bigger
    • Apml is part of the dataportability stack
    • Apml usage
    • Apml buzz • Particls ­ http://www.particls.com • Engadgd ­ https://www.engagd.com/ • Idiomag ­ http://www.idiomag.com/apml/ • Ma.gnolia ­   http://www.ma.gnolia.com • Cluztr ­ http://cluztr.wordpress.com/2007/10/15/support­for­apml/ • BBC Radio Labs ­  http://www.bbc.co.uk/blogs/radiolabs/2008/01/apml_isnt_just_for_humans. shtml • Dandelife ­ http://www.profy.com/2008/01/21/dandelife­review/ • Bloglines ­ http://www.bloglines.com/about/news#147
    • Examples
    • Apml would be ideal for music sharing
    • Apml on the desktop too
    • Apml for personalisation
    • Music in apml <ImplicitData>     <Concepts> <Concept key=quot;trancequot; value=quot;1.00quot; from=quot;Amarokquot; updated=quot;quot;/> <Concept key=quot;progressive trancequot; value=quot;0.94quot; from=quot;Amarokquot;  updated=quot;quot;/> <Concept key=quot;dancequot; value=quot;0.59quot; from=quot;Last.FMquot; updated=quot;quot;/> <Concept key=quot;rockquot; value=quot;­0.5 from=quot;Last.FMquot; updated=quot;quot;/> </Concepts> <Sources>      <Source key=quot;http://www.last.fm/music/Armin+van+Buuren/quot;  value=quot;0.9quot; /> <Source key=quot;http://www.last.fm/music/Tiesto/quot; value=quot;0.6quot; />     </Sources> </ImplicitData>
    • TV recommendations
    • TV favourites
    • Sharing between sites
    • Better recommendations
    • Better recommendations
    • The killer example
    • Dating profiles should be portable
    • Dating is in need of apml
    • Maybe apml can fill this in for me?
    • Apml = portability
    • Dating would never be the same
    • Apml could bring you love
    • Thank you, any questions? Ian Forrester – Senior Producer at BBC Backstage Backstage.bbc.co.uk | Cubicgarden.com | Dataportability.org