DCMI Collection Description Community Group
From today, 18 December 2006, the Dublin Core Metadata Initiative (DCMI) Collection Description Community Group is available as a forum for discussion about collection-level description. The charter of the group is:
---
The DCMI Collection Description Community is a forum for individuals and organisations with an interest in collection-level description and in the use of Dublin Core metadata for that purpose.
More specifically, it also provides a forum for discussion of issues related to the implementation of the DCMI Collection Description Application Profile.
---
The group operates as a jiscmail listserv (http://www.jiscmail.ac.uk/lists/DC-COLLECTIONS.html) open to everyone, although you do have to join the list to be able to post to it. The group also has a website at http://www.dublincore.org/groups/collections/
There is also an associated Task Group that is responsible for continuing the development of the DCMI Collection Description Application Profile. Progress is available from the Wiki:
http://dublincore.org/collectionwiki/
[The listserv was previously the DCMI Collection Description Working Group. But the structure for DCMI technical work has now been changed. DCMI Working Groups have been restructured as Community Groups that serve as open forums for discussion on particular topics or domains, and Task Groups that develop specific deliverables.]
Collection Description is an important component of a Service Registry. The purpose of very many services is to provide access to a collection of data / information. In IESR terminology these are known as 'informational' services, whereas 'stand-alone' services are known as 'transactional'. The collection description part of the IESR metadata is based on the DCMI Collection Description Application Profile (which also informs the NISO Metasearch Initiative Collection Description Schema), although there are some IESR-specific extensions. The use of standard application profiles is important for interoperability. IESR is an example of using the DCMI Collection Description Application Profile in practice.
There have been suggestions that a service registry such as IESR should describe services as primary resources, with any data collections they support as secondary. But it seems to me that such a model is not so clean as the IESR model. Because most services provide access to data, that data collection needs some description, and where several services provide access to a single collection there would be multiple descirptions of it.
There have also been suggestions that there should be separate registries for collections and for services. However IESR's experience has shown that describing both types of resource in a single registry fits together well. It would be possible to provide effectively separate registries by appropriate views on IESR if there were a requirement.
---
The DCMI Collection Description Community is a forum for individuals and organisations with an interest in collection-level description and in the use of Dublin Core metadata for that purpose.
More specifically, it also provides a forum for discussion of issues related to the implementation of the DCMI Collection Description Application Profile.
---
The group operates as a jiscmail listserv (http://www.jiscmail.ac.uk/lists/DC-COLLECTIONS.html) open to everyone, although you do have to join the list to be able to post to it. The group also has a website at http://www.dublincore.org/groups/collections/
There is also an associated Task Group that is responsible for continuing the development of the DCMI Collection Description Application Profile. Progress is available from the Wiki:
http://dublincore.org/collectionwiki/
[The listserv was previously the DCMI Collection Description Working Group. But the structure for DCMI technical work has now been changed. DCMI Working Groups have been restructured as Community Groups that serve as open forums for discussion on particular topics or domains, and Task Groups that develop specific deliverables.]
Collection Description is an important component of a Service Registry. The purpose of very many services is to provide access to a collection of data / information. In IESR terminology these are known as 'informational' services, whereas 'stand-alone' services are known as 'transactional'. The collection description part of the IESR metadata is based on the DCMI Collection Description Application Profile (which also informs the NISO Metasearch Initiative Collection Description Schema), although there are some IESR-specific extensions. The use of standard application profiles is important for interoperability. IESR is an example of using the DCMI Collection Description Application Profile in practice.
There have been suggestions that a service registry such as IESR should describe services as primary resources, with any data collections they support as secondary. But it seems to me that such a model is not so clean as the IESR model. Because most services provide access to data, that data collection needs some description, and where several services provide access to a single collection there would be multiple descirptions of it.
There have also been suggestions that there should be separate registries for collections and for services. However IESR's experience has shown that describing both types of resource in a single registry fits together well. It would be possible to provide effectively separate registries by appropriate views on IESR if there were a requirement.
0 Comments:
Post a Comment
<< Home