Abstract
This document lists the design principles, scope and requirements for XML Key
Management specifications and trust server key management implementations. It
includes requirements as they relate to the key management syntax,
processing, security and coordination with other standards activities.
Status of this Document
This is the XML Encryption Requirements Note from the
XKMS (
Activity Statement).
This version represents the consensus of the Working Group since
March
2002 on the requirements for the
XML Key Management Specification .It
has also underwent minor changes resulting from the
Last Call
(issues) ending on
May 23 2003. The Working Group has no plans
to update the content of this document; it serves to document the agreed upon
set of requirements the specification will address.
This document is a NOTE made available by the W3C for archival purposes.
Publication of this Note by W3C indicates no endorsement by W3C or the W3C
Team, or any W3C Members. A list of current W3C technical reports and
publications, including Recommendations, Working Drafts, and Notes can be
found at http://www.w3.org/TR/.
Please send comments to the editors<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and
cc: the working group mailing list<EMAIL_ADDRESS>(public archive).
A list of current W3C working drafts can be found at http://www.w3.org/TR/.
Patent disclosures relevant to this specification may be found on the
Working Group's patent
disclosure page in conformance with W3C policy.
Table of Contents
- Introduction and Terminology
- Requirements
- Universality and Usability
- Security Model
- Trust Server
- Protocol Capabilities and
Format
- Objects and Processing
- Out of Scope
- Coordination
- Intellectual Property
- References
1 Introduction and Terminology
XML-based public key management should be designed to meet two general goals.
The first is to support a simple client's ability to make use of
sophisticated key management functionality. This simple client is not
concerned with the details of the infrastructure required to support the
public key management but may choose to work with X.509 certificates if able
to manage the details . The second goal is to provide public key
management support to XML applications that is consistent with the XML [XML] architectural approach. In particular, it is a goal
of XML key management to support the public key management requirements of
XML Encryption [XML Encryption], XML
Digital Signature [XMLDSIG] and to be consistent
with the Security Assertion Markup Language [SAML].
This specification provides requirements for XML key management consistent
with these goals, including requirements on the XML key management
specification, server implementations and the protocol messages.
XML key management services will primarily be of interest to clients that
intend to communicate using XML-based protocols bound to SOAP. It may be that
such clients will not have sufficient ASN.1 capabilities in which case the
benefits of offloading the parsing of certificates and other traditional PKI
structures (e.g. CRLs or OCSP responses) is clear. Clients which possess such
capabilities and have no preference to work with XML-based protocols may opt
to use non-XML-based protocols defined by PKIX, for example.
The following terms and phrases are used throughout the remainder of this
draft.
- 4-Corner Model
- A processing and/or trust environment where each end-entity interacts
with a single trusted point of contact, and each such contact has a
peerwise trust relationship with all other contacts[4-corner model].
- Asynchronous exchange
- An exchange where the synchronous service response is incomplete,
requiring the client to perform a subsequent request at some later
time. When client registration requires time consuming checks it is
more practical for a client to return at a later time for a completed
response, for example. For XML Key Management all requests producing
asynchronous results MUST produce a synchronous response status
indicating an incomplete response, such as "Pending", for example. Such
responses might also provide a URL for the client to check back to
obtain the complete response at a later time.
- Client
- An application that makes requests of a service. The concept of a
"client" is relative to a service request; an application may have the
role of client for some request and service for others.
- Deferred Request Authentication
- A mechanism to allow a client to verify that the server processed the
correct request. The client may verify the server response, for
example, by comparing the elements returned in the response, or
comparing a digest of the request with a digest returned in a secured
response. This ensures that an attacker has not diverted or otherwise
changed portions of a request. For example, a client request might be
directed to a particular URI so that a specific policy will be enforced
as part of the service processing the request. Inclusion of the URI in
the response ensures that the expected server policy was followed and
that the request was conveyed correctly.
- Key
- An input parameter that varies the transformation performed by a
cryptographic algorithm [RFC2828]. For the
purpose of XML key management we specifically mean public keys and
private keys as used in a public key cryptosystem.
- Key Management
- Key management relates to the management of a public key's validity
status over its lifetime. Typically, operations are defined for
controlling the validity (e.g. register, revoke) and querying the
validity.
- Key Binding
- A property associating additional information with a public key. This
might be used to convey status and validity period information for key
validity queries or used to convey private key information as part of a
registration request or response.
- Key Location
- A service that locates and returns a public key given identifying
information for the key. Generally the request will include a KeyInfo
element containing information sufficient for the service to locate the
key. A common example is to provide the key name.
- Key Name
- A property defined in the XML Digital Signature recommendation,
allowing a name to be associated with a key within a <ds:KeyInfo>
element. The Key Name property is not required and when associated with
a key in registration is not required to be a unique identifier for
that key.
- Key Validation
- A service that verifies the binding of information to a public key
and also determines the current status of that binding, if appropriate
or possible for the information in question. For example, key
validation [SECGL] may be performed based
on elements secured to a public key in an X.509 certificate as outlined
in PKIX [RFC 2459].
- Pass Phrase Key
- A key derived from a pass phrase may be used for authentication in
circumstances where public key based authentication is not
possible.
- Payload Security
- The XKMS request or response XML obtains integrity and/or
confidentiality by being signed using an XML digital signature and/or
encrypted using XML Encryption. The signature itself may be placed in
the SOAP header when using a SOAP binding, for example. This is in
contrast to transport integrity, where a SOAP message containing the
XKMS payload is secured using TLS or other transport security
mechanisms.
- Proof of Possession (POP)
- Performing an action with a private key to demonstrate possession of
it. An example is to create a signature using a registered private
signing key to prove possession of it.
- Service
- An application that provides computational or informational resources
on request. A service may be provided by several physical servers
operating as a unit.
- TLS
- Transport Layer Security, a protocol layer designed to provide
message integrity and confidentiality for a message during transit
between two endpoints. An earlier version is known as SSL, the Secure
Socket Layer [TLS].
- Trust Service
- A service that is capable of registering public keys and/or providing
key information services, including key validation and location.
- Web Service
- A service that is accessible by means of messages sent using standard
web protocols, notations and naming conventions, including XML Protocol
(or until XML protocol is standardized, SOAP). Web service may also
imply the use of ancillary mechanisms, such as WSDL [WSDL ] and UDDI [ UDDI ]
for defining Web services interfaces.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
are to be interpreted as described in RFC 2119. [RFC
2119].
2 Requirements
Familiarity with the W3C XKMS Note [XKMS Note]
is assumed for this section.
2.1 Universality
and Usability
- Request and response messages SHOULD be extensible.
- All messages and data structures MUST be specified in XML using XML
Schema [XMLSchema]. Schema validation is
not required of applications or trust server implementations. Clients and
servers are not required to implement a general purpose XML parsing
capability. Note that common PKIX structures such as X.509 certificate
and CRL structures may be embedded as binary (base64 encoded) data within
XML elements as indicated by the KeyInfo definition [ XMLDSig ].Applications which expect to process
X.509 certificates will require ASN.1 and certificate processing
capabilities.
- Use of optional features is discouraged. Optional features SHOULD be
justified in the specification.
- The specification MUST provide a binding to XML Protocol (SOAP 1.2),
provided that the SOAP 1.2 specification has reached Candidate
Recommendation (CR) status prior to the XKMS WG completing its work. In
this case the specification SHOULD also provide a binding to SOAP 1.1
(for interoperability purposes). If SOAP 1.2 has not reached CR status
then the specification MUST provide a binding to SOAP 1.1. The XKMS
specification SOAP binding is required to profile SOAP for
interoperability, including use of document literal encoding. [ SOAP ] [XMLProtocol]
[List( Blair
Dillaway)].
- XKMS services MUST implement SOAP 1.2 once that specification has
achieved Candidate Recommendation status.
- The design MUST be transport protocol agnostic - SOAP content may be
carried over different transport protocols. [List( Blair
Dillaway)]
- The specification MUST ensure the correspondence of responses with
requests, aiding correlation of asynchronous responses with requests and
also ensuring that the appropriate request was processed.
- The specification MUST NOT require clients to implement traditional PKI
processing such as ASN.1, certificate revocation or certificate chain
processing. Usability and simplicity are paramount to enable clients to
obtain the benefits of public key technology. {Reuters} [XKMSPositionPapers].
- The specification MUST clearly define the set of responses expected by
a client for each type of request and clearly define the expected actions
of a client receiving those responses. For example, responses that apply
to a validation request will not necessarily apply to a registration
request.
- Underlying PKI or other trust server mechanisms SHOULD be transparent
to the client, with exception that credentials such as X.509 certificates
may be explicitly retrieved. This should leverage the <ds:KeyInfo>
work. {IAIK position} [XKMSPositionPapers]
- A mechanism for versioning SHOULD be defined. If a good reason exists
for an approach other than XML Namespaces, it MUST be justified.
- Server support for legacy formats such as PKCS#10 and PKCS#7 SHOULD be
defined, but their support is OPTIONAL. An example use is in smartcard
personalization or bulk registration applications.
- An XKMS server SHOULD be able to pass requests to another XKMS server
for processing with minimal overhead. The definition of server chaining
and referral messages are out of scope, but such mechanisms SHOULD NOT be
precluded. An example of meeting this requirement is to provide support
for a 4 corner application model [4-corner
model].
- Use of XML elements with unbounded maxOccurs schema values SHOULD be
justified in the specification.
2.2 Security
Model
[Data Confidentiality and Integrity]
- Every trust service MUST support TLS and payload security. Trust
services MAY support secure networks such as IPSec for integrity and
confidentiality. Every client MUST support at least one of these
mechanisms appropriate for the servers contacted.
- Payload security MUST be based on XML Encryption and XML Signature and
MAY be usable to secure the body content of SOAP messages. Individual
elements of XML Key Management protocol messages SHOULD not be encrypted,
except for the Private element which is a special case (since it
transports a private key) and MUST be encrypted using XML Encryption.
Exclusive Canonicalization SHOULD be used as the XML Digital Signature
canonicalization method.
- The specification MUST define how XML Key Management messages and
transactions can be secured (for confidentiality and integrity) where
payload security is not implemented. In particular, the specification
MUST define how transport layer security such as SSL/TLS is to be used.
The specification MUST profile TLS, by requiring a subset of the defined
cipher suites to be supported, for example.
- The security section of the specification MUST recommend that at least
one form of integrity and confidentiality protection of service requests
and responses be used by applications, either transport security or
payload protection.
[Transaction Security]
- All trust server responses MUST include a digest of the
request payload and the request URL.
- Techniques for protection against replay attacks MUST be defined in the
security considerations section. Specific techniques SHOULD be defined,
such as nonce, origination time, and serial numbers in requests, for
example.
[Trust Service Trust]
- Trust services MUST make their public keying information
(i.e. the public keys to be used to authenticate the trust service)
publicly available in at least the <ds:KeyValue> format, since that
is the minimal [XMLDSIG] key
representation.
- The specification MUST support different means of establishing a trust
relationship with the trust service, and not be limited to client caching
of a trusted certificate or trusted key. Other possibilities include key
establishment using a shared secret, for example.
[Authentication]
- The specification MUST allow use of user-generated pass
phrases as a means of authenticating requests in lieu of access to a
valid private key. binding.
- The specification MUST provide a means of employing a secret, agreed
out-of-band, between the registration service and end-user as a means of
authorizing a registration action. [List( Blair
Dillaway)]
[Privacy]
- The specification MUST state in the security section that
concerns over the privacy of registration information may be addressed
through server P3P privacy policies. The definition and retrieval
mechanisms for these policies are defined in the P3P recommendation and
do not require definition in the XKMS specifications [P3P].
[Security considerations]
- The specification MUST include a discussion of potential
vulnerabilities and recommended practices when using the defined
processing model in a larger application context. While it is impossible
to predict all the ways the specification may be used, the discussion
MUST alert users to ways in which potentially subtle weaknesses might be
introduced. At a minimum, security issues arising from known plain-text
and data length information MUST be addressed.
2.3. Trust Server
- A server MAY be deployed that implements a subset of XKMS service
functionality, such as Locate but not Validate, for example.
- Selection of differently configured trust services SHOULD use standard
HTTP binding techniques such as URLs, rather than requiring the XKMS
protocol to define this functionality. For example, a URL may be used to
define access to a trust service and possibly distinguish the underlying
technologies (e.g. PGP, X509 etc.).
- The specification MUST define asynchronous registration responses.
- More generally, the specification MUST allow asynchronous transport of
both registration requests and responses, but not require this of trust
servers.
2.4. Protocol
Capabilities and Formats
[Registration Capabilities]
- The specification MUST describe how to register key information, and in
particular, associate additional information with the public key. A
public key pair may be generated at a client and the public key
registered with the trust service; a key pair may be generated at the
trust service and the private key may be delivered to the client.
- The specification MUST describe how to revoke a registered key
binding.
- The specification MUST describe how to update registered public key
information. Reasons include the need for atomic transactions and the
ability to update a portion of a defined key binding.
- The specification MUST describe how to support a user recovering their
own private key, such as might be needed to restore a lost private
encryption key. This requirement does not imply any form of key escrow as
used in the sense of mandated government access to private keys.
- The specification MUST describe how to register more than one public
key in a single registration request, supporting bulk registration. The
specification MAY generalize this to define how to perform compound
requests and obtain compound responses, including both registration and
information service messages
- The specification MUST describe how to request an update as to the
status of a multi-key request.
[Key Information Service Capabilities]
- The specification MUST define a request for retrieving a
public key, given a <ds:KeyInfo> element containing one or more
children containing key information. The mechanism of processing KeyInfo
and obtaining the key is implementation dependent, but a server MUST be
able to return key information corresponding to a KeyInfo returned in a
registration response from the same server. Population of the server
database for responding to service requests (locate and validate) is out
of scope and implementation specific.
- This specification MUST define a protocol for validating the status of
a public key and additionally validating the binding between a public key
and other related information.
- The specification MUST describe how a client can specify or determine
the context in which a public key binding will be validated {Certicom,
Microsoft, Sun, Zolera} [XKMSPositionPapers]. Context enables
4-corner model support for example. As another example, the context may
include the trust anchors and certificate policies the client wants the
server to use for validation. [List( Yassir
Elley)]
[Formats]
- The specification MUST define payload and header XML
formats. XML Protocol bindings may be published as a separate document
from the specification to avoid dependencies on the XML Protocol
schedule. XML Bindings other than XML Protocol MAY be defined in the
specification [List( Blair
Dillaway)].
- The specification MUST define how to convey application context in
requests/responses, e.g. transaction amount, arbitrary XML {Microsoft,
Sun}
- All formats SHOULD permit application/trust server extension through
the use of additional elements in another namespace.
- The specification MUST define a unified request/response mechanism
across services (Locate, Validate etc.), including uniform error
responses, query and response formats.
- The specification MUST permit opaque data to be associated with a
request and returned with the corresponding response. Parties that are
not concerned with opaque data may ignore it.
- The specification MUST define which requests are idempotent (can repeat
without ill effect) and which are not.
- The specification MUST define a protocol that provides the means to
match requests and responses.
- A client SHOULD be able to control the number of key bindings in a
response returned (e.g. specify the maximum to be returned).
- The specification MUST use schema typing and namespace support for the
<Respond> element in <Locate> and <Validate> responses
(rather than strings). {Reagle}, [WorkshopMeeting]
- A Validate request MAY also include values to be Located and returned
in the response.
- The specification MUST allow the server to return a subset or superset
of the elements requested by the clients. {Reagle} [WorkshopMeeting]. Security
implications MUST be discussed in the Security Concerns section of the
specification.
- The specification MUST define unambiguous multi-valued responses,
removing the ambiguity possible with valid, invalid and indeterminate key
binding status responses, for example.
2.5. Objects and
Processing
- The specification SHOULD define how to register a key for specific uses
and how to update the allowed uses over time. [XKMSPositionPapers ]
- A key registration request MUST be able to specify the appropriate key
usage of a key.
- Key bindings MUST have issuers associated with them.
- The following KeyInfo formats MUST be supported: KeyName, KeyValue, and
RetrievalMethod.
The X509Certificate KeyInfo format MUST be supported by a trust server
if the service claims interoperability with PKIX X.509. Additional
KeyInfo formats such as X509Chain, OCSP, and X509CRL MAY be supported.
X509Chain and OCSP MUST be defined in the XKMS specifications. X509CRL is
defined in the XML Signature recommendation.
The XKMS registration Private format MUST be supported if the service
supports either service generated key pairs or key recovery.[List( Sebastien
Pouliot)]
- Exclusive Canonicalization [ExclusiveCanonicalization] support is required
to assure robust XML digital signatures when the context of the XKMS
content may be changed, such as in the case of intermediate SOAP
processors altering the SOAP envelope context.
- XML Key Management applications MUST be XML-namespaces [XML-namespaces] aware.
- XML Key Management applications MUST be XML Schema [XML-schema] aware in that they create XML Key
Management instances conforming to the key management schema definitions.
{Reagle} Schema validation is not required.
- Implementation of the specification SHOULD work with existing XML
parser and schema implementations. However, alterations to particular DOM
and/or XML parser implementations may prove beneficial in terms of
simplifying application development or improving runtime efficiency.
These details are outside the scope of the XML Key Management
specification.
- The specification SHOULD be compatible with the use of authentication
mechanisms carried in SOAP/XML Protocol messages and/or the transport
protocol.
- The specification MUST describe how to provide proof of possession of
private keys.
- The KeyInfo returned in a registration response SHOULD be a unique key
identifier for the responder for subsequent service requests. Subsetting
this KeyInfo may make this not true. Server implementations may define
uniqueness properties and relate them to clients - how this is done is
implementation dependent.
3. Out of Scope
These items are out of scope(at least for the initial specifications
produced by the working group). In some cases an in-scope requirement (e.g.
the ability to use XKMS in the context of the 4 corner model) may imply some
of this functionality, but that does not mean the XKMS specification is
required to define that functionality.
- Design of new cryptographic algorithms.
- Issues of non-repudiation, including but not limited to 'technical
non-repudiation' and 'contractual non-repudiation'.
- Sources of trusted time.
- Models and data structures for establishing inter-domain trust,
including but not limited to 'cross-certification'.
- Redefining existing PKI structures using an XML syntax, such as
redefining certificates in XML. Existing PKI structures may be
encapsulated within XML elements however.
- Specification of inter-domain trust semantics.
- Authorization issues and more specifically authorization assertions
(e.g. SAML).
- Attribute certificates.
- Knowledge representation syntax.
- Audit management.
- Establishment of trust server key authority delegation [XTAML]. This does not preclude requiring the
ability to sign/encrypt requests and responses, nor preclude discussion
of establishing trust with the XKMS Trust server. [List ( Stephen
Farrell)]
- The XML Key Management recommendation will not define generic
mechanisms for securing SOAP or XML Protocol, but rather define a payload
security mechanism. A goal is to reduce external standards dependencies.
[List( Blair
Dillaway)]
- Issues of anonymous access and service use are not the primary focus of
the work, but may be supported.
- Private key retrieval services that extend beyond the return of a
service-generated private key as part of registration (e.g. Roaming).
- Server chaining and referral mechanisms.
- XML Key Management of symmetric keys.
- Caching support.
- The specification is not tailored to but does not preclude support of
highly constrained devices[List (Yassir Elley)].
- Defining authentication mechanisms.
4 Coordination
Coordination with other groups is as specified in the Charter [Charter].
- The Working Group may satisfy the {Payload, Transaction, and
Authentication} requirements via its own specification or via normative
reference to other specifications. The Working Group SHOULD avoid
redundant specification of those features where possible but SHOULD also
consider the timely completion of its own deliverable, this choice is at
the Working Group's discretion.
5 Intellectual Property
Intellectual property issues are as in the Charter [Charter].
6 References
- 4-Corner Model
- http://www.w3.org/2001/07/xkms-ws/ashwood-4-corners.pdf
- DOM
- Document Object Model (DOM) Level 3 Core Specification, Version 1.0,
W3C Working Draft, Arnaud Le Hors. 22 October 2002.
- http://www.w3.org/TR/DOM-Level-3-Core/core.html
- Exclusive
Canonicalization
- Exclusive XML Canonicalization Version 1.0 W3C Recommendation, John
Boyer, Donald E. Eastlake 3rd, Joseph Reagle18 May 2002
- http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/
- MIME
- RFC2046. MIME Part Two: Media Types November 1996.
http://www.ietf.org/rfc/rfc2046.txt
- P3P
- The Platform for Privacy Preferences 1.0 (P3P1.0) Specification, W3C
Recommendation, Lorrie Cranor,Marc Langheinrich, Massimo
Marchiori, Martin Presler-Marshall,Joseph Reagle, 16 April
2002
http://www.w3.org/TR/P3P/
- RFC 2119
- "Key words for use in RFCs to Indicate Requirement Levels", S.
Bradner, March 1997, RFC 2119.
http://www.ietf.org/rfc/rfc2119.txt
- RFC 2459
- "Internet X.509 Public Key Infrastructure Certificate and CRL
Profile",R. Housley, W. Ford, W. Polk, D. Solo, January 1999, RFC 2459.
http://www.ietf.org/rfc/rfc2459.txt
- RFC 2828
- "Internet Security Glossary", R. Shirey, May 2000, RFC 2828.
http://www.ietf.org/rfc/rfc2828.txt
- SAML
- Security Assertion Markup Language (SAML).
http://www.oasis-open.org/committees/security/docs/
- SOAP
- Simple Object Access Protocol (SOAP) 1.1, W3C Note 08 May 2000.
http://www.w3.org/TR/SOAP/
- SOAP Schemas
- http://schemas.xmlsoap.org/soap/encoding/
http://schemas.xmlsoap.org/soap/envelope/
- TLS
- The TLS Protocol, Version 1.0, RFC 2246, T. Dierks, C. Allen.
http://www.ietf.org/rfc/rfc2246.txt
- XKMS Activity
Statement
- http://www.w3.org/2001/XKMS/Activity.html
- XKMS Change Proposal
- http://www.xmltrustcenter.org/xkms/docs/xkms_change_proposal.html
- XKMS Charter
- http://www.w3.org/2001/XKMS/2002/11/charter.html
- XKMS Mailing Lists
- http://lists.w3.org/Archives/Public/www-xkms-ws/
- http://lists.w3.org/Archives/Public/www-xkms/
- XKMS-Proposal
- http://lists.w3.org/Archives/Public/www-xkms-ws/2001Aug/att-0048/02-xkms-activity.html
- XKMS 1.1 W3C Note
- http://www.w3.org/TR/xkms/
- XKMS
Workshop Meeting Minutes
- http://www.w3.org/2001/07/xkms-ws/minutes.html
- XKMS Workshop
Position Papers
- http://www.w3.org/2001/07/XKMS-Ws/positions/
- Meetings
- http://lists.w3.org/Archives/Public/www-xkms-ws/2001Nov/0028.html
- http://www.w3.org/2001/XKMS/Minutes/011114-tele.html
- http://www.w3.org/2001/XKMS/Minutes/011209-slc/011209-slc-f2f1.html
- http://www.w3.org/2001/XKMS/Minutes/020123-tele.html
- XML
- Extensible Markup Language (XML) 1.0 (Second Edition), W3C
Recommendation, T. Bray, J. Paoli, C. M. Sperberg-McQueen. 6 October
2000.
http://www.w3.org/TR/REC-xml
- XML-C14N
- Canonical
XML. W3C Recommendation. J. Boyer. March 2001.
- http://www.w3.org/TR/2001/REC-xml-c14n-20010315
- http://www.ietf.org/rfc/rfc3076.txt
- XMLDSIG
- XML-Signature
Syntax and Processing. W3C Recommendation. D. Eastlake, J. Reagle,
and D. Solo. February 2002.
http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/
- XML Signature
Requirements. W3C Working Draft. J. Reagle. October 1999.
http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014
- XML
Encryption
- XML Encryption Syntax and Processing, W3C Recommendation T. Imamura,
B. Dillaway, J. Schaad, E. Simon. December 2002.
http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/
- XML Encryption
Requirements. W3C Note J. Reagle. March 2002.
http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304
- XML-ns
- Namespaces in XML Recommendation. T. Bray, D. Hollander, A. Layman.
January 1999.
- http://www.w3.org/TR/1999/REC-xml-names-19990114/
- XML Protocol
- http://www.w3.org/2002/ws/
- XML-schema
- XML
Schema Part 1: Structures W3C Recommendation. D. Beech, M.
Maloney,N. Mendelsohn, H. Thompson. May 2001.
- http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
- XML
Schema Part 2: Datatypes W3C Recommendation. P. Biron, A. Malhotra.
May 2001.
- http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
- Universal Description, Discovery
& Integration (UDDI) specifications
- http://www.uddi.org/specification.html
- URI
- RFC2396. Uniform Resource Identifiers (URI): Generic Syntax.
T. Berners-Lee, R. Fielding, L. Masinter. August 1998 http://www.ietf.org/rfc/rfc2396.txt
- Web Services Description Language
(WSDL)
- W3C Note 15 March 2001 http://www.w3.org/TR/wsdl
- XML Trust Axiom Markup Language
(XTAML)
- http://www.xmltrustcenter.org/research/xtaml/index.htm


