zilongwang/ReadingBank huggingface dataset:
Our efforts to create jobs are taking place against the backdrop of the devastating global and domestic recession that has resulted in significant job losses in Gauteng and the world over. In improving the efficiency of the economy and its capacity to create jobs, we will pay particular attention to the freight logistics sector. We will establish three freight logistics hubs in Rosslyn, the West Rand and at OR Tambo International Airport. In addition, our plan is to transform the economy of Gauteng from a predominantly mining to a diversified and modern economy. This transformation will place emphasis on the industrial policy framework which is underpinned by areas that include metals and minerals beneficiation; clothing and textiles; leather and footware; tooling and foundries; business process outsourcing and off-shoring; transport; capital equipment; tourism; the green economy and alternative energy. Job creation will be our main area of emphasis in the year ahead. By investing in economic and social infrastructure delivery, we will create jobs whilst improving the development of the Gauteng City Region and our communities. Our new infrastructure programme will create at least 130,000 jobs this year through the construction and maintenance of education and health infrastructure. The quality of school infrastructure remains a major challenge. Despite the investment over the years in new infrastructure, existing infrastructure is dilapidating rapidly. We will deliver 4 new schools during 2011 for the 2012 school year and will initiate plans for the building of 13 new schools to be delivered in the 2012/13 financial year. A total of 30 schools will be renovated. While we have a backlog in new infrastructure and budget constraints, we have commissioned work on alternate financing to eradicate the backlog in new schools. We are investigating public-private partnerships and will seek donor funding from the business sector. In addition, we will review the current school admission policy to ensure optimal utilisation of public schools. Through the Expanded Public Works Programme (EPWP), we will create over 175,000 work opportunities of 100 days each as well as 88 379 full time equivalents targeting one individual per poor household. The Community Works Programme, which provides a jobs safety net, will be rolled out in six sites this year – one in Metsweding, three in Ekurhuleni, and two in Tshwane. These sites are based in the 50 poorest wards in the province. This programme will generate a minimum of 6000 jobs, with 40% of the jobs being reserved for young people.
Addresses: Director of Social Services: County Hall, Carmarthen SA31 1JP Tel : Care and Social Services Inspectorate Wales: South West Region Government Buildings Picton Terrace Carmarthen SA31 3BT Tel : 0300 7900 126 Hywel Dda Local Health Board Headquarters: Merlin’s Court Winch Lane Haverfordwest Pembrokeshire SA61 1SB Tel : 01437 771220 The Local Government Ombudsman: PO Box 4771 Coventry CV4 0EH Tel: 0845 602 1983 or 024 7682 1960 Fax: 024 7682 0001
Instructions: Place an “X” in the column titled “Required?” for all Special Inspections and Tests required for this project. In the column marked “Required Qualifications” provide the qualifications for the special inspector, using the list beginning on page 4, for all required Structural Tests and Special Inspections. For those items listed as “Continuous,” continuous special inspection shall be as defined in Section 1702.1 and Chapter 2, IBC-15. For those items listed as “Periodic” provide the minimum number of tests, i.e. 20% of all field welds, or the amount of work to be inspected (e.g. 10% of all wall surfaces). Attach completed Statement of Structural Tests and Special Inspections to the end of the Specification Section 01 40 00, Quality Requirements. Qualification Requirements for Inspectors and Testing Technicians PE/SE Structural Engineer – licensed PE or SE specializing in the design of buildings and structures PE/GE Geotechnical Engineer – licensed PE specializing in soil mechanics and foundations EIT Engineer-In-Training – graduate engineer who has passed the Fundamentals of engineering examination American Concrete Institute (ACI) Certification ACI-CCSI Concrete Construction Special Inspector ACI-LTT Concrete Laboratory Testing Technician Level 1 or 2 ACI-STT Concrete Strength Testing Technician ACI-FTT Concrete Field Testing Technician – Grade I American Society of Non-Destructive Testing (ASNT) Certification Non-Destructive Testing Technician – Level II or III American Welding Society (AWS) Certification AWS-CWI Certified Welding Inspector
EVALUATION CRITERIA: Contract will be awarded only to a qualified consultant. Minimum standards for qualifications are: Having the necessary airport experience, organization, technical and managerial staff, and facilities to carry out the work. (30%) Having an adequate record of performance on similar airport projects. Verifiable through references. (25%) Creative insight to airport operations, aviation security, and airspace surrounding the Marion County Airport. (10%) Having familiarity with the Marion County Airport and the surrounding area. (15%) Having the financial and personnel resources for the performance of the Contract, or the ability to obtain such resources. (10%) Being an Equal Opportunity Employer and being otherwise qualified by law to enter into a contract such as this. (5%). Consultant’s proximity to the Marion County Airport. (5%) SELECTION: Final recommendation for selection will be made following the review and ranking of the submittals and interviews, should interviews be held. After selection of a Consultant, a contract will be prepared based on a negotiated scope of services and fee. Should negotiation be unsuccessful with the number one ranked firm, negations will cease with that firm, and negotiations will begin with the number two ranked firm. This process will continue until a satisfactory contract is obtained. CONTRACT REQUIREMENTS: The successful Consultant will be required to complete a Service Contract describing task orders and scope of service fees. Successful Consultant shall have Workman’s Compensation and Professional Liability insurance, naming Marion County as a coinsurance for airfield construction projects. Disadvantaged Business Enterprise (DBE) goals will be established for selected subcontracted tasks. Marion County will require a list of DBE’s, and their responsibilities and qualifications, including dollar value of their participation. DBE firms must certified by SCDOT and/or USDOT to the satisfaction of the Federal Aviation Administration (FAA).
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 1.0 None No changes to the meaning, language, or
Index A Abstract data model 17 17 9 C 10 30 11 12 D Data model - abstract 17 17 Data types 11 E 12 14 Events timer server 22 Examples 24 F 10 27 G 5 I 27 26 26 7 Initialization 18 18 5 M 12 Messages 11 12 14 11 Methods 20 13 12 N 15 16 7 O 7 P 26 9 9 29 Protocol Details 17 R 6 7 7 8 20 14 S Security 26 26 Server 17 18 NetEventForwarder 17 18 20 22 18 22 18 10 Structures 12 14 13 12 15 16 12 T Timer events 22
language, or formatting of the technical content. 5/15/2014 2.1 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 3.0 Major Significantly changed the technical content. 10/16/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2017 4.0 Major Significantly changed the technical content. 6/1/2017 4.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 10 9 6 8 7 C 6 15 Client 10 10 10 10 10 10 10 8 7 D Data model - abstract 10 9 8 8 E 8 Events 10 9 10 9 11 F 6 13 G 4 7 I 12 12 5 Initialization 10 9 4 L Local events 10 9 M Message processing 10 9 Messages 8 7 8 7 8 7 7 7 7 7 7 7 N 7 4 O 5 P 12 6 6 14 R 4 5 4 6 S 8 Security 12 12 Sequencing rules 10 9 Server 9 9 9 9
0x37 0x64 0x37 0x39 0x61 0x64 0x37 TIP command line terminator 0x0A LF When the TIP superior transaction manager receives the QUERY TIP command from the TIP subordinate transaction manager, it attempts to locate the transaction in its list of transaction objects by using the superior's transaction identifier. If the TIP superior transaction manager can successfully locate the transaction object, it will respond to the TIP subordinate transaction manager with the QUERIEDEXISTS TIP command. Field Value description TIP command 0x51 0x55 0x45 0x52 0x49 0x45 0x44 0x45 0x58 0x49 0x53 0x54 0x53 "QUERIEDEXISTS" TIP command line terminator 0x0A LF The TIP superior transaction manager will then establish a TIP connection to the TIP subordinate transaction manager as in section 4.1.1. It will send a TIP command, specifying the subordinate's transaction identifier. For this example, the subordinate's transaction identifier is Field Value Value description TIP command 0x52 0x45 0x43 0x4F 0x4E 0x4E 0x45 "RECONNECT"
Index A ABORT TIP ( 50, 64) 35 Abstract data 21 46 31 62 20 20 35 18 B 43 43 44 76 64 20 20 27 C 27 27 18 82 57 COMMIT TIP ( 50, 65) 36 21 13 Create Subordinate Enlistment 44 45 Create Superior Enlistment 58 58 Create Transaction 66 66 76 D Data - abstract 21 46 31 62 E TIP ( 41, 55, 65) Examples 76 70 70 80 F 18 24 G 22 23 8 H 24 triggered events 49 34 64 I 27 20 20 28 77 77 10 Initialization 26 48 33 63 8 L events 56 41 66 M Message processing 27 49 35 64 Messages 20 20 20 19 20 20 20 20 20 19
19 29 29 N 29 10 30 51 36 37 O Overview 21 21 26 27 27 10 10 P 77 73 67 75 67 17 51 37 17 25 56 78 Propagation 71 72 Protocol Details 21 11 20 20 38 49 51 20 20 52 34 20 20 39 Q 53 53 20 20 48 40 R 73 40 30 20 20 54 41 74 10 10 10 17 Rollback Complete ( 61, 68) S Scenarios 76 13 70 26 77 77 77 Sequencing rules 27 49 35 64 76 18 80 10 19 T 24 events 56 41 66 Timers 48 33 63 12 56 24 70 22 22 TIP subordinate transaction manager facet 46 49 48 56 49 46 49 56 48
A 7 C 7 24 E Examples 18 18 F 7 G Getpackage 10 10 10 10 13 10 11 10 13 10 18 5 H HTTP headers 8 8 I 20 6 5 M Message processing 10 14 Messages 9 9 9 9 9 8 8 9 8 9 N 8 6 O Other local events 13 17 6 P 7 7 23 Protocol Details 10 13 Protocol examples 18 18 R References 6 6 7 S Security 20 Sequencing rules 10 14 Setreport 14 14 14 14 14 17 13 14 14 17 14 18 7 T events 13 17
Revision Summary Date Revision History Revision Class Comments 7/14/2016 1.0 New Released new document. 6/1/2017 2.0 Major Significantly changed the technical content. 9/15/2017 3.0 Major Significantly changed the technical content. 12/1/2017 3.0 None No changes to the meaning, language, or formatting of the technical content.
Index A 7 C 7 24 E Examples 18 18 F 7 G Getpackage 10 10 10 10 13 10 11 10 13 10 18 5 H HTTP headers 8 8 I 20 6 5 M Message processing 10 14 Messages 9 9 9 9 9 8 8 9 8 9 N 8 6 O Other local events 13 17 6 P 7 7 23 Protocol Details 10 13 Protocol examples 18 18 R References 6 6 7 S Security 20 Sequencing 10 14 Setreport 14 14 14 14 14 17 13 14 14 17 14 18 7 T Timer events 13 17 24 8
Revision Summary Date Revision History Revision Class Comments 6/30/2015 1.0 New Released new document. 10/16/2015 2.0 Major Significantly changed the technical content. 7/14/2016 3.0 Major Significantly changed the technical content. 3/16/2017 4.0 Significantly changed the technical content. 6/1/2017 4.1 Minor Clarified the meaning of the technical content.
Revision Summary Date Revision History Revision Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.0 Major Significantly changed the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 None Updated the 11/14/2013 release information. 8/8/2013 3.0 Major Significantly changed the technical content. 11/14/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 3.0 None No changes to the meaning, language, or formatting of the
Index A Abstract data model 8 8 5 C 5 13 Client 8 8 8 8 8 8 8 8 D Data model - abstract 8 8 F 5 G 4 H Higher-layer triggered events 8 9 I 11 11 4 Initialization 8 9 4 M Message processing 8 9 Messages 7 N 4 O local events 8 9 5 P 11 5 5 12 R 4 4 4 5 S Security 11 11 Sequencing 8 9 Server 8 9 9 9 9 9 9 9 6 T Timer events 8 9 Timers 8 9 13 7 Triggered events - higher-layer 8 9 V 5 5
Index A Abstract data model RMD 12 12 RMS 15 14 15 11 11 9 B 11 11 C 9 28 D Data model - abstract RMD 12 12 RMS 15 14 15 E 11 Examples message 18 19 20 21 22 23 24 18 18 F 10 G 6 H Header block 11 11 Higher-layer triggered events 13 16 I 26 26 8 Initialization 13 15 6 L Local events RMD 13 13 14 14 RMS 16 17 M Message 18 19 20 21 22 23 24 18 processing 13 16
Revision Summary Date Revision History Revision Class Comments 5/22/2009 0.1 Major First Release. 7/2/2009 0.1.1 Editorial Changed language and formatting in the technical content. 8/14/2009 1.0 Major Updated and revised the technical content. 9/25/2009 1.0.1 Editorial Changed language and formatting in the technical content. 11/6/2009 1.0.2 Editorial Changed language and formatting in the technical content. 12/18/2009 1.0.3 Editorial Changed language and formatting in the technical content. 1/29/2010 2.0 Major Updated and revised the technical content. 3/12/2010 3.0 Major Updated and revised the technical content. 4/23/2010 4.0 Major Updated and revised the technical content.
6/4/2010 4.0.1 Editorial Changed language and formatting in the technical content. 7/16/2010 5.0 Major Updated and revised the technical content. 8/27/2010 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 6.0 Major Updated and revised the technical content. 11/19/2010 6.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 7.0 Major Updated and revised the technical content. 2/11/2011 7.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 8.0 Major Updated and revised the technical content.
5/6/2011 9.0 Major Updated and revised the technical content. 6/17/2011 9.1 Minor Clarified the meaning of the technical content. 9/23/2011 9.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 10.0 Major Updated and revised the technical content. 3/30/2012 10.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 11.0 Updated and revised the technical content. 10/25/2012 12.0 Major Updated and revised the technical content. 1/31/2013 12.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 13.0 Major Updated and revised
the technical content. 11/14/2013 14.0 Major Updated and revised the technical content. 2/13/2014 14.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 15.0 Updated and revised the technical content. 6/30/2015 16.0 Major Significantly changed the technical content. 10/16/2015 16.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 16.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 16.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 12 16 8 C 8 24 D Data model - abstract 12 16 E End node 12 higher-layer triggered events 13 13 14 13 15 message processing 14 14 sequencing rules 14 14 15 12 18 F 8 G 6 H Higher-layer triggered events end node 13 13 14 16 I 21 21 7 Initialization 13 16 6 L 9 events 15 17 M Message processing end node 14 14 name server 17 17 17 16 Messages 9 9 9 syntax 9 9 9 9 N Name server 16 16 16 17 message processing 17 17 17 16 sequencing rules 17 17 17 16 17 16 9 9 7 O 7 P 21 8
12/16/2011 7.0 Major Updated and revised the technical content. 3/30/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 7.1 Clarified the meaning of the technical content. 10/25/2012 7.2 Clarified the meaning of the technical content. 1/31/2013 7.2 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 8.0 None No changes to the meaning, language, or formatting of the
Index A 16 16 11 14 14 14 24 16 C 11 41 13 13 RequestSecurityToken2 19 19 19 20 23 21 23 D 16 16 E Elements 13 RequestSecurityToken2 18 18 18 18 18 19 Events 26 26 26 26 27 F 11 39 G 6 14 I 38 38 8 16 16 6 24 K 25 L 26 26 M Message processing 17 RequestSecurityToken2 24 19 18 17 17 17 Messages 14 14 13 13 13 14 13 13 13 13 N
13 7 O Operations 24 17 8 P 38 11 11 Processing rules 24 25 24 25 24 40 Protocol Details 15 Q 25 R 7 8 7 10 24 27 RequestSecurityToken2 24 complex types 19 19 19 20 23 21 23 elements 18 18 18 18 18 19 messages 17 17 17 17 S Security 38 38 SecurityTokenService server 16 16 26 message processing 17 17 15 processing rules 24 25 24 25 24 sequencing rules 17 17 26 16 Sequencing rules 17 RequestSecurityToken2 24 19 18 17 17 17 Server 16 16 26 17 24 17 26 16 17 15 13 12 Syntax 13 13 T 26 26 16 16 41
Revision Summary Date Revision History Revision Comments 12/5/2008 0.1 Major Initial Availability 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 0.2 Minor Clarified the meaning of the technical content. 8/14/2009 1.0 Major Updated and revised the technical content. 9/25/2009 2.0 Major Updated and revised the technical content. 11/6/2009 2.1 Minor Clarified the meaning of the technical content.
11/19/2010 4.1 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 4.2 Minor Clarified the meaning of the technical content. 9/23/2011 4.2 None No changes to the meaning, language, or formatting
5/15/2014 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 8.0 Major Significantly changed the technical content. 10/16/2015 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 8.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 8.0 None No changes to the meaning, language, or formatting of the technical content.
22 22 23 24 25 24 20 17 17 17 SOAP faults resource server 20 26 23 24 21 22 22 23 24 25 24 ResourceFactory server 20 26 23 24 21 22 22 23 24 25 24 SOAP header processing 20 20 12 Syntax 18 17 16 14 18 13 13 13 13 17 T events resource server ( 26, 34) ResourceFactory server ( 26, 36) server ( 34, 36) Timers resource server ( 20, 27) ResourceFactory server ( 20, 34) server ( 27, 34) 56 13 Types 16 17 U 26 V 17 17 12 12 W 23 24 46 21 22 22 23 24 25 24
Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availability 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 0.2 Clarified the meaning of the technical content. 8/14/2009 1.0 Major Updated and revised the technical content. 9/25/2009 2.0 Major Updated and revised the technical content. 11/6/2009 2.1 Clarified the meaning of the technical content.
11 Resource server 27 27 34 message processing 33 27 27 31 overview ( 19, 27) sequencing rules 33 27 27 31 SOAP faults 20 26 23 24 21 22 22 23 24 25 24 20 34 27 ResourceFactory server 34 34 36 overview ( 19, 34) sequencing rules 34 34 SOAP faults 20 26 23 24 21 22 22 23 24 25 24 20 36 34 38 40 S 18 Security 45 45 Sequencing rules resource server 33 27 27 31 ResourceFactory server 34 34 server ( 27, 34) Server abstract data model ( 27, 34) 34 33 27 initialization ( 27, 34) local events ( 34, 36) message processing ( 27, 34) 31 sequencing rules ( 27, 34) timer events ( 34, 36) timers ( 27, 34) Server - resource abstract data model ( 19, 27) initialization ( 20, 27) local events ( 26, 34) message processing 33 27 27 31 overview ( 19, 27) sequencing rules 33 27 27 31 timer events ( 26, 34) timers ( 20, 27) Server - ResourceFactory abstract data model ( 19, 34) initialization ( 20, 34) events ( 26, 36) message processing 34 34 overview ( 19, 34) SOAP faults 20 26 23 24 21 22 22 23 24 25 24 20 timer events ( 26, 36) timers ( 20, 34) Server- resource SOAP faults 20 26 23
24 21 22 22 23 24 25 24 20 17 17 17 SOAP faults resource server 20 26 23 24 21 22 22 23 24 25 24 ResourceFactory server 20 26 23 24 21 22 22 23 24 25 24 SOAP header processing 20 20 12 Syntax 18 17 16 14 18 13 13 13 13 17 T Timer events resource server ( 26, 34) ResourceFactory server ( 26, 36) server ( 34, 36) Timers resource server ( 20, 27) ResourceFactory server ( 20, 34) server ( 27, 34) 56 13 Types 16 17 U 26 V 17 17 12 12 W 23 24 46 21 22 22 23 24 25 24
The Session object's State moves to Ready. The Session object can be used by protocols to create connections to the peer. Handling the Accept Header The following sequence defines the required actions following the activation of the session: The server MUST listen on transports according to information that was exchanged with the client in earlier steps of the protocol. The client MUST attempt to connect to the server on all the transports that the server is listening on. The server chooses the best connection and accepts it. On connection establishment, the client MUST send an Accept Header (section ) to the server. On receipt of the Accept Header, the server MUST validate the SessionID from the Accept Header by comparing it to the ReplyChannelID that it received from the client in the Session Activation message (section ). If the IDs match, the server MUST send the Accept Header back to the client. If the IDs do not match, the server MUST abort the connection. The client MUST validate the Accept Header received from the server by comparing it to the Accept Header it sent before. If the Accept Headers the negotiation is complete; otherwise, the client MUST abort the connection. Timer Events The following timer events are associated with the timers defined by this protocol (section ). SessionProtocolTimer: If this timer fires when the associated Session object (section ) State is WaitingForAck or WaitingForTransmit, the object transitions to the Terminated state. This Session object is not usable by higher-level protocols. If this timer fires when the Session object State is Ready, the timer is ignored. OOBConnectorProtocolTimer: If this timer fires when the associated OOB Connector object (section ) State is WaitingForAck or WaitingForTransmit, the object State transitions to Incomplete. If this timer fires when the OOB Connector object State is any other value, the timer is ignored. OOBConnectorKeepAliveTimer: If this timer fires before the associated OOB Connector object State transitions out of Incomplete, the reference logged at initialization SHOULD be released. If there are no other references to the object, the object SHOULD be destroyed. SessionFactoryKeepAliveTimer: An independent timer for each Session Factory object (section ), which is started when a Session Factory object is created. If it fires before a client takes ownership of the object, the Session Factory object SHOULD be deleted. Other Local Events None.
Index A 13 14 11 C 11 61 E 15 G 5 I 59 59 8 5 M Messages 13 13 14 14 15 15 15 15 22 22 25 25 25 25 26 26 27 27 28 28 29 29 31 31 13 N 7 O 15 22 8 P 59 11 11 60 R 7 8 7 10 25 S Security 59 59 25 26 27 28 29 31 12 T 61 13 V 11
2 Degree - High demand - Greater flexibility - Demand with high degree - Flexibility with greater degree - Yêu cầu cao - Trường hợp phức tạp hơn 3 Manner - Fixed spot - Manual welding - The spot is fixed - Welding with mostly operation - Điểm cố định - Hàn thủ công 4 Order - Final product - Following steps - Product at final order - at following order - Sản phẩm cuối cùng - Những bước sau 5 Standard Accurate fixing Fixing has to be accurate Cố định chính xác Minimum requirement Correct orientation Requirement is minimum Orientation has to be correct Yêu cầu tối Đúng hướng 6 Time Recent research Research in recent time Nghiên cứu gần đây 7 Structure - objects - Short welds - Objects with dimensions - Welds with short structure - Đối tượng/ vật thể ba chiều - Những mối hàn ngắn Complex form with more than an Adj and a Noun Besides the simple form, has been occurrence of NPs which consists not only an adjective and a noun but also more constituents. Their structure can be classified into these following types: No Structures NPs Target language 1 Adj+Adj+N Innovative new application Ứng dụng mới và tiến bộ Poor mechanical reliability Kém bền cơ học
Revision Summary Date Revision History Revision Class Comments 10/16/2015 1.0 New Released new document. 7/14/2016 2.0 Significantly changed the technical content. 9/26/2016 3.0 Major Significantly changed the technical content. 6/1/2017 4.0 Major Significantly changed the technical content.
Messages Transport The HTTPS protocol MUST be used as the transport. Common Data Types HTTP Headers The messages exchanged in the OAuth 2.0 Protocol Extensions for Broker Clients use the following HTTP headers in addition to the existing set of standard HTTP headers. Header Description This optional header can be used by the client to specify a primary refresh token when contacting the authorization endpoint. This optional header can be used by the client to prove the identity of the device from which the request is sent when contacting the authorization endpoint. x-ms-RefreshTokenCredential The x-ms-RefreshTokenCredential HTTP header is optional and can be specified by the client role of the OAuth 2.0 Protocol Extensions for Broker Clients. This header is used to pass a previously obtained primary refresh token to the authorization endpoint of the . The primary refresh token can be used by the server to authenticate the user and the device on which the client runs when processing the authorization request. The value of the x-ms-RefreshTokenCredential HTTP header MUST be a signed . The signed JWT format is defined in . The format for the x-ms-RefreshTokenCredential header is as follows. String = *(%x20-7E)
Index A Abstract data model 12 16 8 Authorization endpoint 23 23 23 C 8 32 Client 12 13 12 13 15 13 16 12 13 15 13 16 12 D Data model – abstract 12 16 10 10 10 E 10 Examples 27 27 28 27 F 9 G 5 H Higher-layer triggered events 13 16 10 10 10 I 30 30 7 Initialization 12 16 5 L Local events 16 26 M Message processing 13 15 13 server 23 17 Messages 10 N 6 O Oauthbrokerextension client 12 13 12 13 16 16 12 Oauthbrokerextension server 16 16 16 16 26 26 16 7 P 30 8 8
Message Processing Events and Sequencing Rules Added Logout endpoint (/logout) resource and OIDCSession reference. Major OpenID Provider Configuration endpoint Updated product version information regarding applicability of protocol. major 3.1.5.3 OpenID Provider Configuration endpoint information for OIDC client-role support in Windows 10 v1607. Major Logout endpoint (/logout) Added section for the Logout endpoint (/logout) resource. Major GET section with content. Major Request Body Added section with content. Major Response Body Added section with content. Major Processing Details Added section with content. Major Message Processing Events and Sequencing Rules Logout endpoint (/logout) resource and OIDCSession reference. Major Logout endpoint (/logout) Added section for the Logout endpoint (/logout) resource. Major GET Added section with content. Major Request Body Added section with content. Major Response Body Added section with content. Major Processing Details Added section with content. Major Appendix A: Product Behavior Updated product version information regarding applicability of protocol. major
Index A Abstract data model 11 14 8 7 C 8 24 9 Client 11 11 11 11 14 11 11 14 11 D 9 E Examples 21 21 21 Extensions 9 9 F 8 G 5 H 9 Higher-layer triggered events 11 15 I 22 22 6 Initialization 11 15 5 L 8 M 9 Message processing 11 15 Messages 9 N 6 O Openid connect extension client 11 11 11 11 14 14 11 Openid connect extension server 14 15 15 15 20 19 14 Other local events 14 20 7 P 9 22 7 7 23 Protocol Details 11 11 14 14 Protocol examples 21 21 8 7 Q
RpcAsyncGetPrinterData retrieves printer data from a specified printer or print server. Opnum 16 RpcGetPrinterData RpcAsyncGetPrinterDataEx retrieves configuration data for the specified printer or print server. Opnum 17 RpcGetPrinterDataEx RpcAsyncSetPrinterData sets the configuration data for a printer or print server. Opnum 18 RpcSetPrinterData RpcAsyncSetPrinterDataEx sets the configuration data for a printer or server. Opnum 19 RpcSetPrinterDataEx RpcAsyncClosePrinter RpcAsyncClosePrinter closes a handle to a printer object, server object, job object or port object, opened by calling RpcAsyncOpenPrinter or RpcAsyncAddPrinter. Opnum 20 RpcClosePrinter RpcAsyncEnumPrinterData enumerates configuration data for a specified printer. Opnum 27 RpcEnumPrinterData RpcAsyncEnumPrinterDataEx enumerates all value names and data for a specified printer and key. Opnum 28 RpcEnumPrinterDataEx RpcAsyncEnumPrinterKey enumerates the subkeys of a specified key for a specified printer. 29 RpcEnumPrinterKey RpcAsyncDeletePrinterData deletes a specified value from the configuration of a specified printer. Opnum 30 RpcDeletePrinterData RpcAsyncDeletePrinterDataEx deletes a specified from the configuration data of a specified printer, which consists of a set of named and typed values stored in a hierarchy of registry keys. Opnum 31 RpcDeletePrinterDataEx RpcAsyncDeletePrinterKey deletes a specified key and all of its subkeys from the configuration of a specified printer. 32 RpcDeletePrinterKey
Index A Abstract data model 87 25 91 90 91 90 17 B 86 C 18 15 128 Client 87 88 89 88 88 89 88 19 14 24 D Data - abstract 87 25 19 19 E 91 92 92 91 20 Events 89 87 89 87 Examples 91 90 91 90 91 92 92 91 90 93 93 F 18 70 70 98 G 7 I 98 97 97 12 Initialization 88 26 Interfaces - server 25 7 25 J 73 73 84 84 76 76 L Local events 89 87
M 13 Message processing 88 26 Messages 19 19 19 Methods 86 70 73 84 76 68 33 48 62 79 65 N 12 23 23 O 13 P 97 97 68 68 17 17 14 15 13 33 33 48 48 62 62 79 79 65 65 121 R 93 93 12 12 12 17 79 70 75 69 46 64 36 50 65 41 58 44 71 85 69 47 37 43 43 52 52 61 45 43 67 78 78 72 86 74 68 47 63 41 42 51 42 46 67 66 57 71 74 84 38 38 39 50 51 60 66 83 53 87 36 45
Revision Summary Date Revision History Revision Class Comments 9/23/2011 0.1 New Released new document 12/16/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 Major Significantly changed the technical content. 8/8/2013 3.0 Major Significantly changed the technical content. 11/14/2013 3.0 None No changes to the meaning,
language, or formatting of the technical content. 2/13/2014 4.0 Major Significantly changed the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 5.0 None No changes to the meaning, language, or formatting of the technical content.
Relationship to Protocols and Other Structures The data structure is built on and relies on the Microsoft implementation of DPWS. For more information, see . Because the number of resources on a computer and the data associated with them can increase over time, clients also implement the Size Negotiation Extension as specified in to be able to retrieve resources completely.<1> The HomeGroup Protocol , which is used to create a trust relationship that facilitates the advertising and publishing of content between machines in a home environment, and the Shell Publishing data structure use the Publication Services data structure to advertise their content and resources. Applicability Statement Use of this data structure is suitable for clients if: The is a compliant DPWS implementation. The client requires communication with the DPWS representation of a computer and its resources. The client supports the Size Negotiation Extension and can receive messages longer than 32767 octets ( section 2.1.5). Use of this protocol is suitable for service implementations if: The will represent itself as a DPWS-compliant computer on the network. The service supports the Size Negotiation Extension [MS-DPWSSN] and can send messages longer than 32767 octets. Versioning and Localization This data structure is not versioned and it does not explicitly support localization. Vendor-Extensible Fields This data structure does not define any additional vendor-extensible fields.
1 17 125-KB content example ( 17, 17) 18 22 19 20 23 A 8 B 9 C 27 15 9 9 Content validation - security considerations ( 25, 25) 14 11 D 9 Details 9 9 9 9 9 9 25 E 17 17 125-KB content ( 17, 17) 18 22 19 20 23 17 18 19 20 22 23 F 25 8 G 5 I 25 7 5 K 9 L 8 N 7 O 7 P 26 R
1 17 125-KB content example ( 17, 17) 18 22 19 20 23 A 8 B 9 C 27 15 9 9 Content validation - security considerations ( 25, 25) 14 11 D 9 Details 9 9 9 9 9 9 25 E 17 17 125-KB content ( 17, 17) 18 22 19 20 23 17 18 19 20 22 23 F 25 8 G 5 I 25 7 5 K 9 L 8 N 7 O 7 P 26 R 7 7 7 7 S Security content block validation ( 25, 25) 25 25 9 14 SegmentDescription packet ( 13, 16) 9 Structures 9 9 T 27 V 8 17 18
Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availability 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.2 Clarified the meaning of the technical content. 4/10/2009 0.3 Minor Clarified the meaning of the technical content. 5/22/2009 0.4 Minor Clarified the meaning of the technical content. 7/2/2009 1.0 Updated and revised the technical content. 8/14/2009 1.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 1.1 Minor Clarified the meaning of the technical content. 11/6/2009 2.0 Major Updated and revised the technical content. 12/18/2009 2.0.1 Editorial Changed language and formatting
in the technical content. 1/29/2010 2.1 Minor Clarified the meaning of the technical content. 3/12/2010 3.0 Updated and revised the technical content. 4/23/2010 3.1 Minor Clarified the meaning of the technical content. 6/4/2010 4.0 Major Updated and revised the technical content. 7/16/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 4.0 None No changes to the meaning, language,
12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 6.0 Major Updated and revised the technical content. 7/12/2012 7.0 Major Updated and revised the technical content. 10/25/2012 8.0 Updated and revised the technical content. 1/31/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 9.0 Major Updated and revised the technical content. 11/14/2013 9.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 9.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 9.0 None No changes to the
15 17 11 11 14 16 16 N 11 8 O Operations 20 9 P 25 9 9 Probe message 12 20 21 21 ProbeMatch message 12 19 22 23 27 Protocol Details 18 R 8 9 8 9 S 14 15 15 Security 25 25 25 Sequencing 18 20 Server 19 20 20 20 20 20 18 20 20 20 20 19 17 10 Syntax 11 11 T Timer events 19 20 Timers 18 19 29 11 Types 17 17 14 V 10 10 W 26 X 16
Protocol Details Common Details Abstract Data Model The abstract data model follows what is specified in . Timers None. Initialization During initialization, the -compliant random-number generator for keys and nonces is initialized. Higher-Layer Triggered Events None. Message Processing Events and Sequencing Rules In addition to the required ( section 3.1.1) and recommended ([RFC4556] section 3.1.2) algorithms, PKCA supports the rc2-cbc ([RFC4556] section 3.1.4) algorithm. An implementer SHOULD specify ([RFC4556] section 3.1.2) as the default algorithm.<13> PKCA does not implement the id-pkinit-san algorithm ([RFC4556] section 3.2.2). PKCA supports PKInit freshness extensions .<14> Client The Kerberos client SHOULD send only a PA-PK-AS-REQ pre-authentication data identifier.<15><16> Kerberos clients can process either the PA-PK-AS-REP_OLD or the PA-PK-AS-REP pre-authentication data identifier in the reply, but not both.<17> For computer AS-REQ, PKCA clients SHOULD fail unless all of the following conditions are met.<18> The computer certificate contains: subjectAltName (SAN) DNSName field: <computer name>.<DNS domain name> where <computer name> matches the computer name and <DNS domain name> matches the computer’s DNS domain name. Enhance Key (EKU): id-pkinit-KPClientAuth (1.3.6.1.5.2.3.4) or TLS/SSL Client Authentication (1.3.6.1.5.5.7.3.2). The KDC certificate contains: SAN DNSName field: the DNS name of the domain EKU: (1.3.6.1.5.2.3.5)
Index A 13 9 9 C 9 25 D 13 E Examples 19 16 smart cards 16 18 F 9 9 G 5 H 13 I 20 20 20 8 13 5 L 15 M Message processing 13 14 13 Messages 12 10 11 12 10 10 N 19 7 O 8 P 12 12 11 10 11 12 12 10 20 20 8 8 21 R 7 8 7 8
Index A 13 9 9 C 9 24 D 13 E Examples 19 16 smart cards 16 18 F 9 9 G 5 H 13 I 20 20 20 8 13 5 L 15 M Message processing 13 14 13 Messages 12 10 11 12 10 10 N 19 7 O 8 P 12 12 11 10 11 12 12 10 20 20 8 8 21 R 7 8 7 8 S Security 20 20 Sequencing rules 13 14 13 Smart cards 16 18 9 10 T 15 13 24 10 13 V 9 9
Revision Summary Date Revision History Revision Class Comments 1/29/2010 0.1 Major First Release. 3/12/2010 1.0 Major Updated and revised the technical content. 4/23/2010 1.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 1.0.2 Editorial Changed language and formatting in the technical content. 7/16/2010 1.1 Minor Clarified the meaning of the technical content. 8/27/2010 1.2 Clarified the meaning of the technical content. 10/8/2010 1.2 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 2.0 Major Updated and revised the technical content. 1/7/2011 2.0 None No changes to the meaning, language, or formatting
or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 6.0 Major Updated and revised the technical content. 11/14/2013 6.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content.
6/30/2015 7.0 Major Significantly changed the technical content. 10/16/2015 8.0 Significantly changed the technical content. 7/14/2016 9.0 Significantly changed the technical content. 6/1/2017 10.0 Significantly changed the technical content.
Index A Abstract data model 44 41 31 13 C 13 10 54 D Data model - abstract 44 41 31 E 27 50 50 Examples 50 50 F 13 G 7 Group connect authenticator 44 45 45 local events 48 49 48 message processing 47 45 45 46 47 45 44 sequencing rules 47 45 45 46 47 45 48 45 15 Group connect requestor 41 41 41 events 44 44 43 message processing 41 42 42 42 43 40 sequencing rules 41 42 42 42 43 43 41 11 10 H 15 15 Higher-layer triggered events 45 41 peer 36 34 35 34 37 37 I 52 52 9 Initialization 45 41 32 7 J 11 L
Local events group connect authenticator 48 49 48 group connect requestor 44 44 43 peer 40 40 40 record 37 38 M 21 21 Message processing group connect authenticator 47 45 45 46 47 45 group connect requestor 41 42 42 42 43 37 Messages 27 15 15 15 21 16 28 15 17 14 22 22 18 18 28 18 23 14 25 XML 30 28 28 16 16 16 N 8 O 28 Overview 10 11 10 11 10 10 10 11 10 9 12 9 P 10 52 15 17 Password packet ( 17, 20) Peer 31 higher-layer triggered events 36 34 32 35 34 37 37 32 local events 40 40 40 record 37 38 37 31 37 37 32 10 14 10 12 12 53 Protocol Details 31 R 22 22
Record subprotocol 11 11 11 12 12 22 Records 21 18 18 18 8 9 8 12 Roles 28 10 S Security 52 52 18 18 Sequencing rules group connect authenticator 47 45 45 46 47 45 connect requestor 41 42 42 42 43 37 23 23 13 T Timer events 48 43 37 Timers 45 41 32 54 14 Triggered events 45 41 peer 36 group 34 32 35 34 37 37 V 13 13 X 25 25 XML 30 28 28 Y 16 16
technical content. 3/30/2012 7.0 Major Updated and revised the technical content. 7/12/2012 7.1 Minor Clarified the meaning of the technical content. 10/25/2012 7.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 7.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 8.0 Major Updated and revised the technical content. 11/14/2013 8.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 8.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model server ( 25, 60) 60 25 11 B 67 67 C 11 77 13 13 14 D Data model - abstract server ( 25, 60) 60 25 13 13 65 65 67 66 66 E 14 Events local - server ( 60, 63) - server ( 60, 63) Examples 67 65 65 67 66 64 64 65 65 65 65 64 64 66 66 67 F 12 69 G 6 I 69 68 68 10 Initialization server ( 26, 61) 61 26 64 64 Interface 25 26 26 25 26 26 Interfaces - server 60 25 6 L Local events server ( 60, 63) 63 60 M Message processing server ( 26, 61) 61 26 Messages 13 13 16 13 13 13 13 Methods 44 63 45 52 39 58 38 54
45 52 39 58 38 54 52 42 55 51 46 28 49 53 48 31 56 57 43 61 33 50 sequencing rules ( 26, 61) events ( 60, 63) timers ( 26, 61) 60 25 13 12 16 T events server ( 60, 63) 63 60 Timers server ( 26, 61) 61 26 77 13 13 13 13 67 67 V 12 11 W WINS RPC common messages 14 14 14 16 60 63 63 winsi2 server 60 61 61 61 61 25 25 26 60 26 25 26 60 26 14 16 19 16 23 23 15 14 15 17 22 23 21 19 16 24 19 15
Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 Updated and revised the technical content. 4/3/2007 1.1 Clarified the meaning of the technical content. 5/11/2007 1.2 Minor Addressed EU feedback 6/1/2007 1.3 Minor Clarified the meaning of the technical content. 7/3/2007 1.3.1 Editorial Changed language and formatting in the technical content. 8/10/2007 1.3.2 Editorial Changed language and formatting in the technical content. 9/28/2007 1.3.3 Editorial Changed language and formatting in the technical content. 10/23/2007 2.0 Major Converted document to unified format. 1/25/2008 2.0.1 Editorial Changed language and formatting in the technical content.
3/14/2008 2.0.2 Editorial Changed language and formatting in the technical content. 6/20/2008 2.1 Minor Clarified the meaning of the technical content. 7/25/2008 2.2 Clarified the meaning of the technical content. 8/29/2008 2.2.1 Editorial Changed language and formatting in the technical content. 10/24/2008 2.2.2 Editorial Changed language and formatting in the technical content. 12/5/2008 3.0 Updated and revised the technical content. 1/16/2009 3.0.1 Editorial Changed language and formatting in the technical content. 2/27/2009 3.0.2 Editorial Changed language and formatting in the technical content. 4/10/2009 3.0.3 Editorial Changed language and formatting
in the technical content. 5/22/2009 4.0 Updated and revised the technical content. 7/2/2009 5.0 Major Updated and revised the technical content. 8/14/2009 5.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 5.1 Minor Clarified the meaning of the technical content. 11/6/2009 5.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 6.0 Major Updated and revised the technical content. 1/29/2010 6.1 Minor Clarified the meaning of the technical content. 3/12/2010 6.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 6.1.2 Editorial Changed language and formatting
meaning, language, or formatting of the technical content. 3/25/2011 7.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 7.1 Clarified the meaning of the technical content. 9/23/2011 7.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 8.0 Major Updated and revised the technical content. 3/30/2012 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 8.0 None No changes to the
the technical content. 10/16/2015 11.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 11.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 11.0 None No changes to the meaning, language, or formatting of the technical content.
Index A 14 9 C 9 21 15 13 D 14 13 E 13 18 F 9 G 5 H 14 I 19 19 7 14 5 L 17 M 14 Messages 10 12 10 10 N 6 O 7 P 19 9 9 20 Protocol Details 14 R 6 7 6 8 S 13 Security 19 19 14 Server 15 16 SSL_CERT_LOGON_REQ ( 15, 15) 10 10 16 12 12 9 10 T 16 14 21 10 10 14 V 9 9
Progressive Entropy Encode and Decode 72271 : Added examples for the process of entropy encoding and decoding for a tile at various quality levels. Y New content added. Encode #2 at 50% 72628 : Changed the results in bytes example. Y Content update. Appendix A: Product Behavior Added Windows 10 to applicability list. Y Content update.
Index A Abstract data model client ( 65, 83) server ( 65, 73) 13 C 13 124 Client abstract data model ( 65, 83) higher-layer triggered events ( 65, 86) initialization ( 65, 86) 65 message processing 65 89 89 87 89 89 88 86 88 88 87 88 88 88 87 88 87 87 86 86 90 sequencing 65 89 89 87 89 89 88 86 88 88 87 88 88 88 87 88 87 87 86 86 events ( 65, 89) timers ( 65, 85) D Data model - abstract client ( 65, 83) server ( 65, 73) 64 E 64 F 13 G 8 H Higher-layer triggered events client ( 65, 86) server ( 65, 74) I 122 122 9 Initialization client ( 65, 86) server ( 65, 74) 8 L events 65 65 M