Iptc Update 2007 05 29
Upcoming SlideShare
Loading in...5
×
 

Iptc Update 2007 05 29

on

  • 1,984 views

description of SportsML 2.0 specification recommendations

description of SportsML 2.0 specification recommendations

Statistics

Views

Total Views
1,984
Views on SlideShare
1,984
Embed Views
0

Actions

Likes
0
Downloads
17
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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

Iptc Update 2007 05 29 Iptc Update 2007 05 29 Presentation Transcript

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