Sinopia Known Issues

This page will be updated to reflect Sinopia version 3.5 at the end of the current Work Cycle in October 2020. For now, please see known issues listed in Release Notes

last updated 11/21/19

• See the issue lists (Sinopia Editor, QA current issues, Profile Editor, general) for complete list of known issues.
• See the Work Cycle 2 User Requirements board for a picture of what's being worked on Sept 26 - Dec 6, 2019.

Documentation Needed

• How to Load RDF into Sinopia.

Supported Browsers

• Not all browsers are fully supported. For details see Supported Browsers

Linked Data Editor: General

• A single Resource Template cannot have multiple Property Templates using the same Property URI. For details see Why Sinopia doesn't allow repeated propertyURIs in a single Resource Template
• All Linked Data Editor actions require login. The desired behavior is to be forced to log in only when doing actions that require login (importing resource templates, saving data). Issue 495
• Sign out button doesn't always sign you out. Issue 556
• If you have unsaved changes in the Edit tab, you will lose your changes if you refresh your browser window.

Linked Data Editor: Lookups

• Search behaves differently depending on what you are looking up. Looking up Sinopia-created items supports use of wildcard. Looking up items via Questioning Authority (QA) uses a whole-word search and does not support wildcards. Issue 99
• Literals and URIs are both expressed in the same RDF pattern; in other words, literals are not expressed as labels of a blank node.

Profile Editor

• Clicking the back button in your browser erases your entries. Issue 158
• We are not adding or updating the list of available vocabularies for "Select Resource" and "Select Property". Workaround: profile creator can manually enter any class or property URI and label into the necessary fields. Issue 182
• While it's possible to add a default value and/or default URI in a property template with type = resource, Sinopia ignores those, as a single default value for a nested Resource Template does not make sense.