See also: IRC log
<Susie> Martin - Lee is meant to be scribing, but he doesn't appear to be here, so would be great if you could scribe.
bengee reports on the progress with logo, with plans for a mtg -- probably next week
there was a mail out to the list about the logo preferences, current votes are well dispersed
probably too early to make conclusions, currently no.1 and no.9 are emerging
bengee added some more variations + added more technology logos
<Susie> http://esw.w3.org/topic/SweoIG/TaskForces/Logos
<bengee> http://esw.w3.org/topic/SweoIG/TaskForces/Logos/SemWebTechLogoIdeas
also logos added for grdl, rif
there are different opinions on logos, how abstract they should be, etc.
first grddl seems preferred and maybe the rif one, but may be a bit abstract
let's wait for mtg with comm. team and see what they like
ivan updates on use cases; in particular teh Dow Jones case looks very positive and enthusiastic; the author of their tool was responsive to the request for a use case
so far no additional feedback received from others
ivan also says that guys in DJ want a more active contact with W3C; ivan found they are already in W3C, so may also participate in SWEO (one day)
<uldis_> regrets, can't participate in voice call
<danja_> (hi all)
leo says that guys from openlink software are working on getting the software working
ivan talked to info gathering group re issue of licensing
there is a proposal for producing the content of SWEO portal under cr.commons licence, but if we are reusing other data -- that may not be compliant with CC or may not have a statement about copyright (we cnnot assume it be CC)
maybe we can just add a disclaimer about removing data if a problem is found with its copyright?
leo suggests checking with W3C lawyers whether this is a relevant issue and how it should be handled -- whether a statement like "This resource does not contain CC statement explicitly"
ivan suggests making another test of the site, so that ivan can start submitting data -- when data comes from a third party
kingsley mentions about importing all sorts of things into portal (raw RDF, other formats,...) = more or less all is there, but this needs to be clarified
ivan says that legal issues are more critical than actual format support, etc.
kingsley currently waits for an agreement on legal issues
portal is currently tested.
data needs to be visualized -- ideas about the systems considered, no new additions to the existing list
bengee, kingsley et al would discuss the selection of an appropriate technology to implement the agreed on formating, look & feel
susie asks when we expect to have the portal running
kingsley says the portal is done, ready... if we have a sparql endpoint, this is already a tangible deliverable
the second step would be to deliver the same content via web front end
kingsley suggests that spaql endpoint already exists, we just need to start uploading data, so phase one (SPRQL) can be ready by next week's telecon
susie asks if there is some information available to people to learn what is already there, how to access it,...
<leobard> there are two wiki pages:
<leobard> http://esw.w3.org/topic/SweoIG/TaskForces/InfoGathering/DataVocabulary
<leobard> http://esw.w3.org/topic/SweoIG/TaskForces/InfoGathering/HowtoPublish
currently one can add either a resource directly (content) or an RDF representation of a particular resource (e.g. for use cases)
ivan suggests that one possibility would be to use e.g. exhibit applied to parts of content to make some simple demonstrations of content
ivan suggests we could perhaps include some additional links (e.g. to books, ...) into the submitted materials
<scribe> ACTION: by 27 June telecon, a SPARQL engine to be available for some basic demonstrations [recorded in http://www.w3.org/2007/06/20-sweo-minutes.html#action01]
<danja> connection to OpenLinkingData great idea
<scribe> ACTION: by 4 July create some guidance for submitting materials sufficiently friendly for users (based on inputs on links given by leo above) [recorded in http://www.w3.org/2007/06/20-sweo-minutes.html#action02]
leo describes the progress in working on URI document and cnsidering how to make this public
maybe as a tutorial it would be a useful output
susie asks what we need to do to make it into W3C Note
ivan says that would be about structuring, stylesheeting, a bit of editing, and then ivan can publish it under W3C node structure
thus, document may get more credibility if published under W3C
if put as W3C node, it would be with Leo and Richard as editors, might be also useful to include the reviewer (Stuart) as a third editor, if the comments were substantial
would be also a good idea to include a person from other WG so that the doc has broader ownership
broder ownership including TAG group member is good for credibility
<scribe> ACTION: leo to incorporate comments from the review into the doc by mid July [recorded in http://www.w3.org/2007/06/20-sweo-minutes.html#action03]
karen not present, so no progress
susies sent an email re F2F mtg around 24th October in Boston area, to coincide with the broader W3C mtg
most people are fine with this, so there is a proposal for 24th October...
SWEO F2F will take place on 24 October in Boston area -- agreed
ivan will check if it can take place at MIT
bengee asks if there is an open SWEO list? or considerations for one
susie says it was decided earlier to have clsoed list, only for member subscriptions, but the content is publicly available in archives
the W3C mailing list is controlled by membership and user DB, so completely open list might not work in this setup
some groups (like SWIG) have totally open lists, but that's different setup
ivan emphasizes that W3C arcihve actually support RSS feeds, which can actually be subscribed to
susie returns to use cases
there was some interest among hutchinson, etc. but not real input yet
kingsley says he has some customers "under construction" but more work is needed -- he currently works on other stuff, but once finished this will be revisited
there is a progress expected on CRM support, some enterprise things also
<danja> re. use cases/demos