Home

Results 41 - 50 of 538,073 for model correspondence. Search took 4.333 seconds.  
Sort by date/Sort by relevance
In a second step, XKOS, an ontology for modelling statistical classifications, developed by DDI (Data Documentation Initiative) was applied on the artefacts in the Registry to convert them into Linked Open Data. (...) The SDMX standard (SDMX, 2021) defines several objects or artefacts that can be used to model and automate data and metadata exchange (the Information Model), as well as specifications of Registries that allow for the storage and retrieval of these objects. (...) For the purpose of Linked Data Modelling, we used Vocbench4, a RDF web-based multilingual collaborative platform for managing controlled vocabularies and generic RDF datasets.
Language:English
Score: 860508.6 - https://unece.org/sites/defaul...22_Paper_Eurostat_Laaboudi.pdf
Data Source: un
However, this way, the TMN model is an organisational model, which defines what is inside and outside TMN, and is not a reference model in the technical sense we have been discussing reference models in this paper. (...) This architecture has got a much more technical character than that of the TMN model. The bottom ‘planes’ correspond quite well with the internal layer of Figure 7. (...) When we come to the top planes of the IN architecture, it diverges even more from the Interoperability reference model presented in this paper. The Function plane may correspond to the Application schema.
Language:English
Score: 860478 - https://www.itu.int/itudoc/itu...hop/framewrk/014/78085_ww9.doc
Data Source: un
 Page 708 - Cloud computing: From paradigm to operation           Basic HTML Version Table of Contents View Full Version Page 708 - Cloud computing: From paradigm to operation P. 708 3 XaaS Appendix II Modelling usage example of NaaS service, NaaS service operational policy and NaaS resource model (This appendix does not form an integral part of this Recommendation.) (...) Figure II.1 – Example of VPC and VPN relationship II.2 Modelling usage Based on the description given in clause II.1, the VPC service can be modelled as a VPC NaaS service model based on its concrete service attributes, including service ID, tenant ID, access bandwidth, access virtualized network device, attached virtual service, etc. The initial provisioning configuration can be generated based on the VPC NaaS service model, together with the corresponding NaaS service operational policy model, which includes the following aspects: – The required services on data centres according to NaaS CSC's profile are allocated; – Services located in multiple distributed data centres are interconnected via e.g., VPNs; 700     703     704     705     706     707     708     709     710     711     712     713          
