Re: [DAIA] Usage example for additional extent element

[Uwe R. <re...@he...>]

Am 15.03.2013 14:49, schrieb Jakob Voß:
> As far as I understand, you just argued for inclusion of holding
> information (which I called "extent") in DAIA. I got the same request
> from other users of DAIA.
Not in the sense of making DAIA to an OPAC. But yes, I think this could 
be a useful information to present.


>> So we are back to my initial example, which does not need any change of
>> DAIA's model.
>>> <limitation id="sparseHolding">
>>>      1983; 1985; 1988; 1990; 1992 - 1994; 1996
>>> </limitation>
>
> This would make sense if limitation was a property of an item:
>
> <item>
>     <limitation>1983; 1985; 1988; ...</limitation>
>     ...
> </item>
OK, now i got your point. This limitation is one of the item it's 
relevant to all forms of availability, not only for one or some.
Yes you are right.


Trying to follow your other points I'm a bit confused. Is the following 
example be consistent and valid for you?

     <item id="some:item">
       <limitation id="mydefinitions:sparseHolding"> (1)
         <message lang="de">
           Bitte beachten Sie den Bestandsverlauf
         </message> (2)
         1983; 1985; 1988; ...
       </limitation>
       <available service="loan">
         <limitation id="mydefinitions:short-time-loan" /> (3)
       </available>
       <available service="interloan">
         <limitation id="mydefinitions:only-university-libraries" >
           <message lang="en"> (4)
             Restricted to scientific libraries
           </message>
           <message lang="de">
             Nur für Universitäts- und Hochschulbibliotheken
           </message>
         </limitation>
       </available>
     </item>

(1) It should be no problem to construct an URI ;-)
(2) Reference to the discussion about messages. Even there is a message 
given, the content is needed for a raw informations.
(3) An 'id' is given, there is no real need for messages.
(4) An 'id' is given, it's still allowed to provide textual explanations 
anyway.

Uwe