hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.2 Threat, Vulnerability and Intelligence | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.2.1 Overview | A threat database is often a structured collection of information about threats to a system or organization, frequently used to identify and mitigate vulnerabilities. More narrowly, it could also refer to a specific security application that maintains a database of known threats, such as malware or malicious IP address... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.2.2 Application to Online Preventive Security to Protect Users | There are threat, vulnerability databases and intelligence sources that apply to online preventive security, which monitor and track threats and activities that can affect ordinary users [i.46], [i.47]. The types of threat information which can aid in protecting users, either directly or the services they use, include,... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3 Online Preventative Security by Design | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.1 Introduction | In the present document, Human-to-Human Online Preventive Security by design is a proactive approach to security and safety that integrates threat identification, risk assessment, and security controls directly into the design and development process of a service and/or a product. This includes putting user safety and ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.2 Secure by Design | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.2.1 Introduction | Secure by design is a principle of cybersecurity and systems engineering that requires systems to be built with security as a foundational property rather than as an afterthought. It is concerned with embedding protections at the earliest design stages of hardware, software, and services, so that security requirements ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.2.2 Principles | There are different design principles depending on the requirements for different types of organizations and the type of product or service. The following list gives examples of some of these principles, which are relevant to the present document: • Create responsibility for cybersecurity risks. Assign risk owners to b... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.3 Safety by Design | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.3.1 Introduction | Safety by design (online) is the process of designing an online platform to reduce the risk of harm to those who use it. Safety by design is preventative [i.56]. It considers user safety throughout the development of a service, rather than in response to harms that have occurred. By understanding how a platform's servi... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.3.2 Principles | There are a few key principles that can be implemented to create a safer online environment for people who use online services and platforms: • Users are not left to manage their own safety. Anyone who owns or manages a platform should take preventive steps to make sure their service reduces a user's exposure to harm. ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4 Privacy by Design | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.1 Introduction | The topics of "privacy by design" and "privacy by default" are related to data protection. The term "Privacy by Design" can mean "data protection through technology design." [i.57] This means there are different ways to achieve "privacy by design", which depends on what is meant by privacy itself. Privacy can be define... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2 Principles | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.1 Proactive not reactive; preventative not remedial | A proactive approach should be taken to data protection, anticipating privacy issues and risks before they occur, rather than waiting until after the fact. This does not just apply in the context of systems design; it involves developing a culture of 'privacy awareness' across an organization. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.2 Privacy as the default setting | When designing any system, service, product, or business practice, it should protect personal data automatically. With privacy built into the system, the individual does not have to take any steps to protect their data; their privacy remains intact without them having to do anything. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.3 Privacy embedded into design | Embed data protection into the design of any systems, services, products and business practices. It should ensure data protection forms part of the core functions of any system or service, meaning it becomes integral to these systems and services. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.4 Full functionality - positive sum, not zero sum | Also referred to as 'win-win', this principle is essentially about avoiding trade-offs, such as the belief that in any system or service, it is only possible to have privacy or security, not privacy and security. Instead, it should be looking to incorporate all legitimate objectives whilst ensuring compliance with all ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.5 End-to-end security - full lifecycle protection | Putting in place strong security measures from the beginning and extending this security throughout the 'data lifecycle', i.e. process the data securely and then destroy it securely when it is no longer needed. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.6 Visibility and transparency - keep it open | Ensuring that whatever business practice or technology is used operates according to its premises and objectives and is independently verifiable. It is also about ensuring visibility and transparency to individuals, such as making sure they know what data is processed and for what purpose(s) it is processed. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.4.2.7 Respect for user privacy - keep it user-centric | Keep the interests of individuals paramount in the design and implementation of any system or service, e.g. by offering strong privacy defaults, providing individuals with controls, and ensuring that appropriate notice is given. ETSI ETSI TR 104 137 V1.1.1 (2026-03) 41 6.3.5 Balancing the Different Requirements for Onl... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.5.1 Introduction | This clause discusses the balancing of the different requirements of online preventative security by design. The foundation required for online preventative security by design is making use of secure by design principles for a product or service. When it comes to privacy and safety, while some measures for them are com... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.5.2 Age Assurance | Online age assurance is a complex issue regarding privacy, access to content (often to stop children accessing age- inappropriate content) and data protection [i.65]. Verifying the age of an Internet user is hampered by the difficulty for the various stakeholders on the Internet to really know who the person is behind ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.5.3 Signing in or Up to Online Services | The type of personal information that users could provide to access platforms varies. Some online services offer access to content without the need to subscribe or create a profile, while others might require users to create a profile or verify certain information about themselves (for example, their name, age and cont... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.3.5.4 User Participation in Online Services | One way in which online service providers present content is by using content recommendation algorithms, or systems which aim to rank or return content that matches a user's perceived interests [i.67]. A large number of factors are used to do this, including information that constitutes the user's personal data. How al... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4 Education and Digital Literacy | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.1 Introduction | A key part of reducing and preventing harm is for users to have the knowledge to identify the potential risks and to be conscious of personal security while browsing, sharing or surfing the internet through different apps, services and devices they may use. This includes education that enables children (and parents), a... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.2 Ages 6 and under | The age at which digital literacy needs to start is rapidly diminishing. Children, as young as 1 year old, notice their parents' smartphone devices and are interested in pressing the touch-sensitive screens, where displays change rapidly. Before these very young children can read or write, they know how to turn on vari... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.3 Ages 7 to 11 | For this age group, children are becoming aware of themselves and group dynamics [i.70]. This is also an age when they may start to use the internet and access online content unsupervised. They should be taught through lessons and exercises. For example's passwords should not be shared with strangers. To start teaching... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.4 Ages 12 to 18 | This is an age when a child is becoming a teenager and will seek greater independence in their life and online. This can expose them to risk and harm; therefore, it is important to teach them to understand a range of ways to use technology safely, respectfully, responsibly and securely, including protecting their onlin... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.5 Ages 19 to 29 | This is an age where people are considered adults, and they are leaving their parents' home, getting jobs, going to university and are on the road, becoming independent adults. They should be aware of different types of online threats. These include malware, phishing attacks, and scams. Understanding how these threats ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.6 Ages 30 to 55 | Generally, this is a time when people have careers and families. Often, the companies will be responsible for ensuring their employees receive cybersecurity training, and the depth and knowledge will vary for a job's role and responsibilities. Training resources from organizations such as the UK's NCSC [i.72], [i.73] a... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.7 Ages 56 to 75 | Being online can make life easier for older people in many ways, but it also comes with the increased risk of scams and fraud. Online scams are becoming increasingly targeted at older, potentially less tech-savvy users, but they can protect themselves by knowing what to look out for and what to do if they suspect a sca... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.4.8 Ages 76 and Older | This is an age where the likelihood of cognitive decline increases, which can make people more vulnerable to being scammed or manipulated. A solution to this is for them to organize a mechanism, often a power of attorney, where a trusted (younger) family member, friend or solicitor/attorney has joint control or shared ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.5 Support for Users and Content Moderators | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.5.1 Introduction | Ensuring online preventative security for users of ICT requires companies and services to take a proactive approach in support of their users, but also the customer-facing staff, along with content moderators who are responsible for removing and preventing harmful content from spreading on social networks and services. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.5.2 Users | There are different ways and means to provide support to users, and part of this is the user experience and design. A part of this is clear signposting of users to report problems and to find the appropriate help and support. This should not be buried or in an unclear place within submenus or kept within categories whi... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 6.5.3 Content Moderators | Content moderators have become indispensable for online platforms' everyday operations. Their role is to remove reported and flagged harmful and illegal content. Companies have legal responsibilities for this under laws such as the UK Online Safety and the EU's Digital Services Act [i.75]. The turnover for content mode... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 7 Digital Evidence and Social Media | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 7.1 Overview | Given the massive amount of data available, social media has become one of the most fertile sources of information for background checks and intelligence gathering, as well as for various types of investigations, including criminal, regulatory, insurance and civil matters such as cyberbullying and defamation. However, ... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 7.2 Digital Evidence Gathering and Processing | |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 7.2.1 Overview | A key requirement for investigations, prosecutors and defenders is that the digital evidence collected and used is: i) is identical to the source; ii) is not altered; and iii) is traceable, leaving no room for questioning when the evidence is most needed. |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 7.2.2 Gathering and Processing | Computer documents, emails, text and instant messages, transactions, images and Internet histories are examples of information that can be gathered from electronic devices and used as evidence [i.41]. In addition, many mobile devices store information about the locations where the device travelled and when it was there... |
6415f963a1132f0296af8c07ba03f700 | 104 137 | 8 Conclusion | To begin to provide Human-to-Human Online Preventative Security requires an understanding of the digital devices and online services landscape used by the user. Along with the potential threats/harms that emerge from these, which affect the typical end user. This should provide a knowledge base to be able to implement ... |
b63685a584764961b7ae3e51726522bc | 104 081 | 1 Scope | The present document is the TTCN-3 migration guide. It contains the following information: • A list of TTCN-3 standard documents not supported in TTCN-3 V5.1.1. • The new structure of the TTCN-3 language specification V5.1.1. • A list of all language features in the new TTCN-3 core language document V5.1.1. • A list of... |
b63685a584764961b7ae3e51726522bc | 104 081 | 2 References | |
b63685a584764961b7ae3e51726522bc | 104 081 | 2.1 Normative references | Normative references are not applicable in the present document. |
b63685a584764961b7ae3e51726522bc | 104 081 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks in... |
b63685a584764961b7ae3e51726522bc | 104 081 | 3 Definition of terms, symbols and abbreviations | |
b63685a584764961b7ae3e51726522bc | 104 081 | 3.1 Terms | For the purposes of the present document, the following terms apply: actual parameter: value, expression, template or name reference (identifier) to be passed as parameter to the invoked entity (function, test case, altstep, etc.) as defined at the place of invoking automatic type: notation used in variable, constant a... |
b63685a584764961b7ae3e51726522bc | 104 081 | 3.2 Symbols | Void. |
b63685a584764961b7ae3e51726522bc | 104 081 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation 1 ATS Abstract Test Suite BNF Backus-Naur Form CR Change Request FIFO First In First Out IDL Interface Definition Language ITU-T International Telecommunication Union - Telecommunication standardization sector JS... |
b63685a584764961b7ae3e51726522bc | 104 081 | 4 Not supported TTCN-3 standards | After the major revision of the TTCN-3 language, the technical content of the following European Standards (ES) will not be supported any more: • ETSI ES 201 873-3 (V3.2.1) [i.17]. • ETSI ES 201 873-4 (V4.6.1) [i.18]. • ETSI ES 201 873-8 (V4.8.1) [i.19]. • ETSI ES 202 781 [i.8]. • ETSI ES 202 786 [i.12]. |
b63685a584764961b7ae3e51726522bc | 104 081 | 5 New structure of TTCN-3 language specifications | The major revision of the TTCN-3 language will consist of the following seven European Standards (ES): • ETSI ES 201 873-1 (V5.1.1): "TTCN-3 Core Language" will contain the definition of the core language features. • ETSI ES 201 873-12 (V5.1.1): "TTCN-3 Extensions" will contain selected features from TTCN-3 extensions ... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6 Features of new core language document | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.0 General | Features of the new core language standard ETSI ES 201 873-1 (V5.1.1) will include selected and modified features from the ETSI ES 201 873-1 (V4.17.1) [i.1]. For each of the following clauses references to base documents and clauses in base documents are provided. The order of the following clauses does not reflect the... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.1 Modification of major concepts affecting several clauses | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.1.0 General | There are two major concepts that will be changed: • the concept of fuzzy and lazy values and templates and lazy evaluation will be deleted; and • the concept of procedure-based communication will be moved to ETSI ES 201 873-12 (V5.1.1). The clauses affected by these modifications are listed below, and in the rest of t... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.1.1 Fuzzy and lazy values and templates and lazy evaluation | The concepts of Fuzzy and lazy values and templates (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1] and lazy evaluation (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be removed. This change will also have an effect on several additional clauses. Those parts of these clauses that are related to the concept... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.1.2 The concept of procedure-based communication | The whole concept of procedure-based communication (see clause 22.3 in ETSI ES 201 873-1 (V4.17.1) [i.1] will be moved to ETSI ES 201 873-12 (V5.1.1). This change will also have an effect on several additional clauses. Those parts of these clauses that are related to the concept of procedure-based communication will al... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.2 Definition of terms, symbols and abbreviations | The core language document ETSI ES 201 873-1 (V5.1.1) will include clauses on terms, symbols and definitions (see clause 3 in ETSI ES 201 873-1 (V4.17.1) [i.1]). The clauses on terms, symbols and definitions have to be adapted due to changed ETSI rules and due to changes of content in ETSI ES 201 873-1 (V5.1.1) in comp... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.3 Introduction | ETSI ES 201 873-1 (V5.1.1) will have an adapted "Introduction" (see clause 4 in ETSI ES 201 873-1 (V4.17.1) [i.1]). Clause 4.1 of ETSI ES 201 873-1 (V4.17.1) [i.1] will be deleted. References to other TTCN-3 documents will be revised or deleted. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4 Basic language elements | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4.0 General | ETSI ES 201 873-1 (V5.1.1) will include an adapted clause on "Basic language elements" (see clause 5.0 in ETSI ES 201 873-1 (V4.17.1) [i.1]). |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4.1 Identifiers and keywords | ETSI ES 201 873-1 (V5.1.1) will include an adapted clause on "Identifiers and keywords" (see clause 5.1 in ETSI ES 201 873-1 (V4.17.1) [i.1]). |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4.2 Scope rules | In addition to the scope rules defined in clause 5.2 of ETSI ES 201 873-1 (V4.17.1) [i.1], a "root scope" will be introduced. The root scope simplifies scoping rules for predefined functions (see clause C.1 to C.6 in ETSI ES 201 873-1 (V4.17.1) [i.1]) and Useful TTCN-3 types (see clause E.2 in ETSI ES 201 873-1 (V4.17.... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4.3 Ordering of language elements | The rules for the ordering of language elements (see clause 5.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.4.4 Parameterization | In comparison to clauses 5.4 and 5.5 in ETSI ES 201 873-1 (V4.17.1) [i.1] the clause on "Parameterization" in ETSI ES 201 873-1 (V5.1.1) will change in the following manner: • Parameterization concept will be only about dynamic parameterization in runtime, therefore Modulepar concept will be described in a different cl... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5 Types and values | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5.0 General | Clause 6 in ETSI ES 201 873-1 (V4.17.1) [i.1] will be re-structured (see clause 6.5.1 of the present document) and partially modified (see clauses 6.5.2 to 6.5.5 of the present document). The technical contents of clauses from ETSI ES 201 873-1 (V4.17.1) [i.1] which are not mentioned in this clause remain unchanged. ET... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5.2 Changes in "Basic types and values" | The following modifications are proposed in clause 6.1 of ETSI ES 201 873-1 (V4.17.1) [i.1]: • Values of types bitstring, hexstring and octetstring can be denoted not only by the uppercase 'B, 'H, 'O characters, but their lowercase equivalents 'b, 'h, 'o will also be enabled, like: '0101'b, 'ABCD'h and 'ABCD'o. • The d... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5.3 Changes in Records and sets of single types and Arrays | For the Record and Set of elements of the same type (see clause 6.2.3 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the rules describing how many elements a partially initialized record of/set of has, and what happens if a value on the right-hand side of an assignment has different number of elements than that of on the left-h... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5.4 Changes in Port types | Since procedure-based communication will be moved to ETSI ES 201 873-12 (V5.1.1), in the Core Language only the message-based port type will remain. Therefore, in message-based port type definitions the keyword message will become optional. It is kept for backward compatibility. The following two definitions will be id... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.5.5 Changes in Automatic type | The concept of Automatic type (see clause 6.5 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1) without the following exception that will remain in ETSI ES 201 873-1 (V5.1.1): • The automatic typing will only be allowed only if on the right-hand side of the assignment there is a referen... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.6 Expressions | In Expressions (see clause 7 in ETSI ES 201 873-1 (V4.17.1) [i.1]) following change is proposed: • Shift and rotate operators will be moved to ETSI ES 201 873-12 (V5.1.1). |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.7 Modules | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.7.0 General | 6. |
b63685a584764961b7ae3e51726522bc | 104 081 | 7.0 General | Apart from clause 8.2.3 "Importing from modules" in ETSI ES 201 873-1 (V4.17.1) [i.1] the technical contents of clause 8 in ETSI ES 201 873-1 (V4.17.1) [i.1] remain unchanged. Especially: • Transfer syntax of TTCN-3 modules will be UTF-8. • The language keyword remains. The list of language strings will be updated. • D... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.7.1 Changes in Importing from modules | The technical content of clause 8.2.3 "Importing from modules" in ETSI ES 201 873-1 (V4.17.1) [i.1] will be changed in the following manner: • Only import all will be supported. • The rules on import of attributes will be simplified: - If an imported definition has attributes (defined by means of a with statement) then... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.8 Port types, component types and test configurations | The technical contents of clause 9 in in ETSI ES 201 873-1 (V4.17.1) [i.1] will remain unchanged for message-based communication. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.9 Declaring constants | The technical contents of clause 10 in ETSI ES 201 873-1 (V4.17.1) [i.1] remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.10 Declaring variables | The technical contents of clause 11 in ETSI ES 201 873-1 (V4.17.1) [i.1] remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.11 Declaring timers | The technical contents of clause 12 in ETSI ES 201 873-1 (V4.17.1) [i.1] remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.12 Declaring messages | The technical contents of clause 13 in ETSI ES 201 873-1 (V4.17.1) [i.1] remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.13 Declaring templates | The proposed modifications related to templates (see clause 15 in ETSI ES 201 873-1 (V4.17.1) [i.1]) are the following: • Templates without a (possibly empty) parameter list are static templates. They will be evaluated only once, at the place of their declaration. NOTE 1: A static template retains the value was assigne... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.14 Functions, altsteps and testcases | In Functions, altsteps and testcases (see clause 16 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the following change is proposed: • The not-implemented function will be moved to ETSI ES 201 873-12 (V5.1.1). Apart from the changes described above, the technical contents of clause 16 will remain unchanged. ETSI ETSI TR 104 081... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.15 Basic program statements | In Basic program statements (see clauses 18 and 19 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the following changes are proposed: • The goto and label functionality is moved to ETSI ES 201 873-12 (V5.1.1). • Range based loop allow only locally defined iterator, and it will iterate over the possible uninitialized elements (r... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.16 Statements and operations for alternative behaviours | |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.16.0 General | In clause 20 in ETSI ES 201 873-1 (V4.17.1) [i.1] the following changes will be made: • Usage and semantics of the interleave statement will be simplified (see clause 6.5.1). This is a backward- incompatible change. Apart from these changes the concepts described in clauses 20.0 to 20.3 in ETSI ES 201 873-1 (V4.17.1) [... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.16.1 The Interleave statement | For the interleave statement (clause 20.4 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the following semantical simplification is proposed: • Complexity is introduced into the interleave statement by allowing reception statements in statement blocks of alternatives in interleave statements. Each reception statement adds to th... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.17 Configuration operations | For clause 21 in ETSI ES 201 873-1 (V4.17.1) [i.1] the following change is proposed: • The Call test component behaviour operation (see clause 21.3.10 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will be moved to ETSI ES 201 873-12 (V5.1.1). Apart from the change described above, the technical contents of clause 21 will remai... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.18 Communication Operations | In Communication Operations (see clause 22 in ETSI ES 201 873-1 (V4.17.1) [i.1]), the following changes are planned: • The trigger operation will be deleted. This is a backward-incompatible change. • The syntax of the check operation will be simplified, the receive keyword will be optional: - ( check(receive(...)) is t... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.19 Timer Operations | The concept of timer and timer operations (see clause 23 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will not be changed. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.20 Test Verdict Operations | The concept of test verdicts and test verdict operations (see clause 24 in ETSI ES 201 873-1 (V4.17.1) [i.1]) will not be changed. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.21 External actions | For external actions (see clause 25 in ETSI ES 201 873-1 (V4.17.1) [i.1]) the following change is proposed: • The semantics of external actions will not change, but external action will become a predefined function and will be moved to that clause. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.22 Module control | The technical contents of clause 26 in ETSI ES 201 873-1 (V4.17.1) [i.1] will remain unchanged. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.23 Attributes | For clause 27 "Attributes" in ETSI ES 201 873-1 (V4.17.1) [i.1] the following changes are proposed: • Withdrawal of the display attribute (including dynamic configuration). • Removal of code-block-level attributes referencing inner definitions. Attributes that are declared on a code block but bound to individual defini... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.24 Annex A (normative): BNF and static semantics | The core language document ETSI ES 201 873-1 (V5.1.1) will include an annex with BNF rules and static semantics descriptions. |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.25 Annex B (normative): Matching values | The technical contents of Annex B in ETSI ES 201 873-1 (V4.17.1) [i.1] will remain unchanged. The contents of this annex may be merged with the corresponding clause in ETSI ES 201 873-1 (V5.1.1). 6.26 Annex C (normative): Predefined TTCN‑3 functions For clause Annex C in ETSI ES 201 873-1 (V4.17.1) [i.1] the following ... |
b63685a584764961b7ae3e51726522bc | 104 081 | 6.27 Annex D (normative): Preprocessing macros | The technical contents of Annex D in ETSI ES 201 873-1 (V4.17.1) [i.1] will remain unchanged. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.