|
FIXML
< Previous Next >
Re: FIXML Schema sub-set
George Brennan / BIT Ltd.
19 Apr 2006 10:44AM ETHmm,
Ok, from my perspective I can see the need for an easily operated mechanism to treat FIXML as a repository and generate specific sub-schemas containing one or more selected messages and selected atributes maintaining the added-value metadata such as iso*** etc..
From an Enterprise perspective we also need to be able to easily refactor for message/attribute changes and most importantly it needs to be easily reproduced without extensive XSD skills.
My current thoughts are to create a GUI holding the FIXML tree, where the user can select (drag/drop) the messages/nodes into another tree which drives a list of attributes for toggling on/off. Then outputting the refactored schema.
If I were to build such a thing am I barking up the wrong tree?
All opinions wellcome.
Regards
George
> I know what you mean if you use the raw schema you do produce a lot of data, on way we used to get a more reduced set was:
>
> * create data binding classes based on the full schema
> * output fix messages using the the databinding classes
> * use a tool such as XML Spy to reverse engineer the fix messages (xml)
> to schemas (XSD)
>
> You have to ensure that you output FIX messages with all the fields you
> support and of course you lose a lot of the type, enumerations and
> information that you get from the original - but you do get very
> condensed xsd files.
>
> In our case we prefere to use the schema direct despite the size of the
> classes libs generated.
>
>
> > John,
Re: FIXML Schema sub-set
George Brennan / BIT Ltd. 19 Apr 2006 10:44AM ET
|
