Closed (outdated)
Project:
Taxonomy import/export via XML
Version:
6.x-1.x-dev
Component:
Drupal XML format
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 May 2010 at 15:06 UTC
Updated:
27 Jun 2018 at 13:35 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dman commentedthe old 'xml' format hasn't got a lot of love in the last year.
Can you add the vocab file that triggers this error?
Comment #2
kenorb commentedMy mistake, I tried to upload RDF format as XML.
Comment #3
dman commentedOK. Good example.
Yeah, importing RDF as RDF seems to do pretty much what is expected.
There are a few new things there, but those have no good way to be stored, so don't hurt anything.
zthes eh? I'd like to see that in action.
It was odd to see a rdf:resource that's not a URI, But I see by the use of
xml:base="http://www.nsonline.co.uk/that the 'resources seem to resolve toxml:base="http://www.nsonline.co.uk/7f523b53839e0808ff6ea6de2a165f88etc ... so I guess it's all legal.An idea would be to retain the other values - especially the
<skos:scopeNote label="globallyUniqueId">in the term as well. But there's no solid D6 way of doing that. taxonomy_enhancer should have allowed it (and is what I use) but if what you've got is sufficient I think you have a win. If your input isn't too big.Still, I'll see if there is a way to improve detection on the formats, or better error handling in wrong cases.
Comment #4
kenorb commentedI just replaced rdf:resource to localhost manually:)
Thanks.
Comment #5
kenorb commentedDrupal 6 is no longer officially supported. If you think this issue is still relevant for 8.x, feel free to re-open.