Date   

Re: Post-hackathon ontology group #ontology #followup

Bo Weidema
 

Thanks for taking the initiative. I find google.docs to be appropriate for this kind of work. If you prefer an open tool, a less advanced option is a riseup.pad

I would like to distinguish between the BONSAI core, which is what is absolutely needed to perform BONSAI footprints, and then have a separate add-on to enable its more general use in Industrial Ecology, mainly an expansion with the concepts of "stock", "assets" and "behavioural rules" linked to agents. All concepts need to be supported by actual data examples and validations.

Best regards

Bo

Den 2019-03-30 kl. 09.55 skrev Elias Sebastian Azzi:

Hej allihop,

I guess all of us have an outline in mind for the ontology-related paper. Here is what I have in mind; I guess we can build on it, iterate and agree on a suitable structure and contents.
Not sure if groups.io is the best way to keep track of edits in the long run; not sure that google.drive suits everyone either; GitHub would be public; we use BOX.com internally.

INTRODUCTION

§ Paragraph IE

IE's object of study is SEM.

The accounting of social, environmental and economic flows in time and space.

Many fields of sustainability and decision-making towards sustainability rely on such accounting.

Several approaches can exist: MFA / LCA / IOA; but all share the same structure; despite different vocabularies/inconsistencies (ref).

Call to lift up IE methods: Reference to Pauliuk

Call to generalise: Bo, 2018

 

 

§ Paragraph CS

  • Ontology definition
  • Linked Data, Web of Data, background, e.g. in life sciences and what it has enabled
  • Open-source

 

§ IE and CS

Acknowledge previous efforts: LCA ontologies existing, IE GitHub repo open source,…

Still, as of today:

  • Conventional databases, ecoinvent; exiobase, have not yet made the move towards these flexible data structures.
  • Remains a challenge to have interoperability between databases
  • Validation of databases
  • Transparency of assumptions (constructs / system model)
  • Updates of databases

 

§ Bonsai organisation, strech goals, hackhathon

  • BONSAI organisation / Working rules / BEP process
  • Strech goals; highlight the sub-goal of the ontology group
  • Hackhathon, background info

 

§ Paper's aim

  • Describe the ontology developed, providing examples and possible extensions
  • Report on BEP process, main choices, alternatives left out + reproducability

 

§ Outline plan of article

[not sure an IMRaD structure is best suited, maybe better to have numbered section]

Section 2 = BEP process, rules, principles

Section 3 = Ontology description (link to online documentation)

Section 4 = Examples (unlinked, linked)

Section 5 = Advanced example, ideally with actual URIs, online;

Section 6 = Discussion of key choices, extensions per field, future enhancements, validation of rdfs

Section 7 = Conclusions, link to other working groups (e.g. correspondance tables, rdf triplestore)

 

SECTION 2  BEP process, rules, principles

Rules for agreeing; definition; BEPs

Principles:

  • Minimalist principle: core; complementary ontologies for different fields; extensions upcoming
  • On the distinction between A and B; for IA: atmospjhere as a process

 

SECTION 3 Ontology description

Table: 3 columns: Key vocabulary in the ontology; labels as in ontology; other usual names given in different fields (LCA, MFA, IOA, LCC, etc)

 

Figure: online viz of rdfs

 

§ Text description of:

  • Classes
  • Sub-classes
  • Properties, balanceable properties, …
  • Sub activities: market, transport, …

 

§ External ontologies

  • Measure, location,…

 

§ To add:

  • Uncertainty, …

 

 

EXAMPLE / APPLICATION [Section 4 , 5]

§ Current hosting of the ontology; examples are available at the URIs mentioned and on GitHubRepo

 

§ Several examples with figures, from simple to complex

Example Raw data; System model

Example with transport, market, impact assessment

 

DISCUSSION [based on BEPs, Section 6]

  • Validation [oops thing]
  • Why we have made certain choices
  • Alternatives left out
  • Reproducibility
  • Extensions: field specific extensions, agent theory (usually lacking in our field), linkages with other resources on WebOfData
  • Give one example of "re-use" by others of the ontology: accounting framework for Stockholm municipality (REFLOW project), how it fits in the ontology (or not) + ref to

 

CONCLUSIONS / VISION /EXTENSIONS [Section 7]

  • how we see them;
  • e.g. GDP, economic data
  • agent theory (unless we want to add it to the ontology right away)

 

 

Some references

 

