RE: [ebxml-msg] Re: 15-day Review Request for ebms-header-3_0-200704_refactored

["Pim van der Eijk" <pvde@sonnenglanz.net>]

 

Hello,

 

My proposal is that we include the refactored schema as a separate deliverable of Part 2.  It is a schema with the same namespace as the Core schema.  A schema that uses it, imports it using a distinct schemaLocation value.  I think this is acceptable as:

- an XML document is valid according to the refactored schema iff it is valid according to the core schema and

- any element in a valid XML document has the same XML schema type when parsed into an InfoSet using either of the two schemas.

 

The upcoming v64 has the schema in a new appendix B.

 

Pim

---

From: Mary McRae [mailto:mary.mcrae@oasis-open.org]
Sent: 24 June 2010 16:34
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Re: 15-day Review Request for ebms-header-3_0-200704_refactored

Hi Ian,

  I'm not sure what this is or what you're trying to do. ebXML Messaging 3.0 is an OASIS Standard. If you want to make any changes whatsoever they either need to fall under the errata process (which it sounds like this isn't) or to create a 3.1 version of the spec and proceed through the normal document cycle. It's impossible to change just the schema without changing the document itself - even if it's just updating the cover page metadata and including a new schema link.

Regards,

Mary

On Jun 23, 2010, at 2:32 PM, ebxml-msg@lists.oasis-open.org wrote:

The following request was submitted on 23/06/2010:

Submitter's Name
	Ian Jones
TC Name
	OASIS ebXML Messaging Services TC
TC Email Address
	ebxml-msg@lists.oasis-open.org
Specification Title
	ebms-header-3_0-200704_refactored
Resources
	ebms-header-3_0-200704_refactored.zip
Approval Link
	http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/38380/MessagingTC060210.htm
Previous Public Review Announcement
	http://markmail.org/message/ld5yttxstl3cf6oi?q=ebxml+list:org%2Eoasis-open%2Elists%2Etc-announce&page=2
Abstract
	Refactored header XSD in preperation for Part 2 messaging specification review - all existing XML will still be valid and this is a re-organsiation of the XSD to allow re-use of strutures and elements in new data structures to be introduced in Part 2 of the specification which will be sent for ful review shorrtly.
TC Description
	Development of adittionl functiopnality of the ebXML messaging service specification to support more e-business functionality as requested by the user community.
Notes
	This is a review of the XSD only no changes have been made to the specification and no materail changes to the functionality have occuured this is a tidy and improvement of the XSD after implentation and user feedback to easy part 2 development.