Re: "Microsoft Office 2003 WordprocessingML Transform Inference Tool"s STRANGE limitation BUGGGG

In article <uTzNPApZFHA.2768@tk2msftngp13.phx.gbl>, Kashif wrote:
> If pure xml document is created from scratch using third-party xml editor,
> then XSL transformation results in blank document with only header/ footer.
>
I found that there were some rules about namespaces that had to be followed
before the inferred transform would produce anything.

*********************
There seem to be some rules here. To get Word to accept the schema,
you define a target namespace without at prefix. And mine didn't work
properly until I followed that pattern.

The .xlm file defines the same namespace, and also with no prefix.

Finally, the xsl transforms define the same namespace, but with a
prefix, and all the local variables have to use that prefix or the
stylesheet doesn't show anything but the embedded html.
********************

To which Bill Coan replied:

A "Default" namespace is one thing, a "Target" namespace is something else.
The distinction is worth understanding and will help explain what you're
seeing. When I was working on this, I relied on the definition given in the
xml standard.
http://www.w3.org/TR/REC-xml

http://www.w3.org/TR/xmlschema-0/

http://www.w3.org/TR/xslt

http://www.w3.org/TR/xsl/

http://www.w3.org/TR/xpath

--
Bill Coan
billcoan@wordsite.com
*************************************

He has a downloadable sample on his site that you can use as a pattern to
follow.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA

Hi Thanks Again

Finally i do finish with XML namespace and gets my Things working.

I'll found that MS word uses Custom Schema as default namespace for xml
Document created, when xml tagged document is saved as DataOnly xml.

How do i enforce msword to use some NameSpace prefix with XML Elements ??

Thanks in advance

Regards

Kashif Gul Kazi
AMZ Access

"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
news:VA.000021ec.00d51169@obts-outlookdev.outlookbythesound.mukwoods...
> In article <uTzNPApZFHA.2768@tk2msftngp13.phx.gbl>, Kashif wrote:
> > If pure xml document is created from scratch using third-party xml
editor,
> > then XSL transformation results in blank document with only header/
footer.
> >
> I found that there were some rules about namespaces that had to be
followed
> before the inferred transform would produce anything.
>
> *********************
> There seem to be some rules here. To get Word to accept the schema,
> you define a target namespace without at prefix. And mine didn't work
> properly until I followed that pattern.
>
> The .xlm file defines the same namespace, and also with no prefix.
>
> Finally, the xsl transforms define the same namespace, but with a
> prefix, and all the local variables have to use that prefix or the
> stylesheet doesn't show anything but the embedded html.
> ********************
>
> To which Bill Coan replied:
>
> A "Default" namespace is one thing, a "Target" namespace is something
else.
> The distinction is worth understanding and will help explain what you're
> seeing. When I was working on this, I relied on the definition given in
the
> xml standard.
> http://www.w3.org/TR/REC-xml
>
> http://www.w3.org/TR/xmlschema-0/
>
> http://www.w3.org/TR/xslt
>
> http://www.w3.org/TR/xsl/
>
> http://www.w3.org/TR/xpath
>
> --
> Bill Coan
> billcoan@wordsite.com
> *************************************
>
> He has a downloadable sample on his site that you can use as a pattern to
> follow.
>
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
>

Re: "Microsoft Office 2003 WordprocessingML Transform Inference Tool"s STRANGE limitation BUGGGG - XML SOAP