[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
I believe we need to use these schema techniques with caution.
OAGi found they got mixed results with this feature of Schema
and the support provided by the different parsers - and errors
generated. We definately do not want to end up with a=20
schema that fails in certain circumstances.
Remind me why we are using this substitution group again - isn't
much more clear in this instance - and we can just provide people
with parameters they can set to control the timetoperform behaviour...?
Thanks, DW.
----- Original Message -----=20
From: martin.me.roberts@bt.com=20
To: ebxml-bp@lists.oasis-open.org=20
Sent: Monday, March 08, 2004 11:59 AM
Subject: [ebxml-bp] Late Binding
Dear all,=20
I had a discussion with Anders on the Late Binding problem and =
we decided that if we changed the TimeToPerform and associated fields =
from Attributes to Elements. The reason for this is it will allow the =
use of substitution group style replacement of these fields to allow =
functionDefinition to be used.
If this is acceptable, may be we should make a wholesale move =
away from attributes to elements throughout.=20
Martin Roberts
xml designer,
BT Exact
e-mail: martin.me.roberts@bt.com
tel: +44(0) 1473 609785 clickdial
fax: +44(0) 1473 609834
Intranet Site :http://twiki.btlabs.bt.co.uk/twiki=20
pp 16 Floor 5, Orion Building, Adastral Park, Martlesham, Ipswich IP5 =
3RE, UK=20
British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000=20
This electronic message contains information from British =
Telecommunications plc which may be privileged or confidential. The =
information is intended to be for the use of the individual(s) or entity =
named above. If you are not the intended recipient be aware that any =
disclosure, copying, distribution or use of the contents of this =
information is prohibited. If you have received this electronic message =
in error, please notify us by telephone or email (to the numbers or =
address above) immediately.
------=_NextPart_000_01C5_01C4050D.E8185900
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Late Binding</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Martin,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Wooowha! We leapt too far here=20
IMHO.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>From a simple extension to allow one =
small=20
capability to wholesale</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>replacement.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I believe we need to use these schema =
techniques=20
with caution.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>OAGi found they got mixed results with =
this feature=20
of Schema</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the support provided by the =
different parsers -=20
and errors</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>generated. We definately do =
not want to=20
end up with a </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>schema that fails in certain=20
circumstances.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Remind me why we are using this =
substitution group=20
again - isn't</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>much more clear in this instance - and =
we can just=20
provide people</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with parameters they can set to control =
the=20
timetoperform behaviour...?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks, DW.</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dmartin.me.roberts@bt.com=20
href=3D"mailto:martin.me.roberts@bt.com";>martin.me.roberts@bt.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Debxml-bp@lists.oasis-open.org=20
=
href=3D"mailto:ebxml-bp@lists.oasis-open.org";>ebxml-bp@lists.oasis-open.o=
rg</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, March 08, 2004 =
11:59=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [ebxml-bp] Late =
Binding</DIV>
<DIV><BR></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Dear all,</FONT>=20
<BR> <FONT face=3DArial =
size=3D2>I had a=20
discussion with Anders on the Late Binding problem and we decided that =
if we=20
changed the TimeToPerform and associated fields from Attributes to=20
Elements. The reason for this is it will allow the use of =
substitution=20
group style replacement of these fields to allow functionDefinition to =
be=20
used.</FONT></P>
<P> <FONT face=3DArial =
size=3D2>If this=20
is acceptable, may be we should make a wholesale move away from =
attributes to=20
elements throughout.</FONT> </P>
<P><SPAN lang=3Den-gb><I><FONT face=3D"Comic Sans MS" =
color=3D#008080>Martin=20
Roberts</FONT></I><FONT face=3D"Times New Roman"><BR></FONT><FONT=20
face=3D"Comic Sans MS" color=3D#000080 size=3D2>xml =
designer,</FONT><BR><FONT=20
face=3DArial color=3D#000080 size=3D2>BT =
Exact</FONT><BR><B></B><B></B><B><FONT=20
face=3DArial color=3D#000000 size=3D2>e-mail:</FONT></B><FONT =
face=3DArial=20
color=3D#000000 size=3D2> martin.me.roberts@bt.com</FONT><FONT=20
face=3D"Times New Roman"><BR></FONT><B></B><B><FONT face=3DArial =
color=3D#000000=20
size=3D2>tel:</FONT></B><FONT face=3DArial color=3D#000000 size=3D2> =
+44(0) 1473=20
609785</FONT><FONT face=3D"Times New Roman"> </FONT></SPAN><A=20
href=3D"http://clickdial.bt.co.uk/clickdial?001609785.cld";><SPAN=20
lang=3Den-gb><U><FONT face=3D"Times New Roman"=20
color=3D#0000ff>clickdial</FONT></U></SPAN></A><SPAN=20
lang=3Den-gb><BR><B></B><B></B><B><FONT face=3DArial color=3D#000000=20
size=3D2>fax:</FONT></B><FONT face=3DArial color=3D#000000 size=3D2>=20
+44(0)</FONT><FONT face=3D"Times New Roman"></FONT> <FONT face=3DArial =
color=3D#000000 size=3D2>1473 609834<BR></FONT><B><FONT face=3DArial =
color=3D#000000=20
size=3D2>Intranet Site :</FONT></B></SPAN><A=20
href=3D"http://twiki.btlabs.bt.co.uk/twiki";><SPAN =
lang=3Den-gb><U></U><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://twiki.btlabs.bt.co.uk/twiki</FONT></U></SPAN></A><SPAN =
lang=3Den-gb></SPAN> <BR><SPAN lang=3Den-gb><FONT face=3DArial =
color=3D#000000=20
size=3D2>pp</FONT><FONT face=3D"Times New Roman"></FONT> <FONT =
face=3DArial=20
color=3D#000000 size=3D2>16 Floor 5, Orion Building, Adastral Park, =
Martlesham,=20
Ipswich IP5 3RE, UK</FONT><FONT face=3D"Times New Roman"> =
</FONT></SPAN>
<UL>
<P><SPAN lang=3Den-gb><FONT face=3DArial color=3D#c0c0c0 =
size=3D1>British=20
Telecommunications plc</FONT><FONT face=3D"Times New Roman"=20
size=3D1><BR></FONT><FONT face=3DArial color=3D#c0c0c0 =
size=3D1>Registered office:=20
81 Newgate Street London EC1A 7AJ</FONT><FONT face=3D"Times New =
Roman"=20
size=3D1><BR></FONT><FONT face=3DArial color=3D#c0c0c0 =
size=3D1>Registered in=20
England no. 1800000</FONT><FONT face=3D"Times New Roman" size=3D1>=20
</FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3DArial =
color=3D#c0c0c0=20
size=3D1>This electronic message contains information from British=20
Telecommunications plc which may be privileged or confidential. The=20
information is intended to be for the use of the individual(s) or =
entity=20
named above. If you are not the intended recipient be aware that any =
disclosure, copying, distribution or use of the contents of this =
information=20
is prohibited. If you have received this electronic message in =
error, please=20
notify us by telephone or email (to the numbers or address above)=20
immediately.</FONT></SPAN></P><BR></UL></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_01C5_01C4050D.E8185900--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]