Iptc Update 2007 05 29

1,365 views
1,212 views

Published on

description of SportsML 2.0 specification recommendations

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,365
On SlideShare
0
From Embeds
0
Number of Embeds
32
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Iptc Update 2007 05 29

  1. 1. SportsML www.SportsML.org (presentation available at http://www.sportsml.org/dev ) Alan Karben XML Team Solutions Tokyo / May 27, 2007
  2. 2. Agenda <ul><li>Welcome to our Guest </li></ul><ul><li>SportsML 2.0: </li></ul><ul><ul><li>Sports-Specific Improvements </li></ul></ul><ul><ul><li>Option to Use G2 Packaging </li></ul></ul><ul><li>Next Steps </li></ul><ul><li>Open Forum </li></ul>
  3. 3. Welcome: Michael Westbay <ul><li>Owner of http://www.japanesebaseball.com </li></ul><ul><li>First (?) website to cover Japanese Baseball </li></ul><ul><ul><li>Started in 1995 as “Japan Pro Yakyu this Week” </li></ul></ul><ul><li>Frequent contributor to SportsML community </li></ul>
  4. 4. Sports-Specific Improvements <ul><li>Baseball play expansion </li></ul><ul><li>American-Football position expansion </li></ul><ul><li>Highly specific datatypes </li></ul><ul><li>Additional stats absent from SportsML 1.8 </li></ul><ul><li>Other Potential Additions </li></ul><ul><ul><li>Rugby Plug-In? </li></ul></ul><ul><ul><li>Improved / Streamlined / Internationalized wagering line support? </li></ul></ul>
  5. 5. <action-baseball-play> <ul><li>Expand play-type to include wider variety of plays (see spreadsheet) </li></ul><ul><li>Expand hit-type to better modify play-types that are hits </li></ul><ul><li>Expand out-type to better modify play-types that are outs </li></ul><ul><li>Add new modifying attributes: </li></ul><ul><ul><li>interference-type </li></ul></ul><ul><ul><li>base-stolen </li></ul></ul>
  6. 6. <action-baseball-play> <ul><li>Guiding Principle: </li></ul><ul><ul><li>Enable SportsML attributes to describe play for top-level play events that are worthy of searching (via XQuery or SQL) </li></ul></ul><ul><ul><li>The RoSIN &quot;play notation&quot; is recordable to fully describe the play (www.rosin.org) </li></ul></ul>
  7. 7. <action-baseball-pitch> <ul><li>Expand umpire-call attribute of <action-baseball-pitch> from: </li></ul><ul><li>(ball | strike | in-play) </li></ul><ul><li>to: </li></ul><ul><li>(ball | strike | in-play | no-pitch | unknown) </li></ul><ul><li>… and move to external vocabulary </li></ul><ul><li>Add stolen-bases-attempted attribute to <stats-baseball-offensive> </li></ul>
  8. 8. American-Football Positions <ul><li>Allow for more specific positions (see spreadsheet) </li></ul><ul><li>In General, allow for either Generic or Specific positions </li></ul><ul><li>What to do when player takes multiple positions over the course of an event? </li></ul><ul><ul><li>Comma-separated values? </li></ul></ul>
  9. 9. Highly Specific Datatypes <ul><li>Most statistical datatypes are currently specified as “cdata” </li></ul><ul><ul><li>Hadn’t gotten around to making them more specific </li></ul></ul><ul><li>Proposal made for more specific baseball datatypes </li></ul><ul><ul><li>(see spreadsheet) </li></ul></ul><ul><li>Complete this effort for stats for our other sports, and for pieces of Core Schema </li></ul><ul><ul><li>e.g., Core <player-stats> has these attributes: </li></ul></ul><ul><ul><li>time-played-event (ISO time duration) </li></ul></ul><ul><ul><li>time-played-total (ISO time duration) </li></ul></ul><ul><ul><li>time-played-event-average (ISO time duration) </li></ul></ul><ul><ul><li>events-played (integer) </li></ul></ul><ul><ul><li>events-started (integer) </li></ul></ul>
  10. 10. Additional Absent Stats <ul><li>Add stolen-bases-attempted attribute to <stats-baseball-offensive> </li></ul><ul><li>Add rebounds-opponent-total attribute to <stats-basketball-rebounding> </li></ul><ul><li>Add double-doubles attribute to <stats-basketball-offensive> </li></ul>
  11. 11. Rugby Plug-In <ul><li>Initial Inventory of Stats (see spreadsheet) </li></ul><ul><li>Union vs. League </li></ul><ul><ul><ul><li>Question: Can both styles of play be covered by same Plug-In (like with American and Canadian football)? </li></ul></ul></ul><ul><ul><ul><li>Answer: Would be nice. </li></ul></ul></ul>
  12. 12. Better Wagering Structures <ul><li>Good banter on the Yahoo!Group about posting proposals that broaden our wagering-stats coverage to be applicable to more sports in more countries </li></ul><ul><li>Nothing (yet) posted following initial surge in discussion </li></ul>
  13. 13. SportsML 2.0 / G2: Positioning <ul><li>G2 Compatibility for SportsML 2.0: Optional </li></ul><ul><li>Review: Why G2? Publisher can take advantage of: </li></ul><ul><ul><li>Additional packaging functionality </li></ul></ul><ul><ul><li>Additional rights-management functionality </li></ul></ul><ul><ul><li>Cleaner metadata structures, improved versioning </li></ul></ul><ul><ul><li>Potential for content-neutral platforms for permissioning and distribution of content </li></ul></ul>
  14. 14. SportsML 2.0 / G2: Positioning <ul><li>Client can take advantage of: </li></ul><ul><ul><li>Common metadata model, to determine document routing and processing </li></ul></ul><ul><ul><li>Potential for content-neutral platforms for receiving and processing/integrating content </li></ul></ul>
  15. 15. SportsML 1.8 to SportsML G2 <ul><li>XSL file can do conversion </li></ul><ul><ul><li>(only ~400 lines of XSL code -- including comments) </li></ul></ul><ul><li>1.8 metadata properties migrate to newsItem metadata header </li></ul><ul><li>Inline conversions: </li></ul><ul><ul><li>date format </li></ul></ul><ul><ul><li>qcodes for controlled codes </li></ul></ul><ul><ul><li>name/@full </li></ul></ul><ul><ul><li>split out SportsML and Nitf content </li></ul></ul>
  16. 16. Sample SportsML 2.0 <ul><li>Samples validate against latest draft (0.16) except for: </li></ul><ul><ul><li>Relationships (broader, narrower, related, sameAs): need to see samples </li></ul></ul><ul><ul><li>Contenttype (mimetype?): Uncertain how to express. </li></ul></ul><ul><ul><ul><li>contenttype=&quot;application/sportsml+xml” </li></ul></ul></ul><ul><ul><ul><li>contenttype=&quot;application/nitf+xml” </li></ul></ul></ul><ul><ul><ul><li>Why is contenttype not camel-case? </li></ul></ul></ul>
  17. 17. Hybrid Documents <ul><li>Package of SportsML and NITF </li></ul><ul><li>Topic in Cairo </li></ul><ul><ul><li>Contains complementary inline: </li></ul></ul><ul><ul><ul><li>SportsML stats which supplement an NITF story </li></ul></ul></ul><ul><ul><li>Includes two inlineXML </li></ul></ul><ul><li>See sample files at sportsml.org/dev </li></ul>
  18. 18. SportsML “fixture” Resolution <ul><li>Finally resolved sing instanceOf and memberOf (says Paul: “Hooray!”): </li></ul><ul><ul><ul><li><itemMeta> </li></ul></ul></ul><ul><ul><ul><li><instanceOf </li></ul></ul></ul><ul><ul><ul><li>qcode=&quot;fixture:pre-event-coverage&quot;> </li></ul></ul></ul><ul><ul><ul><ul><li><name>Game Preview</name> </li></ul></ul></ul></ul><ul><li>Agreed? </li></ul>
  19. 19. SportsML “fixture” (cont’d.) <ul><li>Also: </li></ul><ul><ul><li><contentMeta> </li></ul></ul><ul><ul><ul><li><genre type=&quot;sml-genre:docClass&quot; qcode=&quot;docClass:event-summary&quot;> </li></ul></ul></ul><ul><ul><ul><ul><li><narrower qcode=&quot;fixture:pre-event-coverage&quot;/> </li></ul></ul></ul></ul><ul><ul><ul><li><genre type=&quot;sml-genre:fixture&quot; qcode=&quot;fixture:pre-event-coverage&quot;> </li></ul></ul></ul><ul><ul><ul><ul><li><broader qcode=&quot;docClass:event-summary&quot;/> </li></ul></ul></ul></ul><ul><li>Dit Paul: “D’accord?” </li></ul>
  20. 20. More Relationships <ul><li><subject type=&quot;subj:person&quot; qcode=&quot;person:l.mlb.com-p.123&quot;> </li></ul><ul><ul><li><name>Freddy Garcia</name> </li></ul></ul><ul><ul><li><sameAs qcode=&quot;fssID:45680&quot;/> </li></ul></ul><ul><li></subject> </li></ul><ul><li>Dit Paul: “C’est bon ou mal?” </li></ul>
  21. 21. sports-metadata <ul><li>SportsML 1.8: </li></ul><ul><ul><li><sports-metadata> </li></ul></ul><ul><ul><ul><li><sports-content-codes> </li></ul></ul></ul><ul><ul><ul><ul><li><sports-content-code code-type=&quot;team&quot; </li></ul></ul></ul></ul><ul><ul><ul><ul><li>code-key=&quot;l.mlb.com-t.19&quot; </li></ul></ul></ul></ul><ul><ul><ul><ul><li>code-name=&quot;Philadelphia Phillies&quot;/> </li></ul></ul></ul></ul><ul><li>Becomes SportsML 2.0 / G2: </li></ul><ul><ul><ul><li><contentMeta> </li></ul></ul></ul><ul><ul><ul><li><subject type=&quot;subj:team&quot; </li></ul></ul></ul><ul><ul><ul><li>qcode=&quot;team:l.mlb.com-t.19&quot;> </li></ul></ul></ul><ul><ul><ul><ul><li><name>Philadelphia Phillies</name> </li></ul></ul></ul></ul>
  22. 22. Other Changes <ul><li>event-key=“l.mlb.com-2007-e. 19358” </li></ul><ul><ul><li>Becomes: event-key=“event:l.mlb.com-2007-e.19358” </li></ul></ul><ul><ul><li>Also: team, player, fixture and all other controlled keys </li></ul></ul><ul><li>start-date-time=“20070528T190500-0400” </li></ul><ul><ul><li>Becomes: start-date-time=“2007-05-28T19:05:00-04:00” </li></ul></ul>
  23. 23. Next Steps <ul><li>Finalize Sports-specific improvements </li></ul><ul><li>Validate G2 samples per ratified (?) NAR spec </li></ul><ul><li>Fully document the recommended SportsML-within-G2 approach </li></ul><ul><ul><li>Release SportsML 1.8-to-2.0/G2 XSL </li></ul></ul><ul><li>TAG urls? (Misha) </li></ul><ul><li>Prepare SportsML 2.0 for vote </li></ul><ul><li>Next meeting… in Prague in September </li></ul>
  24. 24. Open Forum <ul><li>Questions / Comments </li></ul>

×