hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.75.2 Test signal used to build Test Configurations
| The signal's channel bandwidth and subcarrier spacing used to build A-IoT Test Configurations shall be selected according to table 4.75.2-1.
Table 4.75.2-1: Signal to be used to build A-IoT TCs
TC signal
R2D channel BWchannel
200kHz
(Note 1)
400kHz
(Note 1)
600 kHz
(Note 1)
800 kHz
(Note 1)
characteristics... |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.75.3 ATC1: Single carrier operation
| A-IoT support only single carrier operation. Test configuration can be as follows:
The purpose of the TC1 is to test A-IoT R2D carrier aspects.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 4.75.3.1 ATC1 generation
| ATC1 is constructed using the following method:
- The Base Station RF Bandwidth shall be the declared maximum Base Station RF Bandwidth.
- Place an A-IoT R2D carrier within the Base Station RF Bandwidth.
- Set the power of A-IoT R2D carrier to the rated output power Prated,c,AC according to the manufacturer’s declar... |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 6.6.5.5.2 BS type 1-C(void)
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 6.6.5.5.3 BS type 1-C
| The Tx spurious emissions for BS type 1-C for each antenna connector shall not exceed the basic limits specified in clause 6.6.5.5.1.
For Band n41 and n90 operation in Japan, the sum of the spurious emissions over all antenna connectors for BS type 1-C shall not exceed the basic limits defined in clause 6.6.5.5.1.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.1 Definition and applicability
| Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency at the antenna connector for BS type 1-C in... |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.2 Minimum requirement
| The minimum requirements for BS type 1-C are in TS 38.194 [3], clause 7.6.2.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.3 Test purpose
| The test purpose is to verify the ability of the BS receiver to inhibit the generation of intermodulation products in its non-linear elements caused by the presence of two high-level interfering signals at frequencies with a specific relationship to the frequency of the wanted signal.
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.4 Method of test
| |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.4.1 Initial conditions
| Test environment: Normal; see annex B.2.
RF channels to be tested for single carrier (SC): M; see clause [4.9.1]
|
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.4.2 Procedure
| The minimum requirement is applied to all connectors under test.
1) Connect the connector under test to measurement equipment as shown in annex D.2.7 for BS type 1-C.
2) Set the signal generator for the wanted signal to transmit as specified in table 7.7.5-1.
3) Set the signal generator for the interfering signal t... |
a1d9979ec3fb8c2091ddd4425cd961c2 | 38.195 | 7.76.5 Test requirements
| The BLER performance shall be 10% of the reference measurement channel as specified in annex A.1, with a wanted signal at the assigned channel frequency and two interfering signals coupled to the BS type 1-C antenna connector, with the conditions specified in Tables 7.7.5-1 for narrowband intermodulation performance. T... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 1 Scope
| This clause shall start on a new page.
The present document studies media-related aspects for 6G mobile networks for improvement of existing services and support of new services, to meet the 6G system requirements as developed in TR 22.870 [22870] and captured by TS 22.abc [22ABC], as well as in alignment with the arc... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 3 Definitions of terms, symbols and abbreviations
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 4 Preliminaries: assumptions and requirements
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 4.1 Assumptions
| Editor's note: This clause documents the common architecture assumptions identified for the study. This is primarily defined as based on the decisions in SA2 as well as the existing functions in earlier Gs.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 4.2 Requirements
| Editor's note: This clause defines the architectural and media-related requirements that serve as the foundation for the study. It collects SA1 defined requirements and associated use cases.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 4.3 Existing media services
| Editor's note: This clause collects existing media services that are already addressed in 4G and 5G, and identifies the status of the services in terms of relevancy and deployments.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 5 New trends and expected services related to media
| Editor's note: identify media-related industry trends from operators, third-party providers and verticals that may impact 6G media architectures
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6 Work topics: Description and discussion
| Editor's note: This clause identifies work topics based on the objective of the study item and newly defined work topics.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.0 Introduction
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1 Work topic #1: Media delivery architecture
| Editor's note: The present Work Task is structured according to the agreed subsection format, including: Description, Key Issues, Context and External Factors, Potential Solutions, Mapping of Issues to Solutions, and Conclusions. The subsection ordering may be adapted as appropriate for the specific content of the Work... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.2 Work topic #2: 6G media
| Editor's note: The present Work Task is structured according to the agreed subsection format, including: Description, Key Issues, Context and External Factors, Potential Solutions, Mapping of Issues to Solutions, and Conclusions. The subsection ordering may be adapted as appropriate for the specific content of the Work... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.3 Work topic #3: Media aspects related to SA2 topics
| Editor's note: The present Work Task is structured according to the agreed subsection format, including: Description, Key Issues, Context and External Factors, Potential Solutions, Mapping of Issues to Solutions, and Conclusions. The subsection ordering may be adapted as appropriate for the specific content of the Work... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.4 Work topic #4: Media for ubiquitous access
| Editor's note: The present Work Task is structured according to the agreed subsection format, including: Description, Key Issues, Context and External Factors, Potential Solutions, Mapping of Issues to Solutions, and Conclusions. The subsection ordering may be adapted as appropriate for the specific content of the Work... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.5 Work topic #5: Trusted and private communication for media
| Editor's note: The present Work Task is structured according to the agreed subsection format, including: Description, Key Issues, Context and External Factors, Potential Solutions, Mapping of Issues to Solutions, and Conclusions. The subsection ordering may be adapted as appropriate for the specific content of the Work... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 7 Consolidated findings
| Editor's note: This clause can be used to consolidate findings based on the considerations in clause 62.
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 8 Recommendations for follow-up work
| Editor's note: This clause will provide recommendations for follow-up work.
Annex A:
Additional background on selected work topics
Editor's note: The present annex collects supplementary background information related to selected work topics. The intention is to maintain a consolidated and persistent record of con... |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 5 New trends and expected seervices related to media
| Editor's note: identify media-related industry trends from operators, third-party providers and verticals that may impact 6G media architectures
|
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1.1 Description
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1.2 Key questions
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1.3 Context and external factors
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1.4 Potential solutions and way forward
| |
297e549a46ed295a2284fabdceea7f0d | 26.870 | 6.1.5 Conclusions
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 1 Scope
| This clause shall start on a new page.
The present document …
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 3 Definitions of terms, symbols and abbreviations
| This clause and its three subclauses are mandatory. The contents shall be shown as "void" if the TS/TR does not define any terms, symbols, or abbreviations.
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
anisotropic: refers to Gaussians whose shape and orientation vary by direction, allowing ... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 3.4 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
3DGS 3D Gaussian Splatting
SH Spherical Harmonic
PLY Polygon f... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 4 3DGS representation format
| [Editor’s note: Placeholder for the description of the 3DGS format and characteristics]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 4.1 Introduction
| A 3D Gaussian Splatting (3DGS) scene is represented as a set of continuous primitives, anisotropic 3D Gaussians, each carrying geometric parameters and radiometric attributes. It was first introduced in 2023 in research paper 3D Gaussian Splatting for Real-Time Radiance Field Rendering from INRIA [aa]. The data model c... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 4.2 Primitives
| A 3DGS primitive is an oriented 3D Gaussian with the following fields. The items below describe data elements, independent of any specific encoding:
- Position: 3D scene position of the primitive expressed with x, y, and z coordinates in the local space system.
- Rotation: Primitive orientation, that may be defined ... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 4.3 Camera parameters
| To ensure accurate and high-quality rendering, it is important to reuse the position and settings of the cameras used to capture the 3DGS scenes during the rendering process.
For each acquired view, complete camera information may be necessary: extrinsic parameters (pose as a matrix or quaternion translation in the sc... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5 Use cases
| [Editor’s note: Placeholder for the description of the use cases]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.1 Introduction
| The present clause describes service scenarios illustrating the generation and the consumption of 3DGS scenes as well as associated working assumptions on the service configurations that serve as basis for detailed analysis documented in the following clauses of this technical report.
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.2 On-device capture and sharing of a static 3DGS scene
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.2.1 Description
| A user initiates a short capture session on a mobile device (UE) using the rear or front camera(s). Various typical capture patterns may be supported, per example:
- Object/person sweep ("object scan", "3D selfie"): the user moves around a subject at close range, recording multiple viewpoints to ensure good coverage a... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.2.2 Working assumptions
| This section outlines the end-to-end processing chain, from capture to rendering on the receiving UE. It enumerates the key functional blocks, and device capability requirements.
- Acquisition and 3DGS content generation
- Sensor capture (RGB video, potentially depth and position and orientation if available).
- On-... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.3 Exploration of a large 3DGS environment
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.3.1 Description
| In this scenario the user explores a large 3DGS environment on a UE with responsive 6DoF or constrained-6DoF navigation.
A user launches an application and selects a large 3DGS scene (e.g., museum, mall level, outdoor plaza, city, …). The UE requests visible parts of the scenes around the current pose and prefetches l... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.3.2 Working assumptions
| This section outlines the end-to-end processing chain, emphasising adaptive delivery and device capability requirements.
- Acquisition and content generation
- The capture and the generation of large 3DGS scenes are not addressed in this use case.
- Based on the 3DGS models, the region-based parts of the 3DGS scenes... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.4 Dynamic 3DGS content
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.4.1 Description
| A UE receives time-varying 3DGS content depicting a dynamic subject or scene (e.g., a performer, dancer, singer, exhibition moment, band, sport action …). The UE renders the 3DGS content sequence in real time. The delivery and rendering process may also be assisted by the network through mechanisms such as partial deli... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 5.4.2 Working assumptions
| This section outlines the end-to-end processing chain covering the delivery and rendering of dynamic 3DGS content, emphasising adaptive delivery and device capability requirements.
- Acquisition and content generation
- The capture and the generation of dynamics 3DGS models are not the focus of this use case, but the... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6 Quality factors
| [Editor’s note: Placeholder for the description of the quality factors]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6.1 Introduction
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6.2 Discussion
| The objectives of FS_3DGS_MED cover a wide range of aspects in the end-to-end workflow related to 3DGS, including on related to workflow aspects:
b. Consistent end-to-end quality across different capturing and rendering systems for 3DGS representations.
In order to be able to approach this objective it is necessary t... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6.3 Complexity
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6.4 Metrics
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 6.5 Data size
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7 Static 3DGS content creation
| [Editor’s note: Placeholder for the description of the 3DGS content creation processes]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7.1 3DGS generic workflow
| As an example, a 3DGS model construction from the capture of 2D data follows the production workflow as illustrated in figure 2:
Figure 2: 3DGS model production workflow from a 2D video
The workflow consists of three parts. First, the capture phase. During this phase, numerous views of a real-world object or scene... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7.2 Capture
| Content acquisition for 3D Gaussian Splats (3DGS) relies on capturing accurate 3D data from real-world objects and environments. Primary methods include:
- 2D image and video capture: video sequences or sets of 2D images capture from various positions and orientations offer coverage of dynamic or complex environments.... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7.3 Structure from Motion
| The Structure from Motion (SfM) step consists in operating the feature extraction and matching and retrieving the camera parameters when unknown. After image alignment, the process creates a sparse point cloud that is further densified with depth calculation methods.
Camera parameters, often known by the capturing sys... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7.4 Training
| 7.4.1 Introduction
The third step is about the creation of the gaussian splats associated to each 3D point using iterative optimization process that will search for the splats that match as much as possible the source video for a given pose (position + orientation) by optimizing the size, shape, colour and transparen... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 7.4.5 Discussion
| The original paper on 3D Gaussian Splatting for Real-Time Radiance Field Rendering [aa] published in August of 2023 presents a workflow as shown below:
Figure 1: Organization of the workflow [aa]
Whilst the original workflow process includes a closed loop optimization problem using convergence with ground truths t... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 8 3DGS rendering
| [Editor’s note: Placeholder for the description of the 3DGS rendering processes]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 8.1 Pipeline description
| The commonly used pipeline to render 3DGS objects is outlined in this clause. It defines the per-frame inputs, configurable options, and outputs of a representative implementation, without prescribing specific algorithms.
The inputs are, per 3DGS frame and per rasterized image:
• 3DGS data: per-Gaussian attribu... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 8.2 Rasterization process
| 8.2.1 Introduction
This section presents a rendering process used to render a 3DGS model. A 3DGS model is rendered based on the observer’s position and orientation and on the Gaussian, primitives defined in Section 4.1. Depending on the chosen representation format, the rasterization described below may need to be up... |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 9 High level media data workflows
| [Editor’s note: Placeholder for the description of the workflows]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 9.1 All-in-client configuration
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 9.1 Client-server configuration
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 10 Mapping to the 3GPP services
| [Editor’s note: Placeholder for the description of the 3GPP services used]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 10.1 All in UE configuration
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 10.2 Client-server configuration
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 11 Related activities and products and services
| [Editor’s note: Placeholder for the description of the products and services]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 11.1 Standardization activities
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 11.2 Services
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 11.3 Software and products
|
12 Reference implementation
[Editor’s note: Placeholder for the description of the reference implementation]
|
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 12.1 Capture
| |
66b5fc78a94ec8f2de89f788f52261bb | 26.958 | 12.2 Transmission
| 12.4 Rendering
Annex <B>:
<Informative annex title for a Technical Report>
Informative annexes in Technical Reports do not use "(informative") in the title, since all annexes in TRs are informative. Use style "Heading 9" in TRs.
B.1 Heading levels in an annex
Heading levels within an annex are used as in the m... |
1a27a93f1820dce4437159b281db5215 | 28.893 | 1 Scope
| The present document …
|
1a27a93f1820dce4437159b281db5215 | 28.893 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
1a27a93f1820dce4437159b281db5215 | 28.893 | 3 Definitions of terms, symbols and abbreviations
| |
1a27a93f1820dce4437159b281db5215 | 28.893 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
1a27a93f1820dce4437159b281db5215 | 28.893 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
1a27a93f1820dce4437159b281db5215 | 28.893 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
Annex <X> :
Change history
Change hi... |
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 1 Scope
| The present document …
|
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 3 Definitions of terms, symbols and abbreviations
| |
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally.
|
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
dbf6dca34b12a6d0d977b45733f7173e | 32.801-01 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
Annex X (informative):
Change history
Ch... |
37da702570fd408d755f579b39acc541 | 38.742 | 1 Scope
| This technical report addresses the study of GNSS (Global Navigation Satellite System) resilient operation in NR-NTN (Non-Terrestrial Networks), targeting Release 20 enhancements. The objective is to evaluate and define solutions to ensure NR-NTN functionality in scenarios where GNSS signals are unavailable, degraded, ... |
37da702570fd408d755f579b39acc541 | 38.742 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.