Re: Creating a Child Record with a different Namespace
- From: "Tomas Restrepo \(MVP\)" <tomasr@xxxxxxxx>
- Date: Mon, 4 Jul 2005 12:39:58 -0500
Mike,
> here is the Schema I constructed :
I'm not quite sure what the problem you're having is (that is, I don't
understand quite well what you mean).
I took your schema, and changed the Person node to be
minOccurs=1,maxOccurs=1, and the flat file dissasembler correctly generates
three separate output documents as expected.
Checking further, I see that what might be confusing is that the output
documents look like this:
<CSV xmlns="http://CitizenChanges.Input";>
<Person xmlns="">
<Forename>Ritchie</Forename>
<Surname> Terrance</Surname>
<PersonID> ID10001</PersonID>
</Person>
</CSV>
As you can see, the <Person> element is in the default empty namespace
instead of the one the <CSV> node is in. If this is your concern, then that
is easily fixable, just change at the schema level the element form default
property to "qualified" instead of "unqualified", which is the default
value.
--
Tomas Restrepo
tomasr@xxxxxxxx
http://www.winterdom.com/
.
- Follow-Ups:
- Re: Creating a Child Record with a different Namespace
- From: M Stuart
- Re: Creating a Child Record with a different Namespace
- References:
- Creating a Child Record with a different Namespace
- From: M Stuart
- Re: Creating a Child Record with a different Namespace
- From: Tomas Restrepo \(MVP\)
- Re: Creating a Child Record with a different Namespace
- From: M Stuart
- Re: Creating a Child Record with a different Namespace
- From: Tomas Restrepo \(MVP\)
- Re: Creating a Child Record with a different Namespace
- From: M Stuart
- Creating a Child Record with a different Namespace
- Prev by Date: Re: Creating a Child Record with a different Namespace
- Next by Date: Re: Creating a Child Record with a different Namespace
- Previous by thread: Re: Creating a Child Record with a different Namespace
- Next by thread: Re: Creating a Child Record with a different Namespace
- Index(es):
Relevant Pages
|
