[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML Envelopes...

• To: xml-dev@l...
• Subject: Re: XML Envelopes...
• From: "Peter Hunsberger" <peter.hunsberger@g...>
• Date: Fri, 21 Jul 2006 09:53:11 -0500
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iTDhdw8rPg1wnRpaQc9mzi7f57x/ImFxHhl2s7w//AqVWpqrDZt4rgD9fqT2qiVnam3BxxJmZwhX+kgHVZ4E+zT5ifxdnjPOrah6S2kL3iqVnUcF58zJIdfJv0cvpCr/P3NgZcq+gx9R/0hR7bXefDfbkLxwlPpHOmdc6WPpu7g=
• In-reply-to: <OF468B32BA.0C4DF53E-ONCA2571B2.00074932-CA2571B2.0007AF46@p...>
• References: <OF468B32BA.0C4DF53E-ONCA2571B2.00074932-CA2571B2.0007AF46@p...>

> Got a bit of a tough one (for me anyway...).
>
> Got an XSD Envelope that we wish to use for all messages. It's generic.
> At the body node though, we wish to specialise that node & add the specific schemas for that particular service.
>
<snip/>

What you're not telling us is where you need the specific schema?  For
development? For sending the completed package across the wire? For
internal editing (why not just the interior schema in that case)?

Given your description it sound like perhaps you might be able to
maintain the envelope schema completely separately from the rest of
the content schema and then combine them only at run time?  If so,
XSLT would be your friend;  use a transform to read the two documents
and add the specific content schema's to the envelope schema starting
at the "body" (or whatever) tag as needed...

-- 
Peter Hunsberger

• References:
  • XML Envelopes...
    • From: Minas Casiou <casi1min@p...>

• Prev by Date: RE: Re: Why is there little usage of XML on the 'visible Web'?
• Next by Date: XML Versioning
• Previous by thread: XML Envelopes...
• Next by thread: Re: XML Envelopes...
• Index(es):
  • Date
  • Thread