Date: Thu, 28 Mar 2024 22:23:13 +0000 (UTC) Message-ID: <1591976049.13008.1711664593264@5e0fac51be52> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13007_955183611.1711664593260" ------=_Part_13007_955183611.1711664593260 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Great discussion tonight. I think the panel format is grea= t for BESSIG.
I was thinking that, like scholarly publications, data files are bare, s= tatic entities. Both should be encapsulated in more intelligence. &nb= sp;In the Object Oriented paradigm data is protected, encapsulated by softw= are, with methods which provide access to the data inside the object capsul= e. All data could be Object Oriented, perhaps at the file level. &nbs= p;All such OO files could be stored in OO filesystems and OO databases. &nb= sp;There could be a base interface that is common to all such OO files. &nb= sp;These common methods could be stuff like give me your DOI, give me your = provenance. When the software is to tightly bound to the data, unlike= the approach in which you distribute bare files and require software tools= to inspect the data, you can do something like embedding a virus in the da= ta, which is activated whenever the data object is accessed. In OO, w= hen an object is instantiated, its constructor is called. This could = be the virus, which does a number of things, like notify you that your data= is being accessed. You would always know where your data goes and wh= o uses it because it tells you. Otherwise, you rely on people to cite= it or have to search publication databases to discover who mentions your d= ata.