Yes -- in effect, Lars, the ISTC is a FRBR expression identifier, though there may be some minor variations in detail. Of course, you can then build up a cluster of ISTCs, each related to the other in some way (eg by translation, by adaptation, by abridgement, by revision...), and that cluster can be more like a FRBR work. The links between ISTCs are as important as the ISTCs themselves, as they represent both workflow and IP changes. Graham Graham Bell EDItEUR Tel: +44 20 7503 6418 EDItEUR Limited is a company limited by guarantee, registered in England no 2994705. Registered Office: United House, North Road, London N7 9DP, UK. Website: http://www.editeur.org On 26 Feb 2014, at 10:57, Svensson, Lars wrote: All, just a short observation/question from me: • Will your team be making use of ISTC? Again it is still early for decisions in this area. However we would not expect to store the ISTC code as a property of Work ISTC is one of many work based data sets, from national libraries and others, that it would be interesting to investigate processes for identifying sameAs relationships between. I might be mistaken, but IIRC each translation of a text gets its own ISTC which renders the ISTC language-specific. Since frbr:Works are language-independent and language is part of frbr:Expression, the work _cannot_ contain an ISTC. Correct? /Lars P. S. Interesting stuff going on at OCLC, I haven't delved into it yet, but shall try to in the next couple of days!
Received on Wednesday, 26 February 2014 11:09:11 UTC