<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Quaestiones Informaticae Vol 5 No 3</title>
<link>https://ir.unisa.ac.za/handle/10500/24190</link>
<description/>
<pubDate>Wed, 06 May 2026 12:52:56 GMT</pubDate>
<dc:date>2026-05-06T12:52:56Z</dc:date>
<item>
<title>Generating relations using formal grammars</title>
<link>https://ir.unisa.ac.za/handle/10500/24249</link>
<description>Generating relations using formal grammars
von Solms, S. H.
Grammars generating 2-dimensional arrays have been studied by many people [1, 2, 3, 4). One effort was&#13;
Random Context Array Grammars [4], where different types of context conditions placed on the production, were&#13;
used to control the generating process.&#13;
Relations, as used in relational data bases, can be considered as rectangular arrays, and therefore it should be&#13;
possible to generate and manipulate relations using 2-dimensional Grammars.&#13;
Simple Relation Grammars generate relations, and can simulate some unary operations like select and&#13;
project on these relations.&#13;
Extended Relation Grammars also generate relations, but these relations can communicate with each other&#13;
within a "Extended Relation Schema (ERS)". Within such an ERS binary operations like union and join can be&#13;
simulated.&#13;
This paper is a summary of a research project of which certain parts have already been submitted for&#13;
publication.
</description>
<pubDate>Thu, 01 Jan 1987 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://ir.unisa.ac.za/handle/10500/24249</guid>
<dc:date>1987-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Pointers as a data type</title>
<link>https://ir.unisa.ac.za/handle/10500/24246</link>
<description>Pointers as a data type
Philips, N.C.K.; Postma, Stef W.
The distinction between an abstract data type and an implementation of a data type is not as&#13;
clear as is commonly thought. A hash table can be used to implement the type bag but few of our&#13;
colleagues think of a hash table as itself being a data type. Similarly, pointers can be used to give&#13;
a linked implementation of the data type list, but few of us seem to think of pointers as&#13;
themselves forming a data type. However we shall give an algebraic specification of a pointer&#13;
data type which is an abstraction of the representation of pointers in Pascal. The usual linked&#13;
structures can then be specified abstractly via mutually recursive type specifications. In addition&#13;
we shall describe a uniform method of constructing implementations of data type specifications&#13;
via operations on strings.
</description>
<pubDate>Thu, 01 Jan 1987 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://ir.unisa.ac.za/handle/10500/24246</guid>
<dc:date>1987-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Common approach to some informational systems</title>
<link>https://ir.unisa.ac.za/handle/10500/24245</link>
<description>Common approach to some informational systems
Orlowska, M.E.
In this paper we consider relationships between a complete system [6], an L-system [3], a stochastic&#13;
system [13] and an N-system [8]. We introduce a notion of the induction of one system by another. We prove&#13;
the important fact that an N-system is a common generalization of all the systems mentioned above. This fact&#13;
is clearly demonstrated using geometric characterization of the set of subcontinua of the internal &lt;0, l&gt;.
</description>
<pubDate>Thu, 01 Jan 1987 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://ir.unisa.ac.za/handle/10500/24245</guid>
<dc:date>1987-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Three packaging rules for information system design</title>
<link>https://ir.unisa.ac.za/handle/10500/24244</link>
<description>Three packaging rules for information system design
Mende, J.
After identifying the processing functions required in a computer based information system, the designer needs&#13;
to combine them into an optimal set of load units. Some "packaging" arrangements yield a better system than&#13;
others, depending upon characteristics of the data collected from external sources and the data extracted for external&#13;
users. An effective and technically efficient system satisfies three rules.&#13;
1. If two user data types are needed at different times, the corresponding extract functions should be&#13;
separated in different load units.&#13;
2. If source data predates the user data derived from it, the corresponding collect and extract functions&#13;
should be separated in different load units.&#13;
3. If two source data types are available at different frequencies, one being less frequent than the user&#13;
data derived from it, the corresponding collect functions should be separated in different load units.
</description>
<pubDate>Thu, 01 Jan 1987 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://ir.unisa.ac.za/handle/10500/24244</guid>
<dc:date>1987-01-01T00:00:00Z</dc:date>
</item>
</channel>
</rss>
