baskets/baskets.service.ts
Properties |
|
Methods |
|
Accessors |
constructor(userSettingsService: UserSettingsWebService, searchService: SearchService, modalService: ModalService, selectionService: SelectionService, basketComponents: BasketComponents)
|
||||||||||||||||||
|
Defined in baskets/baskets.service.ts:110
|
||||||||||||||||||
|
Parameters :
|
| Public addToBasket | ||||||||||||||||
addToBasket(name: string, ids: string | string[], skipPatch?: boolean)
|
||||||||||||||||
|
Defined in baskets/baskets.service.ts:302
|
||||||||||||||||
|
Adds one or more documents to a basket. Emits a Basket event. Update the data on the server.
Parameters :
Returns :
boolean
true if the document was added |
| Public addToBasketModal | ||||||||||||
addToBasketModal(ids: string | string[], recordBaskets?: string[])
|
||||||||||||
|
Defined in baskets/baskets.service.ts:458
|
||||||||||||
|
Opens a dialog allowing a user to add one (or more) document(s) to a basket. the result is true if the document was added to a basket
Parameters :
Returns :
Promise<boolean>
a boolean promise resolved when the user closes the dialog the result is true if the document was added to a basket |
| Public basket | ||||||
basket(name: string)
|
||||||
|
Defined in baskets/baskets.service.ts:178
|
||||||
|
Parameters :
Returns :
Basket | undefined
a basket with the given name or null if it does not exist |
| Public createBasket | ||||||||
createBasket(basket: Basket)
|
||||||||
|
Defined in baskets/baskets.service.ts:203
|
||||||||
|
Creates a new basket unless it already exists. Emits an Basket event. Update the data on the server.
Parameters :
Returns :
boolean
true if basket was created |
| Public createBasketModal | ||||||||||
createBasketModal(model: Basket)
|
||||||||||
|
Defined in baskets/baskets.service.ts:505
|
||||||||||
|
Opens a dialog allowing a user to create new basket. the result is true if the basket was created.
Parameters :
Returns :
Promise<boolean>
a boolean promise resolved when the user closes the dialog the result is true if the basket was created. |
| Public deleteBasket | ||||||
deleteBasket(basket: Basket)
|
||||||
|
Defined in baskets/baskets.service.ts:273
|
||||||
|
Deletes the given Basket (based on its name) Emits an Basket event. Update the data on the server.
Parameters :
Returns :
boolean
true if basket was deleted |
| makeQuery | ||||||
makeQuery(basket: Basket)
|
||||||
|
Defined in baskets/baskets.service.ts:584
|
||||||
|
Parameters :
Returns :
Query
|
| Public manageBasketsModal |
manageBasketsModal()
|
|
Defined in baskets/baskets.service.ts:543
|
|
Opens a dialog allowing a user to reorganize and edit the list of baskets. the result is true is the list was updated.
Returns :
Promise<boolean>
a boolean promise resolved when the user closes the dialog the result is true is the list was updated. |
| ngOnDestroy |
ngOnDestroy()
|
|
Defined in baskets/baskets.service.ts:594
|
|
Returns :
void
|
| notifyOpenBasket | ||||||
notifyOpenBasket(basket: Basket)
|
||||||
|
Defined in baskets/baskets.service.ts:590
|
||||||
|
Parameters :
Returns :
void
|
| Public removeFromAllBaskets | ||||||||
removeFromAllBaskets(id: string)
|
||||||||
|
Defined in baskets/baskets.service.ts:383
|
||||||||
|
Removes a document from all the baskets
Parameters :
Returns :
boolean
|
| Public removeFromBasket | ||||||||||||||||
removeFromBasket(name: string, ids: string | string[], skipPatch?: boolean)
|
||||||||||||||||
|
Defined in baskets/baskets.service.ts:344
|
||||||||||||||||
|
Removes one or more documents from a basket. Emits a Basket event. Update the data on the server.
Parameters :
Returns :
boolean
true if the document was removed |
| Public removeFromBasketModal | ||||||||||||
removeFromBasketModal(ids: string | string[], recordBaskets?: string[])
|
||||||||||||
|
Defined in baskets/baskets.service.ts:483
|
||||||||||||
|
Opens a dialog allowing a user to remove one (or more) document(s) from a basket. the result is true if the document was removed from a basket
Parameters :
Returns :
Promise<boolean>
a boolean promise resolved when the user closes the dialog the result is true if the document was removed from a basket |
| Public searchBasket |
searchBasket(basket: Basket, path?: string)
|
|
Defined in baskets/baskets.service.ts:437
|
|
Uses the SearchService to perform a search returning all the documents in this basket
Returns :
Promise<boolean>
the search service promise |
| Public updateBasket | ||||||||||||
updateBasket(basket: Basket, index: number)
|
||||||||||||
|
Defined in baskets/baskets.service.ts:228
|
||||||||||||
|
Update the basket at the given index, unless a basket with the same name already exists in the list of baskets. Emits a Basket event. Update the data on the server.
Parameters :
Returns :
boolean
true if basket was updated |
| Public updateBaskets | ||||||||||||
updateBaskets(baskets: Basket[], auditEvents?: AuditEvents)
|
||||||||||||
|
Defined in baskets/baskets.service.ts:259
|
||||||||||||
|
Updates the full list of Baskets. Emits a Basket event. Update the data on the server.
Parameters :
Returns :
boolean
|
| Public basketComponents |
Type : BasketComponents
|
Decorators :
@Inject(BASKET_COMPONENTS)
|
|
Defined in baskets/baskets.service.ts:117
|
| Public modalService |
Type : ModalService
|
|
Defined in baskets/baskets.service.ts:115
|
| Public searchService |
Type : SearchService
|
|
Defined in baskets/baskets.service.ts:114
|
| Public selectedRecordsAction |
Type : Action
|
|
Defined in baskets/baskets.service.ts:110
|
| Public selectionService |
Type : SelectionService
|
|
Defined in baskets/baskets.service.ts:116
|
| Public userSettingsService |
Type : UserSettingsWebService
|
|
Defined in baskets/baskets.service.ts:113
|
| baskets |
getbaskets()
|
|
Defined in baskets/baskets.service.ts:142
|
|
Returns the list of this user's baskets. The list is stored in the user settings (this is a redirection). Using this service creates the list of baskets if it does not already exist.
Returns :
Basket[]
|
| events |
getevents()
|
|
Defined in baskets/baskets.service.ts:154
|
|
Triggers any event among BasketChangeEvent (use for fine-grained control of baskets workflow)
Returns :
Subject<BasketChangeEvent>
|
| changes |
getchanges()
|
|
Defined in baskets/baskets.service.ts:163
|
|
Triggers when events affect the list of baskets (use to refresh basket menus) Cf. CHANGE_EVENTS list
Returns :
Subject<BasketChangeEvent>
|
| hasBasket |
gethasBasket()
|
|
Defined in baskets/baskets.service.ts:170
|
|
Returns :
boolean
|
import {Injectable, Inject, InjectionToken, Type, OnDestroy} from "@angular/core";
import {Observable, Subject} from "rxjs";
import {UserSettingsWebService, AuditEvent, AuditEvents} from "@sinequa/core/web-services";
import {ModalService, ModalResult} from "@sinequa/core/modal";
import {Utils} from "@sinequa/core/base";
import {SelectionService} from "@sinequa/components/selection";
import {Action} from "@sinequa/components/action";
import {SearchService} from "@sinequa/components/search";
import {Query} from '@sinequa/core/app-utils';
// Basket interface (from models/UserSettings)
export interface Basket {
name: string;
description?: string;
ids?: string[];
}
// Audit Events (from models/Audit)
export const enum BasketEventType {
Loaded = "Basket_Loaded",
Add = "Basket_Add",
Delete = "Basket_Delete",
DeleteAll = "Basket_DeleteAll",
Update = "Basket_Update",
Rename = "Basket_Rename",
AddDoc = "Basket_AddDoc",
RemoveDoc = "Basket_RemoveDoc",
Open = "Basket_Open",
ExportCSV = "Basket_ExportCSV",
Patched = "Basked_Patched"
}
// Types of events triggering a change event
export const BASKET_CHANGE_EVENTS = [
BasketEventType.Loaded,
BasketEventType.Add,
BasketEventType.Delete,
BasketEventType.DeleteAll,
BasketEventType.Update,
BasketEventType.Rename
];
// CRUD Events
export interface BasketChangeEvent {
type: BasketEventType;
basket?: Basket;
}
// Model expected by the SelectBasket Modal.
// The filter allows to filter out baskets from the complete list
export interface SelectBasketModel {
basket: Basket | undefined;
basketFilter?: (basket: Basket) => boolean;
allowNew?: boolean;
}
// Model expected by the ManageBaskets Modal.
export interface ManageBasketsModel {
baskets: Basket[];
auditEvents?: AuditEvent[];
}
/**
* The modal types are unknown to this service.
* The module using this service must provide these components
* in their forRoot() method
*
* Example below:
*
* public static forRoot(): ModuleWithProviders<BasketsModule> {
return {
ngModule: BasketsModule,
providers: [
{
provide: BASKET_COMPONENTS,
useValue: {
selectBasketModal: SelectBasket,
editBasketModal: EditBasket,
manageBasketsModal: ManageBaskets
}
},
BasketsService
]
};
}
*/
export interface BasketComponents {
selectBasketModal: Type<any>;
editBasketModal: Type<any>;
manageBasketsModal: Type<any>;
}
export const BASKET_COMPONENTS = new InjectionToken<BasketComponents>('BASKET_COMPONENTS');
@Injectable({
providedIn: 'root',
})
export class BasketsService implements OnDestroy {
private readonly _events = new Subject<BasketChangeEvent>();
private readonly _changes = new Subject<BasketChangeEvent>();
// An application may want to alter the action (icon, etc.)
public selectedRecordsAction: Action;
constructor(
public userSettingsService: UserSettingsWebService,
public searchService: SearchService,
public modalService: ModalService,
public selectionService: SelectionService,
@Inject(BASKET_COMPONENTS) public basketComponents: BasketComponents
){
// Listen to the user settings
this.userSettingsService.events.subscribe(event => {
// E.g. new login occurs
// ==> Menus need to be rebuilt
this._events.next({type: BasketEventType.Loaded});
});
// Listen to own events, to trigger change events
this._events.subscribe(event => {
if(BASKET_CHANGE_EVENTS.indexOf(event.type) !== -1){
this.changes.next(event);
}
});
// Register a basket action onto the selection service, so that users can add/remove to/from baskets when documents are selected
this.selectedRecordsAction = this.buildBasketsAction();
}
// GETTERS
/**
* Returns the list of this user's baskets.
* The list is stored in the user settings (this is a redirection).
* Using this service creates the list of baskets if it does not already exist.
*/
public get baskets() : Basket[] {
if(!this.userSettingsService.userSettings)
this.userSettingsService.userSettings = {};
if(!this.userSettingsService.userSettings["baskets"])
this.userSettingsService.userSettings["baskets"] = [];
return this.userSettingsService.userSettings["baskets"];
}
/**
* Triggers any event among BasketChangeEvent
* (use for fine-grained control of baskets workflow)
*/
public get events() : Subject<BasketChangeEvent> {
return this._events;
}
/**
* Triggers when events affect the list of baskets
* (use to refresh basket menus)
* Cf. CHANGE_EVENTS list
*/
public get changes() : Subject<BasketChangeEvent> {
return this._changes;
}
/**
* @returns true if there is at least one basket
*/
public get hasBasket(): boolean {
return this.baskets.length > 0;
}
/**
* @returns a basket with the given name or null if it does not exist
* @param name
*/
public basket(name: string): Basket | undefined {
const i = this.basketIndex(name);
return i>= 0? this.baskets[i] : undefined;
}
private basketIndex(name: string): number {
for (let i = 0, ic = this.baskets.length; i < ic; i++) {
const basket = this.baskets[i];
if (basket && basket.name === name) {
return i;
}
}
return -1;
}
// CRUD
/**
* Creates a new basket unless it already exists.
* Emits an Basket event.
* Update the data on the server.
* @param basket the basket to create
* @returns true if basket was created
*/
public createBasket(basket: Basket) : boolean {
if(this.basketIndex(basket.name) >= 0)
return false; // This basket already exists
this.baskets.unshift(basket);
this._events.next({type : BasketEventType.Add, basket: basket});
this.patchBaskets([{
type: BasketEventType.Add,
detail: {
basket: basket.name
}
}]);
return true;
}
/**
* Update the basket at the given index, unless a basket with the same name
* already exists in the list of baskets.
* Emits a Basket event.
* Update the data on the server.
* @param basket the basket to update
* @param index the index at which to update the basket
* @returns true if basket was updated
*/
public updateBasket(basket: Basket, index : number) : boolean {
const prevIndex = this.basketIndex(basket.name);
if(prevIndex !== -1 && index !== prevIndex)
return false; // A basket with the same name exists at a different index
if(index >= 0 && index < this.baskets.length){
this.baskets.splice(index, 1, basket);
this._events.next({type : BasketEventType.Update, basket: basket});
this.patchBaskets([
{
type: BasketEventType.Update,
detail: {
basket: basket.name
}
}
], true);
return true;
}
return false; // This basket does not exist
}
/**
* Updates the full list of Baskets.
* Emits a Basket event.
* Update the data on the server.
* @param baskets the new list of baskets
* @param auditEvents the list of audit events to log
*/
public updateBaskets(baskets: Basket[], auditEvents?: AuditEvents) : boolean {
Utils.arraySet(this.baskets, baskets);
this._events.next({type : BasketEventType.Update});
this.patchBaskets(auditEvents, true);
return true;
}
/**
* Deletes the given Basket (based on its name)
* Emits an Basket event.
* Update the data on the server.
* @param basket
* @returns true if basket was deleted
*/
public deleteBasket(basket: Basket) : boolean {
const index = this.basketIndex(basket.name);
if(index === -1)
return false; // Nothing to delete
this.baskets.splice(index, 1);
this._events.next({type : BasketEventType.Delete, basket: basket});
this.patchBaskets([
{
type: BasketEventType.Delete,
detail: {
savedquery: basket.name
}
}
], true);
return true;
}
/**
* Adds one or more documents to a basket.
* Emits a Basket event.
* Update the data on the server.
* @param name basket to which to add the document(s)
* @param ids id(s) of the document(s) to add to the basket
* @param skipPatch if true, will not update the data on the server (use for bulk updates)
* @returns true if the document was added
*/
public addToBasket(name: string, ids: string | string[], skipPatch?: boolean): boolean {
if (!ids) {
return false;
}
const basket = this.basket(name);
if (!basket) return false;
if (!basket.ids) basket.ids = [];
if (Utils.isArray(ids)) {
for (let i = 0, ic = ids.length; i < ic; i++) {
const id = ids[i];
if (basket.ids.indexOf(id) === -1) {
basket.ids.push(id);
}
}
}
else {
if (basket.ids.indexOf(<string>ids) === -1) {
basket.ids.push(<string>ids);
}
}
if(!skipPatch){
this._events.next({type : BasketEventType.AddDoc});
this.patchBaskets({
type: BasketEventType.AddDoc,
detail: {
basket: name,
"doc-id": basket.ids[0]
}
});
}
return true;
}
/**
* Removes one or more documents from a basket.
* Emits a Basket event.
* Update the data on the server.
* @param name basket from which to remove the document(s)
* @param ids id(s) of the document(s) to remove from the basket
* @param skipPatch if true, will not update the data on the server (use for bulk updates)
* @returns true if the document was removed
*/
public removeFromBasket(name: string, ids: string | string[], skipPatch?: boolean): boolean {
if (!ids) {
return false;
}
const basket = this.basket(name);
if (!basket) return false;
if (!basket.ids) basket.ids = [];
if (Utils.isArray(ids)) {
for (let i = 0, ic = ids.length; i < ic; i++) {
const id = ids[i];
const index = basket.ids.indexOf(id);
if (index !== -1) {
basket.ids.splice(index, 1);
}
}
}
else {
const index = basket.ids.indexOf(<string>ids);
if (index !== -1) {
basket.ids.splice(index, 1);
}
}
if(!skipPatch){
this._events.next({type : BasketEventType.RemoveDoc});
this.patchBaskets({
type: BasketEventType.RemoveDoc,
detail: {
basket: name,
"doc-id": basket.ids[0]
}
}, true);
}
return true;
}
/**
* Removes a document from all the baskets
* @param id id of the document to remove
*/
public removeFromAllBaskets(id: string) : boolean {
const auditEvents: AuditEvent[] = [];
for (const basket of this.baskets) {
if( this.removeFromBasket(basket.name, id, true) ){
auditEvents.push({
type: BasketEventType.RemoveDoc,
detail: {
basket: basket.name,
"doc-id": id
}
});
}
}
if(auditEvents.length > 0) {
this._events.next({type : BasketEventType.RemoveDoc});
this.patchBaskets(auditEvents, true);
return true;
}
return false;
}
/**
* Updates Baskets in User settings.
* @param auditEvents : Audit Events to be triggered
* @returns an Observable which can be used to trigger further events
*/
private patchBaskets(auditEvents?: AuditEvents, updateSearch?: boolean): Observable<void> {
const obs = this.userSettingsService.patch({baskets: this.baskets}, auditEvents);
obs.subscribe(
next => {
this._events.next({type: BasketEventType.Patched});
if(updateSearch && this.searchService.query.basket) {
this.searchService.search(); // Update search results to reflect the new basket content
}
},
error => {
console.error("Could not patch Baskets!", error);
});
return obs;
}
// EVENT HANDLERS (Menus)
/**
* Uses the SearchService to perform a search returning all
* the documents in this basket
* @param basket
* @param path
* @returns the search service promise
*/
public searchBasket(basket : Basket, path?: string) : Promise<boolean> {
const query = this.searchService.makeQuery();
query.basket = basket.name;
this.searchService.setQuery(query);
this._events.next({type: BasketEventType.Open, basket: basket});
return this.searchService.search({ path: path }, {
type: BasketEventType.Open,
detail: {
basket: basket.name
}
});
}
/**
* Opens a dialog allowing a user to add one (or more) document(s)
* to a basket.
* @param ids id(s) of the documents to add to a basket
* @param recordBaskets names of the baskets the document already belongs to
* @returns a boolean promise resolved when the user closes the dialog
* the result is true if the document was added to a basket
*/
public addToBasketModal(ids: string | string[], recordBaskets?: string[])
: Promise<boolean> {
const model : SelectBasketModel = {
basket: undefined,
basketFilter: recordBaskets? b => !recordBaskets.includes(b.name) : undefined,
allowNew: true
};
return this.modalService
.open(this.basketComponents.selectBasketModal, {model: model})
.then(result => {
if (result === ModalResult.OK && model.basket) {
return this.addToBasket(model.basket.name, ids);
}
return false;
});
}
/**
* Opens a dialog allowing a user to remove one (or more) document(s)
* from a basket.
* @param ids id(s) of the documents to remove from a basket
* @param recordBaskets names of the baskets the document already belongs to
* @returns a boolean promise resolved when the user closes the dialog
* the result is true if the document was removed from a basket
*/
public removeFromBasketModal(ids: string | string[], recordBaskets?: string[])
: Promise<boolean> {
const model : SelectBasketModel = {
basket: undefined,
basketFilter: recordBaskets? b => recordBaskets.includes(b.name) : undefined
};
return this.modalService
.open(this.basketComponents.selectBasketModal, {model: model})
.then(result => {
if (result === ModalResult.OK && model.basket) {
return this.removeFromBasket(model.basket.name, ids);
}
return false;
});
}
/**
* Opens a dialog allowing a user to create new basket.
* @param model the initial basket object model
* @returns a boolean promise resolved when the user closes the dialog
* the result is true if the basket was created.
*/
public createBasketModal(model: Basket = {name: ""}) : Promise<boolean> {
return this.modalService.open(this.basketComponents.editBasketModal, {model: model})
.then((result) => {
if (result === ModalResult.OK) {
const index = this.basketIndex(model.name);
if (index !== -1) {
return this.modalService.yesNo("msg#baskets.basketAlreadyExists")
.then((result) => {
if (result === ModalResult.Yes) {
return this.updateBasket(model, index);
}
return false;
});
}
else {
return this.createBasket(model);
}
}
return false;
});
}
// Not relevant as of now
// public editBasketModal(basket: Basket)
/**
* Opens a dialog allowing a user to reorganize and edit the
* list of baskets.
* @returns a boolean promise resolved when the user closes the dialog
* the result is true is the list was updated.
*/
public manageBasketsModal() : Promise<boolean> {
const model: ManageBasketsModel = { baskets: Utils.copy(this.baskets) };
return this.modalService.open(this.basketComponents.manageBasketsModal, {model: model})
.then((result) => {
if (result === ModalResult.OK) {
return this.updateBaskets(model.baskets, model.auditEvents);
}
return false;
});
}
private buildBasketsAction() : Action {
return new Action({
icon: "fas fa-shopping-basket",
title: "msg#baskets.baskets",
name: "baskets",
hidden: true,
children: [
new Action({
text: "msg#baskets.addToBasket",
action: (item, $event) => {
this.addToBasketModal(this.selectionService.getSelectedIds());
}
}),
new Action({
text: "msg#baskets.removeFromBasket",
action: (item, $event) => {
this.removeFromBasketModal(this.selectionService.getSelectedIds());
}
})
],
updater: (action) => {
action.hidden = !this.selectionService.haveSelectedRecords;
}
});
}
makeQuery(basket: Basket): Query {
const query = this.searchService.makeQuery();
query.basket = basket.name;
return query;
}
notifyOpenBasket(basket: Basket) {
this._events.next({type: BasketEventType.Open, basket});
}
ngOnDestroy() {
this.events.complete();
this.changes.complete();
}
}


