Import RDF file into an enumeration, with the output of an export of a enumeration from 6.1, throws
File Import Failed Import Failed. The file declares classes, properties or shapes which is not supported for this asset collection type. You should import these into an Ontology. Unsupported resources found: it appears to be new in 6.2 (?) that a custom enumeration types ontology is now required and will need to split such content into classes and instances. +1 for this in general I think.. but 1) if you load a file with classes and instances into the ontology, then the instances show up in the enumerations 2) should be able to ignore classes in instance files (or auto create the ontology) to allow both round-trip, backwards compatibility and user choice of packaging of enumeration content 3) I couldnt find any documentation on this feature 4) it appears the only way to access the enumeration ontology types is to go into a create dialog and then access the editor link for the ontology - so managing these means doing this to delete one after deleting all enums that use it - or does it show up somewhere else? 5) what flexibility does the enumeration types ontology give us - can we actually use standard SKOS for enumerations now? (it was broken before, as AFAICT we couldnt load SKOS to Reference Data and use Property Value Selectors ) 6) the logic appear to be broken for editing - if you create an empty enumeration then the "New" tab says "Enumeration Types must be defined in an Enumeration Ontology." and if you go into details or try to edit, then you get no New button to create instances. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
