Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference unit is not implemented #5

Open
cmutel opened this issue Feb 26, 2020 · 0 comments
Open

Reference unit is not implemented #5

cmutel opened this issue Feb 26, 2020 · 0 comments

Comments

@cmutel
Copy link
Contributor

cmutel commented Feb 26, 2020

@boweidema I am having trouble understanding the language here, or at least how it would be implemented. For example, the wiki says:

Reference unit: This is the quantity of the flow to which the quantity of a datapoint should be seen as proportional to. For example, a flow of a specific quantity of CO2 from an activity may be related to another flow of this activity (e.g. 1 km) or to a time period (it may for example be the annual operation of this activity). In RDF, these relations must be made explicit for each datapoint, while in most raw data sources, the reference unit is implicit in the underlying schema (e.g. a schema-specification can be that numbers are always given per unit of the determining output of the activity).

However, it seems like we could just add a self-referential foreign key in flow which would accomplish the same, and drop the idea of a activities having reference flows altogether. It seems like there could be plenty of data sources where we might only have either activities or flows. Seems like an artificial limitation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant