> There is a difference between how an undefined class and an undefined > property is handled though. When a namespace is used in the xml, the > undefined property is created and defined using the base URI of the > ConvertXMLToRDF step. However, when a namespace is used on an > undefined element, the class is defined using the base URI of the GSI > namespace.
Catrina, thanks for pointing this out. I have changed the behavior for 3.3 so that XML attributes with a namespace prefix will be matched against existing RDF namespaces, like we do for elements. It missed the cut for 3.2.1 though, i.e. you will need to live with the work-arounds (e.g. define existing properties that have sxml:attribute markers on them. Thanks Holger -- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=.
