[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: FpML-AWG View generation syntax
See comments below.
-----Original Message-----
From: awg@xxxxxxxx [mailto:awg@xxxxxxxx] On Behalf Of Anthony Coates
Sent: Thursday, December 27, 2007 4:17 PM
To: awg@xxxxxxxx
Subject: Re: FpML-AWG View generation syntax
Look good, Brian. Can I ask, is the <view:override> element allowed to have an <xsd:annotation> or <view:annotation> child element? I'm thinking that override documents may need override documentation.
>> There's currently no schema for the "view" namespace (should we define one?) so this should be legal (and it is in XML Spy, for example), however it has no effect on the output. If we did this, what should the handling be? Replace the existing documentation? Add to it?
The "result" on page 2 seems incorrect; won't the element be called "pretrade" in the pretrade view?
>> No, on the <view:override> element the "name" attribute is special and means the view name. However, your comment points out that perhaps we might like the ability to override the component name in a view; I therefore suggest changing the <view:override name="[viewname]" ...> syntax to <view:override view="[viewname]" ... > so we can do this. This will also make the "override" element consistent with the "exclusive" element . This change is trivial in the scripts, and shouldn't be too difficult in the schema.
Why does <view:exclusive> support Schema attributes? What would be the use of having them? Are you thinking that different "exclusive" uses of the same element would need different Schema attributes? That's quite plausible, it seems to be, but not discussed in the document.
>> Sorry, this is a cut and paste error. The <view:exclusive> element does not support schema attributes; the example is correct, not the definition. I will correct this.
I find the "skip" attribute on <view:override> to be a curious choice. I don't think the meaning is obvious, or not as obvious as it could be. It would make more sense applied to the <view:exclusive> element, I would have thought, but why not just have a <view:skip>? It would be more straightforward, at least to my mind.
>> Good suggestion. I've been a bit uncomfortable about this as well. I'd be happy to change this as you suggest.
>> I won't make any changes in the syntax until we've discussed them at the AWG, but the changes above (rename view attribute, change "skip" to an element", perhaps add support for view-specific documentation) seem good to me.
Cheers, Tony.
----- Original Message -----
From: "Brian Lynn" <brian.lynn@xxxxxxxxxxxxxxxxxxx>
To: awg@xxxxxxxx
Sent: 18 December 2007 15:50:29 o'clock (GMT) Europe/London
Subject: FpML-AWG View generation syntax
Attached is a first cut of a document describing the FpML 5.0 view generation syntax. I think it needs some work on formatting, and perhaps some additional clarifying text. Also, in doing this I realized that there may be some slight inconsistencies that could be cleaned up.
Comments/suggestions welcome.
Brian
--
Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
Mobile/Cell: +44 (79) 0543 9026
Data standards participant: genericode, ISO 20022 (ISO 15022 XML), UN/CEFACT, MDDL, FpML, UBL.
http://www.mileywatts.com/
-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe awg youremail@address
To view archives: http://www.fpml.org/_wgmail/_awgmail/threads.html
-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe awg youremail@address
To view archives: http://www.fpml.org/_wgmail/_awgmail/threads.html