Home

Results 1 - 10 of 161,636 for property qualified. Search took 1.349 seconds.  
Sort by date/Sort by relevance
A name of a Property Term shall be unique within 74 the Context of an Object Class but may be reused across different Object Classes. 75 4.2 Corrected Rule C27 76 [C27] The name of a Property Term shall occur naturally in the definition and may 77 consist of more than one word. (...) All Rights Reserved. 6.0 Rule B25 – Correct Naming of ASBIEs 91 6.1 Current Rule B25 92 [B25] The Dictionary Entry Name of an Association Business Information Entity shall 93 consist of the following components in the specified order: 94 • the Object Class Term of the corresponding Association Core Component, and 95 possibly additional Qualifier Term(s), 96 • the Property Term of the corresponding Association Core Component, and 97 possibly additional Qualifier Term(s), 98 • the Object Class Term of the Association Business Information Entity on which 99 the corresponding Association Business Information Entity Property is based. 100 6.2 Corrected Rule B25 101 [B25] The DEN of an ASBIE shall consist of the following components in the specified 102 order: 103 • the object class term of the associating BIE, and possibly additional qualifier 104 term(s), 105 • the property term that reflects the nature of the association between object classes, 106 and possibly additional qualifier term(s), 107 • the object class term of the associated BIE, and possibly additional qualifier 108 terms(s). 109 7.0 Rule S28 – Cardinality of Data Type Qualifier Term 110 7.1 Current Rule S28 111 [S28] Stored Data Types shall include the following Attribute: 112 • Qualifier Term (mandatory): A semantically meaningful name that 113 differentiates the Data Type from its underlying Core Component Type. (...) All Rights Reserved. 7.3 Corrected Metamodels 123 • Figure 6-1: Qualifier Term removed from Data Type class 124 • Figure 6-2: The optional Qualifier Term only applies to Data Types for BIE 125 Properties. 126 • Figure 7-1: Qualifier Term removed from Data Type class 127 Technical Corrigendum 2007-02-12 UN/CEFACT – Core Component Technical Specification V2.01 – Technical Corrigendum 1 Page 8 of 8 Copyright © UN/CEFACT 2007.
Language:English
Score: 1279072.7 - https://unece.org/fileadmin/DA...201_Corr_1_12FEB07Approved.pdf
Data Source: un
Col n° Column Name TBG17 website template Name CCL 1.0 (first pass) 1 Source Source 2 Identifier Unique ID 3 Dictionary Entry Name Dictionary Entry Name(DEN) 4 ACC/ BCC/ ASCC/ ABIE/ BBIE/ ASBIE ACC/ BCC/ ASCC 5 Definition Definition 6 Comment Library Note 7 Object Class Qualifier(s) Object Class Term 8 Object Class Term Property Term 9 Property Term Qualifier(s) Representation Term 10 Property Term Associated Object Class Term 11 Data Type / Repesentation Term Qualifier(s) Business Term(s) 12 Representation Term Occurrence Min 13 Associated Object Class Qualifier(s) Occurrence Max 14 Associated Object Class TDED Reference 15 Business Term(s) 16 Cardinality Min 17 Cardinality Max 18 Context Categories Business Process 19 Context Categories Region (Geopolitical) 20 Context Categories Official Constraints 21 Context Categories Product 22 Context Categories Industry 23 Context Categories Role 24 Context Categories Supporting Role 25 Context Categories System Constraints In analysing the differences it can be seen that in some cases columns have been eliminated (shown in bold in the table below). (...) Col n° Column Name TBG17 website template Name CCL 1.0 edition 2005-10-07 Name CCL 1.0 edition 2006-01-18 1 Source Source Source 2 Identifier Unique ID Unique ID 3 Dictionary Entry Name Dictionary Entry Name(DEN) Dictionary Entry Name(DEN) 4 ACC/ BCC/ ASCC/ ABIE/ BBIE/ ASBIE ACC/ BCC/ ASCC ACC/ BCC/ ASCC 5 Definition Definition Definition 6 Comment Library Note Library Note 7 Object Class Qualifier(s) Object Class Term Qualifier(s) 8 Object Class Term Object Class Term Object Class Term 9 Property Term Qualifier(s) Property Term Qualifier(s) 10 Property Term Property Term Property Term 11 Data Type / Repesentation Term Qualifier(s) Repesentation Term Qualifier(s) 12 Representation Term Representation Term Representation Term 13 Associated Object Class Qualifier(s) Associated Object Class Term Qualifier(s) 14 Associated Object Class Associated Object Class Term Associated Object Class Term 15 Business Term(s) Business Term(s) Business Term(s) 16 Cardinality Min Occurrence Min Occurrence Min 17 Cardinality Max Occurrence Max Occurrence Max 18 Context Categories Business Process 19 Context Categories Region (Geopolitical) 20 Context Categories Official Constraints 21 Context Categories Product 22 Context Categories Industry 23 Context Categories Role 24 Context Categories Supporting Role 25 Context Categories System Constraints 26 TDED Reference The fields in the spreadsheet will be mapped as follows: Col n° Name CCL 1.0 UN/CEFACT Registry Name Metamodel name 1 Source Administrative Information-Submitting Organisation Note: Registrar = Stig Korzgard Registration Authority = UN/CEFACT Status information = approved Start Date = approval date 2 Unique ID Registry Class-Unique Identifier Note: Version = 1.0 3 Dictionary Entry Name(DEN) RegistryClass-DictionaryEntryName 4 ACC/ BCC/ ASCC UN/CEFACT Registry Object Type 5 Definition Registry Class-Definition 6 Library Note Descriptive Information-Comments 7 Object Class Term AggregateCoreComponent-ObjectClassTerm 8 Property Term BCC Property-PropertyTerm ASCC Property-Property Term 9 Representation Term DataType-RepresentationTerm (addition needed to maintain coherence) 10 Associated Object Class Term AggregateCoreComponent association mapping 11 Business Term(s) CoreComponent-BusinessTerm 12 Occurrence Min See next line 13 Occurrence Max CCProperty-Cardinality (convention (min-max)) where min can equal 0, 1 or n values and max can equal 1, n, or * values) 14 TDED Reference Descriptive Information-Comments RECOMMENDATION 1: TBG 17 revise the current Excel boilerplate to align it with the published library boilerplate and to provide the procedure defining how the document may evolve. (...) The current directory only references 9 out of some 268 UNCL code lists: 1001 Document name code 4237 Payment arrangement code 4435 Payment channel code 5153 Duty or tax or fee type name code (expressed incorrectly as 513) 5237 Charge category code 5243 Rate or tariff class description code 5305 Duty or tax or fee category code 6245 Temperature type code qualifier 7273 Service requirement code In all there are some 73 coded Basic Core Components one would expect that a significantly higher number of this codes have UNCL code lists.
Language:English
Score: 1269064.6 - https://unece.org/fileadmin/DA...-REPORT-CCL06A-Part-1-of-2.doc
Data Source: un
BIE Cardinality ASCC and BCC properties may have different qualifiers applied. This may result in the ABIE having a greater number of qualified properties than its corresponding ACCs unqualified properties. (...) ASCC and BCC properties may also have multiple qualifiers applied. Multiple qualifiers create a qualifier hierarchy, with each additional qualifier reflecting a further restriction to its less qualified BIE property.
Language:English
Score: 1260541.7 - https://unece.org/fileadmin/DA...ortrade/CCTS/CCTS-Version3.pdf
Data Source: un
The ASCC property consists of a property term that expresses the581 nature of an association between object classes, and the name of the object class582 being associated. (...) Metrics612 The simple properties are BCC properties. They represent a singular613 characteristic and their set of allowed values is defined by a CDT.614 The complex properties are ASCC properties. (...) Just as an682 ACC is the representation of an object class, so too are its derived ABIEs. An ABIE683 may be qualified at the object class level, and its properties may be qualified at the684 [Example] – Aggregate Business Information Entity with context driven685 restrictions and qualifications686 ACC ABIE Business Context Contract.
Language:English
Score: 1233847.9 - https://unece.org/fileadmin/DA.../CCTS-SecondIteration-ODP6.pdf
Data Source: un
Note that the name is just the property term and not the dictionary entry name. UML Profile for Core Components (UPCC) – Version 1.0 – Final Specification - 2008-01-16 Page 18 of 40 Business Information Entity Elements ABIE / BBIE / ASBIE / QDT Qualifier Terms The qualifier prefix (characters before the underscore) of the ABIE, BBIE, ASBIE and QDT name. (...) Basic Business Information Entity – property term Name of a UML attribute with stereotype <> (without qualifier prefix if it exists) Note: The BBIE attribute name is the qualified property term - shall be equal to the property name of the BCC upon which this BBIE is based with an optional prefix equal to the qualifier term. (...) The type of the BBIE must be another class of stereotype <> (Core Data Type) or <> (Qualified Data Type). Note that the representation term is equal to the name of the CDT class (or QDT class without qualifier term) Association Business Information Entity – property term UML aggregation source role name of an aggregation of stereotype <>.
Language:English
Score: 1181728.3 - https://unece.org/fileadmin/DA...ade/UPCC_UML-CoreComponent.pdf
Data Source: un
In the first instance, the qualifier data element may be used to assign different characteristics to the qualified composite data element. (...) [R.840-Rule 31] Rule 54: A segment shall be specified with at least one data element in addition to the qualifier data element that qualifies the segment. (...) [R.1237-Rule 23*] Rule 87: The qualifier of a component data element shall follow the component data element it qualifies.
Language:English
Score: 1167945.5 - https://unece.org/fileadmin/DA...enary/plenary99/docs/99cf3.pdf
Data Source: un
In the first instance, the qualifier data element may be used to assign different characteristics to the qualified composite data element. (...) [R.840-Rule 31] Rule 54: A segment shall be specified with at least one data element in addition to the qualifier data element that qualifies the segment . (...) [R.1237-Rule 23*] Rule 87: The qualifier of a component data element shall follow the component data element it qualifies.
Language:English
Score: 1167945.5 - https://unece.org/fileadmin/DA...enary/plenary99/docs/99cf3.doc
Data Source: un
In the first instance, the qualifier data element may be used to assign different characteristics to the qualified composite data element. (...) [R.840-Rule 31] Rule 54: A segment shall be specified with at least one data element in addition to the qualifier data element that qualifies the segment . (...) [R.1237-Rule 23*] Rule 87: The qualifier of a component data element shall follow the component data element it qualifies.
Language:English
Score: 1167945.5 - https://unece.org/fileadmin/DA...enary/plenary99/docs/99cf3.rtf
Data Source: un
We are looking forward to receiving your […] RFQ 27/2021 Support to National Mental Health Hotline system UNHCR is looking for a qualified service provider to support in the development and implementation of a hotline system at the Abbassia hospital in Cairo. (...) Bidders who express their interest […] RFQ 30/2021 – For the establishment of a contract for the provision of HAUS survey for a period of 1+1 years UNHCR is seeking offers from qualified service providers to undertake the HAUS survey under a contract of duration of 1+1 years. (...) I […] PQ 1/2021 – Prequalification for civil works UNHCR Egypt invites qualified suppliers to submit their application for prequalification for closed biddings for civil works in at its premises in Cairo, October 6 City and Alexandria within the upcoming 12 months.
Language:English
Score: 1163333.9 - https://www.unhcr.org/eg/list/supply/closed-bids/feed
Data Source: un
Microsoft Word - 40A4A9A3-3FFC-206E36.doc ANNEX 2-3 Relevant articles of Act CVI of 2007 on State Property Relevant articles of Act CVI of 2007 on State Property Art. 1(2) In application of this Act the following items shall be considered State property: a) Any objects and natural resources that can be utilised as an object that are in State property; b) All properties not belonging to Point a) above where an Act stipulates so; c) Commercial papers, securities, stocks belonging to the State and any other rights with financial value if stipulated in any laws; d) All financial means in the property of the State. Art. 5(1) All data is public out of public interest that is in connection with the management of State property or any commanding of it unless it is public interest data anyway. Separate Act can restrict the access to such data. (2) All persons or organisations that manage or rule over State property shall qualify as body or person performing public responsibilities within the frames of the Act on the publicity of public interest data.
Language:English
Score: 1162338.7 - https://unece.org/DAM/env/pp/c...ication_State_Property_Act.pdf
Data Source: un