# IfcDoc cross-platform implementation **URL:** \ **Category:** IfcDoc Tool\ **Created:** [April 29, 2019, 6:59am UTC](https://forums.buildingsmart.org/t/ifcdoc-cross-platform-implementation/1361 "2019-04-29T06:59:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Moult](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/moult/32/196_2.png) [@Moult](https://forums.buildingsmart.org/u/Moult)\ **Post date:** [April 29, 2019, 6:59am UTC](https://forums.buildingsmart.org/t/ifcdoc-cross-platform-implementation/1361/1 "2019-04-29T06:59:35Z")
Good morning all! I i specifically referring to this issue here: > > > With the current evolution of dotnet core and the availability of a.o. Xamarin.F…orms, it would be nice that future versions of IfcDoc can be ported to be more cross-platform (e.g. macOS and Linux). I understand there is a scarcity of resources. Perhaps if some of the core maintainers (@TLiebich) could suggests a roadmap, the community can help start porting this tool along with the new overall strategy of how to host the IFC specs. From my understanding this is the current preferred approach: 1. The IFC spec changes into a git-tracked repo with smaller, easier to manage XML chunks. 2. Maintainers of current IfcDoc write a list of MVP usecases to implement for a new, cross-platform IfcDoc 3. The new IfcDoc starts being built, reading from the IFC spec git repo. Whatever technology it uses, it should be cross-platform. A frontend can be built for the web to make it easy for everybody to experiment with, but it should be built in a fashion that is decoupled from application logic, to allow for future frontends. ---
**Author:** ![ReD\_CoDE](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/red_code/32/226_2.png) [@ReD\_CoDE](https://forums.buildingsmart.org/u/ReD_CoDE)\ **Post date:** [April 29, 2019, 8:35am UTC](https://forums.buildingsmart.org/t/ifcdoc-cross-platform-implementation/1361/2 "2019-04-29T08:35:32Z")
@stefkeB, @Moult, @TLiebich, @jwouellette, @pipauwel, @Ali_Ismail @IFCWebServer, It seems that a few works on this and I think is a good idea if we have a web-based/semantic web IfcDoc, but with “Function as a Service” methodology which technical teams be able to work on and improve a piece of codes/functions/extensions constantly. It will speed up IFC Schema development Also, I believe that IFC schema is like PHP and MySQL when they found that they have some issues and other languages and databases are better and started to improve themselves as fast as they could. For instance, as our startup team said, now PHP7 and MySQL8 are better and solved some issues So, IFC needs the same strategy too. Needs “a new” structure > **[Ehsan Azari posted on LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:6528355262531670017)** > > 1. I’m thinking to a cloud platform with a methodology AWS Lambda has (Function as a Service) that you can work on a whole web-based IFC schema and edit... ---
**Author:** ![Moult](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/moult/32/196_2.png) [@Moult](https://forums.buildingsmart.org/u/Moult)\ **Post date:** [June 18, 2021, 12:14am UTC](https://forums.buildingsmart.org/t/ifcdoc-cross-platform-implementation/1361/3 "2021-06-18T00:14:12Z")
For closure, a cross-platform, version controlled, documentation server is now available here: [IFC4.3.x-development/server at master · buildingSMART/IFC4.3.x-development · GitHub](https://github.com/buildingSMART/IFC4.3.x-development/tree/master/server) - hooray and great work by buildingSMART!