Estrategias de Mezcla del Plan de Comercialización A Producto

The last main form of documentation is the written text. Additional information can be added by, for example, illustrations or tables (Reilly 1992, 160; Alusik and Sovarova 2015, 439; Kensek et al. 2004, 179). However, publications in print form previously limited the extent of possible media formats (Reilly 1992, 148; Ryan 2001, 257). With the progress of time, databases (tab. 2) and semantics were added to the traditional form of documentation (Kensek et al. 2004, 108). With the establishment of databases, the explicit documentation of paradata and metadata became more popular and important

40

multiple levels of uncertainty” can be recorded and analyzed (Bruschke and Wacker 2016,

262).

Since the exponential increase of information records, databases have proven in many cases to be standard containers for data storage. Moreover, they also are able to link external objects and models (Guidi et al. 2013, 102; Hermon and Nikodem 2008, 143). Furthermore, real time interactions are possible for analysis purposes (Fanini and Ferdani 2012, 108). Therefore, a model can be linked with its corresponding discussion (Manferdinie et al. 2008, 221ff). However, an intuitive understanding is hard to accomplish. The databases are usually highly complex. Flow charts and diagrams help one to understand and use them, and are therefore highly recommended (Hermon 2008, 38). Additionally, 3D models that are described in a database need to be broken down into smaller segments of logical geometry or architectural parts.

Table 2: Overview of several documentation formats. The table is limited to the best-known examples from archaeology. The most common form of databases in archaeology are marked in blue (Brunke 2017)

Language Text XML SQL Cypher

Software Microsoft Word,

Open Office Writer, … Notepad ++, Atom, … Microsoft Access, PhpMyAdmin, … Notepad ++, Atom, …

Structure Written text Hierarchical Relational Graph

XML is one possible data format (tab. 2). Its advantages are clearly its dynamic structure and the easy way to extend already existing databases. Furthermore, it is readable by humans. The database itself was created with a hierarchic structure. Moreover, the resource description framework is often associated with it. To provide cross- compatibility, an open ontology is advised (Kurocynski et al. 2014, 4; Vatanen 2003, 71). In some cases, it is even possible to incorporate an XML database directly into the file of the 3D model. It is required that the file is also based on an XML structure, such as X3D. However, this should be done only for less complex situations (Martini and Ono 2010, 435; Ryan 2001, 257). A popular ontology that is used with XML based databases is the CIDOC CRM (Bruschke and Wacker 2016, 267).

Another database format is that of the above-mentioned relational databases (tab. 2), which uses SQL as query language. They are the most prominent examples and have already been in use for 40 years in archaeology. However, creating relations between

41 datasets from different tables has its weaknesses. For example, another table must be created that contains only the information for the relation, a so-called join table13_{. The} organization and design are often more complex than that from XML-based databases (Bruschke and Wacker 2016, 267).

A database that is not based on SQL can be a graph database (tab. 2). It can use XML as background language but also has its own languages. These forms of databases are highly suitable for linked datasets with many relationships between the nodes. Each node and relationship can furthermore own properties. If necessary, they also accept ontologies such as the CIDOC CRM (Bruschke and Wacker 2016, 267). The name was coined because the datasets of such databases can be visualized and analyzed as graphs. If this is not desired, the results can also be returned in the form of tables or text (Bruschke and Wacker 2016, 268).

Triple paths can be put under the label of XML databases. They use the same language but a different structure to common xml databases. The structure itself is quite similar to the structure of graph databases. Several publications already recommend the use of this database for archaeological purposes. According to Ryan, they might offer a good opportunity to describe research in virtual archaeology (Ryan 2001, 245). Their value lies in the possibility of connecting uncertainty directly with several alternatives by multiple relationships (Ryan 2001, 246). As ontology, the Dublin core is advised (Ryan 2001, 248; Kuroczynski et al. 2016, 151). Triple paths are related to the resource description framework (rdf), which is understandable by computers and consist of a “Subject (a resource) – Predicate (a property name) – Object (a literal property value)” and a form of ontology. Transferred to a 3D model, the subject is the name of the segment, the predicate the property, such as the size and the object, and the value of the size. As many entries as possible are saved in the form of URIs (Ryan 2001, 254f; Kuroczynski et al. 2016, 152). As previously mentioned, some file formats are capable of incorporating small xml databases in the form of triple paths (Ryan 2001, 257). Those are SMIL (Ryan 2001, 259ff), SVG (Ryan 2001, 261ff) and X3D (Ryan 2001, 263ff).

In conclusion, triple paths provide the opportunity to connect sources, data and interpretation with visualization – another form of interpretation (Kuroczynksi et al. 2016, 150). However, it is not the only possibility to store data. The choice of format depends

13 _{Join tables are a special kind of table in relational databases. They have to be used when a m:n}

(multiple to multiple) relation occurs. Basically, they contain at least two indices in one row. These represent the index of distinct databases, but are hereby connected over a relationship.

42 on the available data and the desired final results. While graph databases are strong in terms of relationships, relational databases can more easily hold and order much larger amounts of data. However, there are also overlaps. For example, a written text can be enriched with XML annotations, or a graph database can display data in tables. However, it is also from importance how the design decisions are processed and stored in such databases. It is not always easy to express them in an understandable way for computers and humans equally.