SemanticWebBestPracticesTaskForceOnApplicationsAndDemosNotes
Additional material from SemanticWebBestPracticesTaskForceOnApplicationsAndDemos
Notes from the Boston meeting
At Boston face to face 2005-03-03/2005-03-04 we discussed how to increase the number of descriptions and improve link integrity.
Important considerations were the audience for it and the criteria for inclusion.
Note:
The Working Group will cooperate with and contribute to efforts to maintain a Tool and application index. This index should provide data in RDF and OWL format in addition to a human-friendly presentation format. The index should provide only references to materials when they have a home elsewhere in the Web but may host materials developed by or contributed to the Working Group. The Working Group may choose to offer some 'value add' by highlighting materials that in its view support the Working Group's other Focus Areas in some noteworthy manner. Preference is given to open-source software.
Audience
Several possible audiences
- 1. researchers or others looking for material to use to promote or explain the Semantic Web (e.g. Guus' usecase - the best business and non-business-related demonstrators showing the value of the semantic web)
- 2. potential users of the semantic web, looking for how it can help them
- 3. developers looking for inspiration
- 4. teachers looking for material for their tutorials
- ...more?
Note that
The aim of this Semantic Web Best Practices and Deployment (SWBPD) Working Group is to provide hands-on support for developers of Semantic Web applications.
Criteria for inclusion
Some suggestions:
- App or demo must have either downloadable application or online demos (or some html page illustrating the application with screenshots?) - aim would be to show people immediately what the application/demo can do (the charter supports any of these)
- App/demo must use RDF or OWL (the charter does not state anything on this)
- Preference should be given to open source applications (see charter). This is because the SWBP's primary audience is developers
- App/demo must have a DOAP file, normally on the site of the app/demo itself
Some other input material:
What is a Semantic Web Application?
A Semantic Web Application has to meet the following minimal requirements.
1. First, the information sources used should be geographically distributed, should have
diverse ownerships (i.e. there is no control of evolution), should be heterogeneous
(syntactically, structurally, and semantically), and should contain real world data, i.e.
are more then toy examples.
2. It is required that all applications assume an open world, i.e. assume that the
information is never complete.
3. Finally, the applications should use some formal description of the meaning of the data.
Besides the minimal criteria, a number of desires are formulated.
The application uses data sources for other purposes or in another way than originally
intended
Using the contents of multi-media documents
Accessibility in multiple languages
Although we expect that most applications will use RDF, RDF Schema, and OWL, this is not an
official requirement.
ADTF History
Below is the template used to create the fields for applications and demos descriptions. This is now obsoleted in favour of using DOAP. We used the ESW weblog - http://esw.w3.org/mt/esw/ to create these, using the html template in Libby's June 2004 mail to add more. See Applications and demos Weblog at http://esw.w3.org/mt/esw/archives/cat_applications_and_demos.html
Template
TITLE Short label of the tool /demo /application. URL Main / official site where it can be found. DATE THE APP OR DEMO WAS CREATED DESCRIPTION Concise description of the tool /demo /application. USECASE Usecase illustrating the tool AUTHOR(S) Use author or contact, preferably author NAME EMAIL ORGANIZATION NAME ORGANIZATION URL CONTACT(S) NAME EMAIL ORGANIZATION NAME ORGANIZATION URL DOCUMENTATION A url of an informative document about the app or demo CATEGORIES VERSION CREATOR OF THE RECORD EMAIL NAME DATE RECORD CREATED DATE RECORD MODIFIED