Schema for an ISO2146 collections and services registry Service object. Services really need some work in order to determine how we can represent them best for both human and machine-usable consumption. This really needs some real-world use cases. Many of the ISO2146 Service object properties have been excluded from this schema. Use cases need to be developed to address this. The assumption at the moment is that Function, Product, Service Times, Access Policy, Policy Combining Algorithm, Service Description and Protocol Information if important would be included in a the 'description' element. I'm not sure the registry would carry out a lot of service execution or simply direct the user/automaton to the correct location. Services can be supported at a higher level than a collection. For example in DSpace OAI-PMH is supported at a repository level however individual collections within the repository can be harvested. What needs to be exposed at a collection level? In the example a link to the default DC implementation is provided for a collection, however if a service user wanted to know about the data source and what metadata prefixes are supported it's the repository level response which provides this information.