Avoiding XML serialization namespace substitution?

[AP]

Hi,

I have a class that I wish to serialize to XML, part of which looks like
this:
public class TitleNotificati on {
[XmlAttributeAtt ribute(Namespac e="xsi",
AttributeName=" noNameSpaceSche maLocation")]
public string NoNameSpaceSche maLocation =
http://www.pdr.com\nhttps://extw3c.p...ification.xsd;
....
}

When the class is serialized, the relevant resulting XML looks like this:

<?xml version="1.0" encoding="utf-8"?>
<TitleNotificat ion xmlns:xsd="http ://www.w3.org/2001/XMLSchema"
xmlns:xsi="http ://www.w3.org/2001/XMLSchema-instance"
d1p1:noNameSpac eSchemaLocation ="http://www.pdr.com&#xA ;https://extw3c.pdr.co
m/prism/b2b/schemas/TitleNotificati on.xsd" ParagonID="1234 " Version="1"
Source="5" SupplierID="PA-1234" xmlns:d1p1="xsi " ...

How can I get it to generate xsi:noNameSpace SchemaLocation instead of doing
the d1p1 substitution thing it's doing now?

Thanks,

Adam

[Derek Harmon]

"AP" <ad***@indra.co m> wrote in message news:OA******** ******@TK2MSFTN GP12.phx.gbl...

I have a class that I wish to serialize to XML, part of which looks like
this:

