search

leerssej / google-refine

Automatically exported from code.google.com/p/google-refine
Other
0 stars 0 forks source link

YAML importer #210

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
It seems that Refine is being used to export YAML data, 
http://code.google.com/p/google-refine/wiki/ExportAsYAML , so a YAML importer 
seems like a good idea.

I reckon this would be fairly similar to the Json importer, so a lot of the 
code could be re-used there.

Original issue reported on code.google.com by iainsproat on 15 Nov 2010 at 10:22

GoogleCodeExporter commented 8 years ago 
An importer that supports a full implementation of YAML would be complex. It's 
actually far harder to parse than JSON, which is 

It looks like the best Java implementation[1] is snakeyaml (Apache 2.0)[2]. 
Some issues reported with things being a little too low level to get started 
with. However , because refine we needs to do things fairly specifically that 
could be a good thing.

[1] 
http://stackoverflow.com/questions/450399/which-java-yaml-library-should-i-use
[2] http://code.google.com/p/snakeyaml/
Here are some other projects:

  - jvyaml (MIT licence) https://jvyaml.dev.java.net/

Original comment by mcnamara.tim@gmail.com on 15 Nov 2010 at 11:06

GoogleCodeExporter commented 8 years ago 
I will NOT support YAML implementations at all.  There are known issues with 
YAML parsing and the whole reason why there are so many YAML sucks pages.  XML 
and JSON are just as Human-readable as a serialization format, which was the 
primary motivator for YAML's creation.

Original comment by thadguidry on 16 Nov 2010 at 12:00

GoogleCodeExporter commented 8 years ago 
Good point Thad. I disagree strongly that XML & JSON are as human readable as 
YAML, but think your main concern that parsing is difficult.  I wouldn't be too 
keen on Refine maintaining its own unique parser.  However, I don't see much 
harm in providing access to someone else's.

Original comment by mcnamara.tim@gmail.com on 16 Nov 2010 at 12:14

GoogleCodeExporter commented 8 years ago 
Not just difficult.  It's error prone and has limitations within context.

Original comment by thadguidry on 16 Nov 2010 at 12:26

GoogleCodeExporter commented 8 years ago 
Sounds like something to be developed as an extension to Refine. If it works 
fine enough and proves to be in popular demand, then we can decide whether to 
incorporate it into the core code base. Tim, do you do Java? ...

Original comment by dfhu...@gmail.com on 16 Nov 2010 at 12:55

GoogleCodeExporter commented 8 years ago

Original comment by iainsproat on 16 Nov 2010 at 12:57