Timeline for Storing survey data from csv to xml
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2022 at 14:58 | comment | added | TextGeek | Methods 1 and 2 seem fine (and +1 for naming the "question" attributes that, instead of calling them "id" -- they are idrefs in XML terms, not IDs). Whether some or all questions are multiple-choice vs. written-in answers is something to consider. I'd avoid method 3, because you'd have to change the schema each time you change the survey, or do a new survey. Though it is nicely compact.... | |
| Apr 9, 2018 at 16:08 | vote | accept | screencut | ||
| Apr 9, 2018 at 7:09 | comment | added | Laiv |
The first one seems to me the more flexible and resilient. The 3rd has an odd semantic. On the other hand, encoding free text into XML attributes can be painful when it comes to encoding special characters like quotes or double quotes. The key around output formats is to ease the reading. Which one is easy to read or easier to implement a reader. So please, don't do things like: <questions><1></1><2></2></questions>
|
|
| Apr 7, 2018 at 19:11 | comment | added | Morgen | Glad to help :), though you may want to wait the customary 24 hours before marking an accepted answer, as there may be a better encoding waiting in the wings | |
| Apr 7, 2018 at 19:05 | vote | accept | screencut | ||
| Apr 7, 2018 at 19:19 | |||||
| Apr 7, 2018 at 19:04 | comment | added | screencut | For the purposes of what I'm being asked, i think the first option with added questions element would be the best. Thanks for your input! | |
| Apr 7, 2018 at 18:05 | history | answered | Morgen | CC BY-SA 3.0 |