Proposal: using ".ifc.json" file extension instead of ".ifcjson"

[tomas-polach]

Thank you for initiating this projects. This does seriously lower the entrance barriers for software engineers not familiar with IFC and clearly empowers interdisciplinary projects!

I would like to like to make a humble proposal: using .ifc.json as file extension instead of .ifcjson.

My considerations are:

• readability: editors do automatically highlight code correctly (including github editor)
• definition: looking at a file named *.ifc.json i intuitively assume that it is a subset of JSON specs. With *.ifcjson it might be a format parallel to JSON and as such not fully compatible.

[jmirtsch]

Sure, I'm happy to do that and will push some new commits shortly. Part of the reason for choosing .ifcjson was following suite with the .ifcxml (http://www.buildingsmart-tech.org/downloads/accompanying-documents/guidelines/ifcXML%20Implementation%20Guide%20v2-0.pdf) but this can be reviewed in the event of Building Smart officially defining json as an official serialization of ifc (which they might use .ifc.json anyway).