Mined Opinions For API: xml-infoset

This tab contains all the opinions collected from Stack Overflow about the API. The other tabs present summaries of the opinions using different algorithms.
  • Empty array, person has no friends: CODESNIPPET_JAVA2 .. details
  • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier).. details
  • It shouldn't touch the entities CODETERM17 and/or clear it's CODETERM18 , for example.. details
  • Well, that's it.. details
  • This is a bit tricky to explain.. details
  • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset.. details
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.. details
  • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined CODETERM15 property (not present in view): CODESNIPPET_JAVA1 .. details
  • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part.. details
  • This is a bit tricky to explain.. details
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.. details
  • Of course with lists this should be more complex.. details
Summaries the opinions about xml-infoset using topic modeling.
  • 0. person needn firstname father touch friend empty fashion functionality add: 4
    • Well, that's it.. details
    • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier).. details
    • Empty array, person has no friends: CODESNIPPET .. details
    • It shouldn't touch the entities firstName and/or clear it's father , for example.. details
  • 0. property deserialize exist empty view null describe merge additionally bit: 6
    • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.. details
    • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset.. details
    • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined friends property (not present in view): CODESNIPPET .. details
    • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part.. details
    • This is a bit tricky to explain.. details
    • Of course with lists this should be more complex.. details
Summaries of the opinions about xml-infoset using three algorithms (Textrank, Lexrank and Luhn) adopted from extractive summarization. Each algorithm was used once for the positive opinions and once for the negative opinions.
  • Well, that's it .
  • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier) .
  • Empty array, person has no friends: CODESNIPPET JAVA2 .
  • It shouldn't touch the entities firstName and or clear it's father , for example .
  • Well, that's it .
  • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier) .
  • Empty array, person has no friends: CODESNIPPET JAVA2 .
  • It shouldn't touch the entities firstName and or clear it's father , for example .
  • Well, that's it .
  • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier) .
  • Empty array, person has no friends: CODESNIPPET JAVA2 .
  • It shouldn't touch the entities firstName and or clear it's father , for example .
  • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset .
  • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined friends property (not present in view): CODESNIPPET JAVA1 .
  • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part .
  • This is a bit tricky to explain .
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null empty property (as it exists in Javascript JSON, XML as described above, PHP, ) is lost .
  • Of course with lists this should be more complex .
  • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset .
  • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined friends property (not present in view): CODESNIPPET JAVA1 .
  • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part .
  • This is a bit tricky to explain .
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null empty property (as it exists in Javascript JSON, XML as described above, PHP, ) is lost .
  • Of course with lists this should be more complex .
  • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset .
  • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined friends property (not present in view): CODESNIPPET JAVA1 .
  • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part .
  • This is a bit tricky to explain .
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null empty property (as it exists in Javascript JSON, XML as described above, PHP, ) is lost .
  • Of course with lists this should be more complex .
Summaries of the opinions about xml-infoset using Opinosis, an abstractive summarizer of opinions..
Summaries of the opinions about xml-infoset using contrastive viewpoints. Each entry contains a pair of positive and negative sentences that are most likely discussing about similar API features.
Summaries of opinions about based on specific API aspects, such as, performance, usability, etc. The 'Overview' page provides an overview of the aspects detected in the opinions. The 'Trend' page shows the distribution of polarity over time for each aspect. The 'Positive Opinions' page groups positive opinions by the detected aspects. The 'Contrastive By Aspect' page shows paris of contrastive opinions under each aspect (where found).
Bug:
  • N/A
  • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.
Features:
  • Empty array, person has no friends: CODESNIPPET_JAVA2 .
  • N/A
Community:
  • N/A
  • This is a bit tricky to explain.
Usability:
  • Well, that's it.
  • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset.
  • Features: 1
    1. general: 1
      • Empty array, person has no friends: CODESNIPPET_JAVA2 .. details
  • Usability: 3
    1. general: 3
      • I've been saying "MUST" a lot, I realize now :) The library needn't actually provide that, but there must be a way to add the functionality in a clean fashion (= not in a way that would make rewriting everything easier).. details
      • It shouldn't touch the entities CODETERM17 and/or clear it's CODETERM18 , for example.. details
      • Well, that's it.. details
  • Bug: 1
    1. general: 1
      • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.. details
  • Community: 1
    1. general: 1
      • This is a bit tricky to explain.. details
  • Usability: 6
    1. general: 6
      • That means I want proper integers, booleans and nulls and I don't want extra object wrappers or something that tries to capture the entire XML Infoset.. details
      • Additionally, arrays must be serialized using nested elements so it's possible to differentiate between empty arrays and properties which aren't present in a given view: Undefined CODETERM15 property (not present in view): CODESNIPPET_JAVA1 .. details
      • Deserialize XML and JSON and merge the data into existing entities** Now this is the difficult part.. details
      • This is a bit tricky to explain.. details
      • Most libraries deserialize into Java objects, but at that time, the distinction between an undefined property and a null/empty property (as it exists in Javascript/JSON, XML as described above, PHP, ...) is lost.. details
      • Of course with lists this should be more complex.. details