hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.1.2 Multi-stream media synchronization | The requirements of clause 10.2.8 of ETSI TS 102 796 [1] that relate to broadband streams shall apply to streams delivered by MSE. In table 14 of ETSI TS 102 796 [1], combinations 1 and 4 shall also be supported for audio delivered by MSE using the timeline for HTML media elements defined in clause 13.1.2. Table 1 show... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.1.3 Memory for MSE | Terminals shall have sufficient memory to load and run a broadcast-related application that does the following: • Creates a video/broadcast object and connects it to a running HD broadcast using bindToCurrentChannel. • While broadcast video is playing and without the broadcast video or audio or subtitles being disturbe... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.1.4 AV Sync | Multiple adverts can be played consecutively using a single video element by appending their data consecutively to the SourceBuffer(s) used by that video element. As noted in clause 4.2.5, the audio and video components of broadband media may not end at precisely the same moment. This could result in AV Sync drifting o... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2 Media switching | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2.1 Advert delivery | Terminals shall support switching from broadcast to any of the following and back to the broadcast. Terminals shall also support switching between any combinations of the following. For each of the following, terminals shall support switching at a defined time (timelineSelector from clause 8.1.3 is not null) and switch... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2.2 Broadcast formats | For each of the following combinations of broadcast video and audio codec that the terminal supports, it shall be able to switch to broadband-delivered content (MSE, DASH, non-adaptive HTTP streaming) encoded using AVC and HE-AAC (with and without subtitles) and return to the broadcast: • MPEG-2 SD video + MPEG-1 layer... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2.3 Timelines | Timelines shall be supported as follows: • When originalMediaObject is a video/broadcast object, PTS ("urn:dvb:css:timeline:pts") and TEMI ("urn:dvb:css:timeline:temi:<component_tag>:<timeline_id>") shall be supported. For more details, see ETSI TS 103 286-2 [i.5] as referenced from ETSI TS 102 796 [1]. • On terminals ... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2.4 Switch preparation deadline | Terminals may require that the switchMediaPresentation method be called some time in advance of the time at which the switch is to happen - the switch preparation deadline. If terminals require this then they shall not require more than 2 seconds advance notice. NOTE 1: It is recommended that broadcasters should call t... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.2.5 Audio considerations | Changes of the audio output format (codec, channel configuration, sampling rate, altered frame timing) may create discontinuities on a digital audio output interface. In order to mitigate audio artefacts from discontinuities on a receiver connected through a digital output, it is strongly recommended that the output fo... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.3 Minimum terminal capabilities | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.3.1 General | Implementations of the present document shall indicate this by the addition of one or more <ta> elements in the XML device capabilities as defined in clause A.2.1. The version attribute shall indicate "1.1.1" for implementations of the present document. Zero, one or more profile elements shall be present as children of... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 10.4 Single and multiple video and audio decoders | The present document can be implemented on terminals with only a single video decoder and a single audio decoder as well as terminals with more than one of each. Annex F provides some background on scenarios for how these can be used. The following shall apply to terminals with only a single video decoder and a single ... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 11 Security | The present document defines extensions to ETSI TS 102 796 [1] that provide additional facilities that can be used by applications. The fundamental aspects of security are inherited from that specification - application signalling, application transport and the use of TLS for security over broadband connections. The ex... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 12 Privacy | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 12.1 General | Privacy in the context of targeted advertising in general is an important subject and in the context of broadcast television possibly even more so, given that a broadcast-related autostart DAS application may start without the viewer being aware (e.g. in the absence of a red button). The present document has been devel... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 12.2 Cookies | In the context of the DAS application, a broadcaster's responsibility includes ensuring data held locally in persistent cookies or local storage can be removed should the viewer wish. Note that, while persistent cookies cannot directly be removed by an application, the expiry date may be modified to be in the past thus... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 13 Media Synchronization | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 13.1 MSE | |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 13.1.1 Use of media elements whose source is MSE | In all places where an application is permitted to use an HTML5 media element in Media Synchronization, it shall be able to use an HTML5 media element whose source is an MSE SourceBuffer as an alternative to an HTML5 media element whose source is a URL. |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 13.1.2 Timeline Selector for media timeline of media elements | The Timeline Selector urn:hbbtv:sync:timeline:html-media-timeline shall refer to the media timeline of the media resource of an HTML media element as defined in clause 4.8.12.6 of the HTML specification [3]. NOTE 1: The timeline specified by this Timeline Selector can be used with an HTML media element in the situation... |
9b9c5899d6b8d1b3eedcb9a7940d7e64 | 103 736-1 | 14 Companion screens | The present document does not introduce any additional requirements beyond those in ETSI TS 102 796 [1]. ETSI ETSI TS 103 736-1 V1.1.1 (2020-06) 41 Annex A (normative): Web and OIPF specification profile A.1 Detailed section-by-section definition for volume 5 Table A.1 defines clauses of the OIPF DAE specification [2] ... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 1 Scope | The present document specifies the IoT communication aspects for Smart Lifts (i.e. the Smart Lift System). It defines the elements involved in such communications and their relations, from the central cloud level to the Smart Lift installations, including the integration with administrative information, the integration... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 2 References | |
522d429a3fccd3c4723aaf195795eace | 103 735 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. 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 i... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 3 Definition of terms, symbols and abbreviations | |
522d429a3fccd3c4723aaf195795eace | 103 735 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [2] and ETSI TS 103 264 [1] apply. |
522d429a3fccd3c4723aaf195795eace | 103 735 | 3.2 Symbols | Void. |
522d429a3fccd3c4723aaf195795eace | 103 735 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADN Application Dedicated Node AE Application Entity API Application programming interface ASN Application Service Node ETSI ETSI TS 103 735 V1.1.2 (2021-07) 8 BCS Bidirectional Communication System CSE Capability Service Entity IoT Internet o... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 4 User roles and use cases | |
522d429a3fccd3c4723aaf195795eace | 103 735 | 4.1 Overview of user roles | In the Smart Lift IoT System there are several types of user roles and there are three main categories: • The users of the lift (the passengers) that could have different need. • The people and companies that work on the lift market. • The owner of the building or administrator of group of building. |
522d429a3fccd3c4723aaf195795eace | 103 735 | 4.2 Description of user roles | Building owner The owner of the building or a group of buildings. Maintenance companies The companies that are in charge of the maintenance of the lifts, with the organization to manage every problem that could arise on the lift. Maintenance technicians The technicians of the maintenance companies, they are the people ... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 4.3 Use cases | The Smart Lift IoT system is designed to be futureproof respect to service innovation and evolution. Some examples are provided in clause 6 of ETSI TR 103 546 [i.3] and are a non-exhaustive list of the ones considered during the present document development. 5 Smart Lift System IoT architecture and supported configurat... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 5.1 Smart Lift System IoT architecture | The Smart Lift System is the composition of the lift installations and the entities that supports their remote communication and control within a Smart Lift administrative domain. The Smart Lift administrative domain corresponds to a provider of services for the Smart Lifts: a consortium, an association, a maintenance ... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 5.2 Supported deployment configurations and numerosity | As described in clause 5.1, the concept of a SLI in the SLS system corresponds to a single lift, with all its elements. The major element in a SLI, from the point of view of the IoT communication aspects, is the Smart Lift Edge Control Unit that is typically associated with the control panel of the lift. As an example,... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 5.4 Security, privacy and cybersecurity support | The security of the Smart Lift System is assured by the communication framework (the oneM2M system) referenced in clause 8. The oneM2M system provides a complete solution for modular security (communication, identification, etc.) and flexible granularity of data access control (access control via identifiers, roles, to... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 5.5 Management support | The management of the components of the Smart Lift System, in particular the remoted components at the edges of the systems, is assured by the communication framework (the oneM2M system) referenced in clause 8, with specific attention to ETSI TS 118 106 [8] (oneM2M TS-006; Management Enablement (BBF)) and ETSI TS 118 1... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.1 Introduction | Clause 6 contains the data to be exchanged by Smart Lift System across its components and with external components from other systems. It has been developed to support the lift industry with a standard capable to provide seamless interoperability among the different lift solution, to assure support for sector specific ... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.2 Smart Lift installation identification | The SLECU, the SLEC, the SLCS and the SLIG, as well the Smart Lift Applications, shall be identified by their respective oneM2M identifiers, i.e. the AE and CSE identifiers; the SLI and the SLI group identifiers are specified in Table 6.2-1. Table 6.2-1: Information group name: SLIIdentification Information Type SLI / ... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.3 Administrative Information | Table 6.3-1: Information group name: AdministrativeInformation Information Type SLIG SLAU SLCS Description liftManufacturingCompanyRepre sentitive String (max 64 characters) M M M E.g. the local representative of the manufacturing company. See note 1. liftInstallerCompany String (max 64 characters) M M M E.g. the repre... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.4 Smart Lift Installation | Table 6.4-1: Information group name: SLInstallation Information Type SLI SLIG SLCS Description technologyUsed It is defined by one of the following String values: • ELECTRICAL • ELECTRICAL MRL • HYDRAULIC • HYDRAULIC MRL • OTHER M M M It provides an indication of the principle of functioning of the elevator. See note 1... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.5 Smart Lift General Configuration | Table 6.5-1: Information group name: SLConfiguration Information Type SLI SLIG SLCS Description carServicesDescription Array (range 0..carServices) of type typeCarService M M M It provides configuration of the lift at a given service (the correspondent car stop and door opening configuration). floorNames Array (range 0... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.6 General Signals | Table 6.6-1: Information group name: GeneralSignals Information Type SLI SLIG SLCS Description currentCarStop Integer (range 0..9999) M MWA M It indicates the car stop; it is used to define a specific carServicesDescription and as index in floorNames See note 1. currentCarService Integer (range 0..9999) M MWA M Index o... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.7 Status Signals | Table 6.7-1: Information group name: StatusSignals Information Type SLI SLIG SLCS Description outOfService Boolean (TRUE/FALSE) M MWA M TRUE when the lift is in out of service state. See note 1. inspectionOperation Boolean (TRUE/FALSE) M MWA M TRUE when the lift is subject to inspection operation by the maintenance tec... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.8 Statistic Signals | Table 6.8-1: Information group name: StatisticSignals Information Type SLI SLIG SLCS Description numberOfCalls Integer M MWA M Total counter from the last reset. See note 1. upwardTravels Integer M MWA M Total counter from the last reset. See note 1. downwardTravels Integer M MWA M Total counter from the last reset. Se... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.9 Fault Signals | Table 6.9-1: Information group name: FaultSignals Information Type SLI SLIG SLCS Description faults Array of Fault (max 9 999 elements) M MWA M The index indicates the sequence of the faults from the last reset. See note 1. floodInTheWell Boolean (TRUE/FALSE) M MWA M TRUE if a flood has been detected (not present in EN... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.10 General Commands | Table 6.10-1: Information group name: GeneralCommands Information Type SLI SLIG SLCS Description sendCarToSpecificService It is defined by one of the following String values: 0.. carServices READY M (the execution of the command may be inhibited in some installations) MWA M 0..n to call the car to a specific service. T... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.11 Real Time Mode Signals | Table 6.11-1: Information group name: RTMSignals Information Type SLI SLIG SLCS Description realTimeModeSignals String O O M This string is deigned to contain information that are not specified in detail in present document, The format shall be accordingly to the realTimeMode Descriptor. ETSI ETSI TS 103 735 V1.1.2 (20... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.12 Power Supply Signals | Table 6.12-1: Information group name: PowerSupplySignals Information Type SLI SLIG SLCS Description emergencyBatteryPower It is defined by one of the following String values: GOOD WARN CRITICAL INSUFFICIENT M MWA M GOOD: the battery power is in good operating conditions; WARN: The Battery is functionally in operating c... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.13 Bidirectional Communication System Configuration | Table 6.13-1: Information group name: BCSConfiguration Information Type SLI SLIG SLCS Description homeNetworkOperator MCC-MNC as defined in Recommendation ITU-T E.212 [33] (5 Digits) M MWA M The allocation of MCC-MNC codes in the different nations and regions is officially traced by ITU-T that releases periodic updates... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.14 Bidirectional communication system alarms | Table 6.14-1: Information group name: BCSAlarms Information Type SLI SLIG SLCS Description alarmInTheCar Boolean (TRUE/FALSE) M MWA M TRUE when the alarm in the car has been activated. Reset to FALSE when the alarm is closed. alarmVoiceCommunicationA ctivated Boolean (TRUE/FALSE) M MWA M TRUE when alarm voice communica... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 6.15 Bidirectional Communication System Signals | Table 6.15-1: Information group name: BCSSignals Information Type SLI SLIG SLCS Description timeOfLastPeriodicTest72h Attempt String representing time according to ISO 8601 [24] Complete Representation Basic Format as described here: YYYYMMDDThhmmss,ssssss The String shall not include the Time Zone: Time shall be inter... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 7 Semantic interoperability | The Smart lift Systems semantic interoperability is based on oneM2M TS 0033 [20], ETSI TS 118 112 [11] and ETSI TS 118 130 [18]. In this context the SAREF standard suite becomes particularly relevant as specified in ETSI TS 103 264 [1], ETSI TS 103 548 [23] and (ETSI TS 103 410 [22] parts 1-10: SAREF Extensions). A ded... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 8 Smart Lifts Communication framework | |
522d429a3fccd3c4723aaf195795eace | 103 735 | 8.1 Introduction | The oneM2M specifications define a framework for the communication and sharing of information. The major paradigm is often referred to as "store & share". De facto any object and information is mapped to resources that is shared, discovered and accessed via a resource-oriented architecture and its related protocols. IP... |
522d429a3fccd3c4723aaf195795eace | 103 735 | 8.2 Smart Lift Communication Framework | The Communication Framework for Smart Lifts shall comply with the following specifications: NOTE: For oneM2M specifications for which the transposition process by ETSI is still ongoing at the date of the present document, only the oneM2M number is provided. • ETSI TS 118 111 (oneM2M TS-0011) [2]. • ETSI TS 118 102 (one... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 1 Scope | The present document defines the development framework for the SAREF ontology [1] and its extensions (referred to in a general way in the present document as SAREF projects) based on the ETSI forge. The development framework defines the different workflows to be followed for new SAREF project versions, SAREF project ve... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 2 References | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. 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 i... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 3 Definition of terms, symbols and abbreviations | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 3.1 Terms | For the purposes of the present document, the following terms apply: ontology: formal specification of a conceptualization, used to explicitly capture the semantics of a certain reality ETSI ETSI TS 103 673 V1.2.1 (2024-01) 8 SAREF actor: role that a person can play when using or contributing to SAREF SAREF core: versi... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 3.2 Symbols | Void. ETSI ETSI TS 103 673 V1.2.1 (2024-01) 9 |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CD Continuous Deployment CI Continuous Integration CSV Comma Separated Values DL Description Logics EUREKA European Research Coordination Agency HTML Hyper Text Markup Language IoT Internet of Things IPR Intellectual Property Right IRI Interna... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 4 Introduction | SAREF consists of SAREF projects, including SAREF core, and many SAREF extensions. SAREF core [1] is a versioned reference ontology for the IoT developed by ETSI TC SmartM2M in close interaction with the industry. SAREF contains core concepts that are common to several IoT domains and, to be able to handle specific dat... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 5 Actors of the SAREF development framework | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 5.1 Introduction | The following list shows the different SAREF actors and the use cases that each actor may carry out in the SAREF public forge and the SAREF public portal. The SAREF actors are organized into the following categories: Steering actors, Development actors, and Community actors: • Steering actors include Steering Board mem... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 5.2 Steering actors | Steering Board member: A Steering Board member belongs to the group of persons in charge of steering the SAREF development, including SAREF core and SAREF extensions. The community involvement and the underlying infrastructure. Steering Board members may have at least the role of Reporter in the SAREF public forge. The... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 5.3 Development actors | Project leader: A project leader is the person in charge of the SAREF project who carries out the project management tasks. A project leader shall have experience in ontology development projects. Project leaders may have at least the role of Maintainer in the ETSI public forge. There should exist at least one project ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 5.4 Community actors | Contributor: A contributor is a person knowledgeable about the ontology domain and proposes contributions. Contributors have an account on the SAREF public forge. The role of contributor is not assigned beforehand, it is obtained when submitting some contribution. The use cases of the contributor are the following: • C... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6 New SAREF project version workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1 Workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.0 Introduction | The new SAREF project version workflow supports the creation of new SAREF project versions proposals from the SAREF community of users. New SAREF project versions may be new versions of SAREF core, new versions of existing SAREF extensions, or initial versions (V1.1.1) of new SAREF extensions. Any contributors may prop... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.1 New SAREF project version proposal is submitted | CONDITION: A contributor wants to request a new SAREF project version. ACTION: The contributor creates an issue in the saref-portal-static issue tracker describing the new SAREF project version. This issue is called the proposal issue. Clause 6.2 specifies how to submit new SAREF project version proposals. OUTPUT: The ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.2 New SAREF project version proposal is not clear | CONDITION: Some of the details of the new SAREF project version proposal are not clear from its description. ACTION: The Steering Board reviews the proposal issue and asks for clarifications. Clause 6.3 specifies the reviewing process for new SAREF project version proposals. OUTPUT: One or more comments in the proposal... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.3 New SAREF project version proposal is updated | CONDITION: The new SAREF project version proposal is updated addressing the petitions raised by the Steering Board. ACTION: A contributor updates the proposal issue. OUTPUT: A new comment in the proposal issue with clarifications. The label of the proposal issue should be updated to "Submitted". |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.4 New SAREF project version proposal is dismissed | CONDITION: The Steering Board decides that the new SAREF project version proposal will not be accepted. ACTION: The Steering Board reviews the proposal issue and takes the decision of not accepting the proposal. Clause 6.3 specifies the reviewing process for new SAREF project version proposals. OUTPUT: The proposal iss... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.5 New SAREF project version proposal is clear | CONDITION: The Steering Board decides that the new SAREF project version proposal will be accepted. ACTION: The Steering Board reviews the "Submitted" proposal issue and takes the decision of accepting the proposal. Clause 6.3 specifies the reviewing process for new SAREF project version proposals. OUTPUT: The label of... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.6 Development infrastructure is ready | CONDITION: The ontology development infrastructure required for the new SAREF project proposal is deployed and configured. ACTION: If it is a new SAREF project, the Technical Board creates the sources of the SAREF project on the SAREF public forge. Clause 6.4 specifies how to set up the sources of a new SAREF project. ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.1.7 New SAREF project version is published in the portal | CONDITION: The new SAREF project is ready for development. ACTION: The project leader and steering board add the new SAREF project version to the portal. Clause 6.5 specifies how to add the new SAREF project version to the portal. OUTPUT: A new release of the ontology portal is published; the project proposal issue is ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.2 Proposing a new SAREF project version | In order to propose a new SAREF project version, a contributor shall create a new issue in the issue tracker of the saref-portal-static project. The issue shall include a description of the new SAREF project version proposal. The issue should be labelled as "Submitted". If the SAREF project version concerns an existing... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.3 Reviewing new SAREF project version proposals | The Steering Board should review periodically the suitability of every SAREF project version proposals. The board may ask for clarifications to the user proposing the new SAREF project version. The proposals may be presented to ETSI TC SmartM2M. The decision to dismiss or accept a new SAREF project version proposal is ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4 Setting up an SAREF project | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4.0 Introduction | The Technical Board and the Project Leader should set up the ontology development infrastructure for a new SAREF project version. If the SAREF project version concerns a new SAREF project, then: • The SAREF project shall be created in the SAREF public forge, as specified in clause 6.4.1. • The SAREF project development... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4.1 Creating a new SAREF project in the SAREF public forge | The source of a SAREF project consists of a git repository called the SAREF project repository, an associated public issue tracker, and a continuous integration and continuous deployment service. The sources of SAREF core shall be in a project named saref-core on the SAREF public forge, accessible at URL https://saref.... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4.2 Setting up the ontology development team | All the users that are involved in the SAREF project shall have a user account in the SAREF public forge. The following roles should be granted to such users in the project: • Members of the Technical Board should have the role of at least Maintainer. • Members of the Steering Board should have the role of at least Rep... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4.3 Preparing the project version development branch | Accepted SAREF project version proposals shall be assigned a target project version number vx.y.z by ETSI TC SmartM2M. If the SAREF project version concerns a new SAREF project, then a new branch named develop-vx.y.z shall be created after the target project version number vx.y.z, and it shall be defined as the "defaul... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.4.4 Configuring continuous integration and continuous deployment | The SAREF project should be configured in order to enable the continuous integration and continuous deployment activities. When a commit is pushed to any branch, a pipeline should be triggered to check the contribution. This pipeline should run the SAREF pipeline program [i.17] whose sources are located at the URL http... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 6.5 Adding a SAREF project version to the portal | The saref-portal-static project on the ETSI public forge contains the static content of the ontology portal. It contains different files that shall be created or updated to include the new extension: • The file named extensions.html contains an overview of all the SAREF project versions. The new SAREF project version s... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7 SAREF project version development workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1 Workflow | |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.0 Introduction | The SAREF project version development workflow supports the development of SAREF project versions from the SAREF community of users. SAREF project versions may be new versions of SAREF core, new versions of existing SAREF extensions, or initial versions (V1.1.1) of new SAREF extensions. The SAREF project version develo... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.1 Change request is submitted | CONDITION: A contributor wants to request a new change to the SAREF project version. ACTION: The contributor creates an issue in the SAREF project issue tracker describing the change request. This issue is called the request issue, and is identified by its issue number. The change request may concern the ontology requi... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.2 Change request is not clear | CONDITION: Some of the details of the change request are not clear from its description. ACTION: The project members review the request issue and ask for clarification. Clause 7.3 specifies the reviewing process for change requests. OUTPUT: One or more comments in the request issue indicating what needs to be clarified... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.3 Change request is updated | CONDITION: The change request is updated addressing the petitions raised by the project members. ACTION: A contributor updates the request issue. OUTPUT: A new comment in the request issue with clarifications. The label of the request issue should be updated to "Submitted". |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.4 Change request is dismissed | CONDITION: There is consensus in dismissing the change request. ACTION: The project leader reviews the request issue, and takes the decision of proposing to close the request. Clause 7.3 specifies the reviewing process for change requests. OUTPUT: The label of the request issue should be updated to "Propose closing". |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.5 Change request is clear | CONDITION: There is consensus in accepting the change request. ACTION: The project leader reviews the request issue, ensures that the change request is approved by ETSI TC SmartM2M, and takes the decision of accepting the request. Clause 7.3 specifies the reviewing process for change requests. OUTPUT: The label of the ... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.6 Change request is closed | CONDITION: There is consensus in closing the change request. ACTION: The project leader ensures that the request closure is approved by ETSI TC SmartM2M. Clause 7.3 specifies the reviewing process for change requests. ETSI ETSI TS 103 673 V1.2.1 (2024-01) 21 OUTPUT: The request issue shall be closed. |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.7 Implementation is clear | CONDITION: There is consensus on how to implement the change request. ACTION: Project members should review the request issue. The implementation plan may include updates to the ontology requirements as specified in clause 9.3. The implementation plan may include updates to the ontology specification as specified in cl... |
58d0b1168f9dc942aa912c8f59e19512 | 103 673 | 7.1.8 Implementation is not clear | CONDITION: There is no consensus on how to implement the change request. ACTION: Project members should review the request issue. OUTPUT: The label of the issue should be updated to "Needs discussion". The request issue should be updated with a description of what needs to be updated. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.