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

Help for DC-ARCHITECTURE Archives


DC-ARCHITECTURE Archives

DC-ARCHITECTURE Archives


DC-ARCHITECTURE@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-ARCHITECTURE Home

DC-ARCHITECTURE Home

DC-ARCHITECTURE  July 2009

DC-ARCHITECTURE July 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: More on lists

From:

Karen Coyle <[log in to unmask]>

Reply-To:

DCMI Architecture Forum <[log in to unmask]>

Date:

Sat, 18 Jul 2009 10:13:05 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (130 lines)

The idea here is that there are folks who want to use standard 
vocabularies, but they don't want to use the ENTIRE  vocabulary, only a 
selection. Language is a good example, because the ISO language list is 
huge and you may not want to allow all those values in your metadata. So 
you make a selection and want to validate that you are using only the 
values in your selection.

You could create your own list and not refer to the standard list, but 
I'm thinking of a case where the standard list may have additional 
information (code + display form, definitions, see references etc.). 
Plus, there is always an advantage to using the standard list because it 
may change and you want to be in sync with those changes.

So, how could this be done in your application profile? Or would you 
have to do this in your application, not the application profile?

kc

Mikael Nilsson wrote:
> tor 2009-07-02 klockan 11:11 -0700 skrev Karen Coyle:
>   
>> The following example shows a /description/ in which the third 
>> /statement/ includes a /non-literal value surrogate/ containing two 
>> /value strings/:
>>
>> [excerpt from example:]
>>
>>   <dcds:statement dcds:propertyURI="http://purl.org/dc/terms/subject"
>>                    dcds:vesURI="http://purl.org/dc/terms/LCSH">
>>       <!-- non-literal value surrogate - multiple value strings -->
>>       *<dcds:valueString>Metadata</dcds:valueString>*
>>       *<dcds:valueString>Métadonnées</dcds:valueString>*
>>     </dcds:statement>
>>
>>
>> Because this is XML and not XSD (or some other language that includes 
>> constraints) it isn't clear to me what the meaning is to having both a 
>> vesURI (as it is called here) and some value strings. I don't see a 
>> reason to include specific values unless the intention is to limit the 
>> selection to those values, but perhaps I am missing something...
>>     
>
> Karen, it seems to me (?) you're missing that this is instance data. In
> instance data there is no notion of "selection". Only gving a VES would
> not actually give you a useful value.
>
> The reason there are several values is in this case simply to give
> several translations, for the benefit of the consumer (who could just as
> well, but not as easily giver the lack of a value URI, lock up the
> translation in an LCSH document somewhere).
>
> Or did you mean something else completely?
>
> /Mikael
>
>  
>
>   
>> kc
>>
>>
>> Karen Coyle wrote:
>>     
>>> I know I may seem obsessed with lists, but the fact is that the 
>>> library world relies heavily on controlled lists of values and these 
>>> will make up a large part of records used by libraries. I'm also 
>>> struggling with the controlled "lists" which are more than simple 
>>> values -- those that have structure or additional data. I'd like to be 
>>> able to define all of these so that we can be clear when we are 
>>> discussing them. Sometimes the current terminology and common view 
>>> gets in our way.
>>>
>>> 1) external lists -- these are lists that are external to the 
>>> application profile, maintained elsewhere. They may be simple lists, 
>>> or they may be data structures such as name authority records. What 
>>> the application profile will incorporate will be an identifier for the 
>>> list, but it seems to me that the AP itself may not have any 
>>> "knowledge" of the nature of what it points to nor of how the 
>>> application gains access to the list values.
>>>
>>> 2) internal lists -- when the values in the list are included in the 
>>> AP definition. These values are probably going to be literals, 
>>> although they may be structured (e.g. a code and a display value). I 
>>> suppose they could have URIs, but that seems both unlikely and 
>>> unnecessary. If you think anyone else will want to share them, then 
>>> you should move them out of the AP into a neutral space or registry.
>>>
>>> I now have a third possible category...
>>>
>>> 3) external lists, with a selection of values -- this is a situation 
>>> where one refers to an external list (e.g. iso 639-2), but the AP 
>>> selects a subset of the values as valid for the application ("en" "fr" 
>>> "sp"). The values may be simple strings, structured strings, or URIs, 
>>> and how the application should work with them should be based on the 
>>> referred to list, not the AP statement.
>>>
>>> Now here's a question: what if the external list is NOT just simple 
>>> values and you want to refer to a part of the structure of those 
>>> values? For example, with the ISO languages, the standard list has 
>>> codes and spelled out forms of the language. How could you indicate 
>>> that you want to use just the code, or just the spelled out form, or 
>>> both? The library name authority records have numerous fields and 
>>> subfields. What if you only want to select personal name fields (100 
>>> tag) and only certain subfields from that field? Can these be defined 
>>> in the AP, and if so, how? Or is this best left for the application 
>>> itself?
>>>
>>> kc
>>>
>>>       
>> -- 
>> -----------------------------------
>> Karen Coyle / Digital Library Consultant
>> [log in to unmask] http://www.kcoyle.net
>> ph.: 510-540-7596   skype: kcoylenet
>> fx.: 510-848-3913
>> mo.: 510-435-8234
>> ------------------------------------
>>
>>     

-- 
-----------------------------------
Karen Coyle / Digital Library Consultant
[log in to unmask] http://www.kcoyle.net
ph.: 510-540-7596   skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2024
January 2024
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
September 2022
August 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
November 2021
October 2021
September 2021
August 2021
July 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
September 2020
August 2020
July 2020
June 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
December 2000
November 2000
October 2000


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