Skip to content

Commit 9beaf0f

Browse files
authored
README: reword and fix errors (#85)
Signed-off-by: Moritz Barsnick <[email protected]>
1 parent 3470fa3 commit 9beaf0f

File tree

1 file changed

+26
-26
lines changed

1 file changed

+26
-26
lines changed

README.md

Lines changed: 26 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# cbExiGen - The V2GTP EXI codec generator
22

3-
cbExiGen is a code generator which creates the codec library **cbV2G** for
3+
cbExiGen is a code generator that creates the codec library **cbV2G** for
44
encoding and decoding messages using the Vehicle To Grid Transport Protocol
5-
(V2GTP). It is capable of processing XML schemas as defined in the standards
6-
DIN 70121, ISO 15118-2 and ISO 15118-20, and derivates of these. It creates
7-
a library capable of encoding and decoding the complete EXI message set of
8-
the defined protocols.
5+
(V2GTP). It is capable of processing XML schemas as defined in the
6+
standards DIN 70121, ISO 15118-2, and ISO 15118-20, as well as derivatives
7+
of these. It creates a library capable of encoding and decoding the
8+
complete EXI message set of the defined protocols.
99

1010
---
1111
## :exclamation: Call for ISO 15118-20 EXI streams :exclamation:
@@ -27,32 +27,32 @@ Thank you!
2727
## What
2828

2929
V2GTP is a protocol for "vehicle to grid" communication. It is used for
30-
control of power flow in charging electrical vehicles (EVs), for the
31-
communication between EV and EVSE (electical vehicle supply equipment, i.e.
32-
charging station).
30+
controlling power flow in charging electric vehicles (EVs) and for
31+
communication between EVs and EVSEs (electric vehicle supply equipment, i.e.
32+
charging stations).
3333

34-
The protocol is originally defined in the global standard ISO 15118. Its
35-
popular implementations are
34+
The protocol is originally defined in the global standard ISO 15118.
35+
Popular implementations of this protocol include
3636
[DIN 70121](https://www.beuth.de/en/technical-rule/din-spec-70121/224350045),
3737
[ISO 15118-2](https://www.iso.org/standard/55366.html), and
3838
[ISO 15118-20](https://www.iso.org/standard/77845.html).
3939

40-
The protocol is XML based, with the messages representable as XML, strictly
41-
defined using XML schemas. The message transfer uses EXI ([Efficient XML
42-
Interchange](http://www.w3.org/TR/exi/)), a compact binary representation of
43-
XML.
44-
45-
The codec is not implemented directly, but using this code generator,
46-
because the standards are evolving, yet share common ground. A code
47-
generator allows modifying a schema e.g. to implement experimental
48-
extensions, and allows creating a codec for future standard variants. The
49-
generator also aids in optimizing the code, by improving the EXI grammar
50-
evaluation, and by implementing configurations for limited protocol coverage
51-
for reduced code size, without the need to manually modify many places
52-
within the complete library.
53-
54-
The code generator takes the standards' XML schema files as input, analyzes
55-
them, and creates the appropriate codec representation.
40+
The protocol is XML-based, with the messages representable as XML and
41+
strictly defined using XML schemas. The message transfer uses EXI
42+
([Efficient XML Interchange](http://www.w3.org/TR/exi/)), a compact binary
43+
representation of XML.
44+
45+
The codec is not implemented directly but is generated using this code
46+
generator because the standards are evolving while sharing common ground. A
47+
code generator allows for modifying a schema, for example to implement
48+
experimental extensions, and enables the creation of a codec for future
49+
standard variants. The generator also aids in optimizing the code by
50+
improving the EXI grammar evaluation and implementing configurations for
51+
limited protocol coverage to reduce code size without the need for manual
52+
modifications in multiple places within the library.
53+
54+
The code generator takes the XML schema files of the standards as input,
55+
analyzes them, and creates the appropriate codec representation.
5656

5757
This codec created by this code generator is designed to take a data
5858
representation of the message data - e.g. as structs or classes - and

0 commit comments

Comments
 (0)