JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-COLLECTIONS Archives


DC-COLLECTIONS Archives

DC-COLLECTIONS Archives


DC-COLLECTIONS@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-COLLECTIONS Home

DC-COLLECTIONS Home

DC-COLLECTIONS  January 2005

DC-COLLECTIONS January 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Betr.: Re: Review of Collection type vocabulary

From:

Pete Johnston <[log in to unmask]>

Reply-To:

DCMI Collection Description Group <[log in to unmask]>

Date:

Fri, 21 Jan 2005 18:17:06 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (70 lines)

Hi Theo,

> For CLDType in case of collections with mixed contents it
> might be worth considering to add a an encoding scheme for a
> value that contain the number of items of a specific type:
>
> <dc:type>collection</dc:type>
> <cld:CLDType xsi:type="key-value">image=1000<cld:CLDType>
> <cld:CLDType xsi:type="key-value">book=1000000<cld:CLDType>
> <cld:CLDType xsi:type="key-value">article=50%<cld:CLDType>
>
> It looks horrible

;-)

> but it might help the user in using the CLD
> for finding his targets to search in.

I can see that providing this information in a structured form could be
valuable for resource discovery, but if we decided to support this in
the DC CD AP, I think we'd need to consider how best to model/represent
it.

I'm inclined to say it isn't an appropriate value for the dc:type
property: the value of dc:type is always a class (or a "value string"
which represents that class - "Text" for the class dcmitype:Text, and so
on). And the use of dc:type in a statement always says "This resource is
an instance/member of that class".

I suppose it could be argued that "image=1000" represents the class of
collections of 1000 image items, but I think it's really stretching the
use of dc:type - that's what I meant in an earlier message about not
"overloading" the type mechanism with information that we should really
provide by other means.

If it is really a requirement to be able to state the collection size in
terms of numbers of items of specific types, then it seems to me we need
to consider something like a "Collection Size"(?) encoding scheme which
would define values for dcterms:extent.

I think to model it properly might be quite complex e.g. the size (the
value of dcterms:extent) isn't just one number-of-items/item-type pair;
it's the aggregation/combination of several such pairs. So (written in
"fully striped" RDF/XML) you'd end up with something like

<dcmitype:Collection>

   <dcterms:extent>
      <some:CollectionSize>
         <some:itemCount>
            <some:ItemCount>
               <some:count>1000</some:count>
               <some:itemType rdf:resource="&dcmitype;Image"/>
            </some:ItemCount>
         </some:itemCount>
         <some:itemCount>
            <some:ItemCount>
               <some:count>1000000</some:count>
               <some:itemType rdf:resource="&dcmitype;Text"/>
            </some:ItemCount>
         </some:itemCount>
      </someCollectionSize>
   </dcterms:extent>

</dcmitype:Collection>

which is even more horrible!

Pete

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2011
November 2010
September 2010
August 2010
May 2010
April 2010
February 2010
September 2009
April 2009
January 2009
July 2008
May 2008
March 2008
January 2008
October 2007
September 2007
August 2007
July 2007
June 2007
April 2007
December 2006
November 2006
September 2006
August 2006
July 2006
June 2006
February 2006
January 2006
December 2005
November 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
February 2003
December 2002
September 2002
August 2002
July 2002
June 2002
April 2002
March 2002
February 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager