Re: Schema & BP Spec: Items for today's BP/CC meeting

[Philip Goatly <philip.goatly@bolero.net>]

Folks,

 I think we need Schema and DTD.

   Schema transformation into DTD is possible but since the Schema contains
more meta information potentially I guess we should define in Schema and be
able to 'reduce ' to a DTD.

Cheers, Phil
----- Original Message -----
From: <Sharon.Kadlec@NWA.COM>
To: <ebxml-bp@lists.ebxml.org>
Sent: Monday, April 16, 2001 9:34 PM
Subject: Schema & BP Spec: Items for today's BP/CC meeting


>
>
> It's only my opinion (I haven't talked to anyone else on the team), but I
> feel very strongly that both Schema and DTD versions should be available.
> They often are used for very different communication/integration purposes
> in different ways... now, you could do one or the other and write a
> tranform document... but don't just do one. Schemas are too hard to
> integrate into narrative text (even though they may/may not be as precise)
> and many times schemas are the best choice for integrating back into
> database situations.
>
> This is just a thought and I know if it does not come to pass in this
> iteration, it will down the line.
>
> Cheers
>
> Sharon Kadlec
> Northwest Airlines, Inc.
>
>
> ---------------------- Forwarded by Sharon Kadlec/MSP/NWA on 04/16/2001
> 02:17 PM ---------------------------
>
>
> "Hayes, Brian" <Brian.Hayes@Commerceone.com> on 04/16/2001 02:03:37 PM
>
>
>
>  To:      ebxml-bp@lists.ebxml.org
>
>  cc:
>
>
>
>  Subject: Schema & BP Spec: Items for today's BP/CC meeting
>
>
>
>
>
>
>
>
>
> Karsten wrote:
> > An issue just raised by Neal: Should we include a W3C schema
> > version of the
> > SpecSchema along with (or instead of) the DTD? What is the
> > recommendation from
> > BP/CC - DTD or Schema, or both?
>
> Time permiting, I strongly recommend we deliver a schema version.  DTDs
are
> not precise enough for defining interfaces (structure and strings) and the
> BP Spec Schema is essentially and interface.
>
> Brian
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org
>
>
>
===========================================================================
>
> This e-mail and any attachment contains information which is private and
> confidential to Northwest Airlines, Inc. and is intended for the addressee
> only. If you are not an addressee, you are not authorized to read, copy or
> use the e-mail or any attachment.  If you have received this e-mail in
> error, please notify the sender by return e-mail and then destroy it.
>
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org
>