--- layout: default ---
We are accepting RSVPs online. Click the button below and you will be directed to the RSVP form.
If you would prefer to get in contact with us directly, contact Sarah via email on<EMAIL_ADDRESS>Calderwood Hall is situated on the R617 just 31km from the Howick turnoff. It is approximately 130km (1 hour 30 minutes) from Durban and 500km (5 hours 15 minutes) from Johannesburg. From the N3 take exit 99 and continue straight on the Underberg road for 31km. Calderwood Hall will be on you right.
GPS co-ordinates:
29°40'56.36"S
30°4'12.43"E
There is limited space available at the venue, however, there are a number of places nearby where you will be able to stay. Please have a look at the options below for more details. Accommodation has been pre-booked for close family and the bridal party (you would have recieved a note with your invitation). If any spaces open up at the venue we will let you know.
Nearby accommodation:
About 8km from Calderwood Hall
Contact person: Noel McLean -<PHONE_NUMBER> or<PHONE_NUMBER>
Email Address<EMAIL_ADDRESS>Website: www.elvesida.co.za
About 7 km from Calderwood Hall
Contact person: Cheryl Scheepers -<PHONE_NUMBER>
About 15 km from Calderwood Hall
Contact person: Gavin Phoenix -<PHONE_NUMBER>
Email address<EMAIL_ADDRESS>Website: None, but sa-venues link and air-bnb link
About 5km from Calderwood Hall
Contact person: Sue Brighton -<PHONE_NUMBER>
E-mail<EMAIL_ADDRESS>Website: www.bostontparty.co.za
There are also many lovely accommodation options available in the Midlands, however, these are further away from the venue.
Having you attend our wedding is the best gift that we could ask for, however, if you would like to spoil us with something special we do have a gift registry available.
We are running an online gift registry with Yuppie Chef. Click to button below to find out more. If you would prefer to buy your own gift and bring it along with you, then please feel free to do so.


