|
Re: Mapping files?: msg#00127text.xml.xtm.general
[Alexander Johannesen] > Now of course; if I saw the four-line xSiteable XML syntax, I could very > quikly get down to business and understand > what it all meant. If I saw the latter 32-line XTM, I would freak out, and > look elsewhere for something simpler. But > it goes without saying that there is *much* I can't express in my simple > xSiteable XML syntax. But as far as > I am concerned (which is GUI development), I don't need > that complexity right now. I want to get comfertable with > what I need first. > > Maybe this is what you adress; the XTM above *looks* complex, > but it really isn't if you bother sitting down with it to > understand it. And, with the risk of stepping on toes, maybe webdevelopers > don't want to be bothering about or > don't even understand the "complexity", and leave it before > they "get it". > Rught, if you have an application that has a small, fixed set of constructions you can make the surface syntax much simpler, and have a GUI to make things even easier. I also use a working transfer format for my application, which tends to look like this: <topic id="tt-research-organisation" type="tt-research-facility" name="Research Organisation"/> <occur parent="o-bond-biz-school" type="tt-website"> <resourceRef>http://www.biz.bond.edu.au/</resourceRef> </occur> And like yours, it cannot capture everything. But it is easier to turn into the javascript that my app uses. Cheers, Tom P |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Mapping files?: 00127, Alexander Johannesen |
|---|---|
| Next by Date: | Getting TM4J started: 00127, Alex Murphy |
| Previous by Thread: | Re: Mapping files?i: 00127, Alexander Johannesen |
| Next by Thread: | Re: Mapping files?: 00127, Martin Bryan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |