Re: [taste-users] ASN.1 to SQL for C-ITS

[Maxime.Perrotin@xxxxxxx]

Dear Karl,

Thanks for your
interest!  Here are answers to your questions:

The current version
does not support OICs, indeed. We had no request for them so far, and since
it is quite a complex structure, we have to be careful - thinking of validation
and maintenance, it can make the parser very complex.

Regarding the
EXT_MARK error, could it be that you forgot to remove the trailing comma
when you deleted the "..." extension mark ?

There is one other
issue with this grammar, the fact that it contains multiple definition
of the same INTEGER constant.
For example :

   
HazardousLocation-AnimalOnTheRoadSubCauseCode ::= INTEGER {
   
    unavailable(0),

This name (unavailable)
is also defined here:
   
CurvatureValue ::= INTEGER {
   
    unavailable(30001)

This is currently
detected as an error, because the code generator generates one constant
per named integers, and does not apply any renaming policy.
With the ENUMERATED
type, this is resolved by adding a prefix to the constants (TYPE_enumerant).


I have added a
ticket in our bugtrack about this one (https://taste.tuxfamily.org/mantis/view.php?id=411).
We should probably manage it the same way for integer constants as we do
for ENUMERATED values.

Kind regards,
Maxime




ESA
- European Space Agency

Maxime Perrotin
Proba-3 Plaftorm & Payload Software Engineer
TASTE
Lead Engineer
System, Software and Technology Department

ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
maxime.perrotin@xxxxxxx
| www.esa.int
T +31 71 565 4923 | F +31 71 565 5420 





From:
       Karl
Svantorp <Karl.Svantorp@xxxxxxxxx>
To:
       "taste-users@xxxxxxxxxxxxxxxxxxx"
<taste-users@xxxxxxxxxxxxxxxxxxx>
Cc:
       Bjørn
Magne Elnes <Bjorn.Elnes@xxxxxxxxx>
Date:
       18/01/2018
14:11
Subject:
       [taste-users]
ASN.1 to SQL for C-ITS

---

Hi TASTE community!

We are trying to use TASTE to make an SQL database from an ISO stardard on C-ITS systems, the specific ASN.1 can be found here: http://standards.iso.org/iso/ts/18750/TS%2018750%20ASN.1%20repository

This ASN.1 uses "Information Object Classes" ( https://en.wikipedia.org/wiki/Information_Object_Class_(ASN.1) ), that seem quite suited for SQL mapping according to that wikipedia article. However, when i try follow the wiki on SQL mapping, either using -toSQL or -toPython, I get this error:

does the TASTE ASN.1 compiler not support IOCs? Is there another way of turning that ASN.1 into a database with TASTE?

Further, we were hoping to use TASTE to make a ASN.1 PER encoder and decoder, preferably in Python or C. The ASN.1 for one type of message we receive can be downloaded here: http://asn1-playground.oss.com/Standards/ITS%20CAM%20v1.3.2.asn

When trying to map this to python we get this error on constraints: (only had the -toSQL picture on hand, but same for python)

When trying to map this to python we get this error on constraints: (only had the -toSQL picture on hand, but same for python)

This is fair and makes sense, but when I then tried to remove the extensions from the ASN.1, I get this error:

with EXT_MARK meaning extension marker "..." in the ASN1SCC code I think. So now asn1scc requires the unsupported extensions? I'm confused. How did asn1scc even know there was supposed to be an extension there?

Thanks a lot for any help or insight

Karl Svantorp

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.