(1)     Pauliuk, S.; Majeau-Bettez, G.; Mutel, C. L.; Steubing, B.; Stadler, K. Lifting Industrial Ecology Modeling to a New Level of Quality and Transparency: A Call for More Transparent Publications and a Collaborative Open Source Software Framework. J. Ind. Ecol. 2015, 19 (6), 937–949; DOI 10.1111/jiec.12316.

(2)     Pauliuk, S.; Majeau-Bettez, G.; Müller, D. B. A General System Structure and Accounting Framework for Socioeconomic Metabolism. J. Ind. Ecol. 2015, 19 (5), 728–741; DOI 10.1111/jiec.12306.

(3)     Pauliuk, S.; Majeau-Bettez, G.; Müller, D. B.; Hertwich, E. G. Toward a Practical Ontology for Socioeconomic Metabolism. J. Ind. Ecol. 2016, 20 (6), 1260–1272; DOI 10.1111/jiec.12386.

(4)     Weidema, B. P.; Schmidt, J.; Fantke, P.; Pauliuk, S. On the Boundary between Economy and Environment in Life Cycle Assessment. Int. J. Life Cycle Assess. 2018, 23 (9), 1839–1846; DOI 10.1007/s11367-017-1398-4.

--


Post-hackathon ontology group #ontology #followup

Elias Sebastian Azzi
 

Hej allihop,

I guess all of us have an outline in mind for the ontology-related paper. Here is what I have in mind; I guess we can build on it, iterate and agree on a suitable structure and contents.
Not sure if groups.io is the best way to keep track of edits in the long run; not sure that google.drive suits everyone either; GitHub would be public; we use BOX.com internally.

INTRODUCTION

§ Paragraph IE

IE's object of study is SEM.

The accounting of social, environmental and economic flows in time and space.

Many fields of sustainability and decision-making towards sustainability rely on such accounting.

Several approaches can exist: MFA / LCA / IOA; but all share the same structure; despite different vocabularies/inconsistencies (ref).

Call to lift up IE methods: Reference to Pauliuk

Call to generalise: Bo, 2018

 

 

§ Paragraph CS

  • Ontology definition
  • Linked Data, Web of Data, background, e.g. in life sciences and what it has enabled
  • Open-source

 

§ IE and CS

Acknowledge previous efforts: LCA ontologies existing, IE GitHub repo open source,…

Still, as of today:

  • Conventional databases, ecoinvent; exiobase, have not yet made the move towards these flexible data structures.
  • Remains a challenge to have interoperability between databases
  • Validation of databases
  • Transparency of assumptions (constructs / system model)
  • Updates of databases

 

§ Bonsai organisation, strech goals, hackhathon

  • BONSAI organisation / Working rules / BEP process
  • Strech goals; highlight the sub-goal of the ontology group
  • Hackhathon, background info

 

§ Paper's aim

  • Describe the ontology developed, providing examples and possible extensions
  • Report on BEP process, main choices, alternatives left out + reproducability

 

§ Outline plan of article

[not sure an IMRaD structure is best suited, maybe better to have numbered section]

Section 2 = BEP process, rules, principles

Section 3 = Ontology description (link to online documentation)

Section 4 = Examples (unlinked, linked)

Section 5 = Advanced example, ideally with actual URIs, online;

Section 6 = Discussion of key choices, extensions per field, future enhancements, validation of rdfs

Section 7 = Conclusions, link to other working groups (e.g. correspondance tables, rdf triplestore)

 

SECTION 2  BEP process, rules, principles

Rules for agreeing; definition; BEPs

Principles:

  • Minimalist principle: core; complementary ontologies for different fields; extensions upcoming
  • On the distinction between A and B; for IA: atmospjhere as a process

 

SECTION 3 Ontology description

Table: 3 columns: Key vocabulary in the ontology; labels as in ontology; other usual names given in different fields (LCA, MFA, IOA, LCC, etc)

 

Figure: online viz of rdfs

 

§ Text description of:

  • Classes
  • Sub-classes
  • Properties, balanceable properties, …
  • Sub activities: market, transport, …

 

§ External ontologies

  • Measure, location,…

 

§ To add:

  • Uncertainty, …

 

 

EXAMPLE / APPLICATION [Section 4 , 5]

§ Current hosting of the ontology; examples are available at the URIs mentioned and on GitHubRepo

 

§ Several examples with figures, from simple to complex

Example Raw data; System model

Example with transport, market, impact assessment

 

