Good morning. I'm very happy to be here. Maybe not happy to have the first talk. Usually
I write it during the talks. So I, it's still not the less, yeah, okay, yes, I mean, I just
remember, as I said, I'm not walking up totally, but I'm working since 1999 on this stuff
with staff in Hamburg, applied to staffers and became a member of some Mike Stim. And the
true kid was what we had in the back end for in Java, with no appatial license, that is for
the back end of the back office, right? And it's used still used to open exchange in the
back end, and as a fork unfortunately, but I popped it back. And only F is the standard that
they did once. And just to mention it, it was quite surprising because they said, when
we're supposed to identify anyway, then we can make an oyster standard of it, and it was
such a wave that that was the reason why Microsoft created their OXML standard. And just
as an anecdote, it's first it was called Open Office XML, but then others, like Alive said,
I don't mention like a product, then we are just second citizen. So we have to make it the
open document format. And Microsoft said, okay, we need a name and from Open Office XML,
they switched the first words. It was Open Office, Office Open XML. I was totally confused
at that time. Okay, 15 minutes, they're starting right away. The ODIFTC, we are just, yeah,
not seven draft, well, one was left. So, and Regina has to grow a little back back. So,
from six people, we're just not more or less than five. And then three freelancers, and I'm
one of the chairs. And Mike Stim, who's not here, is one of the, yeah, aside of Regina,
most, most pushing member, Regina was usually the super fed. I'm working these days mostly
in electronic devices where I make the money. There's an European standard for invoices
and commission pays me now for being added to them. And I tell you some slides that because
we can learn, it's two fields they should learn from it. So, now I have no idea what Mike's
of his doing there. And they, she liked it. They implemented ODIF one or four, even already.
I'm not sure about the quality of that. We have no tests at the standard level, also
the problem. But it's very helpful to have them. And most of the work that we're doing
is now interoperability, things that are missing in the file format for which we exist in
ODIF. And think about the file format, just like the glass of water, glass, sorry, glass,
we're working in full data in, right, and switch it all the time. And we just have to enlarge
the glass to the other liquid for features going in there. So, we need some work, some assistance
here somehow, and also maybe some big players, and maybe some big ideas, and we have to do
some big thing again. So, what is the standard, first of all, I have today's day, again?
It's very, very important, this blueprint, this like a cooking recipe, that all the things
do the same thing, like, you give a recipe to a friend, and the cake should taste the
same thing, or the same way, yeah. And that's the way, like a Dinoff Air Force, a big
big success, even if America used the letter format. But it helps a lot to have usually
a voice lock in, and you can save a lot of money there, and we just have this file format,
this shock frozen runtime, and we haven't standardised layout, we haven't standardised
how the way it's allowed to change the format, and that's the next thing that I would like
to do. So, the other thing is already a toolkit, and the status that, I'm basically really
used there was some work on this electronic invoices, it should become an reference
implementation, it's like, in the back end without view, but it's like easy to, to
high the complexity of this file format, right? And I try to generate as much from the
standard as possible, and this executive generation is a problem. The standard, the
status would part of four years ago, or the F1-3, one that four is already in the queue
should be soon built on an ISO, that's the next level, I usually explain that ISO is
like the king standard, but to me it's a bit old system, I wouldn't, I could not, we should
renovate this system, but it's different talk. Marwood, think about the marwood, which
call for marwood, and then you see that's the problem here. Anyway, Microsoft has this one
of four support, and there's a link in there, and we are just missing other reference
limitations, like ODF, I need to fix the generations from now, and we started working
on ODF 105, and this one thing I like, and then I realized, I want to do not do
the usual slides, I just want to do something like, I'm 54 through something, and I've
got 10 more years, but we now, I want to do something, I want to kick ass, I found something
like this, so I like to tell you, maybe I have to tell you that we have a problem, right?
Maybe we are too busy in maintaining, doing small things, that we forget to see a bigger
picture, right? And I like to give you a wake-up call at the first talk, and I still, I
really, you're not still, I really used that, I mean, no, no, links are here, and that's
the saying that we have no time to sharpen the saw because we have no time for it, we have
to make the trees, so we have so much mental and so much customer work, but we have to
do a big thing, and the one big thing is, think of the browsers, all the browsers are
the JavaScript, dumb API, I don't say we make a syntax API, but they have an API, and
nobody would come along and say Firefox, I want to Firefox API, the real machine API,
I do something totally different, yes, we break the internet, JavaScript works, and all
because they have an API, we do not have something like this, we're going to have a
conformance test on this thing, so I'm asking you to consider, and this is the thing
that I'd like to talk, and to polish up the argumentation, the next time at the
LibreOffice Conference, to come up with him in 17 minutes, maybe, with a better argument,
but let's do step back, what I've learned so far, there are two things, the syntax and
the semantic, when you go to a restaurant, individual group, all get menu cuts, and there's
totally different, there's someone's written, we know, there's vying and wine, yes, but in
the end, this token refers to the same semantic, maybe there's just one bottle of
a tail, okay, so we have, and this like Firefox, yes, it can be always say not all the
F, RTF, and if you load it in the office, it looks all the same, or it should, and the
thing is, I'm telling you, that's not matters so much, we can exchange it, we can prove
that there's so much innovation it, yes, we can go from final state document to change
document, like we have git commits, right, and we have to innovate, and we can go
from XML back to a binary, I mean, text files are binary guys, but it's so ubiquitous
because there's an all, there's a way to, to see them and analyze them so
way, yes, so we can have, we can go back to binary, if we have, and software that
analyze it, okay, and we do much more information, automation, that's a word of
thing, so, and that's exactly, look, if you use the semantic to XML, that's the way
that you've been standard to have, because we have two XML, you know, you'll see
fact whatever, call them a, b, yes, but we have some, we name something, the invoice, and
that's very easy, we have a semantic, we map it, we have two different documents, and
it's very simple, they have, say, the invoice number, you can find here, and there's
a lot of other information, so the great stuff is semantic, but this is X-Bus, and it's
very simple, and I extracted it in most formats, so you can have this mapping in a
structured way, not in PDF, but all I'm saying you, when we at the standard, at Oasis,
are always taken or XML missing pieces, like data, the glasses, not full enough, why
don't we make a picture and create for, oh, XML, this syntax binding between these
formats?
We do this first with large language model, it's commonly done, yes, the company is
giving a mapping, maybe an office mapping, but for invoice and this stuff for 250 years,
but, and this can be, this should be done, and we should have a form away, like this, it
can be, in a table, but we have to share it, it's somewhere in the Libya office code
hidden, it's there and ODF and Oasis, and that last Monday call, last week, we said, we
should write there that we have this new attribute because there are no XML, we have
the same thing, so they understand what's the meaning of it, yes, we're looking for a name,
and we should be very obvious that this purpose, they find another corresponding information
there, and then I realized we need to put this together, we need to expand, yes, it's
not enough to write only ODF syntax, like one menu card, we have to look at the
total restaurant, yeah, and look at the semantic, like, and so, yeah, so what I want
to do is syntax, it's not the first citizen, because you load it, and then you filter
it, it's gone, yeah, but what exists is semantic, there's still the document, there's a table,
and I thought my mama, well, she started that, if I found someone on old people as something
at her, I said, look, there's a paragraph, there's a table, there's an image, right, and
then in the fourth, it's a paragraph as well, then go to the third letter, and please
delete it, because this is wrong, right, you will phone not by open the zip, go to
contradicts and mail, go to office, body text, go to, this is so much implementation detail,
and the funny thing, when I do this by ordering this, it works for RTF, DocX, and it works
for all the different work formats, because we have to track from the center going back
to the semantic, and that's where we should build the API or anything, we should talk about
the human API, sorry, it's human semantic, and for instance, is it table, is it like
a natural, there's, you know, it's the table, it's a two-dimensional array, and it's
another way in XML, because there's a tree, so with the columnist, no cell, and the
every row has a cell, so what you do is basically, when I tell you what the argument
is, please insert the cell at the right, insert the column at the right spot, and
you want, and then insert a cell at the right spot for RTF, and we can define it,
the column, the grammar, in the spec, like, only XML, no we would change it in XML, but
it's still in the front row, okay, we have to start it, but you would do differently, but in
the end, the same output would be, yes, the same layout, the same view, and that's the way,
like I would have go further to not only define the final state, but only define changes,
based on XML changes, and also in mapping, and also in place the complexity of XML,
we are all the custom, we all want to have this work in all formats, yes, build an office
API that works also for Microsoft Office if possible, yes, so, yeah, it must take it out
a height of the code, and it's a run to the API, and the syntax is put at the way semantic
states, we need some some semantic DOM, and the first stack is to define these semantics,
what's the table, and what's, and then later on we might even define what if they're
using changes like this API, this semantic table has, I said before, and insertion of
a column, and you can apply it even to mark up, we understand what change would happen
there, okay, so, yeah, I think I mentioned this all before, and the nice thing, if this
works, you have something like an asset test in HTML, the open document, and it tells
you, it goes up, bleet, very colorful, and says, oh, the format is 37%, and then we can
have some test files, and open up with Microsoft Office 365, and says, oh sorry, the one
that for support really sucks, yes, it's, it's goes to nothing, so it's, because nowadays
you can do any, a little bit tiny bit and say, I'm, I'm conformant though, I'm primitive
already of one or four, but you have no idea, and I heard in a way to, in a, in a, in a cap
that people, when it's not working, they blame the format, and if somebody, think of
a glass, the information is in the glass, but the guy is not drinking it, or they'll
take it out, and it's not in the, when you're not an ODT, it's just not open in Microsoft
Office, then through the user, it's not Microsoft fault, it's the file format fault, so
there's a switch of backdoor, so no, all right, so we might, to make an obvious, that's
not our fault, and to, to, to, to say, look, it's unespecified here, are you, this does
not work, or we can say, this feature set is not implemented, we can name certain feature
set in the column and say, you only when you go through certain loops, jump through
it, you can really state that you implemented, I'm not sure why Max is there, but I believe
it's great, but who have a contract to, to, to, to implement them, and then the next
levers to, to, to, to, to get a contract to say, they have to function, to, to, to, to some
partners functionality like, then even like, change-ficking, they're not changed-tracking,
you know, and change-tracking is just, the list of changes, commits, right, they're only
difference between, get, let's say, get commits, and our change is like, get is, by line
based, and we would position something like, the third thing that is a table, these
in the column, right, and, and what we would do is, we, it's like a macro syntax, another
menu card, we transform it to our free office code, we don't have to hot implemented
in there, right, we just have to, to, to, to map it, compile it over. So what might happen
in the end, we just, load the test document, then, like, like, like, one user action, put
the user cursor here, like, insert column, we would do one API call equivalent to the
story change call, and then we can test the layout that's already been done, but it's
only on the standard level, and, like, the bullets have not moved, sometimes the bullets
won't run away, and I have no way to prove it, right, and I just want to be certain, and
the TC editors, we are keeping one version, we don't touch it, and we are very certain
that there's no break. I'm too afraid to switch all the, the latest version, because
I have no guarantee that my feature said that I need for specification works, and I
want you, I want us all, to have tests that I can guarantee regression tests, that
these layout features, what I'm, or the feature said, and place features that I'm using,
is still available, and this is, I think, one of the biggest properties, this kind
of trust, and then Arthur's layout test, there's some magic in there, then we save it,
and there it uses them, like, insert column, oh, really, the column is at the right place,
we can have the conformance test. And nowadays, you will conformant ODF application, if
you load it and save it, conformant, this can be in bite away, okay, it's, it's ridiculous.
So, thank you very much. I'm six seconds, so it's, that's the references, and I will
improve by argumentation, by discussion, this talk to seven, 70 minutes and be more, more
logical next time. Thank you very much.