FpML-AWG-Legacy Fwd: [fpml-arch-modelling-wg] Re: Critical issues for product WG

["Danielle Cauthen" <dcauthen@xxxxxxxx>]

--- In fpml-arch-modelling-wg@xxxxxxxxxxxxxxx, Marcus_Rainbow@... wrote:



> From an XML standpoint, even if I did not care about classes vs.
> instances, there are cases for nesting.

I agree.  What we should aim for is clarity and simplicity in the XML
itself,
rather than slavishly following some verbose conversion from an object
model.
Clearly there are cases where nesting improves the clarity.

> Any single tag that can contain one (or more) copies of a single tag
> that in turn contains data -- conveys little, if any, information.

XML supports containment but not inheritance.
Where the object model uses containment, this should be reflected in
the XML.
Where the object model uses inheritance, this should not be reflected
in the
XML.

Marcus




**********************************************************************
> This email and any files transmitted with it are confidential 
> and intended solely for the use of the individual or entity to
> whom they are addressed. If you have received this email 
> in error please notify the system manager.
>
> This footnote also confirms that this email message has 
> been swept by MIMEsweeper for the presence of computer
> viruses.
>
**********************************************************************

--- 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