OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [emergency] DE and well formed XML


Lee,
 
These design time artifacts really do not belong in the instance schema themselves.
 
We've solved this in the CAM realm by use of an optional <DataReference> section (non-normative currently).
 
The idea is that the DataReference can point to external definitions and custom XML markup - for the kind of purposes you envision.  This can be at template level, or right down to element and attribute.  The use of UID references also allows definitions across schemas - so that common content need only be referenced once.
 
Obviously you do not want this kind of content impeding into the actual exchange transactions and production content.
 
The Appendix B documentation available from the OASIS CAM TC documents gives further details.
 
Thanks, DW



-------- Original Message --------
Subject: Re: [emergency] DE and well formed XML
From: Rex Brooks <rexb@starbourne.com>
Date: Thu, June 05, 2008 9:42 am
To: "Lee Tincher" <ltincher@evotecinc.com>,
<emergency@lists.oasis-open.org>

Adding this topic if fine with me, Lee,

thanks,
Rex

At 8:51 AM -0400 6/5/08, Lee Tincher wrote:
>All,
>
>I'd like to schedule a topic of discussion about
>a proposal for our future efforts. While
>consuming the DE with "any well formed XML" it
>struck me that we may have an opportunity to
>make our standards much easier to consume from
>the developer standpoint. I would like to
>propose that we develop an attribute level of
>something like "Recommended Display" which could
>have tags like "Title", "Label" and "Length".
> This would potentially allow a developer to
>just create a one time (we could provide code
>samples in differing languages) Form Map to all
>EDXL payloads. It needs to be at the attribute
>level since it would apply to each EDXL element
>in a payload.
>
>This is different that XSL translation since the
>XSL assumes you know the structure of the
>incoming XML and you have created a map based on
>that knowledge. This should be mapped to the
>"language" element we already have and can
>result in Digest population for the DEŠ..
>
>Any thoughts?
>
>Thanks,
>Lee
>
>Action springs not from thought, but from a
>readiness for responsibility. - Dietrich
>Bonhoeffer
>


--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]