Exporting Plink Result to Excel File
Here’s a little tip using plink software. A lot of people might already know this and this might be “the way” to use this software, but I never knew about this until yesterday when I attended a workshop on “genome data analysis” hosted by Seoul National University medical school and they demonstrated to us how to utilize GUI version of plink software, namely gPLINK.
First, you need a GUI version of plink software running. If you’ve already downloaded plink software from plink site, you already have gPLINK jar file in your install directory.
Also, you need a version of Haploview from Haploview site. Download JAR version if you are running this under linux box.
If all set, launch gPLINK.jar from command line
java -jar /path-to-your-plink-directory/gPLINK.jar
When it’s successful, gPLINK launches in GUI mode like shown below.
Go to Project > Open, and open a directory containing ped and map files.
If folder contents are displayed in Folder viewer, go to Project > Configure and set the path to Haploview and plink similar to shown below.
Now, let’s run a simple association test. Once the operation is done, expand Output files section and right click on *.assoc file, then select “Open in Haploview“.
It will open up a dialog called “Open File in Haploview“. Just click_ OK_.
Now, the result is displayed in Haploview. You can use filters or create a Manhattan plot using menu on the bottom.
When you are done exploring and you want to export the result to an Excel file, you can go to File >Export current tab to text.
Save the file as *.txt and you will find that this is a tab-delimited format, which is directly compatible with Microsoft Excel. Simply load file into Excel or right click on the file and use “Open with” option to select Microsoft Excel.
There are many advantages of using command line plink and using custom scripts and shell commands to modify outputs since it fulfills individual’s need. However, this is a good quick and dirty trick if you want to simply convert plink result to a much readable format. Enjoy!
-Hoondy
permalink: /2011/08/26/exporting-plink-result-to-excel-file/
Leave a Comment


Before Change
)
// test if signal repetition is performed according to configuration
hass.async_create_task(
hass.services.async_call(
DOMAIN, SERVICE_TURN_OFF, {ATTR_ENTITY_ID: f"{DOMAIN}.test"}
)
)
// wait for commands and repetitions to finish
await hass.async_block_till_done()
assert protocol.send_command_ack.call_count == 2
// test if default apply to configured devices
hass.async_create_task(
hass.services.async_call(
DOMAIN, SERVICE_TURN_OFF, {ATTR_ENTITY_ID: f"{DOMAIN}.test1"}
)
)
// wait for commands and repetitions to finish
await hass.async_block_till_done()
assert protocol.send_command_ack.call_count == 5
// test if device defaults apply to newly created devices
event_callback({"id": "protocol_0_2", "command": "off"})
// make sure entity is created before setting state
await hass.async_block_till_done()
hass.async_create_task(
hass.services.async_call(
DOMAIN, SERVICE_TURN_OFF, {ATTR_ENTITY_ID: f"{DOMAIN}.protocol_0_2"}
)
)
// wait for commands and repetitions to finish
await hass.async_block_till_done()
After Change
)
// test if signal repetition is performed according to configuration
await hass.services.async_call(
DOMAIN, SERVICE_TURN_OFF, {ATTR_ENTITY_ID: f"{DOMAIN}.test"}
)