public class TitleNotificati on {
[XmlAttributeAtt ribute(Namespac e="xsi",
AttributeName=" noNameSpaceSche maLocation")]
The Namespace property represents a namespace URI -- not a prefix.

[XmlAttribute( Namespace="http ://www.w3.org/2001/XMLSchema-instance",
AttributeName=" noNamespaceSche maLocation")]

Also observe that the QName, xsi:noNamespace SchemaLocation, is
case-sensitive.

: : How can I get it to generate xsi:noNameSpace SchemaLocation instead of doing
the d1p1 substitution thing it's doing now?

Try using the namespace URI, XmlSerializer may re-use the xsi prefix.
If it doesn't, then it's choice of prefix is arbitrary. Correct implementations
that honor xsi:noNamespace SchemaLocation are actually looking for:

{http://www.w3.org/2001/XMLSchema-instance,noName spaceSchemaLoca tion}

Therefore, it doesn't matter what prefix it's given.

Ordinarily, you would use a public field of type XmlSerializerNa mespaces,
and mark it with the [XmlNamespaceDec larations] attribute. You could
initialize this field by Add'ing prefix and namespaceURI pairings into it.

However, the XML Schema namespace declarations are emitted by the
XmlSerializer prior to consulting the XmlNamespaceDec larations field,
so you cannot count on your xsi namespace declaration appearing early
enough in the root element (it'll be there, though, because XmlSerializer
needs the XMLSchema-instance namespace itself.)
Derek Harmon

[AP]

So in other words there's no gauranteed way of doing it?

"Derek Harmon" <lo*******@msn. com> wrote in message
news:eQ******** *****@TK2MSFTNG P11.phx.gbl...

"AP" <ad***@indra.co m> wrote in message news:OA******** ******@TK2MSFTN GP12.phx.gbl...

I have a class that I wish to serialize to XML, part of which looks like
this:

public class TitleNotificati on {
[XmlAttributeAtt ribute(Namespac e="xsi",
AttributeName=" noNameSpaceSche maLocation")]

The Namespace property represents a namespace URI -- not a prefix.

[XmlAttribute( Namespace="http ://www.w3.org/2001/XMLSchema-instance",
AttributeName=" noNamespaceSche maLocation")]

Also observe that the QName, xsi:noNamespace SchemaLocation, is
case-sensitive.

: :

How can I get it to generate xsi:noNameSpace SchemaLocation instead of doing the d1p1 substitution thing it's doing now?

Try using the namespace URI, XmlSerializer may re-use the xsi prefix.
If it doesn't, then it's choice of prefix is arbitrary. Correct

implementations that honor xsi:noNamespace SchemaLocation are actually looking for:

{http://www.w3.org/2001/XMLSchema-instance,noName spaceSchemaLoca tion}

Therefore, it doesn't matter what prefix it's given.

Ordinarily, you would use a public field of type XmlSerializerNa mespaces,
and mark it with the [XmlNamespaceDec larations] attribute. You could
initialize this field by Add'ing prefix and namespaceURI pairings into it.

However, the XML Schema namespace declarations are emitted by the
XmlSerializer prior to consulting the XmlNamespaceDec larations field,
so you cannot count on your xsi namespace declaration appearing early
enough in the root element (it'll be there, though, because XmlSerializer
needs the XMLSchema-instance namespace itself.)
Derek Harmon

[Daniel Cazzulino [MVP XML]]

You can get rid of the xsd and xsi namespace declarations by using the
technique explained here:
http://weblogs.asp.net/cazzu/archive.../23/62141.aspx, at the very
beginning of the post.

HTH
--
Daniel Cazzulino [MVP XML]
Clarius Consulting SA
http://weblogs.asp.net/cazzu
http://aspnet2.com
"Derek Harmon" <lo*******@msn. com> wrote in message
news:eQ******** *****@TK2MSFTNG P11.phx.gbl...

"AP" <ad***@indra.co m> wrote in message news:OA******** ******@TK2MSFTN GP12.phx.gbl...

I have a class that I wish to serialize to XML, part of which looks like
this:

public class TitleNotificati on {
[XmlAttributeAtt ribute(Namespac e="xsi",
AttributeName=" noNameSpaceSche maLocation")]

The Namespace property represents a namespace URI -- not a prefix.

[XmlAttribute( Namespace="http ://www.w3.org/2001/XMLSchema-instance",
AttributeName=" noNamespaceSche maLocation")]

Also observe that the QName, xsi:noNamespace SchemaLocation, is
case-sensitive.

: :

How can I get it to generate xsi:noNameSpace SchemaLocation instead of doing the d1p1 substitution thing it's doing now?

Try using the namespace URI, XmlSerializer may re-use the xsi prefix.
If it doesn't, then it's choice of prefix is arbitrary. Correct

implementations that honor xsi:noNamespace SchemaLocation are actually looking for:

{http://www.w3.org/2001/XMLSchema-instance,noName spaceSchemaLoca tion}

Therefore, it doesn't matter what prefix it's given.

Ordinarily, you would use a public field of type XmlSerializerNa mespaces,
and mark it with the [XmlNamespaceDec larations] attribute. You could
initialize this field by Add'ing prefix and namespaceURI pairings into it.

However, the XML Schema namespace declarations are emitted by the
XmlSerializer prior to consulting the XmlNamespaceDec larations field,
so you cannot count on your xsi namespace declaration appearing early
enough in the root element (it'll be there, though, because XmlSerializer
needs the XMLSchema-instance namespace itself.)
Derek Harmon

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004

[Daniel Cazzulino [MVP XML]]

Well, not quite what you wanted anyway :S

--
Daniel Cazzulino [MVP XML]
Clarius Consulting SA
http://weblogs.asp.net/cazzu
http://aspnet2.com
"Daniel Cazzulino [MVP XML]" <kz***@NOaspnet 2SPAMPLZ.com> wrote in message
news:#3******** ******@TK2MSFTN GP10.phx.gbl...

You can get rid of the xsd and xsi namespace declarations by using the
technique explained here:
http://weblogs.asp.net/cazzu/archive.../23/62141.aspx, at the very
beginning of the post.

HTH
--
Daniel Cazzulino [MVP XML]
Clarius Consulting SA
http://weblogs.asp.net/cazzu
http://aspnet2.com
"Derek Harmon" <lo*******@msn. com> wrote in message
news:eQ******** *****@TK2MSFTNG P11.phx.gbl...

"AP" <ad***@indra.co m> wrote in message

news:OA******** ******@TK2MSFTN GP12.phx.gbl...

I have a class that I wish to serialize to XML, part of which looks like this:

public class TitleNotificati on {
[XmlAttributeAtt ribute(Namespac e="xsi",
AttributeName=" noNameSpaceSche maLocation")]

The Namespace property represents a namespace URI -- not a prefix.

[XmlAttribute( Namespace="http ://www.w3.org/2001/XMLSchema-instance",

AttributeName=" noNamespaceSche maLocation")]

Also observe that the QName, xsi:noNamespace SchemaLocation, is
case-sensitive.

: :

How can I get it to generate xsi:noNameSpace SchemaLocation instead of doing the d1p1 substitution thing it's doing now?

Try using the namespace URI, XmlSerializer may re-use the xsi prefix.
If it doesn't, then it's choice of prefix is arbitrary. Correct

implementations

that honor xsi:noNamespace SchemaLocation are actually looking for:

{http://www.w3.org/2001/XMLSchema-instance,noName spaceSchemaLoca tion}
Therefore, it doesn't matter what prefix it's given.

Ordinarily, you would use a public field of type XmlSerializerNa mespaces, and mark it with the [XmlNamespaceDec larations] attribute. You could
initialize this field by Add'ing prefix and namespaceURI pairings into it.
However, the XML Schema namespace declarations are emitted by the
XmlSerializer prior to consulting the XmlNamespaceDec larations field,
so you cannot count on your xsi namespace declaration appearing early
enough in the root element (it'll be there, though, because XmlSerializer needs the XMLSchema-instance namespace itself.)
Derek Harmon

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004