HCLSIG/SWANSIOC/Meetings/2008-10-03 Conference Call

From W3C Wiki

Conference Details

  • Date of Call: Friday October 3, 2008
  • Time of Call: 11:00am Eastern Time
  • Dial-In #: +1.617.761.6200 (Cambridge, MA)
  • Dial-In #: +33.4.89.06.34.99 (Nice, France)
  • Dial-In #: +44.117.370.6152 (Bristol, UK)
  • Participant Access Code: 4257 ("HCLS")
  • IRC Channel: irc.w3.org port 6665 channel #HCLS (see W3C IRC page for details, or see Web IRC)
  • Duration: ~1 hour
  • Convener: Tim Clark
  • Scribe: Susie

Agenda

  • Introductions
  • Optimal integration points
  • AOB

Minutes

<Susie> Attendees: Holger, Matthias, Susie, Kei, Tim, Paolo, Alex, Jun

<Susie> Tim: Last call came up with a technical sub-committee

<Susie> Tim: Focus on directions for integrating ontologies

<Susie> Tim: Bunch of work done

<Susie> Tim: Paolo and Alex can present

<Susie> Tim: There was a scope discussion

<Susie> Tim: Susie, John, Tim discussed scope after the discussion too

<Susie> Tim: Is focus on integrating SWAN & SIOC or to explore this more broadly

<Susie> Tim: Susie, John, Tim agree focus is to integrate SWAN & SIOC

<Susie> Tim: Astronomy people are becoming interested in this work too because of the citation model

<Susie> Tim: Suggestion is to have a 2 track thing.

<Susie> Tim: Track 1 focuses on SWAN SIOC and is implemented quickly and robustly

<Susie> Tim: Track 2 focuses on broader context

<Susie> Susie: Wants HCLS2 to deliver quickly, so prefer narrow SWAN SIOC scope to start with

<Susie> Kei: What does SWAN SIOC integration mean in general?

<Susie> Tim: SIOC ontology of discussion boards, etc.

<Susie> Tim: SIOC is done at a high level

<Susie> Tim: SWAN focused on scientific discourse and is more finely grained

<Susie> Tim: Both SWAN & SIOC are implemented

<Susie> Tim: Interesting & helpful to have them aligned ontologically

<Susie> Tim: Conversation with Science Commons to discuss how to intergrate SWAN & SIOC in broader context

<Susie> Paolo: Now in progress for SWAN 1.2

<Susie> Paolo: At point where can easily plug in new features

<Susie> Paolo: Broader ontology alignment will be the release after next

<Susie> Paolo: Not a good time to integrate a new citation ontology, but could do that for the next release.

<Susie> Alex: 1st point. SIOC different types of high level items. In SWAN more specific, e.g. journal comments

<Susie> Alex: Align SIOC Post and Item with SWAN Citation and Discourse Element

<Susie> Alex: Align Container with Online Book

<Susie> Tim: Real software project can use this work today

<Susie> Alex: 2nd point. Talk about Discussion and Argumentative Discussion

<Susie> Paolo: SWAN currently uses the SWAN Citation Ontology

<Susie> Paolo: Will defer using the Bibliographic ontology until the next release

<matthias_samwald> http://bibliontology.com/

<Susie> Paolo: Should talk about the tag ontology in a future meeting

<alex_> tag ontology - http://www.holygoat.co.uk/owl/redwood/0.1/tags/

<Susie> Paolo: Can show progress on the wiki page

<alex_> http://esw.w3.org/topic/HCLSIG/SWANSIOC/Actions/Alignment

<alex_> http://esw.w3.org/topic/HCLSIG/SWANSIOC/Actions/Alignment/EmbedsKnowledge

<matthias_samwald> SCOT: http://scot-project.org/

<alex_> MOAT : http://moat-project.org (MOAT and SIOC are based on the TAg Ontology)

<Susie> Paolo: in SCF they have articles, and they are easy to connect to SIOC

<Susie> Paolo: Harder to integrate with SWAN as they are already using triples

<Susie> Paolo: Suggestons for overcoming this are posted on the wiki

<Susie> Paolo: What is the practical approach for implementing this?

<Susie> Paolo: Clean approach to add a URI that you call and retrieve all triples for a hypothesis

<Susie> Paolo: Consider that as the graph that represents the hypothesis.

<Susie> Jun: Been working to connect work between researchers

<Susie> Jun: Want to use SWANSIOC and build demos

<Susie> Paolo: Thinking about moving to a more RESTful approach

<Susie> Paolo: Could use same URI notation as Alex uses

<Susie> Paolo: Straightforward to implement in SCF

<Susie> Paolo: For SWAN could provide all triples for a graph

<Susie> Paolo: SWAN isn't currently RESTful, so will need to change URIs

<Susie> Paolo: SWAN is more annotation

<Susie> Paolo: In SWAN the document is out of the system

<Susie> Paolo: That's why everything is expressed in triples

<Susie> Tim: Looking to go to a document metadata model

<Susie> Paolo: It shouldn't be a huge step, but will take some time

<Susie> Paolo: Have URI where could ask for annoation, metadata, or the document should work nicely for SWAN

<Susie> Paolo: Need another technical meeting to work out the details

<Susie> Paolo: Focus on tagging ontology

<Susie> Paolo: Put bibliography on hold for a while

<Susie> Alex: Want to discuss Dublin Core Properties

<Susie> Alex: SIOC currently uses Dublin Core Properties such as Creator

<Susie> Paolo: Dublin Core Properties aren't currently be used in SWAN

<Susie> Paolo: Would be some limitations in using Dublin Core Properties

<Susie> Alex: Why do you need to re-define the domain and range of properties

<Susie> Alex: To make it more consistent with reasoning

<Susie> Matthias: Some of the constraints will be relaxed in OWL2

<Susie> Paolo: AlanR recommends keeping a separate file for now

<Susie> Tim: SIOC meeting is bi-weekly

<Susie> Tim: Gives time to do work between meetings

<Susie> Tim: Will do meeting announcements

<Susie> Tim: SWANSIOC people will try to be represented in the HCLS calls

<Susie> Tim: This is good work

<Susie> Tim: Happy to extend the scope long term, but get the SWANSIOC work done first

<Susie> Matthias: Will need to bring in a broad community later to reach concensus around a standard

<Susie> Tim: Overhead in bringing in lots of people, rather than small focused group, and we need to balance these things

Retrieved from "https://www.w3.org/wiki/index.php?title=HCLSIG/SWANSIOC/Meetings/2008-10-03_Conference_Call&oldid=32813"