Kiyong Lee · Cambridge University Press eBooks · 2023
This chapter introduces a concrete syntax. It is ideally isomorphic to an abstract syntax that specifies a semantic annotation scheme, while providing a format for representing annotation structures. This format can represent them either in a serialized way from left to right, or in graphic images or tabular forms with linking arrows. Representation formats may vary, depending on kinds of the use of annotation. Human readers, for instance, prefer tabular formats especially for illustrations or demonstrations. For the purposes of merging, comparing, or exchanging various types of annotations or different annotations of the same type, graphs are considered useful. In this chapter, I introduce a graphic annotation format, called GrAF, for linguistic annotation. For the construction of larger corpora, however, there are practical computing reasons to prefer a serialization of annotations. For the serialized representation of annotation structures, this chapter mainly discusses two formats: (i) XML and (ii) pFormat, a predicate-logic-like representation format, which represents annotation structures in a strictly serial (linear) manner by avoiding embedded structures.
Cited by 0
Apress eBooks · 2006
This chapter introduced the topic of object serialization services. As you have seen, the .NET platform makes use of an object graph to correctly account for the full set of related objects that are to be persisted to a stream. As long as each member in the object graph has been marked with the [Serializable] attribute, the data is persisted using your format of choice (binary, SOAP, or XML).
Cited by 0
Ger P. Reesink · 1987
Cited by 0
Colden Cullen, Wozniak, Tyler, Christenson, Eric et al. · Zenodo (CERN European Organization for Nuclear Research) · 2014
Fixed issues with serializing multidimensional arrays as Component members.
Cited by 0Open access
Mathias Göbel · Front Matter · 2018
Here is a cheat sheet to XQuery serialization.
Cited by 0Open access
Hoz Baños, Giovanna de la · Gredos (University of Salamanca) · 2019
Trabajo de Fin de Máster en Evaluación y Desarrollo de Medicamentos. Curso 2018-2019
Cited by 0
Apress eBooks · 2007
In Chapter 16, you learned about the functionality provided by the System.IO namespace. As shown, this namespace provides numerous reader/writer types that can be used to persist data to a given location (in a given format). This chapter examines the related topic of object serialization. Using object serialization, you are able to persist and retrieve the state of an object to (or from) any System.IO.Stream-derived type.
Cited by 0
B Beumers · Bristol Research (University of Bristol) · 2009
Cited by 0
Requena Espí, Francisco · RiuNet (Politechnical University of Valencia) · 2015
The lack of Unity3D runtime serialization support made me research what solutions other teams were using to achieve what we wanted. \nI found tons of serialization solutions out there developed by third-parties, but none of them fit our needs for Tactical Heroes, the mobile game I’ve been working on for almost two years now at eRepublik Labs. \nAfter some time using others’ solutions, I found we were using tools that weren’t giving results we were comfortable with. So, I decided to develop a robust set of tools and libraries to help any Unity3D user to handle runtime serialization, and carry the process as comfortable as possible. \nThe APIs are cleverly designed to fit Unity3D ones. They’re extensible and nonintrusive, made to be easily implemented on every project that demands runtime serialization. And the system don’t rely on an specific serialization format or language, but instead gives you the choice of implement your own language parsers and writers on top. Those are the key features of the tool I’m going to talk about in this paper, a tool codenamed as Abaddon.
Cited by 0
António Rito Silva, João Pereira, Rito Silva Jo Ao Pereira et al. · 2007
This paper describes the Local Serialization pattern which decouples object concurrency control policies from objectspecific algorithm semantics and concurrency generation policies. The pattern was designed in the context of a development process for distributed applications which considers concerns and abstractions. Concerns are the distribution issues that should be solved during the development process. Concerns are divided into three levels of abstraction: model, policy and mechanism. The Local Serialization pattern intends to support policies for the concurrency control concern within a shared resource. 1 Introduction In this paper we present the Local Serialization pattern designed according to the approach presented in [Silva 95d] for the development process of distributed applications. We proposed a constructive development with separation of concerns. Applications are developed in a stepwise manner, handling one concern at a time. The Local Serialization pattern is related ...
Cited by 0
Stachówna, Grażyna · Homo Politicus (Academy of Humanities and Economics in Lodz) · 2015
Cited by 0
Michael McMillan · Cambridge University Press eBooks · 2004
Serialization is the process of capturing the current state of a class object and writing the state to disk. Serialization allows you to make a class object persistent, which means that you can save the current state of an object while a program is running and at a later time retrieve that state and continue using the object. In this chapter, we'll show you how to perform both serialization and deserialization, which is retrieving an object's state from disk.
Cited by 0
Matthias Schlögl, Maximilian Kaiser, Ágoston Zénó Bernád et al. · Zenodo (CERN European Organization for Nuclear Research) · 2020
This is a Json serialisation of the enriched version of the Austrian Biographical Dictionary. The data was enriched during the Austrian Prosopographical Information System (APIS) project. It contains data on ~19.000 persons who had an impact on Austrian soil and died between 1815 and 1955. This version of the APIS data uses the internal Json schema for serialization. It is the most complete serialization of the data. Please refer to Matthias Schlögl for any inquiries.
Cited by 0Open access
Mathias Göbel · Front Matter · 2018
Here is a cheat sheet to XQuery serialization.
Cited by 0Open access
III Bobbitt · OSTI OAI (U.S. Department of Energy Office of Scientific and Technical Information) · 2023
Methods for forming an identifying mark in a structure are described. The method is used in conjunction with an additive manufacturing method and includes the alteration of a process parameter during the manufacturing process. The method can form in a unique identifying mark within or on the surface of a structure that is virtually impossible to be replicated. Methods can provide a high level of confidence that the identifying mark will remain unaltered on the formed structure.
Cited by 0Open access
Matthias Schlögl, Maximilian Kaiser, Ágoston Zénó Bernád et al. · Zenodo (CERN European Organization for Nuclear Research) · 2021
This datatset contains a Json serialization of the enriched version of the Austrian Biographical Dictionary. The data was enriched during the Austrian Prosopographical Information System (APIS) project. It contains data on ~19.000 persons who had an impact on Austrian soil and died between 1815 and 1955. This version of the APIS data uses the internal Json format and contains therefore the richest data available. Please refer to Matthias Schlögl for any inquiries.
Cited by 0Open access
Nick Wienholt · Apress eBooks · 2004
As with other areas of functionality within the Framework Libraries, the System.IO namespace replaces a multitude of APIs that exist in the unmanaged world for file and directory management. The types in the IO namespace offer most of the functionality available through Win32, with some notable exceptions such as multistream and memory-mapped files. Streams play an important role in the IO namespace, and they allow services to be transparently applied to data flow, which can be used to boost performance in a number of scenarios.KeywordsFile SystemBuffer SizeStream TypeDisk AccessInternal BufferThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
Cited by 0
Troy J. Bassett · Opus: Research & Creativity (Indiana University – Purdue University Fort Wayne) · 2014
Cited by 0
Chaokun Yang, Pengbo Nie, Ziyi Lin et al. · 2026
Object serialization is critical in Java, which preserves objects in memory and transfers them among software systems if needed. However, the serialization techniques of modern Java systems are usually inflexible and inefficient under heavy serialization workloads, as they rely on manually-defined object schemas or omni-functional serializers. To tackle the above problem, we reveal a novel, serialization-specific optimization opportunity in Java. Based on it, we develop JOSer (Just-in-time Object SERializer), an efficient, Just-in-Time (JIT) object serialization technique. At runtime, JOSer generates a set of class-specific, JIT-friendly object serializers (i.e., serialization code), and then continuously optimizes them with the JIT compiler of Java Virtual Machine (JVM). JOSer also shares the metadata of objects under serialization and the serializers under optimization. We evaluate JOSer against six Java serialization techniques including OpenJDK's built-in serialization technique. Overall, JOSer improves the throughput by up to 20~83× in serialization and 43~229× in deserialization. JOSer has been successfully deployed in real-world products, reducing serialization CPU usage of Flink by 35.32~41.14% and latency of search recommendations by 30+ ms. JOSer grounds Apache Fory#8482;, an open-source serialization framework available at https://fory.apache.org/.
Cited by 0Open access
Michæl Philippsen, Bernhard Haumacher · Lecture notes in computer science · 1999
Cited by 43