Language:English
Score: 860315.1 - https://www.itu.int/en/publica.../files/basic-html/page708.html
Data Source: un
Page 719 - 2015 Security in Telecommunications and Information Technology           Basic HTML Version Table of Contents View Full Version Page 719 - 2015 Security in Telecommunications and Information Technology P. 719 Unleashing the potential of the Internet of Things 5 Appendix I Deployment model with WoT (This appendix does not form an integral part of this Recommendation.) (...) Figure I.1 shows the deployment model in which the HGW is connected to a constrained device and a fully-fledged device. Figure I.1 – Deployment model with WoT The management PF provides the virtual devices to the application developers to be treated as web resources through the web-based application interface so that they can develop applications for the mash-up service defined in [b-ITU-T Y.2063], which is a combined service integrating WoT services in a WoT broker with web services outside of the WoT broker.
Language:English
Score: 860314.3 - https://www.itu.int/wftp3/Publ.../files/basic-html/page719.html
Data Source: un
Table 1: Mapping of XSD schema components XSD schema component W3C XML Schema reference Mapping defined by attribute declaration Part 1, 3.2 Clause 15 element declaration Part 1, 3.3 Clause 14 complex type definition Part 1, 3.4 Clause 20 attribute use Part 1, 3.5 Clause 15 attribute group definition Part 1, 3.6 not mapped as such model group definition Part 1, 3.7 Clause 17 model group Part 1, 3.8 Clause 18 particle Part 1, 3.9 Clause 19 wildcard Part 1, 3.10 Clause 21 ITU-T Rec. (...) NOTE – This means that all ASN.1 type reference names in the ASN.1 module can be imported into other modules. 10 Name conversion 10.1 General 10.1.1 This Recommendation | International Standard specifies the generation of: a) ASN.1 type reference names corresponding to the names of model group definitions, top-level element declarations, top-level attribute declarations, top-level complex type definitions, and user-defined top-level simple type definitions; b) ASN.1 identifiers corresponding to the names of top-level element declarations, top-level attribute declarations, local element declarations, and local attribute declarations; c) ASN.1 identifiers for the mapping of certain simple type definitions with an enumeration facet (see 12.4.1 and 12.4.2); d) ASN.1 type reference names of special type assignments (see clauses 29, 30, and 31); and e) ASN.1 identifiers of certain sequence components introduced by the mapping (see clause 20). 10.1.2 All of these ASN.1 names are generated by applying 10.3 either to the name of the corresponding schema component, or to a member of the value of an enumeration facet, or to a specified character string, as specified in the relevant clauses of this Recommendation | International Standard. (...) NOTE - Other top-level schema components are not mapped to ASN.1, and XSD built-in datatypes are mapped in a special way. 10.4.2 The order is specified in the three following subclauses. 10.4.2.1 Top-level schema components shall first be ordered by their target namespace, with the absent namespace preceding all namespace names in ascending lexicographical order. 10.4.2.2 Within each target namespace, top-level schema components shall be divided into four sets ordered as follows: a) element declarations; b) attribute declarations; c) complex type definitions and simple type definitions; d) model group definitions. 10.4.2.3 Within each set (see 10.4.2.2), schema components shall be ordered by name in ascending lexicographical order. 10.4.3 The mapping generates some ASN.1 type assignments that do not correspond directly to any XSD schema component.
Language:English
Score: 859747.6 - https://www.itu.int/ITU-T/2001...com17/languages/X.694-0401.pdf
Data Source: un
 Page 614 - 5G Basics - Core Network Aspects           Basic HTML Version Table of Contents View Full Version Page 614 - 5G Basics - Core Network Aspects P. 614 2 Transport aspects 9 System design for supporting a radio access system over an optical access network 9.1 Measurement test model for mobile front-hauling over an optical distribution network Figure 9-1 shows a general test model for physical-level quality measurement of RF signal in MFH with the RoF technology, which is based on the RF-band subcarrier signals transmission shown in Figure 6-1-a. (...) Here, thin and thick lines represent electrical and optical wirings, respectively. In this model, it is assumed that the OAN under test corresponds to a link between service network interface (SNI) and user network interface (UNI). (...) For the purpose of transmitting a RoF signal, a set of one E/O converter, one O/E converter, and one MUX/DEMUX at the network side corresponds to an OLT, and another set of one E/O converter, one O/E converter, and one MUX/DEMUX at the user side corresponds to an ONU.
