|
|
| Line 3: |
Line 3: |
| | ==Data Referencing - Invalid JSON== | | ==Data Referencing - Invalid JSON== |
| | The JSON conversion does not support control characters like line breaks.<br/>Especially the "Instructions for proper use" usually have a longer text that must be cleaned to a "one-liner".<br/>see [http://stackoverflow.com/questions/25871477/postgresql-text-to-json-conversion http://stackoverflow.com/questions/25871477/postgresql-text-to-json-conversion]<span class="userid-227 comment-signature" timestamp="20160718143007">[[User:Ludwig Schneider|Ludwig Schneider]] 18 July 2016, 16:30 (CEST)</span> | | The JSON conversion does not support control characters like line breaks.<br/>Especially the "Instructions for proper use" usually have a longer text that must be cleaned to a "one-liner".<br/>see [http://stackoverflow.com/questions/25871477/postgresql-text-to-json-conversion http://stackoverflow.com/questions/25871477/postgresql-text-to-json-conversion]<span class="userid-227 comment-signature" timestamp="20160718143007">[[User:Ludwig Schneider|Ludwig Schneider]] 18 July 2016, 16:30 (CEST)</span> |
| | + | ==JSON structure== |
| | + | Just a short question:<br/>did you invent the structure of the JSON yourself or did you lean towards an established standard? I don't think it's a good idea to create your own standard there, so if you find something suitable, I would go for something established.<br/>The JSON Table Schema standard of the Open Knowledge looks similar: http://specs.frictionlessdata.io/json-table-schema/<br/>Another point: When making up example email addresses, try to use @example.com as, as that is what the domain is there for according to RFC 2606.<br/>cheers<br/>Ingmar <span class="userid-5 comment-signature" timestamp="20161205121127">[[User:Ingmar Schlecht|Ingmar Schlecht]] 5 December 2016, 13:11 (CET)</span> |
| | <span class="NiceDiscussions END"></span></div> | | <span class="NiceDiscussions END"></span></div> |
Latest revision as of 12:11, 5 December 2016
[edit] Data Referencing - Invalid JSON
The JSON conversion does not support control characters like line breaks.
Especially the "Instructions for proper use" usually have a longer text that must be cleaned to a "one-liner".
see http://stackoverflow.com/questions/25871477/postgresql-text-to-json-conversion
[edit] JSON structure
Just a short question:
did you invent the structure of the JSON yourself or did you lean towards an established standard? I don't think it's a good idea to create your own standard there, so if you find something suitable, I would go for something established.
The JSON Table Schema standard of the Open Knowledge looks similar: http://specs.frictionlessdata.io/json-table-schema/
Another point: When making up example email addresses, try to use @example.com as, as that is what the domain is there for according to RFC 2606.
cheers
Ingmar