×
Getting started with DeepTeach...
youtube
DeepTeach -
the Interactive Deep Image Classifier Builder
Back
How to get started?


As an owner of Trezor, I always want to get my hand on a Ledger Nano S as they are the most famous hardware wallet in the field. This was ordered at EUR 45 during the Black Friday deal which offered 21% discount, the overall experience is also complimented by the speedy DHL shipping service.
The Walk-through
The first impression was the packaging. I have to say Ledger paid close attention to their product packaging, the box itself just feels a lot more premium than the Trezor’s. The minimal design on the front is very much appealing too.
The Nano S is secured firmly in the protective foam. So far there is no anti-tampering sticker on this box like what Trezor did with their box. Ledger claims that the wallet is built on a distinctive operating system (OS) called BOLOS which is tamper resistant.
The EAL 5+ certified secure chip we are using is the same one on your credit card or in your passport. Hacking a secure chip takes formidable efforts while information can be easily extracted from generic microcontrollers by amateurs.
In other words, Ledger Nano S is physically unhackable so they would not even bother to prove its authenticity with packaging tricks.
A small envelope consists of three pieces of paper. From left to right, they are:
- Recovery phrase sheet to backup the seed while setting up the wallet. There are only one and I would suggest it is better to backup on another piece of paper as well. Redundancy never goes wrong.
- Explanation of why the box isn’t using an anti-tempering sticker.
- Simple instruction to start setting up the wallet.
Bunch of accessories like the key ring, key chain, USB cable, and necklace.
The detachable necklace is what surprise me the most. Now you can carry the precious wallet with all fund inside with you whenever you go. Although I doubt that would be a good idea.
Front and back of the Nano S. An interesting phrase Vires in numeris
was printed on the back. After some googling, that is a sentence in Latin meaning “Strength in numbers”, which is also the tagline of Bitcoin. Indeed, the whole idea of cryptocurrency is just dealing with all kind of numbers.
Two buttons at the bottom of the screen. They will be responsible for all the operations.
Nano S use a USB drive-like design with a joint to protect the screen and USB port. As you can see in the GIF, the joint is strong and doesn’t wobble at all. The sturdiness of small detail like this definitely convinces users on the build quality.
The Thoughts
In the sense of packaging and build quality, I would say Ledger Nano S with a cheaper price tag already surpassed Trezor in many ways. More accessories, beautiful box architecture, and great wallet design.
Of course, we cannot judge the wallet simply by its physical appearance. We shall cover more in the wallet configuration and software part. Til then.
Posted on Utopian.io - Rewarding Open Source Contributors
This page is synchronized from the post: ‘TechReview#1 - Unboxing of Ledger Nano S’


