Talk:Abstract Syntax Notation One
|This article is of interest to the following WikiProjects:|
|A Wikipedia contributor, ITU-T (talk · contribs), may be personally or professionally connected to the subject of this article. This user's editing has included contributions to this article. Relevant guidelines include Wikipedia:Conflict of interest, Wikipedia:Autobiography, and Wikipedia:Neutral point of view.|
- 1 Captial letters
- 2 ASN.1 versus text encodings
- 3 Website advertising in the external links?
- 4 A small error in DER encoding example?
- 5 DER example -- VisibleString tag wrong?
- 6 KISS
- 7 Proposal for edits
- 7.1 Abstract Syntax Notation One
- 7.1.1 ASN.1 in transfer
- 7.1.2 Example
- 7.1.3 ASN.1 versus other data structure definition schemes
- 7.1.4 Encoding Control Notation (ECN)
- 7.1.5 Using ASN.1 in practice
- 7.1.6 Standards
- 7.1.7 See also
- 7.1.8 Notes
- 7.1.9 References
- 7.1.10 External links
- 7.2 Yes!
- 7.1 Abstract Syntax Notation One
- 8 Example encoded in PER (unaligned)
- 9 Propose to add link to Online ASN.1 encoder/decoder of 3GPP messages
Why the capital letters in the article's title while lower-case is used in the first sentence? Which is correct? (Wikipedia articles conventionally do not capitalize words in article titles unless they would otherwise be capitalized, except that the first letter is case-insensitive and always gets rendered as a capital.) Michael Hardy 20:26, 13 Sep 2004 (UTC)
- I spotted this in the page history, 02:18, 26 January 2006 Mulad m (moved Abstract syntax notation one to Abstract Syntax Notation One: Being a standard, this should be uppercase)--Kelby 23:19, 8 June 2006 (UTC)
More accurately, this is a proper name for a particular standard, not a general term. Proper names can be capitalized in English. Sources almost always do in this case. W Nowicki (talk) 21:40, 11 July 2011 (UTC)
ASN.1 versus text encodings
This recently added section is problematic as there are multiple ASN.1 encoding rules which produce textual output, such as GSER. Additionally one doesn't need a compiler to produce encoders/decoders for binary encodings, and one may use a compiler to produce encoders/decovers for textual encodings. I recommend this section be deleted or significantly rewritten. Kdz 20:57, 25 February 2006 (UTC)
- Agreed. GSER is not a good example as it's primarily meant merely for inputting/representing data by/for the user, but XER entirely qualifies as a textual representation of ASN.1. -- intgr 22:01, 25 February 2006 (UTC)
I tried to fix this and be more complete and consise, as I think the text-vs-binary debate in an important point in the real world of protocol design. Perhaps this discussion should be somewhere else, but it is often associated with ASN.1.
There are 6 external links that all lead to pages on http://asn1.elibel.tm.fr/ This number of links make it feel like advertising for the website. I suggest there should be just a single link to the website. --Kelby 23:27, 8 June 2006 (UTC)
- Agreed. I removed all the links except for one that links to the homepage. -- intgr 12:41, 12 June 2006 (UTC)
A small error in DER encoding example?
Shouldn't the length of the "Anybody there?" string be 14 instead of 13?
- Note that all values are in hexadecimal, so we have: 1 (length of integer tag) + 1 (length of integer length) + 1 (length of integer value) + 1 (length of string tag) + 1 (length of string length) + 0e (length of string value) = 13. Rasmus (talk) 20:06, 18 June 2006 (UTC)
DER example -- VisibleString tag wrong?
The example says:
04 -- tag indicating VisibleString 0e -- length in octets
However, in X.680 section 37.1, VisibleString is listed as having universal tag 26 (0x1A). It's true that all strings are B/C/DER encoded like an OCTET STRING (universal tag 4), but it seems the encoded tag should still be 0x1A, see for instance the example of X.690 section 220.127.116.11.
- The SEQUENCE tag should be 0x30, the VisibleString tag should be 0x1A. Verified with an ASN.1 compiler. So, there were two wrong tags, not one.
- -- Vlm 20 September 2006
Or Keep It Simple, Stupid! Example section is meant for people who completely don't understand what ASN.1 is about. And not for people who want to learn how unaligned PER is "better" than XER. I've noticed a trend to overly complicate this section.
So be gentle and don't throw all information at once. Step by step, step by step. Simple language. One new term per paragraph :)
--Kubanczyk 23:02, 18 December 2006 (UTC)
Proposal for edits
Please find below a proposal for edits to the current article. There are minor changes in text, links and layout, but also a new paragraph - Encoding Control Notation (ECN).
Feel free to contact us regarding any of the changes made. If there are no comments within the next days the edits are considered supported and we will publish the revised article. ITU-T 11:43, 10 December 2007 (UTC)
- Thanks a lot for your thoughts and support, we will post the edits. “Using the ASN.1 in practice” could indeed be expanded. Please add what you find valuable and do not hesitate to contact us and discuss the article further. ITU-T 11:05, 17 December 2007 (UTC)
Example encoded in PER (unaligned)
The text says "122 bits (less than 16 octets)" then shows 16 hexadecimal pairs which would be 16 full octets or 128 bits. There is an example at the end showing 17 octets, but none has the highest bit set. If these are septets, that's 119 bits. I notice that the first three pairs don't change between the two examples, so if I read the second example as three octets followed by 14 septets that makes 122, but the text should lead me to a 122 bit explanation. Randall Bart Talk 17:53, 12 January 2013 (UTC)
Online ASN.1 encoder/decoder A free tool that encodes/decodes ASN.1 messages defined by 3GPP. The link: http://3gpp-message-analyser.com/