No representations in disk image and video examples?

[kieranjol]

Hi,

I'm more familiar with the standard PREMIS data dictionary than with linked data, but I'm confused as to why there's just Intellectual Entities and Files in the video and disk image examples. There are two physical representations in the disk image example (two computers if I recall correctly), but the representation for the disk images themselves isn't present, and the same is true for the video example. Is there a reason why representation was skipped here? it is present for the classic Animal Antics example. I found this commit from @BertrandCaron where Representation was (correctly it appears) changed to File PREMIS-OWL-Revision-Team/premis-owl@1fdda92 - but I'm mostly just curious why Representation was skipped in general.

Best,

Kieran O'Leary
National Library of Ireland

[BertrandCaron]

Hi @kieranjol,

Intellectual Entities in PREMIS can be represented by any other type of Object: Representation, File or Bitstream (cf. the diagram p. 9 of the Data Dictionary, https://loc.gov/standards/premis/v3/premis-3-0-final.pdf#page=19).

So institutions might prefer to skip the Representation level if they don't need this way of grouping files - the property "is represented by" conveys the information that all resources this property points to are alternative representation of an IE.

(Which suggests, by the way, that Representation should not be a disjoint class from File and Bitstream.... we should correct this!)

Kind regards,

Bertrand

[kieranjol]

Thank you so much for this!! I’m not as familiar with OWL so I think I understand disjoint classes more due to your pull request!

…

On Thu 2 Feb 2023 at 17:19, Bertrand Caron ***@***.***> wrote: Hi @kieranjol <https://github.com/kieranjol>, Intellectual Entities in PREMIS can be represented by any other type of Object: Representation, File or Bitstream (cf. the diagram p. 9 of the Data Dictionary, https://loc.gov/standards/premis/v3/premis-3-0-final.pdf#page=19). So institutions might prefer to skip the Representation level if they don't need this way of grouping files - the property "is represented by" conveys the information that all resources this property points to are alternative representation of an IE. (Which suggests, by the way, that Representation should not be a disjoint class from File and Bitstream.... we should correct this!) Kind regards, Bertrand — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAITFPTJULU4LEJFPH36SKTWVPUB3ANCNFSM6AAAAAATQ52D3Y> . You are receiving this because you were mentioned.Message ID: ***@***.***>