Although there were some changes in the metadata response format during the Madrid 2005 meeting, it was not thoroughly reviewed. Currently, a metadata response looks like:
http://www.flies.au/pywrapper/flies Australian fruit flies collection of georeferenced records observations fuit flies observation australia diptera Tephritidae Australian Fruit Flies free 2006-01-01T00:00:00 TAPIR working group Frank Sinatra f.sinatra@tapir.com system administrator Hosting Provider However, many elements overlap with other elements from well-known schemas like DublinCore and GeoRSS. If we encode such contents using these other schema elements, a metadata response could look like:
Australian Fruit Flies http://purl.org/dc/dcmitype/Service http://www.flies.au/pywrapper/flies Australian fruit flies collection of georeferenced records observations EN fuit flies observation australia diptera Tephritidae Australian Fruit Flies TAPIR provider free 2006-01-01T00:00:00 technical host someGUID TAPIR working group TAPIR-WG http://somehost/entitylogo.png Description about the TAPIR working group http://somehost/moreinfo system administrator Frank Sinatra Main singer some phone number f.sinatra@tapir.com 45.256 -71.92 ---+ Roles Both entities and contacts are repeatable and have a role assigned to them. The role is based on a simpletype union between an enumeration (to have a common base set of roles) and xsd:string to allow any other role as well. ---+++ entityRoleType * data supplier * technical host ---+++ contactRoleType * data administrator * system administrator