Managing entity versions within their contexts: A formal approach

Gançarski, Stéphane; Jomier, Geneviève

doi:10.1007/3-540-58435-8_205

Cited by 12 publications

(9 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This triggers a change propagation procedure, since the new version of an object X implies in a new version of the complex objects that have X as a component and cascades can reach very many objects [21]. This procedure automatically generates a lot of new, often useless, configurations [16].…”

Section: Version Control and Managementmentioning

confidence: 99%

“…Both identifiers are unique in the database. The multiversion database can be analyzed under two operational levels: logical level-presented to the client application-and physical level-managed by the DBMS [16]. At the logical level, the database is seen as a set of Database Versions (DBVs).…”

Section: The Multiversion Database Modelmentioning

confidence: 99%

“…9, DCC_X is a multiversion object with three versions v1, v1.1, and v1.2. It has an identification (Oid) that is independent of its version, as well as its physical version identification (PVid) [16]. Both identifiers are unique in the database.…”

Section: The Multiversion Database Modelmentioning

confidence: 99%

See 2 more Smart Citations

A Component Model and Infrastructure for a Fluid Web

Santanchè

Medeiros

2007

IEEE Trans. Knowl. Data Eng.

View full text Add to dashboard Cite

The Web is evolving from a space for publication/consumption of documents to an environment for collaborative work, where digital content can travel and be replicated, adapted, decomposed, fusioned, and transformed. We call this the Fluid Web perspective. This view requires a thorough revision of the typical document-oriented approach that permeates content management on the Web. This paper presents our solution for the Fluid Web, which allows moving from the document-oriented to a content-oriented perspective, where "content" can be any digital object. The solution is based on two axes: a self-descriptive unit to encapsulate any kind of content artifact-the Digital Content Component (DCC) and a Fluid Web infrastructure that provides management and deployment of DCCs through the Web, and whose goal is to support collaboration on the Web. Designed to be reused and adapted, DCCs encapsulate data and software using a single structure, thus allowing homogeneous composition and processing of any digital content, executable or not. These properties are exploited by our Fluid Web infrastructure, which supports DCC multilevel annotation and discovery mechanisms, configuration management, and version control. Our work extensively explores taxonomic ontologies and Semantic Web standards, which serve as a semantic bridge, unifying DCC management vocabularies, and improving DCC description/indexing/discovery. DCCs and infrastructure have been implemented and are illustrated by means of a running example, for a scientific application.

show abstract

Section: Version Control and Managementmentioning

confidence: 99%

Section: The Multiversion Database Modelmentioning

confidence: 99%

See 1 more Smart Citation

A Component Model and Infrastructure for a Fluid Web

Santanchè

Medeiros

2007

IEEE Trans. Knowl. Data Eng.

View full text Add to dashboard Cite

show abstract

“…The UMV methodology is supported by a multiversion database (Gançarski & Jomier, 1994), which is introduced in the next sub-section. We assume that both the producer and the user have a multiversion geographic database.…”

Section: S3mentioning

confidence: 99%

“…Internal identifiers are managed only by the system, conversely to external identifiers, managed by users. For further details on this approach, the reader is referred to (Cellary & Jomier, 1990;Bauzer-Medeiros & Jomier, 1993;Gançarski & Jomier, 1994;Cellary & Jomier, 2000).…”

Section: The Multiversion Geographic Databasementioning

confidence: 99%

A Methodology for Updating Geographic Databases using Map Versions

Peerbocus

Jomier

Badard

2002

Advances in Spatial Data Handling

Self Cite

View full text Add to dashboard Cite

Management Software for Monitoring Related Versions of Cultural Heritage Artifacts for Libraries and Museums

Athreya

Taswell

2021

Proceedings of the Association for Information Science and Tech

View full text Add to dashboard Cite

In cultural object conservation, tracking provenance has served as the foundational method of managing information for historical artifacts. To find data points, archivists identify related versions of an artifact at various time points. In this paper, we discuss four categories with versioned examples to display the importance of data points for identifying patterns over time through events in history, cultural heritage, performing arts, and fine arts. We describe our use of the Ashurbanipal diristry to document scholarly research regarding library tools and technologies for the preservation of cultural objects as well as the implementation of PORTAL-DOORS Project (PDP) utilities for tracing provenance and distribution of cultural objects and interoperability with bibliographic formats such as BIBFRAME and MARC from existing archival methods. KEYWORDS PORTAL-DOORS Project; time points; cultural heritage; archiving; artifact conservation. INNOVATIONS IN INFRASTRUCTUREWith the creation of cities, our definition of design principles has continuously changed to fit innovations of infrastructure in numerous fields of study. Buetow (2005) describes how biomedical database infrastructure, a fundamental archiving system, could improve the cross disciplinary transfer of knowledge between various communities. Similarly, infrastructure takes on many terms, from biomedical database infrastructure to civil engineering infrastructure which actively serves communities. During the Great Plague of London, without a plan to salvage the European sewage system, lack of maintenance led to the decline of the quality of city life (Bramanti et al., 2019). Following the plague, Bazalgette, the chief engineer of the Metropolitan Board of Works in London, proposed developing a system of collectors to drain sewage that overflowed from the River Thames (De Feo et al., 2014). These design principles have served as the basis for sewage infrastructure for decades, building on the foundations of basic infrastructure to iterate more effective forms of design in the future. Universally, the creation of infrastructure can be attributed to design principles that inform its use, meaning, and underlying features. Design principles are subject to iterations, changes, or improvements that in select cases create different versions of the same entity, or a form or variant of a type or original (Ganҫarski & Jomier, 1994). To evaluate the changes between key iterations of an object between various points in time, we examine sequential points in time and their comparable versions in a variety of fields: cultural heritage, events in history, fine arts, and performing arts. IDENTIFYING PATTERNS OVER TIMEEach domain-specific field uses its own defined methods of tracking related versions of historical artifacts. We explore four fields of study that aid in identifying trends in history, including events in history, cultural heritage, performing arts, and fine arts.

show abstract

Managing entity versions within their contexts: A formal approach

Cited by 12 publications

References 12 publications

A Component Model and Infrastructure for a Fluid Web

A Component Model and Infrastructure for a Fluid Web

A Methodology for Updating Geographic Databases using Map Versions

Management Software for Monitoring Related Versions of Cultural Heritage Artifacts for Libraries and Museums

Contact Info

Product

Resources

About