SWAD-Europe Overview

Goals for kick-off meeting...

Review workplan, objectives, deliverables
Assign names to deliverables
Relate project work to wider W3C SW activity
Practicalities: Handbook issues
Progress reporting: formal and informal
Begin technical discussions

Project Goals

Implement scenario-led examples showing the integration of multiple Semantic Web technologies.
Develop a Semantic Web technology integration strategy that emphasises the utility of XML languages (SVG, MathML etc) as complementary rather than competing components of the Web.
Ensure that European Community is kept aware of international best practice for SW technology, and that best practice within Europe is recognised internationally.
Undertake targeted research and development in support of these objectives.

Milestones and Results

(what we said we'd do, part 2...)

Delivered a series of research demonstrations showcasing Semantic Web technology for consumer and industrial applications
Created a methodology demonstrating the integration of RDF and Semantic Web tools with a range of XML and Web standards
Facilitated SW technology maturation, aiding the deployment of Semantic Web-enhanced Web Services
Deployed an education and outreach programme

Workplan Review: Structure and Themes

A lot of work!
Many overlaps and common themes; minimal dependencies
57 (non-standard) deliverables (over 224+ person months)
5 partners, 30 month lifecycle
15 workpackages (some paired; 12 main work areas)
objectives: answer questions, foster community
4 broad categories: project-wide; 'hot topics'; tools and maturity; scenarios and applications

Cross-project WPs

Admin/Finance/Management (WP1)

Tech/Content Coordination (WP2)

Dissemination/Exploitation/Outreach (WP3)

Current W3C SW-related 'hot topics'

Web Services and Semantic Web (WP4)

RDF/SW and XML Integration (WP5, demo: WP6)

Visualisation and Accessibility (WP9, WP12.3)

RDF Tools and Maturity

Databases, Query, API, Interfaces (WP7)

Tools for scalability, storage (WP10, demo: WP12.4)

Distributed Trust (WP11)

Scenarios and Applications

Thesaurus systems (WP8)

Annotations (WP12.2)

Open demos (WP12.1, topics to be decided)

...visualisation, ...web services, ...trust

Getting Started

What questions are being asked? (RDF FAQ, FAQ ideas draft)

An early deliverable: WP10 rdf_scalable_storage_report/ draft (and notes)

What questions might this answer?

What applications and scenarios might inform this WP? (thesaurus? annotations?)

SWAD-Europe and W3C

'SWAD-Europe: W3C Semantic Web Advanced Development for Europe'

SWAD-Europe...

...is a 5 partner collaborative EU project

...originated within W3C's SW Activity (SW home page, Activity Statement)

...extends SWAD(-MIT) previous development model

...is about and in support of W3C's SW Activity, but managed independently.

...complements and feeds into 'standards track' work

SWAD-Europe and W3C (part 2)

...contribute test suite materials (eg. rdf core, rdf query, webont, scalability testing)

...sponsor and lead Interest Group task forces (query languages, thesaurus systems, calendar tools...), contribute to Notes

...generate proposals that could feed into W3C's standards-track work (APIs?)

...create supporting materials (FAQs, worked examples, 'hot topics', online tools, primers)

...collaborate with related projects (SWAD-MIT; Question-How, ...)

Project Handbook

Practical issues need addressing:

Administrative and Finance (separate doc)

Content and Technical

Web site (structure, write access, content)

mailing lists (w3c-swad-europe, public-esw, ...)

Workpackage descriptions (HTML, RDF, spreadsheet etc.)

Deliverable templates (draft)

Teleconference, IRC and other supporting machinery

Key Documents

SWAD-Europe home page

Project Objectives (and Factsheet)

Events calendar (RDF version)

Workplan overview

Workpackage descriptions (one per WP, by number)

Deliverable reports (one per deliv, by name)

W3C: SW, SWAD, Process document, Software License

Technical Coordination (WP2)

Each WP has a lead partner and needs named contacts per-partner

project partner interests/expertise aren't always reflected in workplan (eg. query)

Workpackage and deliverable owners take responsibility for:

promoting open discussion while ensuring for timely delivery

scheduling telephone, irc, mail and f2f work towards delivering their commitments

devolving their work items within project team

reporting (to partners and collaborators, and via WP1 machinery to Commission)

Next Steps...

Review workpackages, assign names, begin technical discussion

Arrange WWW access, mailing lists

Begin workshop and outreach planning

Drafting and review of early deliverables