-
Notifications
You must be signed in to change notification settings - Fork 0
Modals
This modal asks for the user's confirmation before clearing the state.
This modal is used to edit the properties for a given shape:
-
IRI
-
Name (for property shape) or label (for node shape)
- Language
-
Description
- Language
-
The IRI entered will only be accepted if it is valid and unique.
-
The label/name and description can be empty.
-
The languages can be selected using a dropdown with a list of languages. These languages will be translated into language tags in the internal model.
This modal is used to export the shapes to a file chosen by the user. After confirming, this will prompt a text file download with the given filename and extension.
- The user can choose between the extensions
json
andttl
, which will result in the corresponding file formats. - The modal can only be confirmed if the user has entered a valid filename.
This modal is used to edit the used namespaces and to indicate the base URI. The main component is the NamespaceTable. Underneath this table, there is a small form to add new namespaces.
- The prefix will only be accepted when it is unique.
- The URI will only be accepted when it is unique and valid.
- The button will only be enabled when both the prefix and the URI pass the requirements.
The namespace table shows all the used namespaces and their prefixes.
- Namespaces can be deleted by clicking the
x
button of the desired row. The current base URI cannot be deleted as for now. - The prefix and URI of each row can be edited by clicking the value. The changes will be saved as soon as the user exits the input field or presses the
enter
key. - When an entered value is invalid or not unique, the input field will be red. Any changes will not be saved as long is the entered value is invalid.
- At most one namespace can be selected as a base URI. This URI will be used when creating new shapes. If there is no base URI selected, only the default identifier will be used for the creation of new shapes.
- A namespace can be selected as base URI by clicking the radio box. Deselect by clicking this same radio box again.
The path modal is used to choose the path of a new property shape or to edit an existing one. When clicking on a property shape or when creating a new property shape, this modal will be shown. Any changes will only be accepted when the user has entered a valid IRI.
This modal is used to add a new constraint to a shape or to edit an existing constraint value. The main component is the PredicateTable.
- The search field can be used to filter the contents of the table. The table will be filtered based on the input value and both the predicate and category columns.
- The currently selected predicate will always be shown, regardless of the filter.
- When editing, it is not possible to edit the predicate.
- When the user has selected a predicate from the table, an input field will appear underneath the table. The value type of this field is dependent on the predicate.
- Checkbox for boolean values.
- Number input fields for numbers.
- Select box for datatypes.
- Text input fields. These might suggest shape paths or URIs in a dropdown when possible.
The predicate table shows the possible predicates with a description and their category.
- A predicate can be selected by clicking on the row of the desired predicate. Click the selected row again to deselect the predicate.
- The table can be sorted by both predicate and category. To sort the table, click on the table header of the desired column. Click again on the same header to invert the order.
- The predicate column will be sorted alphabetically by default.
The content of the predicate modal depends on different factors.
- The content will be filtered when the user enters a search term.
- If the modal is opened for the editing of a constraint value, only this predicate will be visible. It is not possible to change the predicate at this point.
When the user chooses to validate uploaded data, the validation report will be visualized in a modal. This modal will show both a general overview of the report and a detailed list of the violations, if there are any.
The general overview consists of two parts.
- A message will indicate if the data conforms to the given model.
- If so, the message will be green and the modal will not contain anything more.
- If not, the message will be red.
- If the data does not conform, the modal will show a list with the URIs of the shapes that violate the model.
Underneath this general overview, there will be a detailed list of the different violations in each data shape, if there are any.
- Every violating data shape will have a list of violations.
- Every violation entry will contain more details about what caused the violation, what exactly is wrong and where.
Questions? Anything unclear? Feel free to message me!