My name is Lionel. I'm a teacher, developer and life long learner. I
love to pick up new skills and enrich others with what I know.
I enjoy minimalistic and functional design and I love to experiment.
I'm currently pursuing opportunities in the tech sector. If you
think I'd be a good fit for your team or you just want to chat, send
me an email or message! I'm something of a jack-of-all trades and
have mostly been trained in full stack development.
My main language is Java, but I consider myself a polyglot and I
love to pickup new languages!
Here is a link to my CV. Feel free to take a look!
Everything here seems a little basic. Why is that?
Good observation! While I strongly believe in the appeal of mainstream web design, I chose to emphasize
accessiblity for my personal website. Why? I want it to be as friendly as possible to as many people as possible!
By no means is this a perfect attempt, mind you. I just want to promote mindfulness for others. Feel free to audit this page and give me feedback.
What technologies are you most interested in?
Too many to count! I love learning about emerging technologies and seeing how they can be applied to real world scenarios. I also love modern programming languages and implementations such as Kotlin and Rust and Deno.
What specifically is your main stack?
I work mostly with Java utilizing Spring Boot. If I need to implement a frontend, I'll gravitate towards using vanilla HTML/CSS/JS.
Do you think love can bloom even on a battlefield?
Yeah. I do.


The liverbird is used as a a symbol for the City of Liverpool, some of the places these symbols can be found are...
Designed to watch the City (Our People) and the Sea (Our Prosperity). Another legend says that if an honest man and a virgin woman were to fall in love in front of the liverbird that the couple of liverbirds that are in statue form would come to life, fly away and Liverpool would cease to exist.
http://en.wikipedia.org/wiki/Liver_bird
There are multiple stories and myths about the two Liverbirds on top of the Liver building. Generally they revolve around one facing the sea to protect the sailors and properity of the city and the other looking over the people of Liverpool. And that if the two were ever to disappear then the city would be in danger or cease to exist all together.
There has been a few issues over the years as to the use of the Liverbird symbol and its use in football.
Prince Rupert Tower. However some fans still think it should be shown on the kit
Read more on Wikipedia
See the BBC News Report
Read more on Wikipedia
| Steven Gerrard | Glen Johnson | Craig Bellamy |
|---|---|---|
| Andy Carrol | Dirk Kuyt | Pepe Reina |


I have always had a large number of interests, although I am not fanatically committed to any specific one in any extreme. I love learning new things, achieve a certain level of working competence, and then continue to something new. Here are some of the areas I have either dabbled in or adopted as longterm interests and activites. For some of the entries, a link is provided to the corresponding entry in the hobby references.
|
|


public class Editor
extends java.lang.Object
| Modifier and Type | Field | Description |
|---|---|---|
static int |
MAX_BLINK_RATE |
|
static int |
MAX_TAB_SIZE |
|
static int |
MIN_BLINK_RATE |
|
static int |
MIN_TAB_SIZE |
| Modifier and Type | Method | Description |
|---|---|---|
boolean |
close() |
Perform "close" operation on current tab's file.
|
boolean |
closeAll() |
Close all currently open files.
|
boolean |
editsSavedOrAbandoned() |
Called by several of the Action objects when there is potential
loss of editing changes.
|
java.lang.String |
getCurrentOpenDirectory() |
Get name of current directory for Open operation.
|
java.lang.String |
getCurrentSaveDirectory() |
Get name of current directory for Save or Save As operation.
|
java.lang.String |
getNextDefaultFilename() |
Generates a default file name
|
void |
newFile() |
Perform "new" operation to create an empty tab.
|
boolean |
open() |
Open file in a new tab.
|
boolean |
save() |
Perform "save" operation on current tab's file.
|
boolean |
saveAll() |
Perform save operation on all open files (tabs).
|
boolean |
saveAs() |
Perform "save as" operation on current tab's file.
|
(package private) void |
setCurrentOpenDirectory(java.lang.String currentOpenDirectory) |
Set name of current directory for Open operation.
|
(package private) void |
setCurrentSaveDirectory(java.lang.String currentSaveDirectory) |
Set name of current directory for Save operation.
|
void |
setEditTabbedPane(EditTabbedPane editTabbedPane) |
Set associated EditTabbedPane.
|
void |
setTitle(java.lang.String path,
java.lang.String name,
int status) |
Places name of file currently being edited into its edit tab and
the application's title bar.
|
public static final int MIN_TAB_SIZE
public static final int MAX_TAB_SIZE
public static final int MIN_BLINK_RATE
public static final int MAX_BLINK_RATE
public Editor(GUI gui)
gui
- the GUI that owns this editorpublic void setEditTabbedPane(EditTabbedPane editTabbedPane)
editTabbedPane
- an existing editTabbedPane objectpublic java.lang.String getCurrentOpenDirectory()
String
containing directory pathname. Returns null if there is
no EditTabbedPane. Returns default, directory MARS is launched from, if
no Opens have been performed.void setCurrentOpenDirectory(java.lang.String currentOpenDirectory)
currentOpenDirectory
- String containing pathname for current Open directory. If
it does not exist or is not a directory, the default (MARS launch directory) will be used.public java.lang.String getCurrentSaveDirectory()
void setCurrentSaveDirectory(java.lang.String currentSaveDirectory)
currentSaveDirectory
- String containing pathname for current Save directory. If
it does not exist or is not a directory, the default (MARS launch directory) will be used.public java.lang.String getNextDefaultFilename()
public void setTitle(java.lang.String path, java.lang.String name, int status)
path
- Full pathname for filename
- Name of file (last component of path)status
- Edit status of file. See FileStatus static constants.public void newFile()
public boolean close()
true
if succeeded, else false
.public boolean closeAll()
true
if succeeded, else false
.public boolean save()
true
if succeeded, else false
.public boolean saveAs()
true
if succeeded, else false
.public boolean saveAll()
true
if succeeded, else false
.public boolean open()
true
if succeeded, else false
.public boolean editsSavedOrAbandoned()
true
, then give user
a dialog box with choice to save, discard edits, or cancel and
carry out the decision. This applies to File-New, File-Open,
File-Close, and File-Exit.true
means caller can proceed (edits were saved or discarded).


Removes an items.
remove(id1, [id2], ...)
| id |
string, id of the item |
Returns integer.
Description
Removes a item or items from the .items array and refreshes them on screen. The item object is identified by the
.id property. The method returns the number of items it removes.
If you have listview defined in the following way:
You can remove items:


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
IN THE HIGH COURT OF JUDICATURE AT PATNA Criminal Writ Jurisdiction Case No.1383 of 2018 Arising Out of PS. Case No.-69 Year-2018 Thana- BARUN District- Aurangabad ====================================================== YUGAL YADAV @ JUGAL YADAV S/o Mahendra Yadav, R/o Vill.- Keshopur, Post - Jakhim, P.S.- Phesar, Distt.- Aurangabad.... ... Petitioner Versus 1. The State of Bihar, Through The Principal Secretary, Mines And Mineral Department, Govt. of Bihar, Patna. 2. The District Magistrate, Aurangabad. 3. The Superintendent of Police, Aurangabad. 4. The District Mining Officer, Aurangabad. 5. The Station House Officer Cum Officer In Charge Pauthu P.S. in the District- Aurangabad. ... ... Respondents ====================================================== Appearance : For the Petitioner/s : Mr. Ranjit Kumar, Advocate For the Respondent/s : Mr. Kumari Amrita ====================================================== CORAM: HONOURABLE MR. JUSTICE RAJEEV RANJAN PRASAD ORAL ORDER
2 11-07-2018 Heard learned counsel for the petitioner and learned counsel representing the State.
Petitioner has prayed for release of the vehicle Sonalika D135 (Tractor and Trailer) bearing Regd. No. BR-24- GA-1748 which has been seized by the Police in connection with Barun P. S. Case No. 69 of 2018, District- Aurangabad for the offences punishable under Sections 379, 420/34 of the Indian Penal Code, Section 40 of Bihar Minor Minerals Concession Rules and Section 15 of Prevention of Pollution Act. It is alleged that the vehicle in question was carrying sand illegally.
Learned counsel for the petitioner submits that the petitioner is ready and willing to abide by the terms and Patna High Court Cr. WJC No.1383 of 2018(2) dt.11-07-2018 2/3 conditions which may be imposed by this Court for provisional release of the vehicle in question.
In the facts and circumstances, pending initiation or finalization of the confiscation proceeding, let the vehicles of the petitioner be provisionally released on production of proof of ownership and registration of the vehicle in his favour subject to the following conditions:-
(i) Petitioner shall furnish surety bond of Rs. 4,00,000/- (four lakhs) (not in form of bank guarantee or cash) together with two sureties of the like amount to the satisfaction of the court below or the authority concerned.
(ii) The petitioner shall also give an undertaking that he will not deal with the vehicle in question and shall not alienate or encumber the same creating any kind of adverse interest against the interest of the State, he will not use the vehicle for nay illegal purpose and as and when required, he will produce the vehicle in question before the competent court/authority.
 WJC No.1383 of 2018(2) dt.11-07-2018 3/3 certified in presence of the petitioner and panchnama of the vehicle in question shall also be prepared and keep the same on record which may be used as secondary evidence.