DISCUSSION [based on BEPs, Section 6]

  • Validation [oops thing]
  • Why we have made certain choices
  • Alternatives left out
  • Reproducibility
  • Extensions: field specific extensions, agent theory (usually lacking in our field), linkages with other resources on WebOfData
  • Give one example of "re-use" by others of the ontology: accounting framework for Stockholm municipality (REFLOW project), how it fits in the ontology (or not) + ref to

 

CONCLUSIONS / VISION /EXTENSIONS [Section 7]

  • how we see them;
  • e.g. GDP, economic data
  • agent theory (unless we want to add it to the ontology right away)

 

 

Some references

 

(1)     Pauliuk, S.; Majeau-Bettez, G.; Mutel, C. L.; Steubing, B.; Stadler, K. Lifting Industrial Ecology Modeling to a New Level of Quality and Transparency: A Call for More Transparent Publications and a Collaborative Open Source Software Framework. J. Ind. Ecol. 2015, 19 (6), 937–949; DOI 10.1111/jiec.12316.

(2)     Pauliuk, S.; Majeau-Bettez, G.; Müller, D. B. A General System Structure and Accounting Framework for Socioeconomic Metabolism. J. Ind. Ecol. 2015, 19 (5), 728–741; DOI 10.1111/jiec.12306.

(3)     Pauliuk, S.; Majeau-Bettez, G.; Müller, D. B.; Hertwich, E. G. Toward a Practical Ontology for Socioeconomic Metabolism. J. Ind. Ecol. 2016, 20 (6), 1260–1272; DOI 10.1111/jiec.12386.

(4)     Weidema, B. P.; Schmidt, J.; Fantke, P.; Pauliuk, S. On the Boundary between Economy and Environment in Life Cycle Assessment. Int. J. Life Cycle Assess. 2018, 23 (9), 1839–1846; DOI 10.1007/s11367-017-1398-4.


#evaluation #evaluation

Massimo Pizzol
 

Dear all

 

Here a simple evaluation form for the Hackathon.

 

It’s anonymous.


BR
Massimo


Next steps for post-hackathon Bonsai

Tom
 

In the Friday morning meeting, Chris gave his ideas for next steps to capitalise on the outputs and momentum of this week. I took some notes (as shared on Slack) and have improved them a littie for sharing here. Comment and suggestions very welcome!

Outreach
We should reach out to other communities and invite them into the fold: what kind of communities to reach out to, and how best to do it?

Grants
With or without Bonsai as official partner
For example: open energy data -> September deadline. H2020 proposal

System Improvement iterations
Assumptions we don't need in Exiobase -> simplify the logic of it
        uniform distribution? No: market. We don't have that information
More general system modelling choices -> average or marginal production values?
Quantifying substitution vs allocation (on specific industries/products?)
Data validation dash-board.
  • here's our model: CO2 emissions, trade etc.
  • here's other data: surveys, satellites, other primary data or model results
  • What's the difference between ours and the others?
Run it daily whilst the data improves -> are we getting closer to "truth"?
   
New sources of data linked to our model
New inventory data, and scripts for generating them
        e.g. population changes

Document now!
In one week, the fine details will be gone from our minds.
So go back, look at functions, add docstrings
Can we make the ontology more useful or easier?
Which things have we talked about but haven't yet built and uploaded examples for?
To help new people coming in to not get overwhelmed... These "potential useful contributors" need to be able to read and understand the code.
Reproducibility goals aren't yet met by the repository structure yet. Even people following the hackathon aren't all sure. Housekeeping and clear descriptions needed.


Re: Summary of working groups_ 28th March2019

mmremolona@...
 

I'm creating the sparql queries for the competency questions and double checking the examples as well as the ontology. I'm also working on a converter using sparql. Not sure if Tomas was able to upload the entire OM into the test db in Jena so I can continue working on the converter, I think it's the same with the property paths but I have to verify how to end the property paths early.

Miguel Remolona


Summary of working groups_ 28th March2019

Agneta
 

Hi everyone

As we suspended the meeting this evening, here is a quick overview of what we have been doing in Barcelona. Do feel free to add a summary of what you have been doing.

@Chris Writing codes to export exiobase to rdf format (conceptual framework and how to make it rdf compliant) repo name arboris. Each function documented in the source code. Standardize where and how uri is created, used existing scripts and developed a formalized version. Converting electricity data to RDF.

 
@Tomas: Working on Bontoform with @CHris .Can produce JSON-LD of the use tables from the raw files of Exiobase.
 
