The Internet Engineering Task Force (IETF) is the premier standards development organisation for the Internet. One of the ways that their work finds its way to the public in general and to engineers and techninians in particular is via documents, specifically RFCs (RFC stood originally for Requests For Comments). Each one is numbered and they describe fundamentals of the Internet, with RFCs ranging from core building blocks such as TCP/IP:
protocols that you and I deal with more closely and regularly, such as:
- RFC2616 HTTP/1.1
as well as somewhat more "unusual" protocols, such as RFC1149, and even non-protocol defining RFCs such as:
- RFC2119 Key words for use in RFCs to Indicate Requirement Levels
which is as wonderful as it is useful and meta.
RFCs remain essential to how and why things work.
In CDS modelling there are many built-in types, such as Boolean, Integer, DateTime and more. One of these built-in types is UUID, the type behind the common aspect cuid, which is defined thus:
aspect cuid {
key ID : UUID;
}This built-in type UUID is compliant with a specific standard described in an RFC document. What is that RFC document's number?
This is a question from the June Developer Challenge on CAP Knowledge. And don't forget: always submit your answer as a hash, on its own - read the Taking part section of the intro post for more info. At the end of today, this question will be updated with links to further reading on this topic.
Further info:
- The Core / Built-in Types topic in Capire has the list of types and links to reuse types and aspects (which includes
cuid) as well as how the types relate to e.g. OData and HANA types.
Bluesky
