LogosLink User's Manual · LogosLink version 2.0.0.2

Convert Files from a Previous Version

LogosLink version 2.0.0.2 stores datasets in a format that is slightly different from that of previous versions. If you have models or corpora created with previous versions of LogosLink, you will need to convert them before you can use them with LogosLink version 2.0.0.2.

To convert file versions, you use a special application, called LogosLink VersionConvert. This application is installed on your computer together with LogosLink Desktop. To find it, enter its name in the Windows search bar.

General process

To convert a model file or a corpus to the new version, follow these steps:

Open the LogosLink VersionConvert application.
Decide whether you want to convert a whole corpus, an argumentation model file, or an ontology file. LogosLink VersionConvert has a separate section for each one. If you convert a corpus, the corpus itself plus all the model files in it will be converted.
Enter the full path to the corpus or model file into the "Source" box. You can also click the button to the right of the box to browse your computer.
Once you have entered a source corpus or model file name, LogosLink VersionConvert will suggest a destination directory or file name. You can edit and change this if you want.
Click the Convert button underneath.
If this is the first time that you convert a corpus or file, LogosLink VersionConvert will ask you to enter some options. Enter the necessary details and click OK. See below for a detailed description of conversion options.
LogosLink VersionConvert will convert the corpus or model file, and show any relevant messages in the Messages box at the bottom.
Revise the message list. Messages that indicate issues or that need your attention start with three asterisks ***. See below for a list of possible messages that require your attention.
If the process finishes successfully, the converted corpus or model file should be in the "Destination" location that you specified. Check that you can open it with LogosLink version 2.0.0.2.
If the conversion process issued any messages requiring attention, please check the converted corpus or model to address the necessary issues.

Options

There are some options that you can specify before you convert a corpus or model file. Click the Options... button to enter options, and click OK to save them.

Options are as follows:

Use association auto-pair up. Ontology associations in previous versions of LogosLink were unidirectional, so you needed to create two of them if you wanted to connected two categories bidirectionally. However, associations in LogosLink version 2.0.0.2 are bidirectional in nature. This means that each association in a LogosLink version 2.0.0.2 ontology is composed of two opposite connections. LogosLink VersionConvert generates the new associations from the old ones, but sometimes it may be difficult to decide which old associations must be paired up as a new association. If this box is checked, LogosLink VersionConvert will try to automatically pair up old associations by looking at the owner and target categories, and will ask you to manually decide when it cannot be automatically decided. If, on the contrary, this box is unchecked, LogosLink VersionConvert will let you decide the pairing of each association, even when it would be safe to automatically do it. Using automatic pair up is safe, as LogosLink VersionConvert will only do it when it is formally proven that the two old associations are in fact components of a new one.
Analyst: This information represents you as an analyst.
- User name. This is the user name that you want to use for the converted corpus or model files. This must be the same user name that you set up in LogosLink Desktop. You can use any user name, but is is suggested that it matches the user name that you use to log into Windows.
- Given name. This is your given or first name.
- Family name. This is your family or last name.
- Email. This is your email.

Limitations

File conversion has some limitations that may impact the results

References and associations

LogosLink 1 used unidirectional references (between entities) and associations (between categories), so that you needed two of them if you wanted to connect two entities bidirectionally. The two references or associations could not be paired up in any manner, so it was up to the analyst to create them and make sure that they were "in sync". In LogosLink version 2.0.0.2, to the contrary, introduces bidirectional links and associations, each made up of a pair of references and connections, respectively.

When converting a LogosLink 1 ontology, LogosLink VersionConvert attempts to pair up associations and references into LogosLink version 2.0.0.2 associations and links. You can select via options whether LogosLink VersionConvert should attempt the pairing automatically or rather ask you as needed. In any case, pairing is often unambiguous and conversion can proceed. However, there may be ontologies for which pairs cannot be established. In these cases, LogosLink VersionConvert will create connections or references as needed to complete any incomplete pairs. When this occurs, a message is shown.

Incoming transitions

LogosLink 1 allowed locutions having multiple incoming transitions in argumentation models. LogosLink version 2.0.0.2, to the contrary, only allows one incoming transition per locution.

When converting a LogosLink 1 argumentation model, LogosLink version 2.0.0.2 will discard any additional incoming transitions to a locution beyond the first one. When this occurs, a message is shown.

Denotations

LogosLink 1 anchored argumentation model denotations onto propositions, with an optional additional anchor onto the corresponding locution. LogosLink version 2.0.0.2, to the contrary, anchors denotations onto locutions only.

When converting a LogosLink 1 argumentation model, LogosLink version 2.0.0.2 will convert denotations that have a locution anchor. Denotations that lack a locution anchor and are anchored onto a proposition only cannot be converted and are discarded. When this occurs, a message is shown.

Messages requiring attention

Differences in the conceptual models of LogosLink version 2.0.0.2 and previous versions, as well as issues during conversion, can produce messages that require your attention. This is a list of the potential messages that you may see.

Aborting. This indicates that the conversion process has been interrupted, and the expected converted corpus or model file has not been produced. Please check previous messages to determine the cause of the problem.
Error: (error description). This indicates that an unexpected error occurred during conversion, and the expected converted corpus or model file has not been produced. The error description may point at the underlying issue. If you are stuck, contact us and we will be happy to help.
Mapping source id (source id) to target id (target id). This indicates that an element in the target corpus has an id that is different to the equivalent element's id in the source corpus.
Text range (source range) is out of bounds in locution (id); adjusting to (adjusted range). This indicates that the text range of a locution in a source argumentation model extends beyond the text boundaries, which should not be the case. LogosLink VersionConvert adjusts the range for you, but you will still need to revise the source locution and make sure that the new one is correctly defined.
Fixing text range (source range) to (adjusted range). This indicates that the text range of a locution in a source argumentation model extends beyond the text boundaries, which should not be the case. LogosLink VersionConvert adjusts the range for you, but you will still need to revise the source locution and make sure that the new one is correctly defined.
Omitting transition (id) as all of its final locutions already have an incoming transition. This indicates that the mentioned source transition is being omitted in the new argumentation model, because its final locution already has an incoming transition, and LogosLink version 2.0.0.2 only allows one incoming transition per locution as maximum.
Skipping proposition group (id), as proposition groups are not supported anymore. Argumentation models in previous versions of LogosLink supported proposition groups, but these have been dropped from LogosLink version 2.0.0.2 for lack of use.
Omitting (arguing/agreeing/disagreeing/restating) (id) as its anchor transition (id) was omitted too. If a transition is omitted (see above), any outgoing illocutionary forces are omitted as well.
Denotation (id) cannot be converted because there is no associated locution. Argumentation models in previous versions of LogosLink anchored denotations on propositions, and allowed you to optionally add an anchor locution. However, denotations in LogosLink version 2.0.0.2 are anchored on locutions only. This message indicates that the mentioned source denotation cannot be converted because it has no anchor locution.
Denotation (id) cannot be converted because there is no range in locution. This indicates a situation similar to the one in the previous message above. In this case, despite there being a target locution for the denotation, there is no range to indicate a term in the locution.
Denotation (id) cannot be converted because its range in locution is out of bounds. This indicates a situation similar to the one in the previous two messages above. In this case, despite there being a target locution and a range for the denotation, the range is out of bounds.

Contents distributed under a Creative Commons Attribution 4.0 International License · About · Terms of Use · Contact Us · last updated on 19/12/2024 13:17