@Carlos: Python optimization model integrated into Bentso. Modify the generation of electricity by technology by subtracting the electricity consumption of pump hydro storage. final output will generate the main database for bentso.
 
@Bo: Helping around with ontologies- compartment issue in Simapro. 
 
@Rutger: Worked with the new examples. Identified how compartments could be defined using the ontology without modifying the BONSAI ontology. Looked at how the URIs could be used for the Simapro platform.
 
@Tom: Testing SPARQL queries. Generating lists of metadata for RDF files.
 
@Tiago: Converted csv files to correspondence tables to rdf.  Other rdf conversions to US EPA, exiobase to US EPA and climate change files. 
@Miguel: Converted bentso to rdf. Started to develop Metadata for rdf. 
 
@Matteo: Developed examples in turtle to integrate concepts of markets and transport in relation to BONSAI ontologies. Created rdf repo (This has all the contents of http:/rdf.bonsai.uno). Namespace for year has been created. 
 
@Arthur and @Stefano: Developing the system model (works!!!) needs to be updated with electricity information and then it needs to be scripted in mojo.

Regards
Agneta


Re: Namespaces (URIs)

 

Prefixes like `act` don't really work, as the expansion is specific to
exiobase; I have been using brdfexat (Bonsai RDF exiobase activity
type), and similar, see
https://github.com/BONSAMURAIS/bontofrom/blob/master/bontofrom/exiobase_header.py

On Wed, 27 Mar 2019 at 13:41, Agneta <@Agneta.Ghose> wrote:

Hi everyone

The ontology group understands that most of us are currently busy converting their raw data to rdf format based on the bonsai ontology. We have the following namespaces to refer to the vocabularies we need to refer to. Here are some example prefixes* and the URLs the refer to:

@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> . #(generic rdf schema to define class, subclass, etc)

@prefix bont:<http://ontology.bonsai.uno/core#>. #(Bonsai rdf schema to define activity, flow, flow objects)

@prefix om2:<http://www.ontology-of-units-of-measure.org/resource/om-2/> . #(Schema for units of measure, used to define units, give numerical value)

@prefix time:<https://www.w3.org/TR/owl-time/>. #(Schema to define temporal extent)

@prefix act:<rdf.bonsai.uno/activitytype/exiobase3_3_17/>. #(exiobase URI to define the activity type instances)
@prefix flo:<rdf.bonsai.uno/flowobject/exiobase3_3_17/>. #(exiobase URI to define the flow object instances)
@prefix unit:<rdf.bonsai.uno/unit/exiobase3_3_17/>. #(exiobase URI to define the unit instances)
@prefix loc:<rdf.bonsai.uno/location/exiobase3_3_17/>. #(exiobase URI to define the location instances)

*prefixes used to shorten the URL, it can be defined by the user

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: Namespaces (URIs)

Matteo Lissandrini (AAU)
 

The README has been updated with the name spaces (and names of graphs) defined within BONSAI




Currently the following named graphs (and namespaces) are defined

  • Bonsai rdf schema to define activity, flow, flow objects

    <http://ontology.bonsai.uno/core#>
    
  • URI for Time intervals

    <http://rdf.bonsai.uno/time/>
    
  • URI for core activity types

    <http://rdf.bonsai.uno/activitytype/core/>
     
    • Example <http://rdf.bonsai.uno/activitytype/core/Market>

  • Exiobase 3.3.17 URI to define the activity type instances

    <http://rdf.bonsai.uno/activitytype/exiobase3_3_17/>
    
  • Exiobase 3.3.17 URI to define the flow object instances

    <http://rdf.bonsai.uno/flowobject/exiobase3_3_17/>
    
  • Exiobase 3.3.17 URI to define unit of measures not defined in the OM ontology

    <http://rdf.bonsai.uno/unit/exiobase3_3_17/>
    
  • Exiobase 3.3.17 URI to define the location instances that are not defined in GeoNames or other ontologies

    <http://rdf.bonsai.uno/location/exiobase3_3_17/>
    




From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of Agneta via Groups.Io [agneta.20@...]
Sent: Wednesday, March 27, 2019 1:41 PM
To: hackathon2019@bonsai.groups.io
Subject: [hackathon2019] Namespaces (URIs)

Hi everyone

The ontology group understands that most of us are currently busy converting their raw data to rdf format based on the bonsai ontology. We have the following namespaces to refer to the vocabularies we need to refer to. Here are some example prefixes* and the URLs the refer to:

