Dear kevingupton,
in my case, the buttons weren't grayed out but dead as a doornail. I could click them, but nothing happened. As yet, I haven't found a solution but perhaps my first steps lead you to an idea:
1. In Specialize > Manage-Tech, the ODM checkbox was checked, however, the "Set active" button was not grayed out. So I set ODM active.
2. After that, the import button
did open an import dialog. After selecting an RDF file, a package import started and failed (with the dialog closing somewhere during the import). An empty package with the name of the RDF file was created, that was all.
3. During the import, an XMI file was created in C:\Users\[user name]\AppData\Local\Temp (example file name: EA8C66.tmp) which looked okay (you have to copy it during the ongoing import, it's deleted afterwards), meaning, it contains data from the imported file within an apparently valid XMI structure.
4. An attempt to import this XMI file (via Publish > Model Exchange) resulted in another empty package.
5. That's where I stand now.
Hope this helps. Any ideas?
Best,
Michael
Best,
Michael
UPDATE:
1. XMI consists only of packaged elements of type
<packagedElement xmi:type="uml:Association" xmi:id="rdf:Description_timelineTrackDescription_rdfs:domain_3_assoc"> and of
<connector xmi:idref="rdf:Description_ruleStatement_rdfs:domain_4_assoc">
<xrefs value="$XREFPROP=$XID={rdf:Description_ruleStatement_rdfs:domain_4_assocSTEREO}$XID;$NAM=Stereotypes$NAM;$TYP=connector property$TYP;$DES=@STEREO;Name=rdfsDomain;FQName=RDF:rdfsDomain;@ENDSTEREO;$DES;$CLT={rdf:Description_ruleStatement_rdfs:domain_4_assoc}$CLT;$ENDXREF;" />
</connector>
All classes from the source files are ignored.
RDF Source file:
https://www.ebu.ch/metadata/ontologies/ebuccdm/ebuccdm.rdf