|
Home > Archive > BizTalk Server General > April 2005 > Best practices, xsi:schemaLocation : .NET and XML namespace synchr
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Best practices, xsi:schemaLocation : .NET and XML namespace synchr
|
|
| shawnk 2005-04-26, 5:53 pm |
| I am developing some namespace partitioning conventions for XML/.NET namspaces
when working with Biztalk. I am familar with the Biztalk generated
project.filename
default namespace conventions.
I am working on providing some commonality between XML and .NET namespaces
in the form of
prefix, infix and postfix name tags.
During the process I noted that packaging 'message transformers' in .NET
assemblies
as my_input_msg, my_msg_IO_map and my_output_msg is pretty handy!
Since I want to use many other tools outside of VS.NET and Biztalk (for XML
validation,
editing, etc) I want to web host the schemas for validation. This means that
the xml validation 'routing' information in the <xs:schema>,
xsi:schemaLocation attribute
appears in all document instances (*.xml files).
The good thing about replicating the message schemas on a web host (WSS) is to
make them available to trading partners and (most important) my other
tools. The bad thing is replication exposes information artifacts to
de-sychronization. I have to take care that the schemas
packaged in a .NET assembly match the identical schema on the WSS (or
whatever platform) web host (for the xsi:schemaLocation locator).
Also note the logical objects may exist in databases, C#, C++, XML and Biztalk
domains.
Are there any best practices for enterprise namespace archtitecture that
deal with
conformance and synchronization between the XML and .NET namespace
mechanisms? Core 'logical taxonomies' that extend platform independent
namespacing
into platform and technology domains is a key interest.
Are there some features in Biztalk I may have missed the
allow you to set up a different namespace generation convention (ie.
instead of project.filename)?
System configuration synchronization (IT
sync) is my key interest in automation of configuration checking. Currently
the concern is to have several tools to run XML validation and ensure they
always agree.
It would be nice to leverage such practices in the form of tools that could
search
the .NET namespace in the GAC, find Biztalk messages via a naming
convention, and
then compare the packaged schemas in the assemblies with their web hosted
conterparts
on IIS/WSS. Ensuring configuration integrity via IT artifact synchronization
is the intention.
Future direction and use of such practices deals with taxonimies for
message/object classification
and comparison of message/object taxonomies from different corporations and
federated namespaces such
as the U.S. federal government's Office of Management and Budget (OM )
Federal Enterprise Architecture (FEA) Data Reference Mode (DRM).
The immediate need is to ensure my current namespace architecture will
produce a viable environment for
the development and use of such tools.
If you know of any links to biztalk specific related discussion and best
practices in namespace conformance please
let me know.
Thanks ahead of time for any info or thoughts.
shawnk
PS. I have reviewed many of the posts in Biztalk regrading schema validation
and other tools.
Since this is a known problem and issue I wanted to find any focused attempt
to guide the Biztalk
community in this regard. Being a Biztalk newbie this would be helpful.
| |
| Scott Colestock 2005-04-26, 5:53 pm |
| Gosh, I'll only attempt to tackle part of your question...
With regard to: > Are there some features in Biztalk I may have missed the
> allow you to set up a different namespace generation convention (ie.
> instead of project.filename)?
When you select a schema in the solution explorer, note that you can set the
..NET namespace and type name there, and of course when you click on the root
node of the schema, you can set the target namespace independently.
Perhaps you are looking to change the defaulting mechanism - in which case I
can't help you there.
As for synchronization, I've often thougth it might be interesting to start
with some of the info in Gilles blog (like
http://blogs.msdn.com/gzunino/archi.../20/232003.aspx) and a little
Reflector spelunking, so as to build a BizTalk schema assembly that
consulted an external-source-of-truth at run time. But of course, once
you've deployed to a biztalk server, the game is done since the schema is
stored in the database.
Scott Colestock
www.traceofthought.net
"shawnk" <shawnk@discussions.microsoft.com> wrote in message
news:A74C6241-ADBC-493B-8673-8125DD9C57A5@microsoft.com...
>I am developing some namespace partitioning conventions for XML/.NET
>namspaces
> when working with Biztalk. I am familar with the Biztalk generated
> project.filename
> default namespace conventions.
>
> I am working on providing some commonality between XML and .NET namespaces
> in the form of
> prefix, infix and postfix name tags.
>
> During the process I noted that packaging 'message transformers' in .NET
> assemblies
> as my_input_msg, my_msg_IO_map and my_output_msg is pretty handy!
>
> Since I want to use many other tools outside of VS.NET and Biztalk (for
> XML
> validation,
> editing, etc) I want to web host the schemas for validation. This means
> that
> the xml validation 'routing' information in the <xs:schema>,
> xsi:schemaLocation attribute
> appears in all document instances (*.xml files).
>
> The good thing about replicating the message schemas on a web host (WSS)
> is to
> make them available to trading partners and (most important) my other
> tools. The bad thing is replication exposes information artifacts to
> de-sychronization. I have to take care that the schemas
> packaged in a .NET assembly match the identical schema on the WSS (or
> whatever platform) web host (for the xsi:schemaLocation locator).
> Also note the logical objects may exist in databases, C#, C++, XML and
> Biztalk
> domains.
>
> Are there any best practices for enterprise namespace archtitecture that
> deal with
> conformance and synchronization between the XML and .NET namespace
> mechanisms? Core 'logical taxonomies' that extend platform independent
> namespacing
> into platform and technology domains is a key interest.
>
> Are there some features in Biztalk I may have missed the
> allow you to set up a different namespace generation convention (ie.
> instead of project.filename)?
>
> System configuration synchronization (IT
> sync) is my key interest in automation of configuration checking.
> Currently
> the concern is to have several tools to run XML validation and ensure they
> always agree.
>
> It would be nice to leverage such practices in the form of tools that
> could
> search
> the .NET namespace in the GAC, find Biztalk messages via a naming
> convention, and
> then compare the packaged schemas in the assemblies with their web hosted
> conterparts
> on IIS/WSS. Ensuring configuration integrity via IT artifact
> synchronization
> is the intention.
>
> Future direction and use of such practices deals with taxonimies for
> message/object classification
> and comparison of message/object taxonomies from different corporations
> and
> federated namespaces such
> as the U.S. federal government's Office of Management and Budget (OM )
> Federal Enterprise Architecture (FEA) Data Reference Mode (DRM).
>
> The immediate need is to ensure my current namespace architecture will
> produce a viable environment for
> the development and use of such tools.
>
> If you know of any links to biztalk specific related discussion and best
> practices in namespace conformance please
> let me know.
>
> Thanks ahead of time for any info or thoughts.
>
> shawnk
>
> PS. I have reviewed many of the posts in Biztalk regrading schema
> validation
> and other tools.
> Since this is a known problem and issue I wanted to find any focused
> attempt
> to guide the Biztalk
> community in this regard. Being a Biztalk newbie this would be helpful.
>
|
|
|
|
|