New answers tagged


The most efficient would probably be a binary format which you could read directly into memory, skipping the parsing step.


You can do better than either XML or JSON by exploiting the particular characteristics of your particular data. If the data is completely flat and every row contains the same fields, then CSV is going to be more efficient than either XML or JSON. The reason people generally prefer formats like XML and JSON is because they recognise that the life-time cost of ...


URI = namespace's globally unique name or identifier = globally unique vocabulary (e.g., as alphabetical list, or a hierarchy of broader to narrower meaning) = globally unique jargon. Consider building a database or document on the financial management of the logistics of the oil industry. That would need to use specific vocabularies (i.e., controlled ...


You will need to map the all tags from all the feeds to the correct field. For example in one feed if you have sku you map it to product_sku In other feed say you have an other tag sku_product and you need it mapped to product_sku. Now since only one tag will exist in one feed for a product ( hopefully) , you can have a config mapping the tags to a ...

Top 50 recent answers are included