The CONTSEM ontology defines the necessary concepts to descrube public procurement contracct and various elements needed to describe its procedure.
The ontology has been designed with the main purpose of publishing data about public contracts. The starting point of it has been the Public Contracts Ontology, an ontology developed by the czech Open Data initiative.
The ontology defined in this document can be obtained in RDF/XML format here.
The CONTSEM ontology has been developed under the project "Public procurement optimization through semantic technologies" (CONTSEM as spanish acronym). this project involves the participation of iASoft (OESIA) company, the University of Zaragoza and, as public entities users, the Goverment of Aragón, the Provincial Council of Huesca and the town halls of Huesca and Zaragoza. The main purpose of the project is to add semantic technologies in the software used by public authorities in the procurement procedures. More specifically, one of the core objetives is to describe semantically the information published in official procurement bulletins. For this purpose CONTSEM participants have developed the ontology, focused towards Spain laws and Europe in general.
The ontology reuses various ontologies and schemes to describe some entities, more specifically, we make use of the following ontologies and schemes:
| contratacion | <http://contsem.unizar.es/def/sector-publico/contratacion#> |
| owl | <http://www.w3.org/2002/07/owl#> |
| rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
| xsd | <http://www.w3.org/2001/XMLSchema#> |
| dcterms | <http://purl.org/dc/terms/#> |
| pc | <http://purl.org/procurement/public-contracts#> |
| loted | <http://loted.eu/ontology#> |
| org | <http://www.w3.org/ns/org#> |
| s | <http://schema.org/> |
| skos | <http://www.w3.org/2004/02/skos/core#> |
| gr | <http://purl.org/goodrelations/v1#> |
| ex | <http://example.com/> |
The main class of CONTSEM ontology is contratacion:Contract
. This class act as a core from which most of properties that defines the contract starts from.
The CONTSEM Contract class is a subclass of pc:Contract
as some properties are reused and many other are with the ones introduced here.
The Contract class has many subclasses that helps to better define the nature of the contract, the full classification of the Contract class is the following.
As we can see the contratacion:Contract
class may represent both a full contract and a lot of a contract. Obviously, there are some limit when using this classification, and contracts without lots cannot have related lots and viceversa. We can see the lot classification usage in the next figure.
Surrounding contratacion:Contract
class, we may find several classes that are firmly related with the contract itself, i.e. tenderers requirements or the object of the contract. We include this set of classes and properties altogether and name them as Contract box. Though this entity does not exist as it in the CONTSEM ontology, it helps us to explain some relations and easy understand the diagrams. The Contract box is composed by the next classes.
Once defined some core concepts of the contract we can expand its description and use the rest of the classes and properties.
A document describing more in-depth the CONTSEM ontology can be found here. We are working on expanding the actual web document to include full specification and examples that the linked document has.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#AcceptedTender
IRI: http://contsem.unizar.es/def/sector-publico/contsem#AdditionalInformationNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#AgreementContract
Class describing the contract concerts with natural or legal person performing similar services at the public service in question.
IRI: http://purl.org/procurement/public-contracts#AwardCriteriaCombination
IRI: http://purl.org/procurement/public-contracts#AwardCriterion
IRI: http://contsem.unizar.es/def/sector-publico/contsem#AwardedTender
Class describing the awarded tenders.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Briefing
Informative meeting about the public procurement contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#BundlePriceSpecification
Class used to describe the price a set of objets.
Can be used to define the total price of an gr:Offering. Its value must be equal to the gr:UnitPriceSpecification multiplied by the number of items.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#BuyContract
Class to describe the supplies contracts aimed to buy supplies.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#CommitteeMember
Class that describes the member a committee.
IRI: http://www.w3.org/2004/02/skos/core#Concept
IRI: http://www.w3.org/2004/02/skos/core#ConceptScheme
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ConcessionContract
Class of the contracts in which the awarded tenderer manage the public service themselves.
IRI: http://purl.org/procurement/public-contracts#Contract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractAbandonment
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractAdditionalObligations
Class describing the additional obligations the contract needs (e.g. guarantees or advertisement costs)
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractAwardNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractBodies
Class describing the bodies related to the contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractCompensation
Class that defines the object of the contract and the conditions or modifications the contract can have.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractEconomicConditions
Class defining the actual economic conditions of the contract (e.g. budget or the formula that describes the revision of its price).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractExecutionConditions
Class that defines the execution conditions of the contract (e.g. special execution conditions or subcontracting percentage amounts).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractModification
During the execution of a contract it could happen that the contract should be modified, to describe these kind of situations we use this class.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractModificationConditions
Class describing the conditions for which a contract can be modified (e.g. maximum percentage of its price or budget).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractOrProcedureExtinction
Abstract class. There are some circumstances resulting in the extinction of the procedure of the contract or the contract itself. To describe that situations we may use one of its subclasses.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractProcedureSpecifications
Class that specifies the procedure of a contract (e.g. type of procedure or its urgency).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractProcedures
Class describing all procedures of a contract (e.g. meetings or agreements of the contracting body).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractResolution
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractTemporalConditions
Class that describes the temporal conditions of the contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractWaive
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractWithLots
Class of the contract that have lots.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractWithoutLots
Class to describe the contract not divided into lots.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ContractingBodyAgreement
IRI: http://contsem.unizar.es/def/sector-publico/contsem#CorrectionNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#CriterionScore
Class to describe each award criterion and its score.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#DeclarationContract
Class describing the contracts consisting in the declaration of a framework agreement or a dynamic purchasing system.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#DerivativeContract
Class describing contracts derived from a framework agreement or a dynamic purchasing system.
IRI: http://xmlns.com/foaf/0.1/Document
IRI: http://contsem.unizar.es/def/sector-publico/contsem#DynamicPurchasingSystemDeclarationContract
Class describing the contracts consisting in the declaration of a dynamic purchasing system.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#DynamicPurchasingSystemDerivativeContract
Class describing contracts derived from a dynamic purchasing system.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ElectronicAuction
Class that specifies the existence of an electronic auction of one or more of the award criterions.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ElectronicAuctionPhase
Class describing a phase of an electronic auction.
IRI: http://schema.org/Event
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ExcludedTender
Class that defines the tenders excluded from the procurement procedure.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ExpertCommittee
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ExtendableContract
Class describing contracts whose end date can be extended.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#FormalizationNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#FormalizedTender
Class describing tenders being formalized.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#FrameworkAgreement
Class used to describe a contract that is a declaration of a framework agreement or a dynamic purchasing system.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#FrameworkDeclarationContract
Class describing the contracts consisting in the declaration of a framework agreement.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#FrameworkDerivativeContract
Class describing contracts derived from a framework agreement.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#HarmonizedContract
Class to describe harmonized contracts (i.e. contracts that reachs the threshold to be treated as highlighted in the procurement Directives of the European Commision and European Council).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#InformationProvider
Class defining the provider of information about the contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#LeaseContract
Class defining supplies contracts aimed to lease supplies.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#LegalRemedy
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Lot
Class describing contracts that are an actual lot of another contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#MixedCapitalCompanyContract
Class describing the contracts where the contracting authority participates concurrently with the natural or legal person.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#MixedContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#MultiannualContract
Class describing the multiannual contracts (i.e. contract whose duration extends over more than one financial year).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Notice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ObjectiveAwardCriterion
Class describing criterioa that depend on a value judgement.
IRI: http://purl.org/goodrelations/v1#Offering
IRI: http://contsem.unizar.es/def/sector-publico/contsem#OrdinaryAdministrativeRemedy
IRI: http://www.w3.org/ns/org#Organization
IRI: http://xmlns.com/foaf/0.1/Person
IRI: http://schema.org/Place
IRI: http://schema.org/PostalAddress
IRI: http://purl.org/goodrelations/v1#PriceSpecification
IRI: http://contsem.unizar.es/def/sector-publico/contsem#PriorInformationNotice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#PrivateContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Contract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#PublicServicesManagementContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#PublicWorksConcessionContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#PublicPrivateCooperationContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Remedy
Remedy lodged concerning a resolution about the procurement procedure.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#RentContract
Class defining supplies contracts aimed to rent supplies.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#ServicesContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#SpecialAdministrativeContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#SpecialAdministrativeRemedy
IRI: http://contsem.unizar.es/def/sector-publico/contsem#SubjectiveAwardCriterion
Class used to describe criteria that depend on a subjetive opinion.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#SuppliesContract
Class describing contracts whose object is the acquisition of supplies.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#TechnicalCommittee
IRI: http://purl.org/procurement/public-contracts#Tender
IRI: http://contsem.unizar.es/def/sector-publico/contsem#Committee
Abstract class describing a set of persons in committee and its roles.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#TenderCommittee
IRI: http://contsem.unizar.es/def/sector-publico/contsem#TenderMeeting
Class describing the meetings of tender committee.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#TenderRequirements
Class to define the tender requirements needed to submit a tender (e.g. tender document needs).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#TenderersRequirements
Class defining the tenderers requirements (e.g. required classification or financial capability).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#VoidProcedure
IRI: http://contsem.unizar.es/def/sector-publico/contsem#WorksContract
IRI: http://contsem.unizar.es/def/sector-publico/contsem#additionalDocumentReference
IRI: http://contsem.unizar.es/def/sector-publico/contsem#alternateMember
Points to an alternate member of a committee.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#awardAgreement
Points to the body agreement where a tender has been awarded.
IRI: http://purl.org/procurement/public-contracts#awardCriteriaCombination
IRI: http://purl.org/procurement/public-contracts#awardCriterion
IRI: http://contsem.unizar.es/def/sector-publico/contsem#briefing
IRI: http://contsem.unizar.es/def/sector-publico/contsem#committee
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractCompensation
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#complementaryContract
Relates a contract with a complementary contract.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractAbandonment
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractAdditionalObligations
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractBodies
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#budgetPrice
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractEconomicConditions
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractExecutionConditions
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractModification
Points to contract modifications being made.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractModificationConditions
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#item
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractOrProcedureExtinction
Abstract property pointing to extinction of contract or procedure. Use any of its subclasses.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractProcedureSpecifications
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractProcedures
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractResolution
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractTemporalConditions
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractWaive
IRI: http://purl.org/procurement/public-contracts#contractingAuthority
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractingBody
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#contractingBodyAgreement
IRI: http://contsem.unizar.es/def/sector-publico/contsem#criterion
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#criterionScore
Property that points to an unique criterion and its score.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#delegatingAuthority
Points to the authority that is delegating the contract.
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#documentReference
Links to external documents.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#electronicAuction
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#electronicAuctionPhase
IRI: http://contsem.unizar.es/def/sector-publico/contsem#electronicAuctionWeb
Property that indicated where the electronic auction is made or where we can look for more information about the auction.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#estimatedPrice
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#feePrice
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#frameworkAgreement
Property that indicates the framework agreement in which the contract consists.
This property is used when the actual contract consist in the declaration of a framework agreement or a dynamic purchasing system.
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#frameworkAgreementDerivativeContract
has characteristics: inverse functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#fullMember
Points to a full member of a committee.
IRI: http://www.w3.org/2004/02/skos/core#inScheme
IRI: http://contsem.unizar.es/def/sector-publico/contsem#informationKind
Property pointing to the type of the information is provided.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#legalDocumentReference
IRI: http://schema.org/location
IRI: http://contsem.unizar.es/def/sector-publico/contsem#lot
IRI: http://purl.org/procurement/public-contracts#lot
IRI: http://contsem.unizar.es/def/sector-publico/contsem#mainObject
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#managingDepartment
Property that indicates the managing departament responsible of the contract.
has characteristics: functional
IRI: http://xmlns.com/foaf/0.1/member
IRI: http://contsem.unizar.es/def/sector-publico/contsem#minutesDocumentReference
IRI: http://contsem.unizar.es/def/sector-publico/contsem#notice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#noticeWeb
IRI: http://contsem.unizar.es/def/sector-publico/contsem#object
Property that points to the concept of the CPV code of an object.
The concept used should be a valid representation of a CPV code, as it is in http://cpv.data.ac.uk/.
IRI: http://purl.org/procurement/public-contracts#offeredPrice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#location
IRI: http://contsem.unizar.es/def/sector-publico/contsem#price
IRI: http://purl.org/goodrelations/v1#hasPriceSpecification
IRI: http://contsem.unizar.es/def/sector-publico/contsem#procedureType
has characteristics: functional
IRI: http://purl.org/procurement/public-contracts#actualPrice
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedy
IRI: http://contsem.unizar.es/def/sector-publico/contsem#resolutionDocumentReference
IRI: http://purl.org/procurement/public-contracts#tender
IRI: http://purl.org/procurement/public-contracts#supplier
IRI: http://contsem.unizar.es/def/sector-publico/contsem#technicalDocumentReference
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderAdmissionMeeting
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderBriefing
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderInformationProvider
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderMeeting
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderRequirements
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderSubmissionLocation
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderersRequirements
has characteristics: functional
IRI: http://www.w3.org/2004/02/skos/core#topConceptOf
IRI: http://contsem.unizar.es/def/sector-publico/contsem#urgencyType
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#voidProcedure
IRI: http://contsem.unizar.es/def/sector-publico/contsem#websiteWithInformation
IRI: http://contsem.unizar.es/def/sector-publico/contsem#actualDuration
has characteristics: functional
IRI: http://schema.org/address
IRI: http://schema.org/addressCountry
IRI: http://schema.org/addressLocality
IRI: http://contsem.unizar.es/def/sector-publico/contsem#advertisementAmount
IRI: http://contsem.unizar.es/def/sector-publico/contsem#assumptionProtectingProcedureType
IRI: http://contsem.unizar.es/def/sector-publico/contsem#constructionSubsidies
Description of the public subsidies to construction works contracts.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#criterionEvaluationMode
Property textually describing the criterion evaluarion mode.
IRI: http://purl.org/procurement/public-contracts#criteronName
IRI: http://purl.org/procurement/public-contracts#criterionWeight
IRI: http://contsem.unizar.es/def/sector-publico/contsem#criterionMaxAndMinScores
IRI: http://purl.org/dc/terms/date
IRI: http://contsem.unizar.es/def/sector-publico/contsem#awardDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#noticeDate
IRI: http://purl.org/dc/terms/description
IRI: http://contsem.unizar.es/def/sector-publico/contsem#disposableMeansAppointment
IRI: http://contsem.unizar.es/def/sector-publico/contsem#duration
IRI: http://contsem.unizar.es/def/sector-publico/contsem#durationChange
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#earlyTramitation
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#estimatedDuration
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#estimatedEndDate
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#executionRequeriments
Property to define alternative execution requirements (e.g. legal form to be adopted by tenderers).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#expectedCauseModification
IRI: http://contsem.unizar.es/def/sector-publico/contsem#extinctionCause
IRI: http://contsem.unizar.es/def/sector-publico/contsem#finalFinancialGuarantee
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#finalFinancialGuaranteeDuration
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#formalizedDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#isNegotiable
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#lodgedRemedyDate
Date where a remedy is lodged.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#lotCount
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#maxBudgetChange
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#maxFinalPriceChange
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#maxInvitations
IRI: http://contsem.unizar.es/def/sector-publico/contsem#maxNumberOfOperators
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#maxSubcontracting
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#minInvitations
IRI: http://contsem.unizar.es/def/sector-publico/contsem#minNumberOfOperators
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#minSubcontracting
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#modificationReason
IRI: http://contsem.unizar.es/def/sector-publico/contsem#modificationScope
IRI: http://schema.org/name
IRI: http://contsem.unizar.es/def/sector-publico/contsem#noticeSentDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#noticeSite
Property that indicates the sire where the notice is published. Normally it would be an official source, like the Official Jounral of the European Union, but it can be anywhere else, like press.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#offeredDuration
IRI: http://contsem.unizar.es/def/sector-publico/contsem#offeredEndDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#otherAwardTerms
IRI: http://contsem.unizar.es/def/sector-publico/contsem#otherGuarantee
IRI: http://schema.org/postalAddress
IRI: http://contsem.unizar.es/def/sector-publico/contsem#pricePercentageChange
The range of this property must be a percentage (i.e. float between 0.0 and 100.0)
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#isPriceReviewed
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#priceRevisionFormulaDescription
IRI: http://contsem.unizar.es/def/sector-publico/contsem#prorogationsExpected
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#provisionalFinancialGuarantee
has characteristics: functional
IRI: http://purl.org/procurement/public-contracts#actualEndDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#recurrentRemedy
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedyInterposedTo
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedyReason
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedyResolution
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedyResolutionDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#remedyResult
Contains the result of a lodged remedy. Normally it would contains values like "Estimated", "Rejected" or "Partially estimated".
IRI: http://contsem.unizar.es/def/sector-publico/contsem#requiredCapability
IRI: http://contsem.unizar.es/def/sector-publico/contsem#requiredClassification
IRI: http://contsem.unizar.es/def/sector-publico/contsem#requiredFinancialCapability
IRI: http://contsem.unizar.es/def/sector-publico/contsem#requiredTechnicalCapability
IRI: http://contsem.unizar.es/def/sector-publico/contsem#reservedContractRestrictions
IRI: http://contsem.unizar.es/def/sector-publico/contsem#score
Indica la puntuación que ha recibido un criterio.
has characteristics: functional
IRI: http://schema.org/startDate
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderDossierStartDate
has characteristics: functional
IRI: http://schema.org/streetAddress
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderCommitteeAppointmentDate
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderCommitteePosition
Indicated the role of a person inside the committee.
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderDocumentNeeds
Defines the necessary documentation a tender must include.
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderManteinanceDuration
Define el plazo necesario que una oferta presentada debe permanecer vigente.
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderPurpose
Indicates the purpose of the meeting (e.g. opening of first envelope).
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderSubmissionMode
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderSubmissionSupportedLanguage
IRI: http://contsem.unizar.es/def/sector-publico/contsem#tenderDeadline
has characteristics: functional
IRI: http://purl.org/dc/terms/title
IRI: http://contsem.unizar.es/def/sector-publico/contsem#variantAdmission
has characteristics: functional
IRI: http://contsem.unizar.es/def/sector-publico/contsem#variantDescription
Property to describe the allowed variantes when submitting a variant of a contract.
The develop of the CONTSEM ontology has been funded by the spanish Ministry of Industry, Commerce and Tourism through the project “Optimización de la contratación pública mediante la utilización de técnicas semánticas (CONTSEM)”. TSI-020606-2012-4.
We want to thank to public procurement experts of the public authorities participating in the CONTSEM project: Ana Budría Escudero, Azucena Ayala Andrés (Zaragoza Town Hall), Eva Sanz Ayala, Juan Ramón Cardiel Ibarzo (Government of Aragón) y Montserrat Diez Sánchez (Provincial Council of Huesca); as well as its technical responsibles: María Jesús Fernández Ruiz (Zaragoza Town Hall), José Maria Subero Munilla, Ricardo Cantabrana González (Government of Aragón) y Cristina de la Hera Pascual (Provincial Council of Huesca).
We also greatly appreciate the effort of Oscar Corcho and Carlos Bobed; their comments and contributions have helped to improve the final ontology.
The authors would like to thanks Silvio Peroni for developing LODE, a Live OWL Documentation Environment used for representing the Cross Referencing Section of this document and Daniel Garijo for developing the script used to create the template of this document.
Class describing the tenders accepted in the procurement public contract.