a.  Keep track of the time and different ways you spend communicating, such as talking person-to-person, listening to teachers or the radio, watching television, reading books and other print media, and using any electronic communication device. Discuss with your counselor what your log reveals about the importance of communication in your life. Think of ways to improve your communications skills.
4/26/2017
| Time | Form of Communication |
|---|---|
| 6:40 AM | Said good morning to family |
| 7:05 AM | Checked Email and Instant Messages |
| 7:10 AM | Discussed homework over breakfast |
| 8:05 AM | Said good morning to peers at school |
| 8:32 AM | Collaborated with teacher on coding course |
| 9:50 AM | Talked with friends at recess |
| 10:05 AM | Presented and listened to presentations on evolution |
| 12:07 PM | Watched video presentations in Spanish |
| 1:50 PM | Began online research homework |
| 6:30 PM | Talked with family over dinner |
| 7:30 PM | Worked with scouts at scout meeting |
| 9:00 PM | Checked messages/emails before bed |
| 9:30 PM | Said goodnight to family |
a. Think of a creative way to describe yourself, using, for example, a collage, short story or autobiography, drawing or series of photographs, or a song or skit. Using the aid you created, make a presentation to your counselor about yourself.
Interview someone you know fairly well, like, or respect because of his or her position, talent, career or life experiences. Listen actively to learn as much as you can about the person. Then prepare and deliver to your counselor an introduction of the person as though this person were to be a guest speaker, and include reasons why the audience would want to hear this person speak. Show how you would call to invite this person to speak.
Marcy Taylor Pattinson was born in Illonois and double-majored in History and Political Science at the University of Wisconsin. After graduating in 1969, she spent eight months traveling the world before taking residence in San Francisco, where she took a job working in the Bank of America building at 555 California Street. Working there in May 1971, she became a self-dubbed "international heroine," "Marcy Taylor the Flag Girl," after defending the building's US flag during an anti-war rally (see this link for more information.) She is currently retired and resides in Marin County, California. Marcy is a joy to be around for her ever-positive mentality and interesting stories, and I consider her a part of our family.
Create a web page or blog of special interest to you (for instance, your troop or crew, a hobby, or a sport). Include at least three articles or entries and one photograph or illustration, and one link to some other Web page or blog that would be helpful to someone who visits the Web page or blog you have created. It is not necessary to post your Web page or blog to the Internet, but if you decide to do so, you must first share it with your parents and counselor and get their permission.
[Please see the homepage.]
(A) Find out about three career opportunities in the field of communication. (B) Pick one and find out the (i) education, (ii) training, and (iii) experience required for this profession. Discuss this with your counselor, and explain why this profession might interest you.
(A) Three career opportunities are:
(B) I've chosen to look further into a career as a broadcast journalist. (Information source: study.com)


Pig Dice
Roll the dice
Hold!


University of Kansas (2012-2017)
- PSYC 104 General Psychology
- PSYC 318 Cognitive Psychology (online)
PSYC 104 General Psychology
Student Evaluations:
- Summary of Student Evaluations (Fall 2015/Spring 2016/Fall 2016)
- Fall 2015 (KU Student Survey of Teaching)
- Spring 2016 (KU Student Survey of Teaching)
- Fall 2016 (KU Student Survey of Teaching)
- Spring 2017 (KU Student Survey of Teaching) - forthcoming
Sample Lesson Plans:
Scholarship of Teaching and Learning Posters from PSYC 104:
- Castro, N., Siew, C. S. Q., & McCartney, M. J. (2016, November). H.M. in the Flesh or as a Cartoon: The Influence of Video Type on Learning and Test Performance. Poster presented at the 57th Annual Meeting of the Psychonomic Society. Boston, MA.
- Siew, C. S. Q., & McCartney, M. J. (2016, May). Predictors of Performance in General Psychology. Poster presented at the 28th APS Annual Conference, Teaching Institute. Chicago, IL.
- Siew, C. S. Q. (2016, May). Strategies for Classroom Discussion: Examples from PSYC 104. Poster presented at C21 (21st Century Course Redesign Consortium). University of Kansas.
PSYC 318 Cognitive Psychology (online)
Student Evaluations:


RESThub core has been designed to give your a coherent technology stack and additional functionalities, thus helping you to build your application faster.
You should import the following module in your application to be able to use RESThub in your application :
<dependency>
<groupId>org.resthub</groupId>
<artifactId>resthub-core</artifactId>
<version>1.1</version>
</dependency>
Functionalities available from the core are described below.
Since RESThub application context functionalities extend Spring 3 ones, you should carefully read Spring 3 reference manual.
RESThub default configuration scan all resthubContext.xml and applicationContext.xml files from your classpath. This naming convention and scanning process allows you to build easily a simple plugin-like system, when your functionalities are automatically discovered within the classpath.
You can provide an applicationContext.xml file by module to configure your application.
You should use J2EE6 annotations to declare and inject your beans.
To declare a bean :
@Named("beanName")
public class SampleClass {
}
To inject a bean :
@Inject
@Named("beanName")
public void setSampleProperty(...) {
}
Best practice : Bean injection on setter is better than on protected or private property because it allows subclasses to override this injection.
There is various way to configure your environment specific properties in your application, the one described bellow is the more simple and flexible one we have found.
Maven filtering (search and replace variables) is not recommended because it is done at compile time (not runtime) and makes usually your JAR/WAR specific to an environment. This feature can be useful when defining your target path (${project.build.directory}) in your src/test/applicationContext.xml for testing purpose.
Spring properties placeholders allow you to reference in your application context files some values defined in external properties. This is useful in order to keep your application context generic (located in src/main/resources or src/test/resources), and put all values that depends on the environment (local, dev, staging, production) in external properties. These dynamic properties values are resolved during application startup.
In order to improve testabilty and extensibility of your modules, you should set default values in case no properties are found in the classpath - if properties are found, then default values are obviously overriden. It is acheived by declaring the following lines in your applicationContext.xml :
<context:property-placeholder location="classpath*:mymodule.properties"
properties-ref="databaseProperties"
ignore-resource-not-found="true"
ignore-unresolvable="true" />
<util:properties id="mymoduleProperties" >
<prop key="param1">param1Value</prop>
<prop key="param2">param2Value</prop>
</util:properties>
You should now be able to inject dynamic values in your beans :
<bean id="sampleBean" class="org.mycompany.MyBean">
<property name="property1" value="${param1}"/>
<property name="property2" value="${param2}"/>
</bean>
You can also inject direcly these values in your Java classes thanks to the @Value annotation :
@Value("${param1}")
protected String property1;
Or :
@Value("${param1}")
protected void setProperty1(String property1) {
this.property1 = property1;
}
By default, Spring 3 validation XML schema is declared in your application context. This validation could prevent you to use properties placeholder decribed previously, because you will put a value like ${paramStatus} in a boolean attribute that can take only true or false value.
Since there is no way to fix that in vanilla Spring 3, RESThub provides a way to disable application context XSD validations.
In order to disable validation in your unit tests, annotate your test classes with :
@ContextConfiguration(loader = ResthubXmlContextLoader.class)
In order to disable validation in your web application, you should declare in the web.xml file (ResthubXmlWebApplicationContex is located in resthub-web-server dependency) :
<context-param>
<param-name>contextClass</param-name>
<param-value>org.resthub.web.context.ResthubXmlWebApplicationContext</param-value>
</context-param>
RESThub comes with a preconfigured Spring/Hibernate stack, with a connection to an H2 embedded databse, pooling and cache. Every configured bean could be customized by redefining the bean in your applicationContext.xml files, or more easily by putting a database.properties in your project resources.
Please find bellow the properties keys and default values of database.properties
dataSource.driverClassName = org.h2.Driver
dataSource.url = jdbc:h2:mem:resthub;DB_CLOSE_DELAY=-1
dataSource.maxActive = 50
dataSource.maxWait = 1000
dataSource.poolPreparedStatements = true
dataSource.username = sa
dataSource.password =
hibernate.show_sql = false
hibernate.dialect = org.hibernate.dialect.H2Dialect
hibernate.format_sql = true
hibernate.hbm2ddl.auto = update
hibernate.cache.use_second_level_cache = true
hibernate.cache.provider_class = net.sf.ehcache.hibernate.SingletonEhCacheProvider
hibernate.id.new_generator_mappings = true
Please notice that the new Hibernate id generator is used, as recommended in Hibernate documentation. It allows much better performance (there’s no need of a SELECT request before an INSERT request).
RESThub provides some core jpa properties to configure entityManagerFactory in resthubContext.xml (real values are provided thanks to placholders - cf. database.properties configuration) :
<util:map id="resthubCoreJpaProperties">
<entry key="hibernate.dialect" value="${hibernate.dialect}" />
<entry key="hibernate.format_sql" value="${hibernate.format_sql}" />
<entry key="hibernate.hbm2ddl.auto" value="${hibernate.hbm2ddl.auto}" />
<entry key="hibernate.cache.use_second_level_cache" value="${hibernate.cache.use_second_level_cache}" />
<entry key="hibernate.cache.provider_class" value="${hibernate.cache.provider_class}" />
<!-- New ID generator is now recommanded to true for all projects. It provides
betters performances and better generation behaviour than default one. More
details on http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/mapping.html#mapping-declaration-id-enhanced -->
<entry key="hibernate.id.new_generator_mappings" value="${hibernate.id.new_generator_mappings}" />
</util:map>
In order to allow to add extended and additional JPA or Hibernate configuration properties in your own project using RESThub, we provide a dedicated extension point thanks to spring maps and its merge capacity.
Indeed, resthub entityManagerFacory includes an larger map of properties with an external bean reference :
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
...
<property name="jpaProperties" ref="jpaProperties" />
</bean>
<bean id="jpaProperties" parent="resthubCoreJpaProperties">
<property name="sourceMap">
<map merge="true"/>
</property>
</bean>
By default the map contains only core resthub jpa properties but if you need to add JPA or Hibernate properties, you only have to override the jpaProperties bean with your own configuration. Provided properties will be added to resthub core properties.
Just add in you applicationContext :
<bean id="jpaProperties" parent="resthubCoreJpaProperties">
<property name="sourceMap">
<map merge="true">
<entry key="my.key"
value="my.value" />
</map>
</property>
</bean>
RESThub allows to scan entities in different modules using the same PersitenceUnit, which is not possible with default Spring/Hibernate.
By default, the ScanningPersistenceUnitManager searches entities with the pattern “org.resthub.**.model”. To indicates different packages, you’ll have to override the bean definition in your own Spring configuration file.
<resthub:include-entities base-package="net.myProject.**.model" />
Now, entities within the net/myProject/**/model packages will be scanned.
Beware ! You have to be careful with the loading order of your spring configuration files. Reference the RESTHub file first (and don’t forget the * behind “classpath”), and then your files.
Hades is a really powerful Generic DAO framework, included by default in RESThub, which allows to write your DAO with only an interface (no implmentation needed).
Hades’ ability to generate DAO from interfaces is not activated by default in RESThub application, but could be with the following line in your applicationContext.xml.
<hades:dao-config base-package="org.mycompany.myproject.dao" />
RESThub provides some generic classes in order to quickly implement CRUD functionalities :
Provides some generic classes and interfaces for default DAO, service or controller.
For example, to define a CRUD interface for Booking class :
public interface BookingService extends GenericService<Booking, Long> {
}
RESThub provides some helpers to monitor your application. The monitoring service is based on JAMon (http://jamonapi.sourceforge.net/).
To monitor all methods of a Bean, add annotaion @Monitored upon the service’s implementation.
@Monitored
@Named("beanName")
public class SampleClass {
}
Note: You can exclude some methods by annotated this methods by @NotMonitored.
To activate this annotation add this bean post processor declaration into the application context:
<bean class="org.resthub.core.monitoring.MonitoringBeanPostProcessor" />
As soon this processor declared, all methods of the bean are logged in DEBUG output and compute to JAMon metrics.
JAMon metrics are accessible via the MonitorFactory.
for (Iterator<?> it = MonitorFactory.getFactory().iterator(); it.hasNext();) {
System.out.println(it.next().toString());
}
See more way to view metrics at JAMon site.
Another cool feature is that you can monitor SQL orders. To do that edit database.properties and change the JDBC Driver by JAMon one:


Movie Review by Jonathan Richards
SECRETS AND LIES
BOUNCE
Written and Directed by Don Roos
With Gwyneth Paltrow, Ben Affleck
PG-13 102 min.
2-1/2 chiles
One of the most enduring sub-genres of the romantic movie is the one where the relationship is entered into by one of the parties under false pretenses, and a secret hangs over the proceedings like a dark cloud which is going to have to flash some lightning and rumble some thunder and get everybody wet before the skies clear and the lovers kiss and make up. Often it's a bet the guy's made that he can woo and win (or these days, bed) the girl. Sometimes it's something darker and more personal, as in this year's "Return to Me", where Minnie Driver keeps putting off telling David Duchovny that she's wearing his late wife's heart.20
Writer/director Don Roos, the indie auteur of the quirky "The Opposite of Sex", has chosen to fly these friendly skies in his second outing, a formulaic weeper that waffles between clever charm and awkward writing and is largely rescued by its two stars, Gwyneth Paltrow and Ben Affleck. Their job is made more difficult by some contrived situations, a few tin-eared speeches, and an end game with the subtlety of a rubber boat full of explosives. But these two have the talent, appeal, and chemistry (reinforced by real-life tabloid gossip) to almost pull it off.
 He doesn't, the plane does, and the result is a grieving widow in L.A., and a guilt-ridden ad exec, the guy who gave up the seat, watching the news in the Chicago airport hotel with a shapely stranded fellow traveler.
The air disaster sends Buddy Amaral (Affleck) into a downward spiral of alcoholism. He's part owner of "the hottest little ad agency on the coast," for whom he's just closed a contract with Infinity Airlines before their plane crashes. (Roos shows a weakness for meaningful names - Amaral is amoral, and infinity is just where the passengers go.) Heavy drinking leads Buddy into some inappropriate behavior vis-vis the client, and his partner/boss (Joe Morton) steers him into a rehab clinic.
When he gets out, it's been a year since the crash, and in running over his 12-step AA manual he is struck by #9, which enjoins him to make amends wherever possible. So he looks up the widow Abby (Paltrow) to see if there isn't something he can do for her, and it turns out there is. They meet cute, if you can find cuteness in the jaws of an attack Rottweiler, and he manages to throw some real estate business her way. (The dog's name is also Buddy, which raises complications, but none as great as those inherent in the name itself: a line like "What is it you want, Buddy?" hits the ear differently than it would if his name were, say, Howard.)
The movie takes pains to show the pains he takes not to get involved with her after his 9th step intervention, but the centrifugal force of true love is too strong. And soon we're in a Situation. Roos handles it well, with a slick romanticism reminiscent of the golden days of Hollywood when romantic clichE9s had a good name, when stars like Grant = and Stanwyck and Stewart and Davis stamped their indelible personae on contrived smiling-through-the-tears material. Affleck and Paltrow are up to that standard. He makes a credible transition from glib, shallow jerk to sensitive male, and she handles her role with remarkable subtlety, rejecting easy sympathy while managing to show an irresistible vulnerability. It's a beautiful performance that confirms her Oscar-winning talents.
Movies are easier to begin than to end, but there's no excuse for the depths to which this one sinks in its plot-resolving scene, which involves courtroom testimony and Court TV. There have been problem moments before in the story, but after this clunker, even the winning grace of the actors can't keep it aloft, and the worn places begin to show like threadbare patches of carpet when the furniture is moved. There is also a sense of things inserted as plot devices, and of parts of characters and situations that may have been jettisoned to keep the bounces a little more buoyant.20
Still, for most of its modest length "Bounce" lopes along with the smooth, easy ride of a polished genre picture. On the whole Roos is better at the high points - when he goes for the tear ducts he falls a little short. The movie benefits from a solid supporting cast. Caroline Aaron is all knowing sympathy as Abby's best friend, the usually villainous Tony Goldwyn has a chance here to show his nice side, and the always-welcome Joe Morton is gruff but caring. Johnny Galecki as Buddy's brash recovering alcoholic gay assistant almost steals the show, except that his alcoholism and gayness, inserted as if meaningful, are never revisited.20
When the shoe falls, as it must, just before Buddy summons the courage to confess his secret, it falls with the kind of timing God leaves to screenwriters. But after all, it is a movie; and for all its failings, it's one that almost rises above pleasant to achieve the level of good.20
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Go Back
Changelog
- April 15, 2017
- Moved dependencies to Yarn, removed jquery-ui
- Made list sortable
- March 29, 2017
- Added Fetch support
- April 14, 2017
- Removed some usage of jQuery functions
- March 1, 2017
- Cleaned up page structure
- Cleaned up browser support
- Better editing
- February 28, 2017
- Updated chat limit
- Better language loading
- Changed alerts
- Cleaned up upgrade process
- Removed loading bar
- Improved loading efficiency
- Changed alerts more
- Updated json parsing
- Started adding ES6 features
- February 26, 2017
- Added uptime link
- December 13, 2016
- Fixed output issue
- November 30, 2016
- Action bar fixes
- November 15, 2016
- Improving robustness of mouse actions
- November 10, 2016
- Flight feature for jumping lines around [Experimental]
- April 7, 2016
- Updated libraries
- August 17, 2015
- Fixed an output issue
- August 17, 2015
- Fixed an output issue
- August 14, 2015
- Improved support for local storage
- August 5, 2015
- Changed bools from string to bools
- August 5, 2015
- Fixed editing sometimes loosing attributes
- August 4, 2015
- Fixed more language crashes
- August 3, 2015
- Fixed langauge crashes
- August 2, 2015
- Lots of language improvements
- April 18, 2015
- Fixed saves not saving with special characters
- April 11, 2015
- Language updates
- March 30, 2015
- Fixed language issue
- March 29, 2015
- Added strict functions
- March 19, 2015
- Sweet Alert
- March 14, 2015
- #embed
- Fixed English being shown for more than one language
- March 11, 2015
- Signs and events are clearer
- February 2, 2015
- Fixed an issue with books
- January 24, 2015
- Fixed an issue with Delete All
- Removed language credit line (for now)
- Added Turkish
- Fixed an issue with change_page (/u/Marcono1234)
- January 21, 2015
- Fixed some links
- January 20, 2015
- Remove outline from .no-focus-outline elements
- Add class no-focus-outline to preview buttons.
- January 19, 2015
- Now defaults to @p for signs and books
- January 18, 2015
- Added change_page click event option
- January 17, 2015
- Fixed deleting saves not always working
- Fixed delete all saves not showing updated
- December 31, 2014
- Export box is now easier to select
- December 9, 2014
- Fixed an issue where old exports wouldn't import properly
- November 22, 2014
- Fixed an issue where some buttons were cut off
- Square buttons! May or may not keep this
- Prompt before reporting an issue if its the common issue
- November 4, 2014
- Fixed an issue where editing a snippet might be incorrect
- November 1, 2014
- Improved Error Handling
- October 31, 2014
- Fixed some issues
- October 25, 2014
- Added a dark mode
- Signs no longer pretend to support insertion text
- Fixed a broken URL in the changelog
- Signs no longer pretend to support clicks and hovers.
- October 4, 2014
- Now supports multiple colors and snippets in hovertext
- September 26, 2014
- Fixed sign lines
- Fixed importing being broken
- September 25, 2014
- Fixed an issue with deleting saves
- Fixed an issue with newlines
- Fixed an issue with page loading
- September 24, 2014
- New Sign Lines!
- Better book code yay!
- Added ability to show and hide the nice looking output.
- Fixed quotes in quotes
- September 22, 2014
- Fixed a spelling issue
- Fixed the preview updating incorrectly
- Added an option to delete individual saves
- September 20, 2014
- Fixed scrolling to tellraw button not working as expexted
- Added (WIP) Settings page
- September 18, 2014
- Fixed an issue with templates and exporting
- September 16, 2014
- Temporarily removed translation while I fix it.
- Fixed an issue with the color settings
- Fixed an issue with the delete alert & scrolling
- September 10, 2014
- Added color selection for hover text
- September 2, 2014
- 1.8 is green now, because 1.8 is released
- August 29, 2014
- Fixed some bugs
- August 25, 2014
- Added a new data verification method and changed show_text format
- August 20, 2014
- Finalized new book page feature
- Added an easy way to request languages
- August 18, 2014
- Added a feature for new pages in books. Not yet accessible, WIP
- Changed Exporting to no longer use alert() because some browsers dont allow copying from that dialog.
- August 6, 2014
- Fixed more alignment things
- August 5, 2014
- Fixed a bug with the delete all dialog, thanks stupid3700.
- August 2, 2014
- Updated alignment, made look much better on mobile
- July 24, 2014
- Moved all external resources to repo, no longer requires things not in directory (exception is images and one css sheet, both of which are loaded from http://ezekielelin.com directly
- Removed unneeeded console usage
- July 21, 2014
- Hashes have been added to changelog for github refs
- Fixed a bug where the command block message wouldn't show up.
- July 14, 2014
- The language now automatically changes on first load. This won't affect users who have already loaded the page. Also, this will not work for everyone because language code lists are complicated. Please go to the forum (via the main tellraw page), and tell me if your language isn't automatially set on first load. If you want to test it, use localStorage.clear();location.reload();
- July 12, 2014
- Fixed some broken formatting on the changelog. Now properly handles broken links and reverted changes :D
- July 4, 2014
- Added Minecraftia font, should be all set. Can someone please verify this for me? Should show up in minecraft style on the output.
- June 19, 2014
- Use %e and %s to embed the generated string in the command (%e escapes quotes, %s doesn't)
- Build in ability to generate a /give written_book and /give sign with the embedded text
- You can now save multiple strings and switch between them easily.
- I've made the click and hover event text fields easier to use, automatic suggestions
- June 18, 2014
- Use %e and %s to embed the generated string in the command (%e escapes quotes, %s doesn't)
- June 14, 2014
- tellraw, title, subtitle templates
- June 1, 2014
- None color
- May 16, 2014
- Due to changes in format, I've been forced to make the attributes stricter. This means you will see both true and false values. If you have a real reason to have this rolled back, please reply to this topic making your argument.
- May 14, 2014
- New format, less bytes
- None color option by default, (will appear white in game, however) (may not be immediately available on site)
- May 13, 2014
- Badge items with their version / specific feature.
- May 10, 2014
- Translation is redone
- Modals begone
- May 9, 2014
- Added the command field, which allows for custom commands such as execute. Also supports importing these commands.
- Now stores player in localStorageNow stores command in localStorage
- May 7, 2014
- I've reworked the language system for translations.
- April 27, 2014
- Importing observes the player, mostly
- February 23, 2014
- I've fixed bugs with editing
- February 21, 2014
- Full featured editor. May be a bit buggy, please report that here: https://github.com/ezfe/tellraw/issues
- February 19, 2014
- 1.8 Scoreboard objectives inline
- Translated strings have been redone behind the scenes, and the preview now almost 100% accurately reflects the english output.
- January 19, 2014
- Fixed some text fields clearing when they shouldn't
- Fixed the translations doing a lot of stuff every cycle
- January 15, 2014
- Cool, awesome, totally revolutionary new background image.
- January 10, 2014
- Now supports insertionNow supports show_entity
- December 31, 2013
- Fixed an issue where the GUI could be confusing.
- December 30, 2013
- French has been updated.Hebrew has been added.
- December 27, 2013
- Changed the import function, works easier now, no more dev console needed. If it fails it will fail silently and won't indicate a failure. Sorry.
- Added a newline after the tellraw player section of the output to make it easier to copy paste just the tellraw part.
- Fixed a russian string
- December 26, 2013
- Removed old language strings
- Edit Mode is now always on and works better
- Delete all button
- The command persists across reloads, so if your web browser crashes you may not loose it.
- Moved some things aroundFixed some bugs.
- December 24, 2013
- Fixed a bug where the language wouldn't properly set up
- Changed how falses are done. If you experience problems with this, please tell me ASAP.
- December 16, 2013
- Fixed some missing language strings, still looking for translations.Language settings persist across page loads now
- December 15, 2013
- Background color chooser. Language strings will be available for translation tomorrow.
- December 9, 2013
- Changed more backend systems for applying styles to the previewsRemoved the drop shadow that may or may not have been published live at one point.
- Added highlight for click and hover events to the preview.
- December 8, 2013
- Added Russian
- November 30, 2013
- Language switching is even better
- Cleaned up a bunch of un-needed things
- Added Dutch
- The command list is more complete nowThe achievement list is more complete now
- Upgraded the inline editing, please tell me if something isn't working!
- November 26, 2013
- You can now choose between English, French(kinda) and German
- November 25, 2013
- You can now edit the json text. Click Edit mode, and then start editing.
- November 24, 2013
- You can now click text in the preview to see the hover and click events.The page now fills all the text boxes when the page loads, so pressing refresh without making changes won't do anything.
- November 23, 2013
- Work in progress: I'm making it so all snippets behave the same way, they're all extras. If you have a strong argument against this, please post a comment.
- Fixed some bugs with IE
- Added a color preview in the "Add Text" manager
- Added a preview of what your tellraw will output (more to come)
- Removed the ability to see wether it will work in a command block, all of these commands will require a command block. If you want a more basic generator, send me a private message I can work something outAdded a dictionary function for getting the CSS Color Code from a minecraft color name.
- November 16, 2013
- Added a feature to edit "Extras" text.
- Fixed some bugs with extras resetting their text.
- November 13, 2013
- Changed how to add extras, making way for language strings.
- Fixed some bugs with when it detected changesFixed some bugs with how extras are removed
- Improved mobile support. More coming.
- November 10, 2013
- Deletion of extras asks for a confirmation I'm using table rows for each one now to improve formatting
- Moved the manipulation buttons over to the left in their own table data elementImproved the handling of falses, for now. You can choose to show or hide them in the extras. Whatever goes wrong if you hide them is your problem atm, its a matter of how the game handles it. It will show them by default.
- Minor optimizations and changes.
- October 16, 2013
- Fixed the @a issues with the player field
- Updated the statistics, achievements, and commands for 13w41b
- September 23, 2013
- I'm trying to optimize where it adds the various tags. Currently the first one will do it smartly, I'm working on the extras
- September 22, 2013
- I've updated it so it no longer loops. Side affect is the player field acts oddly. Workaround is to type what you want, then delete the @a.
- Added more things to the suggestion boxes.
- September 20, 2013
- All behind the scenes is done in pure JSON
- Removed Falses option, falses are always shown. Due to the fact command blocks have almost unlimited length, this isn't a problem.Its now easier to remove extra snippets.Better support for achievements and commands.
- September 19, 2013
- Supports 13w28a "show_achievements" parameter
- Autofills text-boxes to show suggestions.
- September 18, 2013
- Automatic quotation escaping
- Preview of the command (not 100% accurate yet, more to come)


WITNESS LIST
Economic Competitiveness, Select Committee
November 15, 2017 - 10:00 AM
Select Committee on Economic Competitiveness
On:
Caldwell, Katie (Self; Legacy Community Health)
Cheney, Jeff (Self; Frisco)
Craymer, Dale (Texas Taxpayers and Research Association)
Cuban, Mark (Self)
Humphries, Fred (Microsoft)
Lites, James (Self; Dallas stars)
Luce, Tom (Self)
Matej, Casandra (Visit San Antonio)
O'NEAL, CHARLES (Texas Association of African American Chambers of Commerce)
Orrenius, Pia (Self)
Perot, Henry (Self)
Perryman, Dr. Ray (The Perryman Group)
Sims, Greg (Self; Greenville Board of Development / Greenville 4a Economic Development
Corporation/Texas Economic Development Council)
Registering, but not testifying:
On:
Potter, Lloyd (Texas Demographic Center)
1


Indonesia suspects outbreak of African swine fever
JAKARTA: An outbreak of African swine fever in Indonesia's North Sumatra province has been detected by laboratory tests carried out after the deaths of thousands of pigs in the area this week, an agriculture ministry official said on Friday (Nov 8).
A provincial official said on Wednesday that more than 4,000 pigs had died after an outbreak of classical swine fever, also known as hog cholera.
READ: Is African swine fever contagious? What you need to know about the disease sweeping across Asia
"Clinical symptoms and laboratory test results point to African swine fever, but there are also samples that are positive for hog cholera," Fadjar Sumping Tjatur Rassa, the agriculture ministry's director of animal health, told Reuters.
Classical swine fever was first detected in September in the province's Dairi district, a local official said.
Rassa could not say how many of the pigs deaths may have been caused by an outbreak of African swine fever (ASF).
"For the ASF, of concern is the economic loss because of its rapid spread and its high mortality rate," Rassa said, adding that both classical swine flu and ASF did not infect humans.
He said the government had implemented bio-security measures in the affected areas by ordering authorities to immediately bury pig carcasses and disinfect areas to prevent the virus spreading.
Pigs and pork products from affected the area could not be transported to other places, he said.
READ: Despite culls, import bans, swine fever to hit pork market for years
Video footage showed officials from authorities in North Sumatra collecting pig carcasses that had been thrown into rivers this week by boat in order to bury them.
East Timor, which shares an island with Indonesia's East Nusa Tenggara province, reported in September that there were 100 outbreaks of ASF, killing 405 backyard pigs.


Negative Effects From Anime
Unfortunately, there is also a negative side to the influence anime has on people. Not everyone reacts the same way to any shared interest, but there have been some particularly bad effects that can be attributed to being a fan of anime. One of them is not really bad at all, which is otaku culture. This is in no way a negative thing. This is a vast group of people who love something and enjoy discussing and promoting it. In fact, the base definition of an otaku is “people with a [highly] evolved sense of sight” (LaMarre, 2009, p. 144). This was based on the ability to find and praise feats of small subsets of the anime staff. An example would be discerning the work of a key animator from that of an in-between animator (LaMarre, 2009, p. 144). This leads to an appreciation that anime staff can take pride in. Now the actual negative side of otaku culture is the view of it from a non-otaku.  People have been bullied and looked down on for having such an interest, but luckily this isn’t as common anymore. The spike in popularity from the 90s has set anime and manga on a course to being mainstream like video-games have become.
One of the reasons for the negative viewpoint on otaku culture is the people who react in unfortunate ways to their love of anime. Primary examples of this are hikikomori, 2D lovers, and lolicon. One of those stands out as being worse for being associated with pedophilia and that is lolicon. In anime it is surprisingly common for underage sex and romance to be a core theme. Back in the 1980s there began a huge kawaii, or cute, craze which is the reason for the strong presence of child or child-like characters (Zanghellini, 2009, p. 163). Attempting to capitalize on the craze manga authors tried to showcase innocence as best they could usually by creating very young looking characters as this was their idea of cute. “Cuteness means a generally more infantile character...” (Ripley, 2014) This unfortunately led to these types of characters being portrayed in erotic manga and anime. This trope is still common in today’s anime and it has grown even more strongly represented. This has led to an unfortunate association for otaku culture.
Other examples of negative influence are the development of hikikomori and 2D Love. These are often one in the same, but not always. There are people who view the characters of an anime as actual friends or romantic interests and are actually able to derive all of their social needs from anime. While this is not particularly harmful to any other people, it does leave them with lessened relationships with their family and friends. The worse one is a hikikomori. These are people who do not leave their home or do so very little. They avoid interacting with other people and seek an indoor isolation. This lifestyle is able to be maintained due to the prevalence of online occupations and food delivery. They are often associated with anime, not just because they watch it, but because they need it for any hope of social interaction. They are more often associated with online gaming though. The good part is that most hikikomori are young people who are supported by their parents. “...the average age for their withdrawal was 15” (Kremer, p. 2013). When that support is cut off they are forced to venture out in order to sustain themselves.


I offer a combination of psychotherapeutic or psychodynamic techniques to channel the physical experience of your body through the yogic tradition as well as raise awareness of your connection to the divine, and your spirit. Know more about me here.
Are you wanting healthier and more balanced relationships in your life?
I offer individual guidance sessions to help you develop positive relationships in your life. I focus on assisting you to develop awareness of yourself. By cultivating your relationship to spirituality you can see the whole world through a meaningful perspective. The more you learn to love yourself and your own divinity, the easier it becomes to relate to others.
Are you wondering how to heal from traumatic experiences?
I facilitate workshops for Conscious Connection. We integrate intimacy games with partners to explore the experience of seeing and being seen. We practice mindful yoga to learn about the internal experience of living in a body. We share our truths and learn from one another. We witness and hold space for one another. We connect from our hearts and understand the way we all reflect each other.
See what people are saying after interacting
with me.
When am around you I feel so happy because you are happy and I also feel calm when am around you and I feel loved.
You have helped me understand romantic relationships and relationships with friends and family by showing me a different perspective. You have helped me break down relationships and situations to see the experience clearly without distractions of emotion or my own self-absorption which helps me in situations now where I reflect on events outside of just my personal view, attachments, and social constraints..
 I think you could support them by giving them some guidance material at first so that they can educate themselves a bit about healing from trauma and to see if this is the best path for them. Then you could answer any questions they might have, and you could ask them questions as well, perhaps questions they never thought of before, which might help them to understand the importance of going through the healing process.
Happy, enthusiastic, courageous, vibrant traveler, concerned, dedicated and good friend.
Lolly has helped me to learn visualizations such as someone's excessive mind chatter or negative vibes to enter into a big black cauldron instead of allowing those vibes be absorbed into my own being. It has helped me to protect myself and harness my own physical, mental & emotional energies. She also deepened my understanding of cord cutting through ceremony and visual techniques. I now feel more in charge of my healing progress and can now share this deep wisdom with others who may suffer from emotional/energetic wounds. Thank you for bringing deep joy, feminine wisdom &&love into my life. Namaste.
Where I have reached is because of your effort, I have moved 50% in my journey because of you, you remain a role model and a kind, caring, supportive and a loving person in my life and family.
You helped to reflect back to me the way that i was judging myself as being either not enough or too much. our session helped bring awareness to how silly my fears and self-judgments are, which allows me to be less attached to these judgments, laugh at them, release them, notice them instead of feeling like they are the truth and move on with my day. you also helped me to feel more comfortable in my own skin, to feel normal, to love myself, my family and my friends even deeper. Thank you.
I felt that I was able to confront some conflict in myself relating to gender roles.
You helped provide guidance as I considered entering into the social work profession. Also, your facebook posts always cause me to self-reflect on areas of improvement. They help to keep me accountable to myself and who I want to be.
I would say that you are a person who can give a good insight on their selfs or relationship
Lolly's has a very diverse background and extensive experience. She tailors her working knowledge and interpersonal skills to best suit an individual's needs.
Strong communicator, provide a relaxed and calm setting, good listener, ability to collect another's thoughts and put it into words and show them a perspective that can help them
Lolly is a grounded person, eager to investigate diverse ways to support you; always willing to learn and try new things
Lolly has a beautiful blend of being soft and playful and loving and yet highly engaged in her work and learning and desire to help.
When am around you I feel so happy because you are happy and I also feel calm when am around you and I feel loved.
You have helped me understand romantic relationships and relationships with friends and family by showing me a different perspective. You have helped me break down relationships and situations to see the experience clearly without distractions of emotion or my own self-absorption which helps me in situations now where I reflect on events outside of just my personal view, attachments, and social constraints..
you are a spiritual healer and that you focus on meditation as a means of becoming centered. I think you could support them by giving them some guidance material at first so that they can educate themselves a bit about healing from trauma and to see if this is the best path for them. Then you could answer any questions they might have, and you could ask them questions as well, perhaps questions they never thought of before, which might help them to understand the importance of going through the healing process.
Lolly has helped me to learn visualizations such as someone's excessive mind chatter or negative vibes to enter into a big black cauldron instead of allowing those vibes be absorbed into my own being. It has helped me to protect myself and harness my own physical, mental & emotional energies. She also deepened my understanding of cord cutting through ceremony and visual techniques. I now feel more in charge of my healing progress and can now share this deep wisdom with others who may suffer from emotional/energetic wounds. Thank you for bringing deep joy, feminine wisdom &&love into my life. Namaste.
Where I have reached is because of your effort, I have moved 50% in my journey because of you, you remain a role model and a kind, caring, supportive and a loving person in my life and family.
you helped to reflect back to me the way that i was judging myself as being either not enough or too much. our session helped bring awareness to how silly my fears and self-judgments are, which allows me to be less attached to these judgments, laugh at them, release them, notice them instead of feeling like they are the truth and move on with my day. you also helped me to feel more comfortable in my own skin, to feel normal, to love myself, my family and my friends even deeper. Thank you.
I felt that I was able to confront some conflict in myself relating to gender roles.
You helped provide guidance as I considered entering into the social work profession. Also, your facebook posts always cause me to self-reflect on areas of improvement. They help to keep me accountable to myself and who I want to be.
I would say that you are a person who can give a good insight on their selfs or relationship
Lolly's has a very diverse background and extensive experience. She tailors her working knowledge and interpersonal skills to best suit an individual's needs.
Strong communicator, provide a relaxed and calm setting, good listener, ability to collect another's thoughts and put it into words and show them a perspective that can help them
Lolly is a grounded person, eager to investigate diverse ways to support you; always willing to learn and try new things
Lolly has a beautiful blend of being soft and playful and loving and yet highly engaged in her work and learning and desire to help.
Ready to heal with me? That's great! Give me a call or send me an email and I will get back to you as soon as possible!
123-456-6789


UFC 244 video: Embedded, part 3 - ‘Somebody’s going to sleep for a while’
by Tim BurkeUFC 244 is almost here, and as usual, Embedded is here as well. The show that gives you an inside look at the marquee contestants on PPVs has issued the third episode for this weekend’s big show in the The Big Apple, and it serves as a brief introduction to the fighters at the top of the card.
We start things off with Kelvin Gastelum, who is ready to go. He’s sitting with his manager, who sets up a FaceTime conversation between Gastelum and lightweight champ Khabib Nurmagomedov.
Corey Anderson says he trains down the street at Renzo Gracie’s and he’s prepared. Johnny Walker talks to the supplement people. An employee explains the supplement process, saying it’s a little different on fight week.
Stephen Thompson is excited to fight. Gastelum does some media, talking about opponent Darren Till coming up in weight like he did. Over at ESPN Studios, Jorge Masvidal is greeted by Jalen Rose. He discusses the Nate Diaz fight with host Mike Greenberg. Greenberg seems surprised by Masvidal’s charisma. On First Take, the host compares him to Roberto Duran, which Gamebred loves.
Now it’s Diaz time. He makes his first appearance in this Embedded series, talking about why he took the Masvidal fight. He then signs some posters and talks to anti-drug czar Jeff Novitzky. Apparently they’re all good. He says he got teased about wearing his hat sideways, but he’s been doing that the same way since he was a teenager. He then tells an amusing story about throwing bananas at a house.
And that’s it! UFC 244 goes down this Saturday night in NYC.


Storage inspection displays log information and data needed by Broadcast to schedule and execute tasks.
Data is segmented into keys that are displayed by the Id element.
Unlike the dashboard, storage inspection displays the raw data with the technical keys used to reference the data.
Servers
Id
Recurring Tasks
Id
Tasks
Id
Queues
Id


---
layout: post
title: Installing the California calendar application on Debian Jessie
categories: []
tags: [Linux,Debian,Source]
status: publish
type: post
published: true
comments: true
meta:
_edit_last: '1'
---
Decided I wanted to try out the new California calendar application from the Yorba folks. Sometimes it can be hard to find ever dev library you need on your platform so I thought I'd write up which packages I needed to install.
First pull down the source from either their git repo or from here
Then install the following packages on your debian jessie:
{% highlight bash %}
sudo apt-get install libgtk-3-dev libgee-0.8-dev libecal1.2-dev libsoup2.4-dev libgdata-dev libgoa-1.0-dev libgirepository1.0-dev itstool valac
{% endhighlight %}
Now just follow the instructions in the INSTALL file:
{% highlight bash %}
./configure
make
{% endhighlight %}
For easy usage you can make a .desktop file with something like this(/home/username/.local/share/applications/california.desktop):
{% highlight bash %}
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Icon=/usr/share/icons/gnome/48x48/mimetypes/x-office-calendar.png
Exec=/path-to-california/california-0.2.0/src/california
Name=California
Comment=California
{% endhighlight %}
Now you can just find it in your menu, or in Gnome just hit the 'Super' key and type California.


Show the User a Check Box
Tags: AppKit
Type: API
Class: NSButton
A check box allows the user to check or uncheck an option. A check box is a variation of a button on macOS, and uses the NSButton class.
See the following links for helpful info:
Link: Apple Developer Docs for NSButton
Sample Code:
// Define a Check Box control as a button
var tagsCkBox: NSButton!
// Create the Check Box
// Note that the combination of target and action specify what
// class and method should be called when the user clicks on the check box
titleCkBox = NSButton(checkboxWithTitle: "Title", target: self, action: #selector(checkBoxClicked))
// Programmatically deselect the checkbox
titleCkBox.state = NSControl.StateValue.off
// Programmatically select the checkbox
titleCkBox.state = NSControl.StateValue.on
// Provide the method to be called when the user clicks
// Note that @objc needs to be prepended in order to enable
// some special Objective-C juju
@objc func checkBoxClicked() {
// Do something about the action
}
Contributed by on


This is a mini IDE for DTrace. It makes use of the Python based DTrace consumer and is itself written in fabulous Python. It supports the creation of Graphs and offers an simple editor which adds DTrace specific syntax highlightings!
© 2012 engjoy UG (haftungsbeschränkt)


Betsie is her name and playing is her game! Betsie is a fiesty tabby with an independent streak and a mind of her own. She likes to unroll yarn, pitter pattering around the living room floor. She also likes to speak to flies and try to swat them with her tenny tiny paws. Although she has yet to successfully capture those little buggers, that doesn't stop her from trying!
Besides playing, Betsie's second favorite activity is napping. On top of her cat house, on top of the refrigerator. Basically, anywhere high up so that she can reign over the house and make sure everyone is in line! She also likes sunny spots so on the window ceil is where you'll find her on a hot summer's day.
| Betsie's Favorites | |
|---|---|
| Edibles | Toys |
| Tuna | Yarn |
| Chicken | Bells |
| Greens | Flies |
Betsie likes treats, lots and lots. She will eat your food when you're not looking but she will make sure to leave some crumbs behind so you know she was there!


A minimalistic HTML5 template created by Elijah Cruz.
You can easily create an amazing about section just using this simple piece. There is even a nice image on the other side. Be sure to change the images and any other items in this template.
123 Fake St. City, ST 12345 Country
+1 (234) 456 - 7890
email@email.com


TCS sets up Innovation Hub in Hyderabad
To utilise the power of AI, IoT and 5G technologies
by Special CorrespondentIT major Tata Consultancy Services (TCS) announced on Wednesday the launch of an Innovation Hub in Hyderabad.
The facility would be used to build domain-specific solutions that utilise the power of artificial intelligence (AI), Internet of Things (IoT) and 5G technologies to help global enterprises, across industries, accelerate their digital transformation journeys, the company said. The Innovation Hub, set up with the support of Qualcomm Technologies, would explore the possibilities opened up by 5G in different industries such as healthcare, automotive, manufacturing, retail and utilities. “The convergence of 5G, AI and edge computing will open unprecedented opportunities for value creation in industrial automation, autonomous vehicles and other industries,” said V. Rajanna, global head of Technology Business Unit of TCS.
Qualcomm India vice-president Rajen Vagadia said, “We are thrilled to extend our long relationship with TCS into a more strategic collaboration through the innovation hub and explore new and innovative use cases of 5G technologies and AI relevant to India and enterprises across the globe”.


Dwarf 'dumped' by adoptive parents denies she tried to poison mum with bleach
Natalia Grace Barnett insists she was just trying to clean when her former adoptive mum claimed she tried to poison her
by Matthew Dresch, https://www.mirror.co.uk/authors/matthew-dresch/A dwarf who was allegedly abandoned by her adoptive parents when she was nine has denied claims she tried to poison her mum with bleach.
Natalia Grace Barnett has hit back at claims by her former parents Kristine and Michael Barnett that she was an adult posing as a child when they took her in.
The Barnetts allege Natalia tried to kill the family after moving into their home and was 22-years-old when they left her, although she claimed to be just a child.
But the Ukrainian has denied the accusations in an extraordinary interview with US TV star Dr Phil.
During the episode the host shows Natalia a clip of Ms Barnett claiming her adoptive daughter tried to spray bleach into her coffee while they were cleaning together.
He added that the American mother said she had video evidence of Natalia's bid to poison her.
However, the Ukrainian told Dr Phil: "It was Lemon Pledge for tables.
"We had missed a spot so what I did was I scooted the chair over so I could get there and I scooted her coffee back so I could grab the thing because it was in front of it.
"So I scooted it back and I grabbed it. She came back and was like 'what are you doing?'.
"She claimed I tried to spray it in her coffee, you can look in her coffee - there was nothing."
She also denied her former mum's claim that she had already started her period - and was trying to cover it up - when she was adopted.

Cynthia Mans, her new adoptive mum who sat alongside her when she met Dr Phil, added: "She's been with us for almost seven years, to this day she does not have a menstrual cycle. Not one."
Mrs Mans and her husband Antwon, who also took part in the interview, described Natalia as a 'genuine and loving young lady who has been through a horrible situation'.
They accused the Barnetts of lying and called for them to be punished for dumping their daughter in an apartment and moving to Canada.
The Barnettsm who were arrested for child abuse in September, adopted Natalia in 2010, when they thought she was six-years-old, before allegedly abandoning her in 2013.
Responding to the Barnetts' allegations that she was an adult, Natalia told Dr Phil: "It's not true.
"It's not true at all. I just want people to hear my side."
Her new adoptive mum Cynthia Mans, who sat alongside her for the interview, said her daughter had bone scans which prove her real age.
The Barnetts previously claimed a bone scan they paid for indicated she was born in 1989, Mail Online reports.
Ms Barnett also said doctors examined Natalia and concluded she was suffering a severe psychological illness only diagnosed in adults.
This illness supposedly led to her jumping from moving cars and smearing blood over mirrors.
The couple had Natalia's age changed to 22 and later rented an apartment in Lafayette, Indiana, in 2013 and left her there alone, according to police.


module Orchestrate::API::Procedural
Procedural interface methods (optional).¶ ↑
This file serves as useful documentation for the Orchestrate.io REST API. Each method illustrates an example for the corresponding HTTP request, and documents the required keys for the send_request argument hash.
Public Instance Methods
-
required: { collection }
# File api/lib/orchestrate_api/procedural.rb, line 29 def delete_collection(args) send_request :delete, args.merge(path: "?force=true") end
-
required: { collection, key, kind, to_collection, to_key }
# File api/lib/orchestrate_api/procedural.rb, line 115 def delete_graph(args) send_request :delete, args.merge(path: "?purge=true") end
-
required: { collection, key }
# File api/lib/orchestrate_api/procedural.rb, line 50 def delete_key(args) send_request :delete, args end
-
required: { collection, key, ref }
# File api/lib/orchestrate_api/procedural.rb, line 65 def get_by_ref(args) send_request :get, args end
-
required: { collection, key, event_type }
-
optional: { timestamp }, where timestamp = { :start => start, :end => end }
# File api/lib/orchestrate_api/procedural.rb, line 87 def get_events(args) send_request :get, args end
-
required: { collection, key, kind }
# File api/lib/orchestrate_api/procedural.rb, line 103 def get_graph(args) send_request :get, args end
-
required: { collection, key }
# File api/lib/orchestrate_api/procedural.rb, line 38 def get_key(args) send_request :get, args end
-
required: { collection }
-
optional: { path }, which should have been called params
# File api/lib/orchestrate_api/procedural.rb, line 17 def list(args) send_request :get, args end
-
required: { collection, key }
# File api/lib/orchestrate_api/procedural.rb, line 56 def purge_key(args) send_request :delete, args.merge(path: "?purge=true") end
-
required: { collection, key, event_type, json }
-
optional: { timestamp }, where timestamp is a scalar value
# File api/lib/orchestrate_api/procedural.rb, line 94 def put_event(args) send_request :put, args end
-
required: { collection, key, kind, to_collection, to_key }
# File api/lib/orchestrate_api/procedural.rb, line 109 def put_graph(args) send_request :put, args end
-
required: { collection, key, json }
# File api/lib/orchestrate_api/procedural.rb, line 44 def put_key(args) send_request :put, args end
-
required: { collection, key, json, ref }
# File api/lib/orchestrate_api/procedural.rb, line 71 def put_key_if_match(args) send_request :put, args end
-
required: { collection, key, json }
# File api/lib/orchestrate_api/procedural.rb, line 77 def put_key_if_none_match(args) send_request :put, args.merge(ref: '"*"') end
-
required: { collection }
# File api/lib/orchestrate_api/procedural.rb, line 23 def search(args) send_request :get, args.merge(path: "?query=#{args[:query].gsub(/\s/, '%20')}") end