@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> . #(generic rdf schema to define class, subclass, etc)

@prefix bont:<http://ontology.bonsai.uno/core#>. #(Bonsai rdf schema to define  activity, flow, flow objects)

@prefix om2:<http://www.ontology-of-units-of-measure.org/resource/om-2/> . #(Schema for units of measure, used to define units, give numerical value)

@prefix time:<https://www.w3.org/TR/owl-time/>. #(Schema to define temporal extent)

@prefix act:<rdf.bonsai.uno/activitytype/exiobase3_3_17/>. #(exiobase URI to define the activity type instances)
@prefix flo:<rdf.bonsai.uno/flowobject/exiobase3_3_17/>. #(exiobase URI to define the flow object instances)
@prefix unit:<rdf.bonsai.uno/unit/exiobase3_3_17/>. #(exiobase URI to define the unit instances)
@prefix loc:<rdf.bonsai.uno/location/exiobase3_3_17/>. #(exiobase URI to define the location instances)

*prefixes used to shorten the URL, it can be defined by the user


Namespaces (URIs)

Agneta
 

Hi everyone

The ontology group understands that most of us are currently busy converting their raw data to rdf format based on the bonsai ontology. We have the following namespaces to refer to the vocabularies we need to refer to. Here are some example prefixes* and the URLs the refer to:

@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> . #(generic rdf schema to define class, subclass, etc)

@prefix bont:<http://ontology.bonsai.uno/core#>. #(Bonsai rdf schema to define  activity, flow, flow objects)

@prefix om2:<http://www.ontology-of-units-of-measure.org/resource/om-2/> . #(Schema for units of measure, used to define units, give numerical value)

@prefix time:<https://www.w3.org/TR/owl-time/>. #(Schema to define temporal extent)

@prefix act:<rdf.bonsai.uno/activitytype/exiobase3_3_17/>. #(exiobase URI to define the activity type instances)
@prefix flo:<rdf.bonsai.uno/flowobject/exiobase3_3_17/>. #(exiobase URI to define the flow object instances)
@prefix unit:<rdf.bonsai.uno/unit/exiobase3_3_17/>. #(exiobase URI to define the unit instances)
@prefix loc:<rdf.bonsai.uno/location/exiobase3_3_17/>. #(exiobase URI to define the location instances)

*prefixes used to shorten the URL, it can be defined by the user


Re: #correspondencetables header format #correspondencetables

Miguel Fernández Astudillo
 

Yes, that makes a lot of sense

-----Original Message-----
From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of Chris Mutel
Sent: 26 March 2019 11:57
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables header format

Please consider https://frictionlessdata.io/specs/csv-dialect/. We don't want to invent our own CSV dialect!

On Tue, 26 Mar 2019 at 11:35, <miguel.astudillo@...> wrote:

Dear all



For consistency I think we should specify a bit more the format of the
final tables



Separator: I’d propose “,”

null values: An empty value seems reasonable to me, but I do not have a strong preference.

Header: just one row, the first one



That should help the parser later on. What do you think?



Miguel



From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io>
On Behalf Of @MicDr
Sent: 25 March 2019 18:21
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables header format



Agree. Isn t this also the current format of the tables?



--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables header format #correspondencetables

 

Please consider https://frictionlessdata.io/specs/csv-dialect/. We
don't want to invent our own CSV dialect!

On Tue, 26 Mar 2019 at 11:35, <miguel.astudillo@...> wrote:

Dear all



For consistency I think we should specify a bit more the format of the final tables



Separator: I’d propose “,”

null values: An empty value seems reasonable to me, but I do not have a strong preference.

Header: just one row, the first one



That should help the parser later on. What do you think?



Miguel



From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of @MicDr
Sent: 25 March 2019 18:21
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables header format



Agree. Isn t this also the current format of the tables?

--
############################
Chris Mutel
Technology Assessment Group, LEA
Paul Scherrer Institut
OHSA D22
5232 Villigen PSI
Switzerland
http://chris.mutel.org
Telefon: +41 56 310 5787
############################


Re: #correspondencetables header format #correspondencetables

Massimo Pizzol
 

When I tried to create metadata yesterday for one of the tables (isic4 to Nace2 I think) that table was in the format you describe. The problem was that some columns had mixed data types (e.g. strings and numbers) and the infer function got it wrong so I had to manually fix this. So I would suggest to keep data types homogeneous within the same column – if possible!

 

