HXLTabConverter common class

[fititnt]

See:

• Spreadsheets
  • https://docs.google.com/spreadsheets/d/1vFkBSharAEg5g5K2u_iDLCBvpWWPqpzC1hcL6QpFNZY/edit#gid=245471857
• Specifications
  • Orange Data Mining Tab
  • https://orange-data-mining-library.readthedocs.io/en/latest/reference/data.io.html
  • HXL
  • https://hxlstandard.org/standard/1-1final/dictionary/
  • https://data.humdata.org/dataset/hxl-core-schemas
  • Other
  • https://en.wikipedia.org/wiki/Statistical_data_type (for naming usage)
  • http://www.saedsayad.com/ (for general idea of how terms are used)
  • https://waikato.github.io/weka-wiki/formats_and_processing/arff_stable/ (Weka may be another exporter)
• Affected libraries:
  • hxl2tab #2
  • hxlquickimporttab #7

---

(As expected) both hxl2tab and hxlquickimporttab are starting to share common code. Also, while the one-liner Orange Data Mining format is actually very similar to HXL itself (sometimes it just add an extra 2 chararacters before the base hashtag, but uses tab instead of comma) if the user is importing back one format already previously saved on the orange data mining, it uses the non-compact format. So some very basic functionality may need to not only export HXL to .tab , but import back.

The initial idea of HXLTabConverter is a move the already existing functionality of export/import to a single class (even if, for sake of simplicity for one-file executable scripts, for now just duplicate the code).

Compared to the base libhxl-python (https://github.com/HXLStandard/libhxl-python), one downside of the HXLTabConverter is that actually may have to implement some of the schema on the code itself instead of use an external schema in special because for sake of simplicity, it would have to make inferences on the type of some hashtags+attributes without explicity attributes understood by the HXLTabConverter

[fititnt]

I will close this issue. Maybe reopen if necessary, but most of the work would be done on the HXLMeta (Usable Class) #9