Activity for BinWatson
-
BinWatson modified a comment on discussion Open Discussion
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ``` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
i have an question, that is openv2g is fully meet iso15118-2014 ?
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ``` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ``` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ``` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ``` but in the c file, openv2g define iso1CertificateChainType as below: ` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ` but in the c file, openv2g define iso1CertificateChainType as below: ` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: ` <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> ` but in the c file, openv2g define iso1CertificateChainType as below: ``` struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { struct { exi_string_character_t characters[iso1CertificateChainType_Id_CHARACTERS_SIZE];...
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> but in the c file, openv2g define iso1CertificateChainType as below: struct iso1CertificateChainType { /* attribute: Id {http://www.w3.org/2001/XMLSchema,ID} */ struct...
-
i have an question, that is openv2g is fully meet iso15118-2015 ?
-
Hi, In V2G_CI_MsgDataTypes.xsd define CertificateChainType as below: xsd <xs:complexType name="CertificateChainType"> <xs:sequence> <xs:element name="Certificate" type="certificateType" /> <xs:element name="SubCertificates" type="SubCertificatesType" minOccurs="0" /> </xs:sequence> <xs:attribute name="Id" type="xs:ID" /> </xs:complexType> but in the c file, openv2g define iso1CertificateChainType as below: c struct iso1CertificateChainType { /* attribute: Id {http://www.w3.org/2001/XMLSchema,ID}...
-
Hi, I may have fix this issue from https://www.w3.org/TR/exi-primer/#encoding: Note that AT(category) is accepted before AT(date) even though their order is reversed in the schema. This is because attributes in schema-informed grammars must be sorted lexicographically, first by local name and then by namespace URI. Attribute sorting reduces the number of options which, in turn, greatly simplifies grammar creation and improves compactness. Since this automaton does not include transitions on AT()...
-
Hi, I may have fix this issue from https://www.w3.org/TR/exi-primer/#encoding: Note that AT(category) is accepted before AT(date) even though their order is reversed in the schema. This is because attributes in schema-informed grammars must be sorted lexicographically, first by local name and then by namespace URI. Attribute sorting reduces the number of options which, in turn, greatly simplifies grammar creation and improves compactness. Since this automaton does not include transitions on AT(*)...
-
Hi, In the function encode_iso1ExiDocument ```c int encode_iso1ExiDocument(bitstream_t stream, struct iso1EXIDocument exiDoc) { errn = writeEXIHeader(stream); if(errn == 0) { /* DocContent[START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVChargeParameter), START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVSEChargeParameter), START_ELEMENT({urn:iso:15118:2:2013:MsgDataTypes}AC_EVSEStatus), START_ELEMENT({urn:iso:15118:2:2013:MsgBody}AuthorizationReq), START_ELEMENT({urn:iso:15118:2:2013:MsgBody}AuthorizationRes),...
1