ACTION SteveH: Write up a service description of features supported for his service

OK, here's a sketch of how I would descibe my main service:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dawg: <http://example.com/dawg#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix akt: <http://www.aktors.org/ontology/> .

<http://triplestore.aktors.org/rdql/>
        rdf:type dawg:HTTPQueryService ;
        dawg:closedOver <http://www.w3.org/2000/01/rdf-schema#> ;
        dawg:supportsDataType xsd:integer, xsd:float ;
        dawg:querySyntax <http://www.w3.org/Submission/RDQL/> ;
        dawg:resultFormat <http://www.w3.org/TR/rdf-sparql-XMLres/> ;
        dawg:usesOntology akt:support, akt:portal, akt:rdfcompat, akt:inca,
                <http://purl.org/dc/elements/1.1/>,
                <http://xmlns.com/foaf/0.1/> .

I attended a workshop on linking semnatic websites on Monday, and briefly
described the DAWG work, including the possibility of a description such
as this, and the idea was warmly received.

At the Helsinki FTF I was in favour of supporting single service URIs that
allowed query with a variety of syntaxes, mainly to prevent duplication of
query service descriptions, but since then I've reconsidered and I now
prefer something where each distinct query URI supports a specific query
syntax.

- Steve

Received on Wednesday, 9 February 2005 15:00:47 UTC