Not sure how to deal with missing values but I don’t think using e.g. zero is a good option so I would also go for empty value. OK for separator and header.

 


Massimo

 

From: <hackathon2019@bonsai.groups.io> on behalf of "miguel.astudillo via Groups.Io" <miguel.astudillo@...>
Reply-To: "hackathon2019@bonsai.groups.io" <hackathon2019@bonsai.groups.io>
Date: Tuesday, 26 March 2019 at 11.35
To: "hackathon2019@bonsai.groups.io" <hackathon2019@bonsai.groups.io>
Subject: Re: [hackathon2019] #correspondencetables header format

 

Dear all

 

For consistency I think we should specify a bit more the format of the final tables

 

Separator: I’d propose “,”

null values: An empty value seems reasonable to me, but I do not have a strong preference.

Header: just one row, the first one

 

That should help the parser later on. What do you think?

 

Miguel

 

From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of michele.derosa@...
Sent: 25 March 2019 18:21
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables header format

 

Agree. Isn t this also the current format of the tables?


Re: #correspondencetables header format #correspondencetables

Miguel Fernández Astudillo
 

Dear all

 

For consistency I think we should specify a bit more the format of the final tables

 

Separator: I’d propose “,”

null values: An empty value seems reasonable to me, but I do not have a strong preference.

Header: just one row, the first one

 

That should help the parser later on. What do you think?

 

Miguel

 

From: hackathon2019@bonsai.groups.io <hackathon2019@bonsai.groups.io> On Behalf Of michele.derosa@...
Sent: 25 March 2019 18:21
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] #correspondencetables header format

 

Agree. Isn t this also the current format of the tables?


#reproducibility #reproduciblemodels subgroup - on slack #reproducibility #reproduciblemodels

Brandon Kuczenski
 

Everyone interested in the reproducibility working group, please be advised that all discussion for this will be on the Slack channel:
https://bonsai-open.slack.com/messages/CH663NGPJ
Thanks!


Re: #correspondencetables header format #correspondencetables

Bo Weidema
 

I still do not understand why we do not use RDF for this? In RDF every one of the relations would be separate.

Bo

Den 2019-03-25 kl. 18.03 skrev miguel.astudillo@...:

Hello all

should the correspondence table have only two columns?



For example, the exiobase to nace codes: to classify exiobase activities to nace codes the names (descriptions) are not needed. For me it would make more sense to have nace code to nace name in a different table. What do you think?

Miguel
--


Re: #correspondencetables header format #correspondencetables

Michele De Rosa
 

Agree. Isn t this also the current format of the tables?


#correspondencetables header format #correspondencetables

Miguel Fernández Astudillo
 

Hello all

should the correspondence table have only two columns?



For example, the exiobase to nace codes: to classify exiobase activities to nace codes the names (descriptions) are not needed. For me it would make more sense to have nace code to nace name in a different table. What do you think?

Miguel


Re: Task in the Ontology development #ontology

Matteo Lissandrini (AAU)
 

This is something we need to add, see  #6


I remember I've seen some "equation/functional" relation in the SIO ontology for instance





From: hackathon2019@bonsai.groups.io [hackathon2019@bonsai.groups.io] on behalf of mmremolona via Groups.Io [mmremolona@...]
Sent: Monday, March 25, 2019 12:21 PM
To: hackathon2019@bonsai.groups.io
Subject: Re: [hackathon2019] Task in the Ontology development #ontology

Hi all,

Is property relation included in current objectives? I was thinking it could be a flow-object divided by a flow-object but this might be too simplistic as the scaling might not be correct in the dataset. But perhaps a simple correction via a multiplier would work?

Miguel Remolona


Re: Task in the Ontology development #ontology

mmremolona@...
 

Hi all,

Is property relation included in current objectives? I was thinking it could be a flow-object divided by a flow-object but this might be too simplistic as the scaling might not be correct in the dataset. But perhaps a simple correction via a multiplier would work?

Miguel Remolona


Task in the Ontology development #ontology

Matteo Lissandrini (AAU)
 

Hi all,
I've created issues for all the tasks that we have now on github

https://github.com/BONSAMURAIS/BONSAI-ontology-RDF-framework/issues

For each task we can use the issue discussion, comment on it,  and activities related to each task should refer to it.

The first outcome are about the formalization of the RDF Schema in TTL (#4) and this depends on having the prefix for the BONSAI vocabulary (#3 ) .

Cheers,
Matteo