In this grapgh we are examining the effects latitude has on humidity
takend from over 2000 different city locations around the world.
Based on the table that is presented the humidity does not seem to be dependent upon the latitude
In order to understand how humidity is effected in different parts of the world you need to take into account many more observations than just the latitude.
Humidity is effected by tempurature and a number of other factors. An easy hypothisis is the closer to the equator you get the warmer the weather should be and thus more humidity.
Humidity is caused by how much moisture the air is able to hold in it. The movement of air from a high pressure system to a low pressure system.
In order to have humidity you need different pressure systems amongst many other things. It is amazing how all the different factors play together to help dictate the weather. Wind, Temperature, terrain, moisture availability all play into the creation of the weather patterns. Which goes well beyond just latitude.


For the sake of this exercise, lets focus only on the API code and any new releases you have. These changes will be tested by VSTS and, pushed into Azure Container Registry (ACR) once all your tests have passed (we won't go into writing tests today). Then VSTS will automatically deploy the latest version of the app into your cluster by obtaining the latest image from ACR.
The following two resources will provide you all the answers on how to accomplish this task, it´s your duty to understand them and consolidate the concepts to set up a full development cycle. Please note that none of these are a step-by-step tutorial to achieve what you want, but jointly you will be able to make it work:
You should be able to do the following steps to provide CI/CD in a Kubernetes cluster using Azure.


ABOUT
The Tentative Collective is a gathering of artists, curators, teachers, architects and often, collaborators from completely different backgrounds including fishermen, housewives and domestic workers. We came together in 2011 and are based in Karachi, Pakistan.
While we work site specifically in response to the city, we are interested in engaging with its peculiar co-opting of global modernity in the rapidly transforming landscapes of the global south; in particular, the precarious urban geographies of the city and the voids it opens for groups like ours to inhabit. Navigating through these precarious urban geographies, we hope to create poetic and ephemeral moments in conversation with the city’s infrastructures, while making connections to its complex ecological and geological histories.
Our work has been presented at the Akademie der Kunste, Munich Kammerspiele,Technical University of Munich, Sarai Centre for the Study of Developing Societies, Asia Research Institute, National University of Singapore, International Institute for Asian Studies & Hong Kong Baptist University, and as part of the Ancestors: Architecture of Memory program hosted by the Lahore Biennale Foundation.


A Public Service
- He pushed the button, which was red.
There was a button.
The button was red.
He pushed it.
Use a comma.- He pushed the button that was red.
-
There were buttons.
One of those buttons was red.
He pushed the red one.
No comma.
The comma separates the initial phrase from another extra bit of information about the thing. In the first case, “which” stands in for “the button”. It’s like saying, “He pushed the button. The button was red.”
In the second case, there is no comma, because “that” is used as a limiter, not a reference. It’s like saying, “He pushed the button. That button, the one that’s red.”
When you say “that one”, you point. You are limiting the referent.
To make things more confusing, “which” can actually be used as a limiter, and sometimes limiters can be used to add information. But when in doubt, follow these rules.


Invictus Obi loses N280 million as court orders final forfeiture
by Ifeanyi NgeremJustice Rilwan Aikawa of the Federal High Court sitting in Lagos has ordered the final forfeiture to the Federal Government of the sum of N280,555,010 linked to Obinwanne Okeke, popularly known as Invictus Obi.
Recall Invictus Obi was arrested by the FBI in August for an alleged $11 million fraud. Invictus is standing trial in the United States of American for an alleged cyber fraud following his indictment alongside 77 Nigerians.
Justice Aikawa ordered the interim forfeiture of the funds and asked the commission to publish in any national newspaper, the interim order for the named parties or anyone who is interested in the monies sought to be forfeited to appear before the court to show cause within 14 days why the final order of forfeiture should not be made in favour of the Federal Government.
The commission said it traced the said amount to Mr Okeke in bank accounts of Invictus Oil and Gas Limited and Invictus Investment Limited.


Provides classes for producing tables in different output formats and for reading such tables. The idea behind these tools is that output is produced and read row-based, so the whole table does not need to fit into heap memory.


THE FIRM [Possible Spoilers] A film review by James Berardinelli Copyright 1993 James Berardinelli
Rating: 5.9 out of 10 (C, ** out of ****)
Date Released: 6/30/93 Running Length: 2:34 Rated: R (Language, mature themes, sexual situations, violence)
Starring: Tom Cruise, Gene Hackman, Jeanne Tripplehorn, Hal Holbrook, Ed Harris, Holly Hunter, Wilford Brimley Director: Sydney Pollack Producers: Scott Rudin, John Davis, and Syndey Pollack Screenplay: David Rabe, Robert Towne, and David Rayfiel based on the book by John Grisham Music: Dave Grusin Released by Paramount Pictures
Mitchell Y. McDeere (Tom Cruise) has just graduated in the top five of his class from Harvard Law School. With a record like his, there are understandably a lot of people interested in employing him. Offers abound from the large, the prestigious, and the desirable, but eventually it's a small firm from Memphis that snares Mitch's services. Bendini, Lambert, and Locke make the terms of his joining them so enticing that the deal is impossible to turn down--a starting salary near $100,000, a low-interest mortgage so he can buy a house, free use of a Mercedes, and repayment of his college loans. At first, Mitch and his wife Abby (Jeanne Tripplehorn) eagerly celebrate their new life and home, but it doesn't take long for the euphoria to wear thin. Two members of the Firm die under suspicious circumstances and soon Mitch begins to wonder what secrets lie behind the locked doors of Bendini, Lambert, and Locke.
John Grisham's novel THE FIRM is a furious page-turner, the kind of book that you don't want to put down once you've started reading it. The characters are well-rounded and developed in such a way that the reader cares about their fates. The fascinating setup (roughly the first 100 pages) is perhaps the novel's greatest strength and, even though the eventual resolution lacks punch, few would deny that THE FIRM is an entertaining read.
Sydney Pollack's film THE FIRM is the kind of movie that almost anyone could walk out on without feeling that they've missed much, regardless of whether they've read the book or not. Very little of what made the written version so enjoyable has made it to the screen and what we're left with instead is an overly-long (two hours and thirty-four minutes, to be exact), pedantic thriller that, at best, can be described as average.
The producer/director has been quoted as saying that he wants his movie to stand on its own, apart from the book. That's a good idea, because the film THE FIRM doesn't come close to reaching the level of intensity achieved by the novel of the same name. Comparisons are inevitable, of course, but it isn't necessary to have read the written version to be disappointed by the visual adaptation.
The plot is a good place to start the discussion. This was the book's weakest element and, if anything, it's worse in the movie. While the final "twist" to the movie's story (which in no way resembles what happens in the novel) is clever, it is also difficult to accept. Let's not forget the forces that Mitch is up against. Is it reasonable to believe everything that happens in the pivotal climactic scenes? I doubt it. While I applaud the screenwriters for coming up with a unique way to conclude the film, their inept execution of the concept causes the ending to seem cheap and contrived.
The unfortunate tone of the movie is set during the first hour. The film spends quite a bit of time using short, often-disjointed scenes in an attempt to recapture the near-perfect mood of Grisham's setup. This would have worked nicely if those various snippets had successfully conveyed the allure of the Firm to Mitch and Abby, but things rush by so quickly and everything is so out-of-sync that the result is to make the first quarter of the movie long and tedious.
There are many differences between motion picture and novel. With numerous expected, mostly-minor cuts and changes, the first half of the film stays reasonably close to its written counterpart. After that, however, the differences become progressively larger until only the names of the characters and certain general events remain the same. Not all of the changes are bad--some, at least in their intent, are intriguing. Unfortunately, the script writers appear not to have thought things through all the way--a fault that Grisham's novel is rarely guilty of.
On the surface, Tom Cruise and Jeanne Tripplehorn might seem like acceptable choices to play the roles of Mitch and Abby McDeere. That is, until they start to "act". Cruise has at times been good in front of the camera (in pictures such as BORN ON THE FOURTH OF JULY), while in other instances he has done little more than show off his good looks (DAYS OF THUNDER). In the case of THE FIRM, which demands range and ability, the star falls solidly in the second category. Not until the last act does he give anything resembling a feeling performance, managing to effectively sabotage Mitch in the process.
Jeanne Tripplehorn is worse, playing Abby with as much enthusiasm and energy as a zombie. Even as I was apathetic towards Mitch because of Cruise, I began to actively dislike Abby as a result of Tripplehorn's unimaginative performance. Consider for a moment someone of Emma Thompson's caliber in this part and you'll want to break into tears of frustration.
Fortunately for the film, the supporting cast is uniformly strong. Especially worthy of mention are Ed Harris as FBI agent Tarrance and Wilford Brimley as De Vasher, the Firm's security strong man. Both of these actors steal many of the scenes that they're in.
As impressive as these two, if not more so, is Gene Hackman's Avery Tolar. Softened in the movie from his counterpart in the book, this Avery becomes the only completely real--and sympathetic--character in the film. Hackman's performance is more than half the reason why. In the hands of a lesser actor, Avery could have become sappy, silly, or stupid, but not in this case. By the closing scenes of THE FIRM, he was the only one I really cared about.
I dislike bashing movies simply because they differ from the books that spawned them. The mediums of entertainment are different, after all, and should be treated as such. No film can do a perfect adaptation of a novel. In the case of THE FIRM, however, the problems have little to do with the changes made to the story. Putting aside the issue of its source, this is not a good movie. If there's a reason to go, and I don't think there is, it's to see Gene Hackman's performance. Unfortunately, given his amount of screen time, there's a lot of other garbage that will have to be endured along the way.
In the past, I've enjoyed many of Syndey Pollack's projects (OUT OF AFRICA and TOOTSIE in particular), but this film got derailed early and even this talented director proved unable to get it back on course. I suppose it's a difficult task to try to please both admirers of the novel and the casual movie-goer who has never read it. In attempting that, Pollack has made a mess of everything--plot, characterization, and pacing. Even the music, by Dave Grusin, is inappropriate.
Fans of John Grisham's novel will see THE FIRM regardless of what reviews it gets, so to them, and to others, I offer a cautionary warning to be wary. THE FIRM had a lot of potential but the production team found numerous ways to mess it up. This isn't an awful film, nor is it unwatchable, but I'd think twice before spending time and money in a darkened theater with telling of Mitch McDeere's struggles.
- James Berardinelli<EMAIL_ADDRESS>.
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


Motives:
Domestic Dispute
Drug Use
Drug Use and Financial Difficulties
Expulsion or Suspension
Failure
Financial Difficulties or Dispute
Gender
Harassment
Legal Dispute
Mental Illness
Multiple Motives
Political or Religious Ideals
Race
Rejection
Robbery
Social Dispute
Terminated, Denied, or Reprimanded
Unknown


Please enter name and password
Name:
Password:
How to login?


RAILWAY
Reservation Cancellation Requisition Form
If you are a Medical Practiciner Please tick () in the box. []Dr.
(You would be of help in the emergency)
If you are a Sr.Citizen ,please write yes/no on the box (If yes please carry a proof of age during the journey to avoid inconvenience of panel charging under extent Railway Rules)
Do you want to be upgraded without any extra charge? Write
Yes/No in the box. (If this option is not exercised,full fare paying passengers may be upgraded automatically)


Where do people share your articles ?
5/Feb 2014
Alright, you have written dozen of articles on your blog now, and you successfully have tagged them as the official author. In addition to that, you got offered some guest blogging offers through your connexions and via MyBlogGuest. So essentially you start running a** successful blogger life**, but you feel a unsatisfied with the standard analytics tools. You don’t really WHO is reading your articles and how you can increase the number of readers.
That is the reason why we introduced a new feature on WordiZ some days ago. As you may know it was already possible to find who is sharing your articles on Google+. That’s a really interesting feature, but we thought that we are somehow missing the big picture. In other words, where are you mostly cited ?
On which network are you visible ?
When you write an article, you will probably share it on Tiwtter, Google+ and/or Facebook and LinkedIn. But, once this step is done,** you don’t really control what’s happening next**. Overtime you might discover that you reach more fans on Twitter or on Facebook.
It is now possible to see that in a bird’s eye view on you WordiZ profile. Have a look at the following picture (taken from my profile) :
What you see is really simple to explain. The more “mentions” my articles get on a social network, the more “visible” I am on this** social network**. Therefore, you can quickly see here that I am equally visible on G+ (39%) and Twitter (42%), but far less on Facebook (19%).
What is the best strategy to get visible ?
Honestly, I cannot pretend that there is a best strategy. Some people tend to be very famous more or less equally on various social networks. That’s not very often, but you have a nice example with Torben Rick :
Indeed most of the famous writers I have met on WordiZ have a** favorite social network**. Well, to be precise, let say that their fans are mostly active on a social network. That is the case for instance of Mark Traphagen or Flavien Chantrel.
How do you improve then ?
In order to improve your social visibility, you have two strategies. The first one is to fight on all fronts at the same time. However this is really time demanding and you might feel discouraged after some time since your efforts will initially lead to few results.
The second strategy is to concentrate on a dedicated social network, possibly the one you know better, and the one where you have more friends and contacts. Try to become visible on this special social network, and the others will follow by themselves.
I cannot show you the result yet, but, take the case of Mark for instance. He started on Google+, and slowly his visibility on Twitter followed. Mark really put a lot of efforts to sustain a constant activity on Google+ and to create long term friendships on the network.
So, here is my take : concentrate on one social network, and then, when you have some traction there, start focusing on a new social network.


Megono Developer
We working as a Freelancer (Web Developer, Web App, and Android App).
YOU CAN FIND ON


| Class | Description |
|---|---|
| BIGINT |
Signed eight-byte integer
|
| BIGSERIAL |
Autoincrementing eight-byte integer
|
| BIT |
Fixed-length bit string
|
| BIT_VARYING |
Variable-length bit string.
|
| BOOLEAN |
Logical Boolean (true/false)
|
| BOX |
Rectangular box on a plane
|
| BYTEA |
Binary data ("byte array")
|
| CHAR |
Fixed-length character string.
|
| CHARACTER |
Character string.
|
| CHARACTER_VARYING |
Variable-length character string.
|
| CIDR |
IPv4 or IPv6 network address
|
| CIRCLE |
Circle on a plane
|
| DATE |
Calendar date (year, month, day)
|
| FLOAT8 |
Double precision floating-point number (8 bytes)
|
| INET |
IPv4 or IPv6 host address
|
| INT |
Signed four-byte integer
|
| JSON |
Textual JSON data
|
| JSONB |
Binary JSON data, decomposed
|
| LINE |
Infinite line on a plane
|
| LSEG |
Line segment on a plane
|
| MACADDR |
MAC (Media Access Control) address
|
| MONEY |
Currency amount
|
| PATH |
Geometric path on a plane
|
| PG_LSN |
PostgreSQL Log Sequence Number
|
| POINT |
Geometric point on a plane
|
| POLYGON |
Closed geometric path on a plane
|
| REAL |
Single precision floating-point number (4 bytes)
|
| SERIAL |
Autoincrementing four-byte integer
|
| SMALLINT |
Signed two-byte integer
|
| SMALLSERIAL |
Autoincrementing two-byte integer
|
| TEXT |
Variable-length character string
|
| TIME |
Time of day (no time zone)
|
| TIMESTAMP |
Date and time (no time zone)
|
| TIMESTAMPTZ |
Date and time, including time zone
|
| TIMETZ |
Time of day, including time zone
|
| TSQUERY |
Text search query
|
| TSVECTOR |
Text search document
|
| TXID_SNAPSHOT |
User-level transaction ID snapshot
|
| UUID |
Universally unique identifier
|
| VARBIT |
Variable-length bit string.
|
| VARCHAR |
Variable-length character string.
|
| XML |
XML data
|


option
option
option
TheBite! Meals in your dining room
Make your order. We serve it where you want it.
Order
View


Open the 'demo.js' file Find in there assignment of 'transpose' variable Assign it by the boolean vaules from 'false' or 'true'


8 characters
Contains Number
Contains Uppercase`
Contains Special Characters
or Generate one
Password Generator
Password length
Include uppercase letters
Include lowercase letters
Include numbers
Include symbols
Generate password


If you do not have a account, you can not edit newsentry. I am deeply sorry that we now can not support Chinese, please do not use Chinese to as username


Changes:
Added rules for SQLite for LEFT and RIGHT functions.
SQLite now dropping schema name when creating and dropping index (as this throws an error if left).
No longer automatically casting literal to TEXT in RedShift CTE. Users are required to do explicit casts instead.
BigQuery insertTable now also uses CTAS hack.
Added translation rules for HASHBYTES.
Bugfixes:
Fixing GETDATE translation for SQLite.
When calling ‘render’, the replacement value can now contain a $ sign. (Previously this caused an error).
isNumeric can now also be applied to numeric fields in Postgres.
Better handling of illegal characters in Impala.
Changes:
- Added rules for Oracle for conditonal indices.
Bugfixes:
- Fixing erroneous variable name translation for BigQuery.
Changes:
- Added rules for Impala for INTEGER NOT NULL and DOUBLE PRECISION.
Bugfixes:
- Fixed isNumeric check for Netezza
Changes:
Major overhaul of BigQuery translation.
Added support for SQLite.
ISNUMERIC translation implemented for Impala, Netezza, and BigQuery.
Performance improvement for Impala temp tables (CREATE TABLE … STORED AS PARQUET).
Adding functions render
and translate
that output strings instead of lists. Deprecating renderSql
and translateSql
.
Added function translateSingleStatement
.
Bugfixes:
Dropping WHERE clause when translating CREATE INDEX for PDW.
Fixed PDW’s equivalent of CREATE TABLE IF NOT EXISTS.
Changes:
- Added translation rules for DATETIME2.
Bugfixes:
- Fixed misspelling of DISTRIBUTE in Netezza translation rules.
Changes:
- Translation for indexes for RedShift and Impala.
- Translation for UPDATE STATISTICS.
Bugfixes:
- Fixed translation of AS when used for table names in Oracle.
Changes:
- Improved support for Netezza.
- Added random distribution hints for PDW, RedShift, Netezza.
- Improved MPP index translation for PDW and Netezza.
- Warnings about missing parameters when rendering SQL can now be turned off.
Bugfixes:
- Translation of camelCase to snake_case now adds underscore before numbers.
Changes:
- Better handling of ‘FROM DUAL’ for Oracle.
- Improved support for Netezza and Impala.
Changes:
- Bigquery support for mismatched string and int arguments in coalesce.
- Translate decimal to float for BigQuery.
- Created rules to add dummy ‘group by’ for Oracle statements combining ‘case’ and ‘count’ to prevent Oracle from crashing.
- Adding ‘UNBOUNDED PRECEDING’ to RedShift windowing functions.
Changes:
- Added a Shiny app for developing parameterized SQL, and view how this would be rendered and translated into the various supported dialects.
- Added support for Google BigQuery.
- Added many more rules for Amazon RedShift, including support for optimization hints.
- Added rules for DELETE FROM translation for Impala.
Bugfixes:
- Fixed issue when splitting SQL containing hints.
Changes:
- Added translation rules for ISNUMERIC and LOG(@expression, @base)
Bugfixes:
- Fixed bug when trying to split SQL where reserved word ‘end’ is used as a field name.
- Fixes for Impala translations.
- Fixed translation issues for Oracle involving ‘FROM DUAL’.
- Added workaround for Oracle bug for intervals greater than 99 days.
- Fixed bug when trying to split SQL where last line has comment but no EOL.
Changes:
- Added ability to use regular expression in translation patterns. This allowed SELECT TOP n to be translated.
- Deprecated sourceDialect argument.
- Added translation for CONCAT function with >2 arguments to Oracle (which only allows 2 arguments)
- Added hints for translation optimation to massive parallel platforms like RedShift
- Throw warnings when translateSql is called with variable names that are not in the SQL
- Throw warnings when table names are too long for Oracle
Bugfixes:
- Fixed translation for date functions so they will now work properly with datetime fields as well.
- Now throwing error when boolean logic cannot be parsed (instead of assuming result is TRUE)
Changes:
- Added support for Impala
Bugfixes:
- Fixed translation for DATEFROMPARTS for RedShift
Changes: initial submission to CRAN


This is the Clipjump settings editor.
You can choose your Clipjump preferences here.
To get help on any setting, keep the mouse static for a while after moving the mouse pointer over it . A Tooltip with description text should pop-up.
After changing settings, hit Apply and then OK.
Tips
- To disable a shortcut , set it to
None
. You can do this by focusing cursor in the Shortcut box and then tapping Backspace once.
- It is recommended to let
Quality of preview thumbnail
be 90 .
- Keep
Threshold = 1
to have the Maximum number of active clipboards equal to the
Minimum number of Active clipboards.
- Keep a reasonable value (say 30 days) for
Days to Store
in the Clipboard history setting panel to have better performance in the History tool.


|
Turtlebot_RRT_SLAM
|
definition of a point in RRT More...
#include <rrt_global_planner_plugin.h>
Public Member Functions | |
| void | setPosition (float x, float y) |
| < set the coordinate of the vertex More... | |
| void | setParentIdx (int idx) |
| set the index of the vertex More... | |
| void | setIdx (int i) |
| get the coordinate of the vertex More... | |
| std::pair< float, float > | getPosition () |
| get the parent index of the vertex More... | |
| int | getParentIdx () |
| get the index of the vertex More... | |
| int | getIdx () |
| class rrt_planner methods More... | |
definition of a point in RRT
| int vertex::getIdx | ( | ) |
class rrt_planner methods
| int vertex::getParentIdx | ( | ) |
get the index of the vertex
| std::pair< float, float > vertex::getPosition | ( | ) |
get the parent index of the vertex
| void vertex::setIdx | ( | int | i | ) |
get the coordinate of the vertex
| void vertex::setParentIdx | ( | int | idx | ) |
set the index of the vertex
| void vertex::setPosition | ( | float | x, |
| float | y | ||
| ) |
< set the coordinate of the vertex
< register this planner as a BaseGlobalPlanner plugin
set the parent index of the vertex
< vertex function implementation


| PostgreSQL 9.0.10 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Appendix E. Release Notes | Next |
Release date: 1996-02-23
The following notes are for the benefit of users who want to migrate databases from Postgres95 1.0 to Postgres95 1.01.
If you are starting afresh with Postgres95 1.01 and do not need to migrate old databases, you do not need to read any further.
In order to Postgres95 version 1.01 with databases created with Postgres95 version 1.0, the following steps are required:
Set the definition of NAMEDATALEN in src/Makefile.global to 16 and OIDNAMELEN to 20.
Decide whether you want to use Host based authentication.
If you do, you must create a file name pg_hba in your top-level data directory (typically the value of your $PGDATA). src/libpq/pg_hba shows an example syntax.
If you do not want host-based authentication, you can comment out the line:
HBA = 1
in src/Makefile.global
Note that host-based authentication is turned on by default, and if you do not take steps A or B above, the out-of-the-box 1.01 will not allow you to connect to 1.0 databases.
Compile and install 1.01, but DO NOT do the initdb step.
Before doing anything else, terminate your 1.0 postmaster, and backup your existing $PGDATA directory.
Set your PGDATA environment variable to your 1.0 databases, but set up path up so that 1.01 binaries are being used.
Modify the file $PGDATA/PG_VERSION from 5.0 to 5.1
Start up a new 1.01 postmaster
Add the new built-in functions and operators of 1.01 to 1.0 databases. This is done by running the new 1.01 server against your own 1.0 database and applying the queries attached and saving in the file 1.0_to_1.01.sql. This can be done easily through psql. If your 1.0 database is name testdb:
% psql testdb -f 1.0_to_1.01.sql
and then execute the following commands (cut and paste from here):
-- add builtin functions that are new to 1.01 create function int4eqoid (int4, oid) returns bool as 'foo' language 'internal'; create function oideqint4 (oid, int4) returns bool as 'foo' language 'internal'; create function char2icregexeq (char2, text) returns bool as 'foo' language 'internal'; create function char2icregexne (char2, text) returns bool as 'foo' language 'internal'; create function char4icregexeq (char4, text) returns bool as 'foo' language 'internal'; create function char4icregexne (char4, text) returns bool as 'foo' language 'internal'; create function char8icregexeq (char8, text) returns bool as 'foo' language 'internal'; create function char8icregexne (char8, text) returns bool as 'foo' language 'internal'; create function char16icregexeq (char16, text) returns bool as 'foo' language 'internal'; create function char16icregexne (char16, text) returns bool as 'foo' language 'internal'; create function texticregexeq (text, text) returns bool as 'foo' language 'internal'; create function texticregexne (text, text) returns bool as 'foo' language 'internal'; -- add builtin functions that are new to 1.01 create operator = (leftarg = int4, rightarg = oid, procedure = int4eqoid); create operator = (leftarg = oid, rightarg = int4, procedure = oideqint4); create operator ~* (leftarg = char2, rightarg = text, procedure = char2icregexeq); create operator !~* (leftarg = char2, rightarg = text, procedure = char2icregexne); create operator ~* (leftarg = char4, rightarg = text, procedure = char4icregexeq); create operator !~* (leftarg = char4, rightarg = text, procedure = char4icregexne); create operator ~* (leftarg = char8, rightarg = text, procedure = char8icregexeq); create operator !~* (leftarg = char8, rightarg = text, procedure = char8icregexne); create operator ~* (leftarg = char16, rightarg = text, procedure = char16icregexeq); create operator !~* (leftarg = char16, rightarg = text, procedure = char16icregexne); create operator ~* (leftarg = text, rightarg = text, procedure = texticregexeq); create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne);
Incompatibilities: * 1.01 is backwards compatible with 1.0 database provided the user follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file. If those steps are not taken, 1.01 is not compatible with 1.0 database. Enhancements: * added PQdisplayTuples() to libpq and changed monitor and psql to use it * added NeXT port (requires SysVIPC implementation) * added CAST .. AS ... syntax * added ASC and DESC key words * added 'internal' as a possible language for CREATE FUNCTION internal functions are C functions which have been statically linked into the postgres backend. * a new type "name" has been added for system identifiers (table names, attribute names, etc.) This replaces the old char16 type. The of name is set by the NAMEDATALEN #define in src/Makefile.global * a readable reference manual that describes the query language. * added host-based access control. A configuration file ($PGDATA/pg_hba) is used to hold the configuration data. If host-based access control is not desired, comment out HBA=1 in src/Makefile.global. * changed regex handling to be uniform use of Henry Spencer's regex code regardless of platform. The regex code is included in the distribution * added functions and operators for case-insensitive regular expressions. The operators are ~* and !~*. * pg_dump uses COPY instead of SELECT loop for better performance Bug fixes: * fixed an optimizer bug that was causing core dumps when functions calls were used in comparisons in the WHERE clause * changed all uses of getuid to geteuid so that effective uids are used * psql now returns non-zero status on errors when using -c * applied public patches 1-14


Snowboarding is a sport that has gained international sensation and continues to gain momentum in the eyes of the young.
These days you can list many snowboarders that continue developing the sport and continue the evolution and enjoyment of it, however, there are some important people who are the original pioneers of the sport:
Below is a table showing the amount of snowboarders that specific year
| 2000 | 2007 | 2015 |
|---|---|---|
| 4,300,000 | 6,100,000 | 5,675,000 |
As you can see during the 2007 season peaked due to storms occuring that brought in enough snow to extend the snow season past normal end season dates, however there has been steady increase in snowboarders.


"The Adventures of Rocky and Bullwinkle" -- The Original Show Had More Charm, Dahlink by Homer Yen (c) 2000
Somewhere in the back of my mind, in a rarely visited location where cartoon characters that I have grown to love but am now too old to remember, there resides a flying squirrel and a likably dimwitted moose. Known as Rocky and Bullwinkle, their show was a crudely drawn but lively post-Cold War adventure that pitted these two against the evil machinations of three scoundrels named Boris Badinov, Natasha, and their fearless leader named Fearless Leader. There was a charming quirkiness to their episodes, which were brutally inane and featured sharp puns and rapid-fire humor. It possessed a shallowness that was just right for Saturday morning mindless fare.
It's now three decades later. Rocky hasn't flown in years. Bullwinkle laments about the disappearing woodlands throughout his home of Frostbite Falls. And our three villains are trapped in an endless cycle of reruns. But in the world of cartoons, anything is possible. Fearless Leader literally reaches out to a hungry movie executive to ink a movie deal. Suddenly, the three of them emerge as flesh-and-blood people (Jason Alexander as Boris, Renee Russo as Natasha, and Robert DeNiro as Fearless Leader). Free of their two-dimensional cartoon world and from Rocky and Bullwinkle, they now see an opportunity to hatch their latest plan to rule the world.
Fearless Leader and his band begin to build a television cable empire called RBTV (Really Bad Television). It will be filled with programs that are so bad that the viewing audience will be turned into zombies susceptible to hypnotic suggestion. The public will be told go out and vote in Fearless Leader as the new President in the next election. This is a plan worthy of Pinky and the Brain (you know, one is a genius and the other's insane).
Out to stop them is FBI agent Karen Sympathy (Piper Perabo) who is a soft, squishy, lovey-dovey, idealistic kind of gal. She enlists the help of Rocky (voiced, as in the original, by June Foray) and Bullwinkle (voiced by Keith Scott), and together, they try to save the world. Their travels are filled with absurd occurrences and pun-filled banter. At one point when the three are being approached by a group of security guards, Sympathy yells, "we've got to get out of here," to which Bullwinkle says, "OK, let's go to a commercial!" We see signs that point out places such as the Crimea River, and we pay a visit to Bullwinkle's alma mater, Wossamotta U. All of this silliness is fine up to a certain point, which is about the first 20 minutes. However, the novelty soon wears thin.
Give credit, though, to the live cast members and all of the cameos who deliver over-the-top acting to lend to its cartoonish personality. Especially good is DeNiro who seemed to be having endless fun as Fearless Leader. He speaks with an almost-impenetrable accent and even takes a turn at parodying the "you looking at me" line made famous from his role in "Taxi Driver."
Alas, "Rocky and Bullwinkle" just doesn't give even the inner child in us enough to sustain an 85-minute film. The story just doesn't go anywhere and we start to wonder if we're watching one of Fearless Leader's RBTV programs. There's a scene in this film that pretty much sums up the film's viewing experience. At Wossamotta U., students are protesting during a speech given by Bullwinkle. However, his speech is so inane that students find that they had nothing to object to. It's equally loony yet insipid, hollow yet harmless.
Grade: C S: 0 out of 3 L: 0 out of 3 V: 1 out of 3
Do You Yahoo!? Get Yahoo! Mail – Free email you can access from anywhere! http://mail.yahoo.com/
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


Bootbox
Bootbox.js is a small JavaScript library which allows you to create programmatic dialog boxes using Twitter’s Bootstrap modals, without having to worry about creating, managing or removing any of the required DOM elements or JS event handlers. For more info please check out the official documentation .


You changed succesfully your password.
Somthing went wrong. Your attend to reset your password has failed.
Try again to change your passwordA mail with a rest token and some instructions was sent to {{reset.email}}.
Check your inbox.
Skhomotech © 2016


Melbournica Thy
I'm an awesome 9th grader,freshman, who's was born in Cambodia. Phnom Penh
is the city that I was born and raised in for 14 years of my life. By the way I
was born in August,10,2001 in the year of the snake. As you look at my webpage,
you will know more about me.


| Opcode/Instruction |
Op/En |
64/32-bit Mode |
CPUID Feature Flag |
Description |
| VEX.256.66.0F3A.W0 39 /r ib VEXTRACTI128 xmm1/m128, ymm2, imm8 |
RMI |
V/V |
AVX2 |
Extract 128 bits of integer data from ymm2 and store results in xmm1/mem. |
Instruction Operand Encoding
| Op/En |
Operand 1 |
Operand 2 |
Operand 3 |
Operand 4 |
| RMI |
ModRM:r/m (w) |
ModRM:reg (r) |
Imm8 |
NA |
Description
Extracts 128-bits of packed integer values from the source operand (second operand) at a 128-bit offset from imm8[0] into the destination operand (first operand). The destination may be either an XMM register or a 128-bit memory location. VEX.vvvv is reserved and must be 1111b otherwise instructions will #UD. The high 7 bits of the immediate are ignored. An attempt to execute VEXTRACTI128 encoded with VEX.L= 0 will cause an #UD exception.
Operation
VEXTRACTI128 (memory destination form)
CASE (imm8[0]) OF
0: DEST[127:0] ← SRC1[127:0]
1: DEST[127:0] ← SRC1[255:128]
ESAC.
VEXTRACTI128 (register destination form)
CASE (imm8[0]) OF
0: DEST[127:0] ← SRC1[127:0]
1: DEST[127:0] ← SRC1[255:128]
ESAC.
DEST[VLMAX-1:128] ← 0
Intel C/C++ Compiler Intrinsic Equivalent
| VEXTRACTI128: |
__m128i _mm256_extracti128_si256(__m256i a, int offset); |
SIMD Floating-Point Exceptions
None
Other Exceptions
See Exceptions Type 6; additionally
| #UD |
IF VEX.L = 0, If VEX.W = 1. |


--- layout: post title: Trouble signing in - Accounts Help categories: [] tags: - googletv - logitech - revue status: publish type: post published: true meta: _original_post_id: '' _original_import_author: John Duprey author: ---
While most of Google TV will work after you use an application-specific password, the Google TV Gallery app is not compatible with 2-step verification. If you want to use the Gallery app, you will need to turn off 2-step verification. See some examples of application-specific passwords.
OK, the Logitech Revue really needs an update.. The gallery app does not support application-specific passwords - yet another annoying problem with the current version of Google TV. When *is* that update coming to the Revue?