roll
> See http://tech.datopian.com/notebook/#package-json-and-npm-were-a-mistake - this makes a strong case that all the "meta" stuff in package.json was a mistake. All you need to identify a resource is a url or...
> b) making it non-sluggy I think I don't have any > a) making this optional I would say it's really big. I haven't analyzed it yet regarding our libs...
I think the name generation should be handled by software as it is already (humans side) by for the interoperability standard it's important to present (machines side)
Data Package Pipelines uses prefixes like `dpp:property`
Greate catch @iSnow !
Is there a chance that we can reduce the number of properties' mixed types as we discussed previously e.g. - making `schema.primaryKeys` an array only - making `schema.foreignKeys.[reference.]fields` and array...
Just wanted to share another thinking. I'm wondering if currently, the specs are too fragmented which makes it hard to understand Frictionless Data conceptually. I think in general we can...
Probably I should have put `headerJoin` into the `Options to consider` category as it's a very minor and rare case. At the same time, people asked for this option for...
Sure. I'll PR (can take some time though)
Yes it's easy on the implementation level