[tdwg-tapir] conceptual binding

["Döring, Markus"]

Well, its only if the xpath is the same.
I dont think we will encounter this in reality easily. But to be correct we should change it to qualified. But then we need to define the prefixes somewhere again. Something we gladly got rid of before.

markus

-----Ursprüngliche Nachricht-----
Von: Javier privat 
Gesendet: Dienstag, 28. Februar 2006 12:12
An: Döring, Markus
Cc: tdwg-tapir at lists.tdwg.org
Betreff: Re: [tdwg-tapir] conceptual binding

Hi,

I think this is not only an issue on filters, is also on mappings.
In the mapping section of the outputModel the path attribute of the nodes shouldn't be also qualified? Is there cases that without qualifying we will have problems? Imagine you have in the outputModel something like: 

...
<gcp:FullScientificName>Quercus ilex</gcp:FullScientificName> <abcd:FullScientificName>Quercus ilex L.</abcd:FullScientificName> ...

I know it is maybe not a good example, but I hope is clear. 

This reminds me also a message from Roger before Christmas about using RDF with TAPIR.

"Tapir has the intention of combining separate 'concepts' (which implies different namespaces) into a single output model but do the concepts all have to be mapped into a single namespace to make the thing workable?"

If I understood the question correctly, the answer is no after import is something supported.

Javier.