- AEON TIMELINE 2 BLACK FRIDAY FULL
- AEON TIMELINE 2 BLACK FRIDAY PRO
- AEON TIMELINE 2 BLACK FRIDAY SOFTWARE
A prominent example is Microsoft’s OXML format, which is a pro forma ISO standard, but with its huge specification has never been fully implemented. However, experience shows that while text-based formats such as XML or JSON represent a major advance over binary formats, they do not solve the problem per se. I agree with you about the requirement for open standards for data exchange.
Just see how Microsoft have changed their attitude toward open source and open data the last 2 decades. The problem is that most users do not know how to, but if they could export to e.g., JSON-LD, the data could with little effort been imported and utilized in multiple other research tools, in addition to web publishing tools…īut, when users just silently accept anything a developer do, and keep on paying them money for “nothing”, nothing will ever change…
AEON TIMELINE 2 BLACK FRIDAY FULL
If there was a full export of Aeon entities and object to Markdown with YAML keywords, those Notes could be used as a “hub” for other research tools, as it is possible now by using CSV and a transcoder script for CSV to MD or by writing a VBA script in Excel or doing the same with a Python script. Just one example that is a digression here…
AEON TIMELINE 2 BLACK FRIDAY SOFTWARE
Sure, but you won’t be able to get around analyzing and filtering the data before it gets into the other app, will you? With a spreadsheet, even users without programming skillsĪt the moment we can agree about that… BUT, and it is a huge BUT… If we, the users don’t start to ask for open data and open standards, nothing will ever change.īUT, if we are active in asking for and discussion open standards and stop use software that doesn’t conform to open data stadards, developers that want to earn money on their products need to start listen…Īnd for data in e.g., Aeon, there is not a problem to make a full export to a format like JSON-ND, GraphML or other open standard interchangeable file formats that will be easier to use for those that would like to use their data in multiple applications, it will also be better for the developer that do not have to bloat their software with a lot of extra features. I just wish Aeon made integration a bit easier… If that doesn’t work (like you, I am struggeling a bit with the Aeon data structure), I’ll bite the bullet and go over to plan C and use the Open Source Timeline and its “wonderful” XMLīTW, I saw that you have done some work with it and yWriter already. An earlier import test produced several error messages because the data types were missing from the blank Aeon target file (instead of creating them). So plan B: I’ll customise a new, blank Aeon file and then see if I can get some mapping automation between the Export/Import working ok. I haven’t figured which hashing algo is being used, and honestly, I don’t feel like spending time on this. Every event has a hashed identifier of length 21 which will need to be added to a (new) event/entry. But writing back to it looks like a hard problem. Reading the JSON of an Aeon file into an external DB is solved. The jellyfish above is actually from an entry in the “Feature Overview.aeon” example that comes with Aeon TL. I also learned that the binary part of an *.aeon file are attachment(s) to an event. Your updated script is working very well! I like the level up/down trick - haven’t thought of that. Apart from that, there was also once talk of an API for synchronization, but I don’t know if that has been realized yet. If you want to send data to Aeon 3 with your own program, the csv import might be the easier way. By the way, this was the decisive reason for me to stay with Aeon 2, whose format I can read and write completely, which I use for synchronization with yWriter. Thus the Aeon 3 format can be read by third-party software, but hardly written. However, the Aeon3 format adds an extensive amount of redundancy, which, as far as I understand it, is supposed to speed up loading, because it takes over various program states directly. By the way, so far this is also true for the Aeon2 file format. That is, it is quite an extensive tree full of cross-references, which in turn are defined in other sub-trees. The file format is not easy to figure out, because the flexibility of the software is reflected in the data structure. My extraction script separates the JSON part, formats it and saves it in a text file. The Aeon3 file, as I know it, is composed of a JSON part and a binary part.
0 kommentar(er)
