Reference data on the Web DEPUIS

Cover page
1 Introduction
2 Simple examples of reference data
3 Simple application using reference data

4 Lifecycle assessment for an individual house
A Lifecycle assessment ontology
B URI assigned to a thing by an ISO standard

3 Simple application using reference data

3.1 CORGI registration for gas fitters

In the UK, any person who installs or repairs gas fittings or appliances must be registered with an accreditation body called CORGI. The UK Government Health and Safety Executive provides advice on the use gas in homes on its site (note the intuitive structure of the HTTP URI). It makes the following statement:

Do I have to use a CORGI-registered installer to complete gas work?

Anyone employed to work on gas appliances in domestic premises must be a CORGI-registered installer and competent in that area of gas work. The gas installerís competencies are clearly marked on the back of the installerís CORGI registration card. If in any doubt you can ring CORGI or check their website to see if the installer is registered. Further information is provided under our registration body page.

The URI for the CORGI organisation is, and this can be regarded as both the web page and the identifier of the organisation. Ideally, CORGI would also define as the URI for the class of person "CORGI registered installer", and would provide a web service to check with the URI (Although this structure has not been followed, the CORGI web site is well structured.)

The use of the URI for the class of person "CORGI registered installer", would enable the following statement to be made using OWL:

The benefit of publishing information in this way, is that a trade directory could reliably compile a list of CORGI registered installers in a particular area.

3.2 A registry of widget maintainers

Consider a hypothetical registry, which maintains a register of widget maintenance organisations, with information about:

The registry may be provided by a commerical organisation, trade association or statutory body.

The information recorded for Fred Bloggs and Co. is expressed using N3 below:
  registry:companyName          "Fred Bloggs and Co." ;
  registry:logo        ;
  a                    ;
    [  :-             
       registry:departmentName  "Head Office" ;
       registry:postcode ;
       registry:location,-0.345678 ;
       registry:maintainedType  urn:iso:std:iso:12345:-6:tech:LowPressureWidget ;
       registry:maintainedType  urn:iso:std:iso:12345:-6:tech:HighPressureWidget
    ] ;
    [  :-             
       registry:departmentName  "Much Binding Depot" ;
       registry:postcode ;
       registry:location,-0.456788 ;
       registry:maintainedType  urn:iso:std:iso:12345:-6:tech:LowPressureWidget
    ] .

This fragment of N3 is more or less readable without a deep understanding of the syntax. It records the following information about company

The recording of this information requires the following reference data:

All that Fred Bloggs and Co has to supply is:

N3 is still a niche technology, so in practice the information will be recorded using RDF/XML as follows:

<registry:Company rdf:about="">
 <registry:companyName>Fred Bloggs and Co.</registry:companyName>
 <registry:logo rdf:resource=""/>
 <rdf:type rdf:resource=""/>
  <registry:Department rdf:about="">
   <registry:departmentName>Head Office</registry:departmentName>
   <registry:postcode rdf:resource=""/>
   <registry:location rdf:resource=",-0.345678"/>
   <registry:maintainedType rdf:resource="urn:iso:std:iso:12345:-6:tech:LowPressureWidget"/>
   <registry:maintainedType rdf:resource="urn:iso:std:iso:12345:-6:tech:HighPressureWidget"/>
  <registry:Department rdf:about=""/>
   <registry:departmentName>Much Binding Depot</registry:departmentName>
   <registry:postcode rdf:resource=""/>
   <registry:location rdf:resource=",-0.456789"/>
   <registry:maintainedType rdf:resource="urn:iso:std:iso:12345:-6:tech:LowPressureWidget"/>

Suppose the registry is maintained by "The Widget Owners Association". This organisation can collect the information provided by widget maintainers and provide it in a convenient form, sorted by location and type of widget. The record for Fred Bloggs and Co. on can be as follows:

Fred Bloggs and Co. Widget Maintainers Society member
Head Office AB12 3CD map low pressure widget
high pressure widget
Much Binding Depot AB12 4EF map low pressure widget

NOTE The ISO standards provide definitions of equipment classes, such as low pressure widget and high pressure widget. At present, with a few exceptions, these standards are on paper. It is important that they soon become Web standards to support the needs of industry.

Annex B is a paper written by the Industrial Data on the Web group under ISO TC184/SC4, which discusses how URIs assigned to things by ISO standards can be used by industry.

© CAESAR Systems Limited — Public deliverable of the DEPUIS project