Timeline for Conditional attribute in XML - most concise solution?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2012 at 14:05 | comment | added | Malachi | if you were converting to HTML you would want to run the XML through a Transformation XML anyways. not seeing how having a list of strings in one attribute is beneficial? using the transformation XML you can do all sorts of neat things for HTML/CSS/JavaScript. if this is a Docbook XML that you are working on then please add that to the Tag and the Question itself. might help you get more answers. | |
| Oct 19, 2012 at 20:30 | comment | added | Lech Rzedzicki | in fact, as I mentioned, we are already using one attribute conditionwhich is part of standard Docbook, using more than one attribute could be an option (and is used for other things too) but we'd depart from the standard and it wouldn't be any easier to parse. Also when outputting HTML, for example those values can be simply transferred to say class attribute with less hassle than merging them... I definitely agree on trying to prevent the attribute value from becoming a very long list | |
| Oct 17, 2012 at 13:21 | comment | added | Malachi | changing the schema is one change in one file to add thousands of records. I would say that it's more maintainable that way? you would have to send the updated schema to your clients, but I would think they would be ready as updates come out to update their end as well. while your solution is quickest with very little change to existing software, it will become cumbersome when the attribute list gets longer and longer, isn't that what you are trying to prevent? | |
| Oct 17, 2012 at 6:43 | comment | added | Lech Rzedzicki | Probably the worst solution of all, as then you'd have to modify schema every time you exceed a given amount of outputs | |
| Sep 11, 2012 at 19:49 | history | answered | Malachi | CC BY-SA 3.0 |