(iv) Petitioner undertakes not to challenge the said photograph and panchnama so prepared in his presence at the time of release of vehicle in question for use in course of trial or the confiscation proceeding, as the case may be.
The application stands disposed of.
(Rajeev Ranjan Prasad, J) avin/-
U T


Skills That I can Bring to EDA From My Life/Work Experience
My Long Term Goal and Career Pathway
After I finish my EDA study, I want to start my career in the web development industry. While I will be working, i wish i can continue my study, learn a programming language (Java/C++). My goal is to become a devOp engineer.
Skills that I Would Like to See Developed in Myself While at EDA
I would like to develop a Growth mindset and a high EQ.
Workload Management during Boot Camp
During the boot camp I will:


Get Metrics V4
This page documents the deprecated version 4 of the Get Metrics end point.
This version MUST be implemented by November 1st 2023 and MAY be retired once v5 has been implemented
Get Metrics
Code samples
GET https://data.holder.com.au/cds-au/v1/admin/metrics HTTP/1.1
Host: data.holder.com.au
Accept: application/json
x-v: string
x-min-v: string
var headers = {
'Accept':'application/json',
'x-v':'string',
'x-min-v':'string'
};
$.ajax({
url: 'https://data.holder.com.au/cds-au/v1/admin/metrics',
method: 'get',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
GET /admin/metrics
This end point allows the ACCC to obtain operational statistics from the Data Holder (at the Data Holder Brand level) on the operation of their CDR compliant implementation. The statistics obtainable from this end point are determined by the non-functional requirements for the CDR regime.
This end point is not required to be implemented by the Australian Energy Market Operator, the Australian Energy Regulator or the Department of State administered by the Minister of Victoria administering the National Electricity (Victoria) Act 2005 (Vic).
Deprecated versions:
If the Data Holder supports private_key_jwt client authentication they MUST validate the scope.
Endpoint Version
| Version | 4 |
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| period | query | string | optional | The period of metrics to be requested. Values can be CURRENT (meaning metrics for current period, dependent on the metric type), HISTORIC (meaning metrics for previous period, depending on the metric type) or ALL. If absent the default is ALL. |
| x-v | header | string | mandatory | Version of the API end point requested by the client. Must be set to a positive integer. The data holder should respond with the highest supported version between x-min-v and x-v. If the value of x-min-v is equal to or higher than the value of x-v then the x-min-v header should be treated as absent. If all versions requested are not supported then the data holder should respond with a 406 Not Acceptable. See HTTP Headers |
| x-min-v | header | string | optional | Minimum version of the API end point requested by the client. Must be set to a positive integer if provided. The data holder should respond with the highest supported version between x-min-v and x-v. If all versions requested are not supported then the data holder should respond with a 406 Not Acceptable. |
Enumerated Values
| Parameter | Value |
|---|---|
| period | CURRENT |
| period | HISTORIC |
| period | ALL |
Example responses
200 Response
{
"data": {
"requestTime": "string",
"availability": {
"aggregate": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"unauthenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"authenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
}
},
"performance": {
"currentDay": "string",
"previousDays": [
"string"
]
},
"invocations": {
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
},
"largeSecondary": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"averageResponse": {
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"largeSecondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
}
},
"sessionCount": {
"currentDay": 0,
"previousDays": [
0
]
},
"averageTps": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"peakTps": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"errors": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
},
"authenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
}
},
"rejections": {
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"customerCount": 0,
"recipientCount": 0,
"secondaryHolder": {
"errors": {
"currentDay": 0,
"previousDays": [
0
]
},
"rejections": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"authorisations": {
"activeAuthorisationCount": {
"individual": 0,
"nonIndividual": 0
},
"newAuthorisationCount": {
"currentDay": {
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
},
"previousDays": [
{
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
}
]
},
"revokedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"amendedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"expiredAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"abandonedConsentFlowCount": {
"currentDay": 0,
"previousDays": [
0
]
}
}
},
"links": {
"self": "string"
},
"meta": {}
}
Responses
| Status | Meaning | Description | Schema |
|---|---|---|---|
| 200 | OK | Success | ResponseMetricsListV4 |
| 400 | Bad Request | The following error codes MUST be supported: |
ResponseErrorListV2 |
| 406 | Not Acceptable | The following error codes MUST be supported: |
ResponseErrorListV2 |
Response Headers
| Status | Header | Type | Format | Description |
|---|---|---|---|---|
| 200 | x-v | string | The version of the API end point that the data holder has responded with. |
Schemas
ResponseMetricsListV4
{
"data": {
"requestTime": "string",
"availability": {
"aggregate": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"unauthenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"authenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
}
},
"performance": {
"currentDay": "string",
"previousDays": [
"string"
]
},
"invocations": {
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
},
"largeSecondary": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"averageResponse": {
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"largeSecondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
}
},
"sessionCount": {
"currentDay": 0,
"previousDays": [
0
]
},
"averageTps": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"peakTps": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"errors": {
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
},
"authenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
}
},
"rejections": {
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"customerCount": 0,
"recipientCount": 0,
"secondaryHolder": {
"errors": {
"currentDay": 0,
"previousDays": [
0
]
},
"rejections": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"authorisations": {
"activeAuthorisationCount": {
"individual": 0,
"nonIndividual": 0
},
"newAuthorisationCount": {
"currentDay": {
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
},
"previousDays": [
{
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
}
]
},
"revokedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"amendedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"expiredAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"abandonedConsentFlowCount": {
"currentDay": 0,
"previousDays": [
0
]
}
}
},
"links": {
"self": "string"
},
"meta": {}
}
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| data | object | mandatory | none |
| » requestTime | DateTimeString | mandatory | The date and time that the metrics in this payload were requested. |
| » availability | AvailabilityMetricsV2 | mandatory | Availability metrics |
| » performance | PerformanceMetricsV2 | mandatory | Percentage of calls within the performance thresholds |
| » invocations | InvocationMetricsV3 | mandatory | Number of API calls in each performance tier over time |
| » averageResponse | AverageResponseMetricsV2 | mandatory | Average response time in seconds, at millisecond resolution, within each performance tier |
| » sessionCount | SessionCountMetricsV2 | mandatory | Session counts over time. Note that a session is defined as the provisioning of an Access Token. |
| » averageTps | AverageTPSMetricsV2 | mandatory | Average transactions per second over time |
| » peakTps | PeakTPSMetricsV2 | mandatory | Peak transactions per second over time |
| » errors | ErrorMetricsV2 | mandatory | Number of calls resulting in error due to server execution over time |
| » rejections | RejectionMetricsV3 | mandatory | Number of calls rejected due to traffic thresholds over time |
| » customerCount | NaturalNumber | mandatory | Number of customers with active authorisations at the time of the call |
| » recipientCount | NaturalNumber | mandatory | Number of Data Recipient Software Products with active authorisations at the time of the call |
| » secondaryHolder | SecondaryHolderMetricsV2 | conditional | Errors and rejections received by the primary data holder from the secondary data holder. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster |
| » authorisations | AuthorisationMetrics | optional | Authorisation counts for the data holder |
| links | Links | mandatory | none |
| meta | Meta | optional | none |
AvailabilityMetricsV2
{
"aggregate": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"unauthenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
},
"authenticated": {
"currentMonth": "string",
"previousMonths": [
"string"
]
}
}
Availability metrics
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| aggregate | object | mandatory | Aggregated availability metrics |
| » currentMonth | RateString | conditional | Percentage availability of the CDR platform so far for the current calendar month. 0.0 means 0%. 1.0 means 100%. Must be a positive value or zero |
| » previousMonths | [string] | conditional | Percentage availability of the CDR platform for previous calendar months. The first element indicates the last month and so on. A maximum of twelve entries is required if available. 0.0 means 0%. 1.0 means 100%. Values must be a positive or zero |
| unauthenticated | object | mandatory | Availability metrics for the unauthenticated aspects of the CDR regime |
| » currentMonth | RateString | conditional | Percentage availability of the CDR platform so far for the current calendar month. 0.0 means 0%. 1.0 means 100%. Must be a positive value or zero |
| » previousMonths | [string] | conditional | Percentage availability of the CDR platform for previous calendar months. The first element indicates the last month and so on. A maximum of twelve entries is required if available. 0.0 means 0%. 1.0 means 100%. Values must be a positive or zero |
| authenticated | object | mandatory | Availability metrics for the authenticated aspects of the CDR regime |
| » currentMonth | RateString | conditional | Percentage availability of the CDR platform so far for the current calendar month. 0.0 means 0%. 1.0 means 100%. Must be a positive value or zero |
| » previousMonths | [string] | conditional | Percentage availability of the CDR platform for previous calendar months. The first element indicates the last month and so on. A maximum of twelve entries is required if available. 0.0 means 0%. 1.0 means 100%. Values must be a positive or zero |
PerformanceMetricsV2
{
"currentDay": "string",
"previousDays": [
"string"
]
}
Percentage of calls within the performance thresholds
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| currentDay | RateString | conditional | Percentage of calls within the performance threshold for the current day. 0.0 means 0%. 1.0 means 100%. Must be a positive value or zero |
| previousDays | [string] | conditional | Percentage of calls within the performance threshold for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. 0.0 means 0%. 1.0 means 100%. Values must be a positive or zero |
InvocationMetricsV3
{
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
},
"largeSecondary": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Number of API calls in each performance tier over time
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| unauthenticated | object | mandatory | API call counts for the unauthenticated tier |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| highPriority | object | mandatory | API call counts for the high priority tier |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| lowPriority | object | mandatory | API call counts for the low priority tier |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| unattended | object | mandatory | API call counts for the unattended tier |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| largePayload | object | mandatory | API call counts for the large payload tier |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| secondary | object | conditional | API call counts for the Shared Responsibility Data Requests tier. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| largeSecondary | object | conditional | API call counts for the large Shared Responsibility Data Requests tier. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster |
| » currentDay | NaturalNumber | conditional | API call counts for current day |
| » previousDays | [integer] | conditional | API call counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
AverageResponseMetricsV2
{
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"highPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"lowPriority": {
"currentDay": 0,
"previousDays": [
0
]
},
"unattended": {
"currentDay": 0,
"previousDays": [
0
]
},
"largePayload": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
},
"largeSecondary": {
"primary": {
"currentDay": 0,
"previousDays": [
0
]
},
"secondary": {
"currentDay": 0,
"previousDays": [
0
]
}
}
}
Average response time in seconds, at millisecond resolution, within each performance tier
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| unauthenticated | object | mandatory | Average response time for the unauthenticated tier |
| » currentDay | number | conditional | Average response time for current day |
| » previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| highPriority | object | mandatory | Average response time for the high priority tier |
| » currentDay | number | conditional | Average response time for current day |
| » previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| lowPriority | object | mandatory | Average response time for the low priority tier |
| » currentDay | number | conditional | Average response time for current day |
| » previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| unattended | object | mandatory | Average response time for the unattended tier |
| » currentDay | number | conditional | Average response time for current day |
| » previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| largePayload | object | mandatory | Average response time for the large payload tier |
| » currentDay | number | conditional | Average response time for current day |
| » previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| secondary | object | conditional | Average response time for the secondary tier. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster |
| » primary | object | mandatory | Average response time as measured for the primary data holder |
| »» currentDay | number | conditional | Average response time for current day |
| »» previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| » secondary | object | mandatory | Average response time as measured for the secondary data holder |
| »» currentDay | number | conditional | Average response time for current day |
| »» previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| » largeSecondary | object | conditional | Average response time for the large payload tier. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster |
| »» primary | object | mandatory | Average response time as measured for the primary data holder |
| »»» currentDay | number | conditional | Average response time for current day |
| »»» previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| »» secondary | object | mandatory | Average response time as measured for the secondary data holder |
| »»» currentDay | number | conditional | Average response time for current day |
| »»» previousDays | [number] | conditional | Average response time for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
SessionCountMetricsV2
{
"currentDay": 0,
"previousDays": [
0
]
}
Session counts over time. Note that a session is defined as the provisioning of an Access Token.
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| currentDay | NaturalNumber | conditional | Session count for current day |
| previousDays | [integer] | conditional | Session count for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
AverageTPSMetricsV2
{
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Average transactions per second over time
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| aggregate | object | mandatory | Aggregate average transactions per second over time for all endpoints |
| » currentDay | number | conditional | Average TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Average TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
| unauthenticated | object | mandatory | Average transactions per second over time for unauthenticated endpoints |
| » currentDay | number | conditional | Average TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Average TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
| authenticated | object | mandatory | Average transactions per second over time for authenticated endpoints |
| » currentDay | number | conditional | Average TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Average TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
PeakTPSMetricsV2
{
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Peak transactions per second over time
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| aggregate | object | mandatory | Aggregate peak transactions per second over time for all endpoints |
| » currentDay | number | conditional | Peak TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Peak TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
| unauthenticated | object | mandatory | Peak transactions per second over time for unauthenticated endpoints |
| » currentDay | number | conditional | Peak TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Peak TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
| authenticated | object | mandatory | Peak transactions per second over time for authenticated endpoints |
| » currentDay | number | conditional | Peak TPS for current day. Must be a positive value or zero |
| » previousDays | [number] | conditional | Peak TPS for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. Values must be a positive or zero |
ErrorMetricsV2
{
"aggregate": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
},
"authenticated": {
"currentDay": {
"500": 0,
"property1": 0,
"property2": 0
},
"previousDays": [
{
"500": 0,
"property1": 0,
"property2": 0
}
]
}
}
Number of calls resulting in error due to server execution over time
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| aggregate | object | mandatory | Aggregate number of calls resulting in error due to server execution over time for all endpoints |
| » currentDay | NaturalNumber | conditional | Error counts for current day |
| » previousDays | [integer] | conditional | Error counts for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| unauthenticated | object | mandatory | Number of calls resulting in error due to server execution over time for unauthenticated endpoints |
| » currentDay | object | conditional | Error counts, by HTTP error code, for current day |
| »» additionalProperties | NaturalNumber | optional | Number of errors for a specific HTTP error code. Note that the property name must be 3 digits represent the HTTP error code the error is for |
| »» 500 | NaturalNumber | optional | Number of errors for HTTP error code 500. Note that this field is an example of a single entry due to the lack of OAS support for the JSON Schema patternProperties syntax. See the additionalProperties field in this schema for the generic property structure for error code counts |
| » previousDays | [object] | conditional | Error counts, by HTTP error code, for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »» additionalProperties | NaturalNumber | optional | Number of errors for a specific HTTP error code. Note that the property name must be 3 digits represent the HTTP error code the error is for |
| »» 500 | NaturalNumber | optional | Number of errors for HTTP error code 500. Note that this field is an example of a single entry due to the lack of OAS support JSON Schema patternProperties syntax. See the additionalProperties field in this schema for the generic property structure for error code counts |
| » authenticated | object | mandatory | Number of calls resulting in error due to server execution over time for authenticated endpoints |
| »» currentDay | object | conditional | Error counts, by HTTP error code, for current day |
| »»» additionalProperties | NaturalNumber | optional | Number of errors for a specific HTTP error code. Note that the property name must be 3 digits represent the HTTP error code the error is for |
| »»» 500 | NaturalNumber | optional | Number of errors for HTTP error code 500. Note that this field is an example of a single entry due to the lack of OAS support for the JSON Schema patternProperties syntax. See the additionalProperties field in this schema for the generic property structure for error code counts |
| »» previousDays | [object] | conditional | Error counts, by HTTP error code, for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »»» additionalProperties | NaturalNumber | optional | Number of errors for a specific HTTP error code. Note that the property name must be 3 digits represent the HTTP error code the error is for |
| »»» 500 | NaturalNumber | optional | Number of errors for HTTP error code 500. Note that this field is an example of a single entry due to the lack of OAS support JSON Schema patternProperties syntax. See the additionalProperties field in this schema for the generic property structure for error code counts |
RejectionMetricsV3
{
"authenticated": {
"currentDay": 0,
"previousDays": [
0
]
},
"unauthenticated": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Number of calls rejected due to traffic thresholds over time
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| authenticated | object | mandatory | Rejection counts for all authenticated end points |
| » currentDay | NaturalNumber | conditional | Number of calls rejected for current day |
| » previousDays | [integer] | conditional | Number of calls rejected for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
| unauthenticated | object | mandatory | Rejection counts for all unauthenticated end points |
| » currentDay | NaturalNumber | conditional | Number of calls rejected for current day |
| » previousDays | [integer] | conditional | Number of calls rejected for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available. |
SecondaryHolderMetricsV2
{
"errors": {
"currentDay": 0,
"previousDays": [
0
]
},
"rejections": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Errors and rejections received by the primary data holder from the secondary data holder. Mandatory for data holders designated for a Shared Responsibility Data Request data cluster
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| errors | object | mandatory | Number of calls resulting in error due to server execution over time |
| » currentDay | NaturalNumber | conditional | Number of errors for current day |
| » previousDays | [integer] | conditional | Number of errors for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| rejections | object | mandatory | Number of calls rejected due to traffic thresholds over time |
| » currentDay | NaturalNumber | conditional | Number of rejections for current day |
| » previousDays | [integer] | conditional | Number of rejections for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
AuthorisationMetrics
{
"activeAuthorisationCount": {
"individual": 0,
"nonIndividual": 0
},
"newAuthorisationCount": {
"currentDay": {
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
},
"previousDays": [
{
"onceOff": {
"individual": 0,
"nonIndividual": 0
},
"ongoing": {
"individual": 0,
"nonIndividual": 0
}
}
]
},
"revokedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"amendedAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"expiredAuthorisationCount": {
"currentDay": {
"individual": 0,
"nonIndividual": 0
},
"previousDays": [
{
"individual": 0,
"nonIndividual": 0
}
]
},
"abandonedConsentFlowCount": {
"currentDay": 0,
"previousDays": [
0
]
}
}
Authorisation counts for the data holder
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| activeAuthorisationCount | object | mandatory | The number of active ongoing authorisations |
| » individual | NaturalNumber | mandatory | Active ongoing authorisation count for individual customers |
| » nonIndividual | NaturalNumber | mandatory | Active ongoing authorisation count for non-individual customers |
| newAuthorisationCount | object | mandatory | The number of new authorisations |
| » currentDay | object | conditional | Number of new authorisations for the current day |
| »» onceOff | object | mandatory | New authorisation count for once-off authorisations |
| »»» individual | NaturalNumber | mandatory | New authorisation count for individual customers |
| »»» nonIndividual | NaturalNumber | mandatory | New authorisation count for non-individual customers |
| »» ongoing | object | mandatory | New authorisation count for ongoing authorisations |
| »»» individual | NaturalNumber | mandatory | New authorisation count for individual customers |
| »»» nonIndividual | NaturalNumber | mandatory | New authorisation count for non-individual customers |
| »» previousDays | [object] | conditional | Number of new authorisations for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »»» onceOff | object | mandatory | New authorisation count for once-off authorisations |
| »»»» individual | NaturalNumber | mandatory | New authorisation count for individual customers |
| »»»» nonIndividual | NaturalNumber | mandatory | New authorisation count for non-individual customers |
| »»» ongoing | object | mandatory | New authorisation count for ongoing authorisations |
| »»»» individual | NaturalNumber | mandatory | New authorisation count for individual customers |
| »»»» nonIndividual | NaturalNumber | mandatory | New authorisation count for non-individual customers |
| »»» revokedAuthorisationCount | object | mandatory | The number of revoked authorisations |
| »»»» currentDay | object | conditional | Number of revoked authorisations for the current day |
| »»»»» individual | NaturalNumber | mandatory | Revoked authorisation count for individual customers |
| »»»»» nonIndividual | NaturalNumber | mandatory | Revoked authorisation count for non-individual customers |
| »»»» previousDays | [object] | conditional | Number of revoked authorisations for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »»»»» individual | NaturalNumber | mandatory | Revoked authorisation count for individual customers |
| »»»»» nonIndividual | NaturalNumber | mandatory | Revoked authorisation count for non-individual customers |
| »»»» amendedAuthorisationCount | object | mandatory | The number of amended ongoing authorisations |
| »»»»» currentDay | object | conditional | Number of amended authorisations for the current day |
| »»»»»» individual | NaturalNumber | mandatory | Amended authorisation count for individual customers |
| »»»»»» nonIndividual | NaturalNumber | mandatory | Amended authorisation count for non-individual customers |
| »»»»» previousDays | [object] | conditional | Number of amended authorisations for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »»»»»» individual | NaturalNumber | mandatory | Amended authorisation count for individual customers |
| »»»»»» nonIndividual | NaturalNumber | mandatory | Amended authorisation count for non-individual customers |
| »»»»» expiredAuthorisationCount | object | mandatory | The number of expired ongoing authorisations |
| »»»»»» currentDay | object | conditional | Number of expired authorisations for the current day |
| »»»»»»» individual | NaturalNumber | mandatory | Expired authorisation count for individual customers |
| »»»»»»» nonIndividual | NaturalNumber | mandatory | Expired authorisation count for non-individual customers |
| »»»»»» previousDays | [object] | conditional | Number of expired authorisations for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
| »»»»»»» individual | NaturalNumber | mandatory | Expired authorisation count for individual customers |
| »»»»»»» nonIndividual | NaturalNumber | mandatory | Expired authorisation count for non-individual customers |
| »»»»»» abandonedConsentFlowCount | object | mandatory | The number of consents flows that were not successfully authorised |
| »»»»»»» currentDay | NaturalNumber | conditional | Number of consents flows that were not successfully authorised for the current day |
| »»»»»»» previousDays | [integer] | conditional | Number of consents flows that were not successfully authorised for previous days. The first element indicates yesterday and so on. A maximum of seven entries is required if available |
Links
{
"self": "string"
}
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| self | URIString | mandatory | Fully qualified link to this API call |
Meta
{}
Properties
None
MetaError
{
"urn": "string"
}
Additional data for customised error codes
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| urn | string | conditional | The CDR error code URN which the application-specific error code extends. Mandatory if the error code is an application-specific error rather than a standardised error code. |
ResponseErrorListV2
{
"errors": [
{
"code": "string",
"title": "string",
"detail": "string",
"meta": {
"urn": "string"
}
}
]
}
Properties
| Name | Type | Required | Description |
|---|---|---|---|
| errors | [object] | mandatory | none |
| » code | string | mandatory | The code of the error encountered. Where the error is specific to the respondent, an application-specific error code, expressed as a string value. If the error is application-specific, the URN code that the specific error extends must be provided in the meta object. Otherwise, the value is the error code URN. |
| » title | string | mandatory | A short, human-readable summary of the problem that MUST NOT change from occurrence to occurrence of the problem represented by the error code. |
| » detail | string | mandatory | A human-readable explanation specific to this occurrence of the problem. |
| » meta | MetaError | optional | Additional data for customised error codes |


You seem to be lost.
Or click here and play Snake to relieve your stress.


- 系统
- 栏目管理
{include file="public/menu" /}
{include file="public/head" /}
{include file="public/top" /}


Travel Tips
Search for Countries
Admin
Sign in to post comments!
Search for Country
Start typing the name of a country in the text box below and select a county from the list to view travel tips for your destination.
Country Name:
Select Country
Enter a name in the box above to select a country.


READY TO RUMBLE *1/2 (out of four stars) A review by Jamey Hughton
Starring-David Arquette, Scott Caan, Oliver Platt, Rose McGowan, Diamond Dallas Page, Bill Goldberg, Joe Pantoliano and Martin Landau Director-Brain Robbins Canadian Rating-14A Released by Warner Brothers - 04/00
MOVIE VIEWS by Jamey Hughton http://Welcome.to/MovieViews
An 80-year old woman jumps enthusiastically on her couch, wearing tight-fitting leather, as she cheers on her favorite TV wrestler by calling his opponent a `pump-bitch'. Two men messily eat fast food as their septic truck leaks raw sewage directly behind them. And roughly 17 people are booted in the crotch. Welcome to `Ready to Rumble'. Judging from the fact that potty-mouth Adam Sandler is the reigning box-office comedy champion, you realize -- albeit while shaking your head -- that yes, there is an audience for this sort of thing.
Ladies and gentlemen, I weep for society.
Mind you, when executed with style and comic ingenuity, jokes like an alarming bodily fluid mistaken for hair gel (`There's Something About Mary') and a laxative-induced attack of explosive diarrhea (`Dumb and Dumber') can be extremely funny. Unfortunately, `Ready to Rumble' is not being helmed by the Farrelly brothers, nor is it bolstered by a script that accommodates the viewer with anything even remotely clever or inspired. `Ready to Rumble' is built around the dedicated fan-base of professional wrestling.... which, in fact, sounded like a fine concept for a goofball comedy. But director Brian Robbins and screenwriter Steven Brill handcuff themselves, and limited to a stampede of asinine, humdrum bathroom humor, basically the only thing they manage is to evoke memories of Pauly Shore and `Bio Dome'.
Gordie Boggs (David Arquette) and Sean Dawkins (Scott Caan) take pride in being hardcore WCW wrestling fanatics. By day, they transport raw sewage. By night (particularly on ‘Nitro' Monday), they pay homage to their personal hero and savior - Jimmy King (Oliver Platt), the undisputed leader of the professional wrestling community. With two tickets to an upcoming Nitro performance, Gordie and Sean are psyched about witnessing The King defend his title first-hand. But unscrupulous boxing kingpin Titus Sinclair (Joe Pantoliano, sporting long hair and cowboy boots) has other plans.  Gordie and Sean are shocked, rioting madly while arguing `this isn't even a Pay-Per View event!!' They take it upon themselves to track The King down and supply the encouragement essential for their fallen idol to make a come-back attempt. Along the way, you can expect a lot of sh-- jokes as well.
You may find something to like in `Ready to Rumble' if a) you are a rasslin' aficionado yourself, or b) you are a dedicated fan of the lowest of low-brow comedies. I welcome low-brow humor with open arms - that is, if its fresh and resourceful. `Rumble' is nothing but a sloppy, frightfully unfunny swamp land of misbegotten retardation. The first half-hour is the ultimate test of patience. Luckily, the simple-minded events pick up steam, particularly with the well-choreographed wrestling action. Director Robbins showed a knack for capturing the brutality and excitement of football in `Varsity Blues', and when in the ring, he does professional work. But the violence is too excessive. Having the fake soap opera of WCW wrestling turn into a bloody skirmish brings back unfortunate memories of Owen Hart's tragic accident just last year, especially with one character's dive during a cage match. This is not something you want a comedy to be reminiscent of. Outside the wrestling action, the lewd jokes and puerile sight gags bring new meaning to the term ‘scattershot', while the dialogue fluctuates in on the vulgarity scale of 1 to 10, with Brill's extensive vocabulary ranging from `diddly' to `boob' and so on. The final tally: I chuckled a few times, groaned a lot, and indulged in one spirited belly laugh involving Martin Landau as a geriatric wrestling coach who fights pretty impressively for 105.
Casting-wise, `Ready to Rumble' is an odd duck. Oliver Platt as a champion wrestling figure? He's perhaps a bit chunky, but fellow wrestlers acknowledge this in the ring by calling him `fatty', which dampens the blow I suppose. Rose McGowan is fully disposable as a sultry WCW cheerleader (`The Nirto-est of the Nitro girls,' proclaims Gordie), but extra pep is added with appearances by wrestlers Goldberg, `Macho Man' Randy Savage and Sting (among others). WCW fans are sure to appreciate these. Others... well, won't. I found merit in David Arquette's bountiful energy as Gordie, which brings me to my finishing.... ahhh.... `praise' for the film: in `Ready to Rumble', I have discovered something even more annoying than Arquette's `AT&T' television commercials. Now there's a low blow for you.
(C) 2000, Jamey Hughton
NEW at MOVIE VIEWS by Jamey Hughton --> The MOVIE STORE http://Welcome.to/MovieViews
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


Company profile - Canadian Company Capabilities
Third-Party Information Liability Disclaimer
Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.
Recall Canada Holdings Inc
Legal Name:
Recall Canada Holdings Inc
Operating Name:
Recall & Mobilshred Inc
Mailing Address:
50 Driver RdBRAMPTON, Ontario
L6T 5V2
Location Address:
50 Driver RdBRAMPTON, Ontario
L6T 5V2
Tel.:<PHONE_NUMBER>
Tel.:<PHONE_NUMBER>
Fax:
Logo
Company Profile
Recall Canada Holdings Inc., is a Canadian company and is part of the Recall Global family which today is known as a global leader in lifecycle information management offering Document Management, Digital Solutions, Data Protection and Secure Destruction. Currently, Recall supports approximately 80,000 customers in more than 20 countries on five continents. With a global footprint of nearly 300 dedicated Operations Centers, we apply best-in-class solutions for small proprietorships to large multi-national corporations across a range of industries including: Financial, Banking, Insurance, Healthcare, Legal, Government, Academic, Manufacturing, Business Services, Entertainment as well as Consumer/Packaged Goods. We are a Government cleared and Controlled Goods cleared Company.
Everything we do is geared towards providing our customers peace of mind. We do this on a platform of four key pillars: Security, Efficiency, Customer Satisfaction and Sustainability.
Recall upholds community-driven values and a Corporate Social Responsibility.
Regardless of your companys size or industry or the format of your information you can count on Recall to physically and digitally manage your critical business items throughout their lifecycle. Just ask the 80,000-plus customers we serve consistently and reliably worldwide.
Recall provides the solutions and expertise you need:
Document Management Solutions - Physical and digital capturing, indexing, storage, and retrieval of critical documents.
Data Protection and Privacy Solutions - Secure storage, protection, and recovery of media and other valuable items.
Secure Media and Document Destruction Solutions - Confidential destruction of sensitive documents, media, and other business items.
Uniting best practices in document management solutions, data protection, and secure media and document destruction, Recall delivers peace of mind and bottom-line results through Security, Efficiency, Customer Satisfaction, and Sustainability.
Recall provides:
Decades of experience providing full lifecycle information management solutions from document and data pick up to storage, imaging, tracking, preservation, and destruction
Optimum security via BABACO-equipped, GPS-monitored vehicles and state-of-the-art Information and Destruction Centers
Better, smarter, more efficient solutions through innovation and a commitment to continuous improvement
Approximately 80,000 satisfied customers who take advantage of our Global Footprint, industry best practices and Perfect Order promise
Sustainable, long term solutions that protect and benefit the community at large and cause zero injuries and zero environmental damage
Ability to track and manage inventory via ReQuest® Web, Recalls intuitive, web-based platform; and
RFID-enabled technology that takes inventory audits to an unprecedented level of speed and efficiency.
Mobilshred Inc as a Canadian company is registered with the Industrial Security Program (ISP) and the controlled goods program, operating as a secure and cleared company, all Canadian employees are registered with the Canadian government and all facilities operating within the PWGSC requirements. For further information on the Canadian systems and security please contact the PWGSC, or the Controlled goods division.
Mobilshred Inc is registered with the Controlled Goods Program (CGP) this is a registration and compliance program that regulates access to controlled goods, including International Traffic in Arms Regulations (ITAR) items, in Canada. The CGP plays a vital role in the prevention and detection of the unlawful examination, possession or transfer of controlled goods in Canada. Under the authorities of the Defense Production Act (DPA) and the Controlled Goods Regulations, the CGP's mandate is to strengthen Canada's defense trade controls through the mandatory registration and regulation of businesses and individuals who examine, possess and/or transfer controlled goods.
Mobilshred Inc can be verified through the Canadian Government web site.
http://ssi-iss.tpsgc-pwgsc.gc.ca/dmc-cgd/rchrch-srch/new-search-eng.html
Full profile
Full profile
Contact information
Company description
541611 - Administrative Management and General Management Consulting Services
Product / Service / Licensing
Single-page documents in highly active files (e.g., customer contracts or medical files)
Internal records (e.g., personnel information)
Regulated files (e.g., legal documentation)
Archived files and/or cartons
Proprietary assets such as patented materials
Digital records (most media types/formats)
Film and Sound materials
Architectural drawings and blueprints
Product samples and/or prototypes
Historical artifacts
Recall also has a fleet of professional couriers and custom-equipped vehicles to retrieve, deliver and exchange your important documents and records securely, according to stringent operating procedures.
With Recall, you can choose from the following document management solutions:
Long-Term Storage:
For customers seeking compliance and space-saving solutions, Recall offers full-service offsite document storage at over 300 securely monitored, fire-protected facilities around the globe. These services include OnCall® and LegacySM storage as well as inventory management solutions via ReQuest® Web Recalls secure tracking, reporting and self-service online system.
Rapid Retrieval:
For the information you need to access - be it specific documents, files or cartons - Recall offers a range of services to ensure your information is well-protected yet securely available when you need it, where you need it and in a format in which you can use it. These services include ProntoSM, Image on ReQuest® and ReFileSM with Routine, Urgent and Priority retrieval options for both physical and digital delivery.
Premium Protection:
When you have items or information of high intrinsic value, Recall offers superior vault storage. ProTectSM entails state-of-the-art security with enhancements such as biometric access, gas suppression systems and VESDA (Very Early Smoke Detection Apparatus). In addition to fragile documents, historical artifacts, patents and the like Recall also serves customers with uncompromised protection of film and sound materials (see RePlay®).
Using advanced technologies such as Optical Character Recognition (OCR), Intelligent Character Recognition (ICR), Global Positioning Software (GPS) and Radio Frequency Identification (RFID) Recall can also help trace, track and audit your documents for the purposes of compliance, risk mitigation and peace of mind.
To help determine the document management solution that is right for you, try our Solution Finder now.
As with all solutions that Recall provides, security is our first priority. We strive to provide you with peace of mind in knowing your data is safeguarded utilizing the right processes, products and partners.
Data Protection & Security
Following global security and efficiency standards Recalls facilities, vehicles and operating procedures abide by some of the highest levels of professional protection services in the industry. Now, your IT staff can focus on mission-critical tasks, as opposed to day-to-day backup and recovery management tasks. With innovations such as Radio Frequency Identification (RFID) and Scan and Track, you can rely on Recalls precise audit trails to fulfill your business compliance requirements.
Single Source Provider
Recall not only offers premium data protection and advanced security features, but a full range of expert solutions to complement your total data protection needs. Our solutions include: Tape-based Backup and Recovery, Data Management, E-Discovery Processing, Automated Online Backup, Managed Recovery, as well as support to your existing Business Continuity and Disaster Recovery plans. Auxiliary services include Media and Tape Sales, Data center staffing, and consulting services.
Trusted Partner
As a global leader in data protection, Recall consistently earns its place at the table with the best of the best within the industry. We are proud to be affiliated with business continuity experts such as SunGard® . In addition, our PCI-certification, pursuant to Payment Card Industry (PCI) Data Security Standards, underscores our strong commitment to the customers and industries we serve. At Recall, we take a consultative approach to you and your business needs by providing custom-tailored solutions to fit your exact requirements. We utilize lean six sigma methodologies, transparent processes, and continuous improvements to ensure we remain innovative in this ever evolving industry.
Recall offers retrieval and transportation of your files or cartons to a secure Destruction Center where they are completely destroyed. To learn more about this service, click here for a DeStroySM Product Sheet.
Recalls online inventory management system, ReQuest® Web, allows customers to submit work orders, request off-schedule and special project services and generate reports at any time. Some additional key benefits of ReQuest Web for Secure Destruction Services include:
Ability to securely manage your account online - no matter where you are for around-the-clock updates;
An audit trail of requests made with customized reporting Measured security including server redundant, user permissions and encryption to the extent necessary; and a faster, more convenient way to search and process your requests.
Recall also offers information management training with our BeSure program which helps inform and educate your employees on the importance of document destruction and how to safeguard your organizations information.
Through DeStockSM, Recall can help establish document and media destruction procedures and provide on-site staff to inventory transport and dispose of excess or unwanted items such as outdated marketing or training materials, obsolete software or damaged, destructible goods. To learn more, click here for a DeStock Product Sheet.
Recalls comprehensive approach to solving your digital document management objectives begins with an analysis of your Technical and Business Requirements. We then take this information in conjunction with our industry expertise and plan, design, and propose a tailored document management solution which includes a schedule for implementation, collective measures of security and criteria for success.
The solution we propose might include one or a combination of these services and/or offerings:
Mail Room Services Handling incoming documents in preparation for digitization.
Data Capture High-quality, high-speed Optical Character Recognition (OCR) and keying activities to extract essential data for activities such as form processing.
Imaging Conversion of paper to electronic images for storage, preservation and workflow purposes.
ReView® Powered by OnBase® Recalls industry-leading, secure, web-based system that enables capturing, storing, routing and accessing data images for workflow applications.
ReQuest® Web Recalls web-based, inventory-management tool for inputting carton/file/ document details, requesting service and much more.
Electronic Data Interchange (EDI) Industry standard for receiving and transmitting information electronically.
Your digital document solutions team will provide insight and guidance in the areas of:
Integration Seamlessly connecting with legacy ERP, CRM, or other corporate systems.
Scalability Devising an enterprise or departmental document management or image hosting solution adaptable to your current and future needs.
Business Process Automation and Workflow Determining ways to eliminate wait times, redundancies, handoffs, and inefficiencies.
Business Solutions Serving specific departments or functions such as:
Accounts Payable Control spending, maximize cash flow, enhance profitability, and improve forecasting by reducing errors and variances in financial data so as to process invoices more accurately and quickly.
Claims Processing Reduce risk, improve compliance, and streamline processes by giving adjusters the information they need from submission to settlement.
Human Resources Focus on talent management versus administrative tasks by streamlining and automating benefits administration, sharing access to knowledge, and standardizing procedures.
Contract Management Capitalize on the wealth of information contained in your contracts to uncover and mitigate areas of risk and exposure, as well as analyze and respond to customer patterns.
Project Management Employ project management methodologies to ensure your budget and deadlines are met.
Learn more or see RFID in action
http://web5.streamhoster.com/mapleloft/recall/RFID/rfid_eng_v1.htm
The PCI Security Standards Council is an open global forum, launched in 2006, that is responsible for the development, management, education, and awareness of the PCI Security Standards, including the Data Security Standard (PCI DSS), Payment Application Data Security Standard (PA-DSS), and PIN Transaction Security (PTS) requirements.
The Council's five founding global payment brands -- American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa Inc. -- have agreed to incorporate the PCI DSS as the technical requirements of each of their data security compliance programs. Each founding member also recognizes the QSAs, PA-QSAs and ASVs certified by the PCI Security Standards Council.
All five payment brands share equally in the Council's governance, have equal input into the PCI Security Standards Council and share responsibility for carrying out the work of the organization. Other industry stakeholders are encouraged to join the Council as Participating Organizations and review proposed additions or modifications to the standards.
In security terms, it means that our business adheres to the PCI DSS requirements for security management, policies, procedures, network architecture, software design and other critical protective measures. In operational terms, it means that you are playing your role to make sure your customers' payment card data is being kept safe throughout every transaction, and that they and you can have confidence that they're protected against the pain and cost of data breaches.
Recall is NAID Certification
The NAID Certification Program is offered on a voluntary basis to all NAID member companies providing information destruction services. Through the program, NAID members may seek certification audits for Mobile and/or Plant-based operations in paper or printed media, micro media, computer hard drive destruction and/or computer hard drive sanitization. The NAID Certification Program establishes standards for a secure destruction process including such areas as operational security, employee hiring and screening, the destruction process, responsible disposal and insurance.
Under this program, the certification application and associated fees cover only individual locations. If a NAID member operates in multiple locations, each location must pass the audit to be certified. NAID members who receive certification must specify the location certified in company literature when referencing the NAID Certification Program.
Recall is registered with the Controlled Goods Directorate
The Controlled Goods Program (CGP) is a Federal Government Program administered by the Department of Public Works and Government Services Canada (PWGSC).
The Controlled Goods Directorate (CGD) administers the Controlled Goods Program, a domestic industrial security program that helps strengthen Canada's defence trade controls and prevents the proliferation of tactical and strategic assets including weapons, satellite global positioning systems and communications equipment, military equipment and related intellectual property. This is done by regulating and controlling the examination, possession, and transfer of controlled goods and controlled technology in Canada. Anyone who conducts business in Canada and examines, possesses and/or transfers controlled goods and/or controlled technology in Canada must comply with the Defence Production Act and the Controlled Goods Regulations.
Technology profile
Market profile
Alliances:
Strategic alliances:
Mobilshread does not Import or ExportIndustry sector market interests:
- Agriculture
- Construction
- Consumer Products
- Culture
- Environment
- Fishery
- Forestry
- Information Technology and Telecommunications
- Manufacturing
- Medical/Biotechnology/Chemical
- Mining/Petroleum/Gas
- Service Industry
- Tourism
- Transportation
- Wholesale/Retail
- Aerospace
- Defence
- Automotive
- Food and Beverage Manufacturing
- Furniture and Wood Product
- Pulp and Paper
- Plastics and Rubber Products
- Primary and Fabricated Metal
- Electrical Equipment
- Textile and Clothing
Geographic markets:
Export experience:
- Australia
- Brazil
- Canada
- France
- Germany
- Ireland
- Mexico
- Pakistan
- Thailand
- United Kingdom
- United States
- Alabama
- Alaska
- Arizona
- Arkansas
- California
- Colorado
- Connecticut
- Delaware
- District of Columbia
- Florida
- Georgia
- Hawaii
- Idaho
- Illinois
- Indiana
- Iowa
- Kansas
- Kentucky
- Louisiana
- Maine
- Maryland
- Massachusetts
- Michigan
- Minnesota
- Mississippi
- Missouri
- Montana
- Nebraska
- Nevada
- New Hampshire
- New Jersey
- New Mexico
- New York
- North Carolina
- North Dakota
- Ohio
- Oklahoma
- Oregon
- Pennsylvania
- Rhode Island
- South Carolina
- South Dakota
- Tennessee
- Texas
- Utah
- Vermont
- Virginia
- Washington
- West Virginia
- Wisconsin
- Wyoming
Sector information
Key / Major clients:
As a Canadian company Recall Canada Holdings Inc., is registered with the Industrial Security Program (PWGSC). This program safeguards sensitive government assets and controlled goods while in the custody of the private sector, they screen private sector organizations and their employees and continue to assess these companies in an ongoing bases.Third-Party Information Liability Disclaimer
Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.
Contacts
Contact information
Description
Company description
541611 - Administrative Management and General Management Consulting Services
Products, services and licensing
Product / Service / Licensing
Single-page documents in highly active files (e.g., customer contracts or medical files)
Internal records (e.g., personnel information)
Regulated files (e.g., legal documentation)
Archived files and/or cartons
Proprietary assets such as patented materials
Digital records (most media types/formats)
Film and Sound materials
Architectural drawings and blueprints
Product samples and/or prototypes
Historical artifacts
Recall also has a fleet of professional couriers and custom-equipped vehicles to retrieve, deliver and exchange your important documents and records securely, according to stringent operating procedures.
With Recall, you can choose from the following document management solutions:
Long-Term Storage:
For customers seeking compliance and space-saving solutions, Recall offers full-service offsite document storage at over 300 securely monitored, fire-protected facilities around the globe. These services include OnCall® and LegacySM storage as well as inventory management solutions via ReQuest® Web Recalls secure tracking, reporting and self-service online system.
Rapid Retrieval:
For the information you need to access - be it specific documents, files or cartons - Recall offers a range of services to ensure your information is well-protected yet securely available when you need it, where you need it and in a format in which you can use it. These services include ProntoSM, Image on ReQuest® and ReFileSM with Routine, Urgent and Priority retrieval options for both physical and digital delivery.
Premium Protection:
When you have items or information of high intrinsic value, Recall offers superior vault storage. ProTectSM entails state-of-the-art security with enhancements such as biometric access, gas suppression systems and VESDA (Very Early Smoke Detection Apparatus). In addition to fragile documents, historical artifacts, patents and the like Recall also serves customers with uncompromised protection of film and sound materials (see RePlay®).
Using advanced technologies such as Optical Character Recognition (OCR), Intelligent Character Recognition (ICR), Global Positioning Software (GPS) and Radio Frequency Identification (RFID) Recall can also help trace, track and audit your documents for the purposes of compliance, risk mitigation and peace of mind.
To help determine the document management solution that is right for you, try our Solution Finder now.
As with all solutions that Recall provides, security is our first priority. We strive to provide you with peace of mind in knowing your data is safeguarded utilizing the right processes, products and partners.
Data Protection & Security
Following global security and efficiency standards Recalls facilities, vehicles and operating procedures abide by some of the highest levels of professional protection services in the industry. Now, your IT staff can focus on mission-critical tasks, as opposed to day-to-day backup and recovery management tasks. With innovations such as Radio Frequency Identification (RFID) and Scan and Track, you can rely on Recalls precise audit trails to fulfill your business compliance requirements.
Single Source Provider
Recall not only offers premium data protection and advanced security features, but a full range of expert solutions to complement your total data protection needs. Our solutions include: Tape-based Backup and Recovery, Data Management, E-Discovery Processing, Automated Online Backup, Managed Recovery, as well as support to your existing Business Continuity and Disaster Recovery plans. Auxiliary services include Media and Tape Sales, Data center staffing, and consulting services.
Trusted Partner
As a global leader in data protection, Recall consistently earns its place at the table with the best of the best within the industry. We are proud to be affiliated with business continuity experts such as SunGard® . In addition, our PCI-certification, pursuant to Payment Card Industry (PCI) Data Security Standards, underscores our strong commitment to the customers and industries we serve. At Recall, we take a consultative approach to you and your business needs by providing custom-tailored solutions to fit your exact requirements. We utilize lean six sigma methodologies, transparent processes, and continuous improvements to ensure we remain innovative in this ever evolving industry.
Recall offers retrieval and transportation of your files or cartons to a secure Destruction Center where they are completely destroyed. To learn more about this service, click here for a DeStroySM Product Sheet.
Recalls online inventory management system, ReQuest® Web, allows customers to submit work orders, request off-schedule and special project services and generate reports at any time. Some additional key benefits of ReQuest Web for Secure Destruction Services include:
Ability to securely manage your account online - no matter where you are for around-the-clock updates;
An audit trail of requests made with customized reporting Measured security including server redundant, user permissions and encryption to the extent necessary; and a faster, more convenient way to search and process your requests.
Recall also offers information management training with our BeSure program which helps inform and educate your employees on the importance of document destruction and how to safeguard your organizations information.
Through DeStockSM, Recall can help establish document and media destruction procedures and provide on-site staff to inventory transport and dispose of excess or unwanted items such as outdated marketing or training materials, obsolete software or damaged, destructible goods. To learn more, click here for a DeStock Product Sheet.
Recalls comprehensive approach to solving your digital document management objectives begins with an analysis of your Technical and Business Requirements. We then take this information in conjunction with our industry expertise and plan, design, and propose a tailored document management solution which includes a schedule for implementation, collective measures of security and criteria for success.
The solution we propose might include one or a combination of these services and/or offerings:
Mail Room Services Handling incoming documents in preparation for digitization.
Data Capture High-quality, high-speed Optical Character Recognition (OCR) and keying activities to extract essential data for activities such as form processing.
Imaging Conversion of paper to electronic images for storage, preservation and workflow purposes.
ReView® Powered by OnBase® Recalls industry-leading, secure, web-based system that enables capturing, storing, routing and accessing data images for workflow applications.
ReQuest® Web Recalls web-based, inventory-management tool for inputting carton/file/ document details, requesting service and much more.
Electronic Data Interchange (EDI) Industry standard for receiving and transmitting information electronically.
Your digital document solutions team will provide insight and guidance in the areas of:
Integration Seamlessly connecting with legacy ERP, CRM, or other corporate systems.
Scalability Devising an enterprise or departmental document management or image hosting solution adaptable to your current and future needs.
Business Process Automation and Workflow Determining ways to eliminate wait times, redundancies, handoffs, and inefficiencies.
Business Solutions Serving specific departments or functions such as:
Accounts Payable Control spending, maximize cash flow, enhance profitability, and improve forecasting by reducing errors and variances in financial data so as to process invoices more accurately and quickly.
Claims Processing Reduce risk, improve compliance, and streamline processes by giving adjusters the information they need from submission to settlement.
Human Resources Focus on talent management versus administrative tasks by streamlining and automating benefits administration, sharing access to knowledge, and standardizing procedures.
Contract Management Capitalize on the wealth of information contained in your contracts to uncover and mitigate areas of risk and exposure, as well as analyze and respond to customer patterns.
Project Management Employ project management methodologies to ensure your budget and deadlines are met.
Learn more or see RFID in action
http://web5.streamhoster.com/mapleloft/recall/RFID/rfid_eng_v1.htm
The PCI Security Standards Council is an open global forum, launched in 2006, that is responsible for the development, management, education, and awareness of the PCI Security Standards, including the Data Security Standard (PCI DSS), Payment Application Data Security Standard (PA-DSS), and PIN Transaction Security (PTS) requirements.
The Council's five founding global payment brands -- American Express, Discover Financial Services, JCB International, MasterCard Worldwide, and Visa Inc. -- have agreed to incorporate the PCI DSS as the technical requirements of each of their data security compliance programs. Each founding member also recognizes the QSAs, PA-QSAs and ASVs certified by the PCI Security Standards Council.
All five payment brands share equally in the Council's governance, have equal input into the PCI Security Standards Council and share responsibility for carrying out the work of the organization. Other industry stakeholders are encouraged to join the Council as Participating Organizations and review proposed additions or modifications to the standards.
In security terms, it means that our business adheres to the PCI DSS requirements for security management, policies, procedures, network architecture, software design and other critical protective measures. In operational terms, it means that you are playing your role to make sure your customers' payment card data is being kept safe throughout every transaction, and that they and you can have confidence that they're protected against the pain and cost of data breaches.
Recall is NAID Certification
The NAID Certification Program is offered on a voluntary basis to all NAID member companies providing information destruction services. Through the program, NAID members may seek certification audits for Mobile and/or Plant-based operations in paper or printed media, micro media, computer hard drive destruction and/or computer hard drive sanitization. The NAID Certification Program establishes standards for a secure destruction process including such areas as operational security, employee hiring and screening, the destruction process, responsible disposal and insurance.
Under this program, the certification application and associated fees cover only individual locations. If a NAID member operates in multiple locations, each location must pass the audit to be certified. NAID members who receive certification must specify the location certified in company literature when referencing the NAID Certification Program.
Recall is registered with the Controlled Goods Directorate
The Controlled Goods Program (CGP) is a Federal Government Program administered by the Department of Public Works and Government Services Canada (PWGSC).
The Controlled Goods Directorate (CGD) administers the Controlled Goods Program, a domestic industrial security program that helps strengthen Canada's defence trade controls and prevents the proliferation of tactical and strategic assets including weapons, satellite global positioning systems and communications equipment, military equipment and related intellectual property. This is done by regulating and controlling the examination, possession, and transfer of controlled goods and controlled technology in Canada. Anyone who conducts business in Canada and examines, possesses and/or transfers controlled goods and/or controlled technology in Canada must comply with the Defence Production Act and the Controlled Goods Regulations.
Technology
Technology profile
Market
Market profile
Alliances:
Strategic alliances:
Mobilshread does not Import or ExportIndustry sector market interests:
- Agriculture
- Construction
- Consumer Products
- Culture
- Environment
- Fishery
- Forestry
- Information Technology and Telecommunications
- Manufacturing
- Medical/Biotechnology/Chemical
- Mining/Petroleum/Gas
- Service Industry
- Tourism
- Transportation
- Wholesale/Retail
- Aerospace
- Defence
- Automotive
- Food and Beverage Manufacturing
- Furniture and Wood Product
- Pulp and Paper
- Plastics and Rubber Products
- Primary and Fabricated Metal
- Electrical Equipment
- Textile and Clothing
Geographic markets:
Export experience:
- Australia
- Brazil
- Canada
- France
- Germany
- Ireland
- Mexico
- Pakistan
- Thailand
- United Kingdom
- United States
- Alabama
- Alaska
- Arizona
- Arkansas
- California
- Colorado
- Connecticut
- Delaware
- District of Columbia
- Florida
- Georgia
- Hawaii
- Idaho
- Illinois
- Indiana
- Iowa
- Kansas
- Kentucky
- Louisiana
- Maine
- Maryland
- Massachusetts
- Michigan
- Minnesota
- Mississippi
- Missouri
- Montana
- Nebraska
- Nevada
- New Hampshire
- New Jersey
- New Mexico
- New York
- North Carolina
- North Dakota
- Ohio
- Oklahoma
- Oregon
- Pennsylvania
- Rhode Island
- South Carolina
- South Dakota
- Tennessee
- Texas
- Utah
- Vermont
- Virginia
- Washington
- West Virginia
- Wisconsin
- Wyoming


Text Mirror is a data analytics web application that uses an individual's text messages (with permission) to make measurements and predictions related to their messaging habits.
Using Microsoft Azure's Machine Learning Studio, Text Mirror can make predictions about whom you plan message, plot the sentiment of conversations over time, and display common words to each friend.


Comparison of the consumption of antibiotics used for the treatment of community-onset pneumonia pre-coronavirus disease 2019 (COVID-19) (blue bars) and during COVID-19 (orange bars). Defined daily doses (DDD) of antibiotics (ceftriaxone, co-amoxiclav, levofloxacin, moxifloxacin, azithromycin and clarithromycin) were higher in February and March during the onset of the COVID-19 pandemic.


Patrick Reynolds
+ About Me
+ Projects
+ Resume
+ Contact Me
Week 1 - HTML and CSS
DBC1 Website
Solo Challange
DBC Wireframing Exercise
Week 1 Technical Blog
Week 2 - More HTML and CSS
Advanced Styling/Responsive Design
Solo Challange - GitHub.io Page
Week 2 Technical Blog
Week 3 - Javascript
Week 3 Cultural Blog
Week 3 Technical Blog
Week 4 - Ruby Algorithms
Week 4 Cultural Blog
Week 4 Technical Blog
Week 5 - Ruby Classes
Week 5 Cultural Blog
Week 5 Technical Blog
Week 6 - Object-Oriented Design
Week 6 Cultural Blog
Week 6 Technical Blog


Wikidata id: Q174989
Individual Properties:
- block_size {#unsigned long long} (size of a single block / sector in bytes) - volume_size {#unsigned long long} (total size of the file system in bytes) - volume_name {#char[256]} - endianness {little, big} - version {#int} - UUID {#char[256]} - floppy_size {DD, HD} (Does the volume_size match the size of a DD/HD floppy?) - last_mounted {#char[256]} (location of the last mounting)
Instance of File System.
Inherited Properties:
+ version (File System) + volume_name (File System) + volume_size (File System) + block_size (File System)
Found in [unix.c]
Subclass of File System.
Inherited Properties:
+ block_size (File System) + volume_size (File System) + volume_name (File System) + UUID (File System) + last_mounted (File System)
Instance of Journaling File System.
Inherited Properties:
+ volume_name (Journaling file system) + UUID (Journaling file system) + last_mounted (Journaling file system) + volume_size (Journaling file system) + block_size (Journaling file system)
Found in [linux.c]
Instance of Journaling File System.
Inherited Properties:
+ volume_name (Journaling file system) + UUID (Journaling file system) + last_mounted (Journaling file system) + volume_size (Journaling file system) + block_size (Journaling file system)
Found in [linux.c]
Instance of Journaling File System.
Inherited Properties:
+ volume_name (Journaling file system) + UUID (Journaling file system) + volume_size (Journaling file system) + block_size (Journaling file system)
Individual Properties:
- format {3.5, 3.6} - standard_journal {true, false} - start_position {#int} (start position in KiB)
Found in [linux.c]


"Freedom" in capitalist countries exists only for those who possess money and who consequently hold power."
-- Nikita Khuruschev
"Mr. Khrushchev opened the doors and windows of a petrified structure. He let in fresh air and fresh ideas, producing changes which time already has shown are irreversible and fundamental"
-- New York Times on the death of Mr. Khrushchev
If you have time, let's read more about this illustrious soviet soldier on his Wikipedia entry.


{% include 'includes/fonts.html' %} {% include 'includes/metas.html' %} {% include 'includes/ldjson.html' %} {% block head_scripts %} {{ javascriptPack(jsPackName, { mjs: true }) }} {% endblock head_scripts %}
{# {% include 'includes/svg-defs.html' %} #} {# {% include 'components/simple-masthead.html' %} #}


Hi - I would like to propose an enhancement to the 'Total pulse count to pulse increment' input processor.
At the moment, if the total pulse count is less than the last value, the processor assumes that the count in the 'transmitter' has been reset to zero, and that the new total pulse count should be treated as the number of pulses that has been received by the transmitter since the reset.
However, I have another scenario: if the transmitter has incorrectly received too many pulses, then it should be possible to reduce the total held by the transmitter to compensate for the error. In my case, this could arise because I am counting pulses of a reed switch connected to a gas meter, and my 'debounce' hardware is not perfect. I therefore need to reduce the total to match that of the gas meter - and I would then like the processor to generate a negative number of pulses.
I had thought of adding a parameter to the processor, but I could also have a (rare!) scenario where the gas meter is replaced and the total reset to zero. My proposal is therefore as follows: The assumption is that if the transmitter has been reset, then the new total number of pulses sent will be a small percentage of the previous total. Similarly, if the total has been reduced to adjust for an error, then the reduction will be a small percentage of the total. So my suggestion is that if the new value is more than half the previous value, then this is treated as a negative adjustment, otherwise it is treated as the first value after a reset.
Here is the code (from input_processor.php) that I am using:
public function pulse_diff($feedid,$time_now,$value) { $value = $this->signed2unsigned(false,false, $value); if($value>0) { $pulse_diff = 0; $last = $this->feed->get_timevalue($feedid); $last['time'] = strtotime($last['time']); if ($last['time']) { // Need to handle resets of the pulse value (and negative 2**15?) if ($value >= $last['value']) { $pulse_diff = $value - $last['value']; } else { if ($value >= $last['value'] / 2) { //Assume that this is a negative adjustment to the total number of pulses $pulse_diff = $value - $last['value']; } else { //Assume that the total number of pulses has been reset $pulse_diff = $value; } } } // Save to allow next difference calc. $this->feed->insert_data($feedid,$time_now,$time_now,$value); return $pulse_diff; } }
Re: Input Processor Enhancement Request
Hi - does anyone else think this is a good (or bad) idea?
Thanks,
Nick
Re: Input Processor Enhancement Request
The flaw I see in your algorithm is, what is the situation when the stored count is small? Any automatic adjustment like this is bound to be wrong in some circumstances, and I can't see an absolutely foolproof algorithm that will satisfy all use cases.
A "feature" like this MUST be carefully documented, else someone is bound to report the "bug" sooner or later.


Users
Name
Tags
Can access virtual hosts
Has password
Add user
Username
Password
Tags
Administrator
|
Policymaker
|
Monitoring
|
Management
|
Impersonator
|
None
Add user


target_Q = rewards + discount_tensor * not_done_mask * next_qf
with torch.enable_grad():
current_qf = self.q_network.dist(state).q_values
// for reporting only
all_q_values = current_qf.mean(dim=2).detach()
target_Q = rewards + discount_tensor * not_done_mask * next_qf
with torch.enable_grad():
current_qf = self.q_network.dist(state)
// for reporting only
all_q_values = current_qf.mean(2).detach()


{% extends "global/Page.html" %} {% load staticfiles otree %} {% block title %} Fair or Unfair? {% endblock %} {% block content %}
Now we would like to know how fair or unfair YOU thought the quiz was.
Here is the same scale you saw earlier: 0 means 'definitely unfair', 100 means 'definitely fair'. Again, this is not a true-false question: we are interested in how fair or unfair the quiz felt to you.
0 = This quiz was definitely unfair.
50 = This quiz was neither fair nor unfair.
100 = This quiz was definitely fair.


[[eventLogObj.timestamp | convertDateToUserTimezone:userTz:'MMM D, YYYY h:mm:ss a']]
Completed with status: [[eventLogObj.data.status]]
Marked as "started"
Dispatched to host [[eventLogObj.data.host_id]]
Undispatched from host [[eventLogObj.data.host_id]]
Task created
Restarted by [[eventLogObj.data.user_id]].
Activated by [[eventLogObj.data.user_id]].
Created Jira Alert .
Deactivated by user [[eventLogObj.data.user_id]].
Marked to abort by user [[eventLogObj.data.user_id]].
Priority Changed to [[eventLogObj.data.priority]] by [[eventLogObj.data.user_id]]
Dependencies overridden by user [[eventLogObj.data.user_id]].
Merge Task Unscheduled by user [[eventLogObj.data.user_id]].


Pramuditha Karunarathna
-
Contribution | Role: Student 3
Education
-
2021
-
Informatics Institue of Technology
B.Eng(Hons)Software Engineering awarded by University of Westminster
-
2020
-
G.C.E.Advance Level Results
SUBJECT GRADE Science for Technology A Engineering Technology B Information communication technology C
-
-
2018
-
NIBM
Certificate in Software Engineering
-
-
2017
-
G.C.E.Ordinary Level Results
SUBJECT GRADE Englsih A History A Information communication technology A History A Buddhism A Mathematics B Science B Sinhala B Appreciation of English Literary Texts B
-
Skills
-
HTML
-
CSS
-
JAVASCRIPT
-
JAVA
-
PYTHON
-
JAVAFX
-
SQL
-
FLUTTER
Contact Details
-
No.189/1 Senarathgama,
Katugastota,
Kandy,
Sri Lanka -
+94 764259425
-
<EMAIL_ADDRESS>-
pramuditha.20200612@iit.ac.lk


?3
4
6
7
8
9
10
_
XI
ã
The
New
York
copyright
reserved
botanical
Garden
PLANTS
OF
BAHAMA
ISLANDS
Proaerpinaca
palustris
L.
Grand
Bahama:
in
water
of
sink
in
open,
Pelican
Lake.
August
16,
1974
BOTANICAL
GARDE^
NEW
YORK
BOTANICAL
GARDEN
5004
Proserpinaca
palustris
L.
var.
palustris
Determined
by
Dr.
P.M.
Catling
-
May
2002
Agriculture
&
Agri-Food
Canada
DAO
Herbarium
d.s.Correli
&
Robert
Krai
42906
Herbarium
FAIRCHILD
TROPICAL
GARDEN
01500432
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high