Trying to translate xml to fixed-width text. xml file is hierarchical, but some elements have only nested elements -- no fields. So there is only a single type of text-line output desired. There is no "line identifier" in the xml -- but I added a line id position to the doc properties and a Field to the innermost Line (the only Line that contains Fields with data). Whenever I try to run the map I'm told that I have a missing ID field. Thanks for your help. --eb
invalid map: missing ID field
| Author | Comment | ||
|---|---|---|---|
 eb44 |
invalid map: missing ID field |
Lead | |
|
Posts: 2 (12/17/06 11:45:45) |
|
||
|
Bryce K Nielsen |
Re: invalid map: missing ID field | ||
|
Posts: 230 (01/05/07 23:32:50) Administrator |
Unfortunately, xmlLinguist doesn't support the ability to have no-field nodes. The error you are receiving is that for every node, xmlLinguist tries to find a corresponding Line. To do this, there *must* be a LineId node.
The only way around this is to apply a stylesheet to the XML document before you apply the xmlLinguist map which either strips out the non-line elements (i.e. flattens the document) or adds a line id to these elements. BUT if you add a Line Id, then the output from xmlLinguist will have effectively an empty line for these nodes, so you'll probably want to "flatten" those nodes... -BKN |
||
|
eb44 |
Re: invalid map: missing ID field | ||
|
Posts: 2 (01/06/07 10:48:04) |
BKN -- thank you for the info; it was quite helpful.
My XSL skills are rudimentary at best. Have you had any requests to allow xmlLinguist to handle no-data-field-nodes? (I assume at present there are no definite plans or you would have let me know.) --thx eb |
||
|
Bryce K Nielsen |
Re: invalid map: missing ID field | ||
|
Posts: 230 (01/12/07 13:28:11) Administrator |
We have at times, but once we explain the philosophy of xmlLinguist, the request tends to die down. xmlLinguist was designed to be a quick, easy way to translate a text document into an XML document. Since there's already a powerful transformation language in XML, the only real trick needed was to get the text into XML. It's also handy that the engine is bi-directional, but to get that feature to work properly, the XML going to Text needs to mirror the Text pretty closely.
The feature that has been requested has been a "non-line-heirarchy" node. This would be a node that exists in the outputted XML document that has no reference to the Text document, but is desired to make the XML document a little more readable. The trickiest part of this feature will be when to inject (or remove if translating the other way) this special node. Do you do it AFTER a certain Line or BEFORE a Line? At any rate, while such a feature could be done for a future version, it will not happen any time soon. In the meantime, you'll need to figure out how to morph your document using XSL. If you'd like, email me a copy of your XML and xmlLinguist Map and I'll see if I can create a stylesheet for you. Bryce K. Nielsen aka BKN |
||