Language:English
Score: 859519.8 - https://www.itu.int/en/publica.../files/basic-html/page614.html
Data Source: un
The model shows an array of the downstream symbol encoders (which represent the data, sync, pilot or initialization symbol encoders shown in Figure 10-1) and the modulation by the IDFT functional blocks of the FTU-Os, with the FEXT cancellation precoder inserted between the symbol encoders and the modulation by the IDFT blocks. The VCE of the vectored group learns and manages the channel matrix per vectored subcarrier, which reflects the channel characteristics of the managed group of lines. In the functional model in Figure 10-16, the channel matrix for each vectored subcarrier is of size NN where N is the number of lines in the vectored group. From the channel matrix, a VCE derives a FEXT precoder matrix, which is used to compensate the FEXT from each line in the vectored group. In the functional model in Figure 10-16, this is shown by a matrix of FEXT 775     780     781     782     783     784     785     786     787     788     789     790          
Language:English
Score: 859519.8 - https://www.itu.int/en/publica.../files/basic-html/page785.html
Data Source: un
., M/S 635, 3B28Andover, MA 01810 USA Tel:Fax:Email: +1 978 623 4324+1 978 749 2804garys@pictel.com Title: Proposal for Test Model Quantization Description Purpose: Proposal _____________________________ INTRODUCTION The Advanced Intra Coding quantization rule in the latest test model document proposal (Q15-C-15) is wrong, and the time has come to correct that section of the document. (...) I suggest that this explanation be added to the text of the test model. There are also a number of editorial problems with the section on quantization (Section 4). (...) If the pdf of the coefficients is modeled by the Laplacian distribution, a simple offset that is the same for each quantization interval can achieve this optimal spacing.
Language:English
Score: 859519.3 - https://www.itu.int/wftp3/av-a...video-site/9804_Tam/q15d30.doc
Data Source: un
The proposed context modeling scheme of CABAC is depicted in Fig. 1. In conventional context modeling scheme, the context template consists of two neighboring syntax elements A and B as depicted in Fig 1(a), while the context template of proposed scheme have the additional syntax element C that is located in corresponding base layer macroblock as shown in Fig. 1(b) and 1(c). (...) Assignment of context index to bin index of mb_type in each slice type Syntax element Bin index 0 1 >=2 mb_type (I) #1 (fixed) Same with AVC Same with AVC mb_type (P) #3 (model-1) Same with AVC Same with AVC mb_type (B) #6 (model-3) #2 (model-2) #1 (fixed) base_mode_flag (P) #3 (model-1) base_mode_flag (I, B) #3 (model-1) base_mode_refinement_flag (P) #3 (model-1) base_mode_refinement_flag (B) #3 (model-1) intra_base_flag (I) #1 (fixed) intra_base_flag (P,B) #1 (fixed) cbpy (I) #6 (model-3) cbpy (P) #6 (model-3) cbpy (B) #6 (model-3) coded_block_flag #4 (model-3) significant_coeff_flag (I) #180 (model-2) significant_coeff_flag (P,B) #180 (model-2) last_significant_coeff_flag (I) #180 (model-2) last_significant_coeff_flag (P,B) #180 (model-2) coeff_abs_level_minus1 #60 (model-2) Same with AVC Same with AVC coeff_abs_level_minus1 #60 (model-2) Same with AVC Same with AVC 3. (...) Conclusion In this document, we proposed new context modeling using inter-layer relationship and binarization process for syntax element corresponding header information and also residual data in enhancement layer.
Language:English
Score: 858954.2 - https://www.itu.int/wftp3/av-a.../2005_07_Poznan/JVT-P067r1.doc
Data Source: un
 Page 1068 - Shaping smarter and more sustainable cities - Striving for sustainable development goals           Basic HTML Version Table of Contents View Full Version Page 1068 - Shaping smarter and more sustainable cities - Striving for sustainable development goals P. 1068 3.5.4 Building information modeling (BIM) Work FG‐SSC SDO Document Corresponding Standardization Future needs area delivera‐ working on this number document title gap in this area and suggestions ble(s) relat‐ area released by to SG5 ed to this this SDO work area Building International To develop infor‐ Alliance for In‐ guidelines for mation teroperability: smart buildings, modeling Industry Founda‐ including use tion Class cases and best practice etc. ISO/TC 184 (Au‐ ISO Industry Foundation Classes tomation sys‐ 16739:2013 (IFC) for data sharing in the tems and inte‐ construction and facility man‐ gration) agement industries (IFC) ISO 29481‐1 Building information model‐ ling ‐ Information delivery manual ‐ Part 1: Methodology and format (IDM) ISO 29481‐2 Building information model‐ ling ‐ Information delivery manual ‐ Part 2: Interaction Framework (IDM) ISO 12006‐3 Building construction ‐ Organi‐ zation of information about construction works ‐ Part 3: Framework for object‐ oriented information (IFD) 3.5.5 Traffic systems Work FG‐SSC de‐ SDO Document Corresponding Standardization Future needs area liverable(s) working on this number document title gap in this area and suggestions related to area released by to SG5 this work this SDO area Road ISO/TC ISO Road traffic safety (RTS) man‐ traffic 241 (Road traffic 39001:2012 agement systems ‐ Require‐ safety manage‐ ments with guidance for use ment systems) Road ISO/TC 22 (Road vehicles vehicles) 1058 ITU‐T's Technical Reports and Specifications     1063     1064     1065     1066     1067     1068     1069     1070     1071     1072     1073          
Language:English
Score: 858709 - https://www.itu.int/en/publica...files/basic-html/page1068.html
Data Source: un