[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FpML-AWG-Legacy Fwd: [fpml-arch-modelling-wg] Re: Class name tags
- To: awglegacy@xxxxxxxx
- Subject: FpML-AWG-Legacy Fwd: [fpml-arch-modelling-wg] Re: Class name tags
- From: "Danielle Cauthen" <dcauthen@xxxxxxxx>
- Date: Thu, 07 Jun 2007 20:02:45 -0000
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=lima; d=yahoogroups.com; b=nFKEJ7nxIexrpgZTz64uvcKOjuONXR/9wgw7OcYzyPdGpw18Af4YuJgcVfP0Jg99aIG/3n6cHp23JlcjRiqydp+y3FJVeNtlu94DNDT1370weu7t3For6uv8RNI5r5Z+;
- Reply-to: awglegacy@xxxxxxxx
- Sender: awglegacy@xxxxxxxx
- User-agent: eGroups-EW/0.82
--- In fpml-arch-modelling-wg@xxxxxxxxxxxxxxx, "Marcus Rainbow"
<marcus_rainbow@...> wrote:
Robert
> I was arguing that FpML
> does not define what is and is not a class. IF classes are to be
> instantiated, THEN
> FpML must also define a standard as to what is a class.
Yes, I accept that position. I like your distinction between built-in
types such as Date and more complex classes. The point I was trying to
make is that OO-modeling and explicit inheritance relationships are
desirable, but not if they can only be achieved at cost to the clarity
of the resulting XML.
Marcus
--- End forwarded message ---
-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe awglegacy youremail@address
To view archives: http://www.fpml.org/_wgmail/_awglegacymail/threads.html