
The Quatro vocabulary is defined in two separate documents: one for humans to read [DEF], the other is expressed as an RDF schema [RDFS] and is for machines to read. This document links the two and enables developers to use the machine-readable version in applications
The Quatro namespace is http://purl.org/quatro/elements/1.0/ and the recommended QName is quatro. The schema itself can be accessed from the namespace URL.
The schema declares that the permitted values for each descriptor is a Boolean, as defined in the XML Schema [XSD]. It is further declared that descriptors have a domain of Content Label as defined in the RDF Content Label schema. [RDF-CL].
The following example shows the key elements.
| Section 1 | <?xml version="1.0"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:label="http://www.w3.org/2004/12/q/contentlabel#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:quatro="http://purl.org/quatro/elements/1.0/#"> |
| Section 2 | <rdf:Description rdf:about="">
<dc:creator rdf:resource="http://www.trustmarkscheme.com" />
<dcterms:issued>2005-08-05</dcterms:issued>
<label:authorityFor>http://purl.org/quatro/elements/1.0/</label:authorityFor>
</rdf:Description> |
| Section 3 | <label:Ruleset rdf:ID="Ruleset">
<label:hasHostRestrictions>
<label:Hosts>
<label:hostRestriction>example.org</label:hostRestriction>
</label:Hosts>
</label:hasHostRestrictions>
<label:hasDefaultLabel rdf:resource="#label_1"/>
</label:Ruleset> |
| Section 4 | <label:ContentLabel rdf:ID="label_1">
<rdfs:label xml:lang="en">Providing suitable identification information;
Use of clear language that is fit for purpose; Privacy statement;
Content provider credentials; Providing relevant information
about content; Fair commercial communications and fair marketing
practices; Protection of children; Providing information on goods
and services; Providing contract information</rdfs:label>
<quatro:ga>1</quatro:ga>
<quatro:gb>1</quatro:gb>
<quatro:gc>1</quatro:gc>
<quatro:gf>ES</quatro:gf>
<quatro:gf>PT</quatro:gf>
<quatro:aa>1</quatro:aa>
<quatro:ab>1</quatro:ab>
<quatro:ra>1</quatro:ra>
<quatro:rb>1</quatro:rb>
<quatro:rc>1</quatro:rc>
<quatro:rd>1</quatro:rd>
<quatro:gk rdf:resource="quatro:WAI-A" />
</label:ContentLabel>
</rdf:RDF> |
Section 1 declares the required namespaces.
Section 2 describes the RDF document itself, when and by whom it was issued, and for which namespaces that labelling organisation is an authority. The last item is provided so that if the RDF instance contains descriptions from other schemes (perfectly possible!) then the responsibility for the use of the Quatro descriptors remains clear.
Section 3, the Ruleset, defines for which hosts the RDF instance can be applied and what the default label is. The data here says that the default Content label for example.org is "label_1".
Section 4 is the label itself. The majority of the descriptors have a Boolean value but two differ from this. First of all quatro:gf which states the labelled resource meets legal practice in ES and PT (Spain and Portugal). Secondly, the final descriptor declares that the labelled resource meets the W3C's Web Accessibility Guidelines to "level A."
RDF-CL is a specialised use case for RDF itself [RDF], designed as a platform for carrying any kind of metadata and as the foundation of the semantic web [SW]. It is anticipated that any trust mark scheme using the Quatro vocabulary will use only a portion of it and will want to add their own descriptors too. A Content Label may look more like the example below which includes terms from the Quatro and ICRA schemas plus another "example.".
<label:ContentLabel rdf:ID="label_ex"> <quatro:ga>1</quatro:ga> <quatro:gb>1</quatro:gb> <quatro:gf>ES</quatro:gf> <quatro:gf>PT</quatro:gf> <quatro:rb>1</quatro:rb> <quatro:rc>1</quatro:rc> <quatro:rd>1</quatro:rd> <ex:terma>1</ex:terma> <ex:termb>1</ex:termb> <extermc>1</extermc> <icra:nz>1</icra:nz> <icra:sz>1</icra:sz> </label:ContentLabel>
The RDF-CL schema also has support for other types of labelling and classification schemes and developers are encouraged to familiarise themselves with the many options.
| Class | Description | |
|---|---|---|
| WAI-A | Web Accessibility Initiative level A, defined by http://www.w3.org/TR/WAI-WEBCONTENT/ | |
| WAI-AA | Web Accessibility Initiative level AA, defined by http://www.w3.org/TR/WAI-WEBCONTENT/ | |
| WAI-AAA | Web Accessibility Initiative level AAA, defined by http://www.w3.org/TR/WAI-WEBCONTENT/ | |
| Property | Description | Range |
| General Criteria | ||
| ga | Providing suitable identification information | Boolean defined by XML schema |
| gb | Use of clear language that is fit for purpose | Boolean defined by XML schema |
| gc | Privacy statement | Boolean defined by XML schema |
| gd | Data protection contact point | Boolean defined by XML schema |
| ge | Enforcement mechanism | Boolean defined by XML schema |
| gf | Meets legal practice in: | ISO3166 two-character country codes. Defined by Dublin Core terms |
| gg | Usability | Boolean defined by XML schema |
| gh | Downloads and plug-ins | Boolean defined by XML schema |
| gi | Cross-browser compatible | Boolean defined by XML schema |
| gj | Transparent domain name | Boolean defined by XML schema |
| gk | WAI Accessibility level | |
| gl | Third-party content | Boolean defined by XML schema |
| Criteria for labelling to ensure accuracy of information | ||
| aa | Content provider credentials | Boolean defined by XML schema |
| ab | Providing relevant information about content | Boolean defined by XML schema |
| ac | Advertising and funding | Boolean defined by XML schema |
| Criteria for labelling to ensure compliance with rules and legislation for e-business | ||
| ra | Fair commercial communications and fair marketing practices | Boolean defined by XML schema |
| rb | Protection of children | Boolean defined by XML schema |
| rc | Providing information on goods and services | Boolean defined by XML schema |
| rd | Providing contract information | Boolean defined by XML schema |
| re | Clear confirmation process | Boolean defined by XML schema |
| rf | Contractual process (acknowledgement of order) | Boolean defined by XML schema |
| rg | Tracking tool | Boolean defined by XML schema |
| rh | Security policy | Boolean defined by XML schema |
| ri | Security of payment | Boolean defined by XML schema |
| rj | Data protection for children | Boolean defined by XML schema |
| rk | Complaints procedure | Boolean defined by XML schema |
| rl | Dispute settlement procedure | Boolean defined by XML schema |
| Terms used in operating the trust mark scheme itself | ||
| rdfURL | URL of the RDF instance | anyURI defined by XML Schema |
| N/A | Use dcterms:issued to specify the date on which the trust mark was awarded | See Dublin Core Terms definition |
| lastReviewed | The date on which the labelled site was last reviewed and on which it was found to still be in compliance with the TMS criteria | Sub Property Of Dublin Core Date |
| withdrawn | The date on which the labelled site was reviewed and found to have breached the TMS criteria | Sub Property Of Dublin Core Date |
| reviewer | The individual who reviewed the resource and awarded the trust mark | |
| approvedBy | The individual who checked the reviewer's awarding of the trust mark | |