Question: I have implemented a C3.js chart in an Angular 2 application but the style in the C3.css file is not being applied to it. I know it is loading (I event copied it all into my component's scss file) but still doesnt work. Is it because the chart loads after css? Does anyone know how to solve this?

I get the data for the chart asynchronously in ngOnInit so I am thinking that the css is applied before the chart is drawn (which happens when the data is received). I am also thinking that it could be something with Angular throwing off the selectors.

```
ngOnInit() {
    // draw pie chart
    this.bitcoinService.getMapData()
        .subscribe(data => {
            var pieChartData = this.formatPieChartData(data);
            this.pieChartInit(pieChartData);  // call this.pieChartInit
        })
}

pieChartInit(data) {
  var chart = c3.generate({
      data: {
          columns: data, // example: [['data1', 30], ['data2', 120]]
          type: 'pie'
      }
});

```

I copied the C3 css right into my scss which is included like this which works for everything else in my component:

```
@Component({
  moduleId: module.id,
  selector: 'bitcoin-dashboard',
  styles: [require('./bitcoin-dashboard.component.scss')],
  template: require('./bitcoin-dashboard.component.html')
})

```

Also, when I d3.select an element of the chart after pieChartInit is called, the styling works. Example: 

```
d3.selectAll('.c3-chart-arc path').style('stroke', 'white')

```

Any help is greatly appreciated!

Answer: 
The table *is* in 1NF, since each relation composed by a set of rows with a unique "atomic" value for each attribute is in 1NF, see for instance the definition in [wikipedia](https://en.wikipedia.org/wiki/First_normal_form). 

Actually, the 1NF has only an historic interest, since it is now considered part of the definition of the relational model.
It really depends on how the blank fields in the second row are supposed to be interpreted. If this is from an exercise, I would say it is quite ambiguous without further context.

If the blank fields are supposed to represent nulls or empty strings in a distinct database row, then the table is indeed in 1NF. But if the layout is supposed to represent a table containing a *nested table* (also known as a repeating group), then it is not in 1NF. Such "repeating" groups were allowed in hierarchical databases, but it not allowed or supported in relational databases.

Given `mem_id` is probably intended to be the primary key, I would *guess* it is intended to represent a nested table, and therefore not in 1NF.

To bring this into 1NF, you will have to split it up into two tables and connect via a foreign key:

```
Mem_id mem_name phone  email 
100     smith    12443 eml1           
101     hena     1020  eml2    
102     moon     2020  eml3    

Book_num Book_titl Author_nam publication edition Mem_id 
200      physics   john         MACGROW   1ST     100
201      math      martin       MACGROW   2ND     100
200      physics   john         MACGROW   2ND     101
204      new java  korth        ALPHA     4TH     102

```

Note I added a foreign key column `Mem_id` in the second table.

By the way, only condition 1 in your list is about 1NF. The conditions 2-4 are the definition of a relation, so would also apply to a relation which is not in 1NF.