Table of Contents
Target Namespace
http://www.cnio.es/scombio/xcesc/1.0
Element and Attribute Namespaces
Global element and attribute declarations belong to this schema's target namespace.
By default, local element declarations belong to this schema's target namespace.
By default, local attribute declarations have no namespace.
Schema Composition
This schema imports schema(s) from the following namespace(s):
Documentation
XCESC XML Schema, made by José María Fernández González (C) 2008-2011
Declared Namespaces
Prefix
Namespace
mgmt
http://www.cnio.es/scombio/xcesc/1.0/xquery/systemManagement
xml
http://www.w3.org/XML/1998/namespace
job
http://www.cnio.es/scombio/xcesc/1.0/xquery/jobManagement
gui
http://www.cnio.es/scombio/xcesc/1.0/xquery/guiManagement
meta
http://www.cnio.es/scombio/xcesc/1.0/xquery/metaManagement
mailcore
http://www.cnio.es/scombio/xcesc/1.0/xquery/mailCore
xsd
http://www.w3.org/2001/XMLSchema
xcesc
http://www.cnio.es/scombio/xcesc/1.0
Schema Component Representation
<
xsd:schema
targetNamespace ="
http://www.cnio.es/scombio/xcesc/1.0 "
elementFormDefault ="
qualified ">
<xsd:import
namespace ="http://www.cnio.es/scombio/xcesc/1.0/xquery/systemManagement " schemaLocation ="systemManagement.xsd "/>
<xsd:import
namespace ="http://www.cnio.es/scombio/xcesc/1.0/xquery/jobManagement " schemaLocation ="jobManagement.xsd "/>
<xsd:import
namespace ="http://www.cnio.es/scombio/xcesc/1.0/xquery/guiManagement " schemaLocation ="guiManagement.xsd "/>
<xsd:import
namespace ="http://www.cnio.es/scombio/xcesc/1.0/xquery/metaManagement " schemaLocation ="metaManagement.xsd "/>
<xsd:import
namespace ="http://www.cnio.es/scombio/xcesc/1.0/xquery/mailCore " schemaLocation ="mailCore.xsd "/>
...
</
xsd:schema >
Name
acceptedQueries
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The set of accepted queries
XML Instance Representation
<
xcesc :acceptedQueries
timeStamp="
xsd :dateTime
[0..1]
'The timestamp assigned to the element either in origin or destination'
" >
<
xcesc :accepted
queryId="
xsd :string
[1]
'The id of the query (typically, a number)'
" />
[1]
'An accepted query'
</
xcesc :acceptedQueries>
Schema Component Representation
<
xsd:element
name ="
acceptedQueries ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
accepted ">
<
xsd:complexType >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
Name
answer
Used by (from the same schema document)
Element
answers
, Element
query
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
An answer about a target
XML Instance Representation
<
xcesc :answer
targetId="
xsd :string
[1]
'The id of the answer'
"
message="
xsd :string
[0..1]
'An optional message, about the answer'
" >
Start Choice
[0..1]
<
xcesc :refContent
ref="
xsd :string
[1]
'This attribute contains the reference'
" >
[1]
'This element is used to reference a common bundle of information'
</
xcesc :refContent>
End Choice
Start Choice
[1]
End Choice
</
xcesc :answer>
Schema Component Representation
<
xsd:element
name ="
answer ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:choice
minOccurs ="
0 ">
<
xsd:element
ref ="
xcesc :target
"
minOccurs ="
1 "
maxOccurs ="
1 "/>
<
xsd:element
name ="
refContent "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:attribute
name ="
ref "
type ="
xsd :string
"
use ="
required "/>
</
xsd:complexType >
<
xsd:keyref
name ="
contentKeyRef "
refer ="
xcesc :contentKey
">
<xsd:selector
xpath =". "/>
<xsd:field
xpath ="@ref "/>
</
xsd:keyref >
</
xsd:element >
</
xsd:choice >
<
xsd:choice >
<
xsd:element
ref ="
xcesc :match
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:choice >
</
xsd:sequence >
<
xsd:attribute
name ="
targetId "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
message "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:complexType >
</
xsd:element >
Name
answers
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The answers bundle sent by the servers. A server can send more than one bundle.
Schema Component Representation
<
xsd:element
name ="
answers ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
ref ="
xcesc :common
"
minOccurs ="
0 "
maxOccurs ="
1 "/>
<
xsd:element
ref ="
xcesc :answer
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
Name
assessment
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
An assessment is the evaluation of the accuracy, recall, etc... for all the experiment participants
XML Instance Representation
<
xcesc :assessment
name="
xsd :string
[1]
'The name (usually the experiment or assessment job ticket), so we can link to it'
"
stamp="
xsd :dateTime
[1]
'The experiment or assessment\'s timestamp (when it started)'
"
baseStamp="
xsd :date
[1]
'The previous experiment or assessment\'s timestamp (used to track changes)'
"
deadline="
xsd :dateTime
[1]
'The experiment or assessment\'s deadline (after this one no result is accepted)'
"
test="
xsd :boolean
[0..1]
'Is it a test experiment/assessment?'
" >
<
xcesc :evaluator
ticket="
xsd :string
[1]
'The unique evaluator ticket'
"
startStamp="
xsd :dateTime
[1]
'The timestamp of the evaluation submission'
"
lastStamp="
xsd :dateTime
[1]
'The timestamp of the last received in time evaluation result'
"
lastMessage="
xsd :string
[0..1]
'Last human-readable message fetched from server on submission, i.e., an error'
" >
[0..*]
<
xcesc :
server > ... </
xcesc :
server >
[1]
'Server information is preserved here, so changes do not affect the calling values'
Start Choice
[1]
<
xcesc :job
participantTicket="
xsd :string
[1]
'The ticket of the participant being assessed in this job'
"
stopStamp="
xsd :dateTime
[0..1]
'The timestamp when a job from this XCESC instance has finished (either properly or with failure)'
"
status="
xsd :string (value comes from list: {'queued'|'submitted'|'running'|'transienterror'|'error'|'finished'})
[1]
'The status of the job at lastQueryStamp'
"
lastMessage="
xsd :string
[0..1]
'Last human-readable message fetched from server or generated by this XCESC instance, usually an error'
" >
[0..*]
'A job is a evaluation target sent to the server'
</
xcesc :job>
<
xcesc :errorMessage
statusCode="
xsd :positiveInteger
[1]
'The HTTP status error code'
" >
[1]
'Last human-readable message fetched from server on submission, i.e., an error'
<!-- Mixed content -->
Allow any elements from any namespace (lax validation). [0..*]
</
xcesc :errorMessage>
End Choice
</
xcesc :evaluator>
</
xcesc :assessment>
Schema Component Representation
<
xsd:element
name ="
assessment ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
evaluator "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :server
"
minOccurs ="
1 "
maxOccurs ="
1 "/>
<
xsd:choice >
<
xsd:element
name ="
job "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence >
</
xsd:sequence >
<
xsd:attribute
name ="
participantTicket "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
stopStamp "
type ="
xsd :dateTime
"
use ="
optional "/>
<
xsd:attribute
name ="
status "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="queued "/>
<xsd:enumeration
value ="submitted "/>
<xsd:enumeration
value ="running "/>
<xsd:enumeration
value ="transienterror "/>
<xsd:enumeration
value ="error "/>
<xsd:enumeration
value ="finished "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
<
xsd:attribute
name ="
lastMessage "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
errorMessage ">
<
xsd:complexType
mixed ="
true ">
<
xsd:sequence >
<xsd:any
minOccurs ="0 " maxOccurs ="unbounded " namespace ="##any " processContents ="lax "/>
</
xsd:sequence >
<
xsd:attribute
name ="
statusCode "
type ="
xsd :positiveInteger
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:choice >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
<
xsd:key
name ="
assessment_target_key ">
<xsd:selector
xpath ="xcesc:target "/>
<xsd:field
xpath ="@id "/>
</
xsd:key >
<
xsd:keyref
name ="
job_targetid_referes_assessment_target "
refer ="
xcesc :assessment_target_key
">
<xsd:selector
xpath ="xcesc:participant/xcesc:job "/>
<xsd:field
xpath ="@targetId "/>
</
xsd:keyref >
<
xsd:unique
name ="
assessor_server_unique ">
<xsd:selector
xpath ="xcesc:assessor/xcesc:server "/>
<xsd:field
xpath ="@id "/>
</
xsd:unique >
</
xsd:element >
Name
common
Used by (from the same schema document)
Element
answers
, Element
queries
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
An area where common content is shared in bundles
XML Instance Representation
<
xcesc :common>
<
xcesc :content
id="
xsd :string
[1]
'The unique id of this bundle within this XML document'
" >
[1]
'A bundle of shared content'
Start Choice
[1]
End Choice
</
xcesc :content>
</
xcesc :common>
Schema Component Representation
<
xsd:element
name ="
common ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
name ="
content ">
<
xsd:complexType >
<
xsd:choice >
</
xsd:choice >
<
xsd:attribute
name ="
id "
type ="
xsd :string
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
Name
configuration
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The configuration of a XCESC system, probably stored at /db/XCESC-config/configuration.xml
Schema Component Representation
<
xsd:element
name ="
configuration ">
<
xsd:complexType >
<
xsd:sequence >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
XML Instance Representation
<
xcesc :experiment
name="
xsd :string
[1]
'The name (usually the experiment or assessment job ticket), so we can link to it'
"
stamp="
xsd :dateTime
[1]
'The experiment or assessment\'s timestamp (when it started)'
"
baseStamp="
xsd :date
[1]
'The previous experiment or assessment\'s timestamp (used to track changes)'
"
deadline="
xsd :dateTime
[1]
'The experiment or assessment\'s deadline (after this one no result is accepted)'
"
test="
xsd :boolean
[0..1]
'Is it a test experiment/assessment?'
"
isAssessed="
xsd :boolean
[1]
'Has the experiment being officially assessed at least once?'
" >
<!--
Key Constraint -
target_key
Selector -
xcesc:target
Field(s) -
@id
-->
<!--
Key Reference Constraint -
job_targetid_referes_target
Selector -
xcesc:participant/xcesc:job
Field(s) -
@targetId
Refers to -
xcesc :
target_key
-->
<
xcesc :participant
ticket="
xsd :string
[1]
'The unique evaluator ticket'
"
startStamp="
xsd :dateTime
[1]
'The timestamp of the evaluation submission'
"
lastStamp="
xsd :dateTime
[1]
'The timestamp of the last received in time evaluation result'
"
lastMessage="
xsd :string
[0..1]
'Last human-readable message fetched from server on submission, i.e., an error'
" >
[0..*]
<
xcesc :
server > ... </
xcesc :
server >
[1]
'Server information is preserved here, so changes do not affect the calling values'
Start Choice
[1]
<
xcesc :job
targetId="
xsd :positiveInteger
[1]
'The Id of the target sent in this job'
"
stopStamp="
xsd :dateTime
[0..1]
'The timestamp when a job from this XCESC instance has finished (either properly or with failure)'
"
status="
xsd :string (value comes from list: {'queued'|'submitted'|'running'|'transienterror'|'error'|'finished'})
[1]
'The status of the job at lastQueryStamp'
"
lastMessage="
xsd :string
[0..1]
'Last human-readable message fetched from server or generated by this XCESC instance, usually an error'
" >
[0..*]
'A job is a target sent to the server'
<
xcesc :
match > ... </
xcesc :
match >
[0..*]
'A result from the job. It can contain from 0 to an undetermined number of matches.'
</
xcesc :job>
<
xcesc :errorMessage
statusCode="
xsd :positiveInteger
[1]
'The HTTP status error code'
" >
[1]
'Last human-readable message fetched from server on submission, i.e., an error'
<!-- Mixed content -->
Allow any elements from any namespace (lax validation). [0..*]
</
xcesc :errorMessage>
End Choice
</
xcesc :participant>
</
xcesc :experiment>
Schema Component Representation
<
xsd:element
name ="
experiment ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :target
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
<
xsd:element
name ="
participant "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :server
"
minOccurs ="
1 "
maxOccurs ="
1 "/>
<
xsd:choice >
<
xsd:element
name ="
job "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
ref ="
xcesc :match
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
<
xsd:attribute
name ="
targetId "
type ="
xsd :positiveInteger
"
use ="
required "/>
<
xsd:attribute
name ="
stopStamp "
type ="
xsd :dateTime
"
use ="
optional "/>
<
xsd:attribute
name ="
status "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="queued "/>
<xsd:enumeration
value ="submitted "/>
<xsd:enumeration
value ="running "/>
<xsd:enumeration
value ="transienterror "/>
<xsd:enumeration
value ="error "/>
<xsd:enumeration
value ="finished "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
<
xsd:attribute
name ="
lastMessage "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
errorMessage ">
<
xsd:complexType
mixed ="
true ">
<
xsd:sequence >
<xsd:any
minOccurs ="0 " maxOccurs ="unbounded " namespace ="##any " processContents ="lax "/>
</
xsd:sequence >
<
xsd:attribute
name ="
statusCode "
type ="
xsd :positiveInteger
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:choice >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
<
xsd:attribute
name ="
isAssessed "
type ="
xsd :boolean
"
use ="
required "/>
</
xsd:complexType >
<
xsd:key
name ="
target_key ">
<xsd:selector
xpath ="xcesc:target "/>
<xsd:field
xpath ="@id "/>
</
xsd:key >
<
xsd:keyref
name ="
job_targetid_referes_target "
refer ="
xcesc :target_key
">
<xsd:selector
xpath ="xcesc:participant/xcesc:job "/>
<xsd:field
xpath ="@targetId "/>
</
xsd:keyref >
<
xsd:unique
name ="
participant_server_unique ">
<xsd:selector
xpath ="xcesc:participant/xcesc:server "/>
<xsd:field
xpath ="@id "/>
</
xsd:unique >
</
xsd:element >
Schema Component Representation
<
xsd:element
name ="
experiments ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :experiment
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
<
xsd:key
name ="
experiments_stamp ">
<xsd:selector
xpath ="xcesc:experiment "/>
<xsd:field
xpath ="@stamp "/>
</
xsd:key >
<
xsd:keyref
name ="
experiments_baseStamp_stamp "
refer ="
xcesc :experiments_stamp
">
<xsd:selector
xpath ="xcesc:experiment "/>
<xsd:field
xpath ="@baseStamp "/>
</
xsd:keyref >
</
xsd:element >
Name
jobEvaluation
Used by (from the same schema document)
Element
jobEvaluation
, Element
answer
, Element
assessment
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The evaluation of each one of the jobs done by the partipant being assessed
XML Instance Representation
<
xcesc :jobEvaluation
targetId="
xsd :positiveInteger
[1]
'The id of a job\'s answer from the participants point of view. i.e. The value of the targetId attribute from the query element inside the arriving target element being assessed.'
"
timeStamp="
xsd :dateTime
[0..1]
'The timestamp assigned to the element either in origin or destination'
" >
<
xcesc :evaluation>
[0..*]
'Each piece to be assessed from this job'
<
xcesc :report> ... </
xcesc :report>
[0..1]
'This It should contain any native output report the server wants to provide'
<
xcesc :placeQuality
precision="
xsd :double (0.0 <= value <= 1.0)
[1]
'Precision is the fraction of retrieved instances that are relevant. See http://en.wikipedia.org/wiki/Precision_and_recall'
"
recall="
xsd :double (0.0 <= value <= 1.0)
[1]
'Recall is the fraction of relevant instances that are retrieved. See http://en.wikipedia.org/wiki/Precision_and_recall'
" >
[0..1]
'Assessment about the place of the annotation (the piece to be assessed)'
xcesc :placeQualityEnum
</
xcesc :placeQuality>
<
xcesc :annotationQuality
precision="
xsd :double (0.0 <= value <= 1.0)
[1]
'Precision is the fraction of retrieved instances that are relevant. See http://en.wikipedia.org/wiki/Precision_and_recall'
"
recall="
xsd :double (0.0 <= value <= 1.0)
[1]
'Recall is the fraction of relevant instances that are retrieved. See http://en.wikipedia.org/wiki/Precision_and_recall'
" >
[0..1]
'Assessment about the quality of the annotation (the piece to be assessed)'
xcesc :annotationQualityEnum
</
xcesc :annotationQuality>
<
xcesc :evaluated>
[1]
Start Choice
[1]
'We can even assess other evaluators'
End Choice
</
xcesc :evaluated>
</
xcesc :evaluation>
</
xcesc :jobEvaluation>
Schema Component Representation
<
xsd:element
name ="
jobEvaluation ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
evaluation "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<xsd:element
name ="report " minOccurs ="0 " maxOccurs ="1 "/>
<
xsd:element
name ="
placeQuality "
minOccurs ="
0 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:simpleContent >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
annotationQuality "
minOccurs ="
0 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:simpleContent >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
evaluated "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:choice >
<
xsd:element
ref ="
xcesc :match
"
minOccurs ="
0 "
maxOccurs ="
1 "/>
</
xsd:choice >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
<
xsd:attribute
name ="
targetId "
type ="
xsd :positiveInteger
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
Name
lastRound
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
Last round document, needed to know where PDB and PDBPre filtered database files are lying
XML Instance Representation
<
xcesc :lastRound
timeStamp="
xsd :dateTime
[1]
'The timestamp assigned to the element either in origin or destination'
" />
Schema Component Representation
<
xsd:element
name ="
lastRound ">
<
xsd:complexType >
</
xsd:complexType >
</
xsd:element >
XML Instance Representation
<
xcesc :managementData>
<!--
Key Reference Constraint -
servers_managerId_keyref_users
Selector -
xcesc:servers/xcesc:server
Field(s) -
@id
Refers to -
xcesc :
users_key
-->
<
xcesc :users>
[1]
'XCESC users are the servers managers'
<!--
Key Constraint -
users_key
Selector -
xcesc:user
Field(s) -
@id
-->
<
xcesc :user
nickname="
xsd :string
[1]
'The unique nickname of the user in the system'
"
nickpass="
xsd :string
[0..1]
'The pasword associated to the user in the system. This attribute is only used in XForms'
"
id="
xsd :string
[1]
'The unique id of the user in the system'
"
status="
xsd :string (value comes from list: {'disabled'|'enabled'|'unconfirmed'|'deleted'})
[1]
'The user/e-mail status: enabled, disabled or unconfirmed. When an user is disabled, all the servers owned by him/her are disabled. When an e-mail is disabled, it is not used to send the user notifications'
"
firstName="
xsd :string
[1]
'The first name(s) of the user (e.g. José María)'
"
lastName="
xsd :string
[1]
'The last name(s) of the user (e.g. Fernández González)'
"
organization="
xsd :string
[1]
'The organization where the user is integrated'
" >
[0..*]
'A XCESC user, with all the contact information'
<
xcesc :eMail
id="
xsd :string
[1]
'The unique id of the user in the system'
"
status="
xsd :string (value comes from list: {'disabled'|'enabled'|'unconfirmed'|'deleted'})
[1]
'The user/e-mail status: enabled, disabled or unconfirmed. When an user is disabled, all the servers owned by him/her are disabled. When an e-mail is disabled, it is not used to send the user notifications'
" >
[1..*]
'The e-mail address(es). They must be valid ones'
xsd :string
</
xcesc :eMail>
<
xcesc :roles>
[1]
'The set of roles associated to the user'
<
xcesc :role
ref="
xsd :string
[1]
'The name of the obtained (or denied) role'
"
isDenied="
xsd :boolean
[0..1]
'Has been this role denied to the user?'
" />
[0..*]
</
xcesc :roles>
</
xcesc :user>
</
xcesc :users>
</
xcesc :managementData>
Schema Component Representation
<
xsd:element
name ="
managementData ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
users "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
user "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
eMail "
minOccurs ="
1 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:simpleContent >
<
xsd:extension
base ="
xsd :string
">
</
xsd:extension >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
roles "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
role "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:attribute
name ="
ref "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
isDenied "
type ="
xsd :boolean
"
use ="
optional "
default ="
false "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
<
xsd:attribute
name ="
nickname "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
nickpass "
type ="
xsd :string
"
use ="
optional "/>
<
xsd:attribute
name ="
firstName "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
lastName "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
organization "
type ="
xsd :string
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
<
xsd:key
name ="
users_key ">
<xsd:selector
xpath ="xcesc:user "/>
<xsd:field
xpath ="@id "/>
</
xsd:key >
<
xsd:unique
name ="
users_nickname_unique ">
<xsd:selector
xpath ="xcesc:user "/>
<xsd:field
xpath ="@nickname "/>
</
xsd:unique >
<
xsd:unique
name ="
users_eMail_unique ">
<xsd:selector
xpath ="xcesc:user "/>
<xsd:field
xpath ="xcesc:eMail "/>
</
xsd:unique >
</
xsd:element >
<
xsd:element
name ="
servers "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :server
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
<
xsd:key
name ="
servers_key ">
<xsd:selector
xpath ="xcesc:server "/>
<xsd:field
xpath ="@id "/>
</
xsd:key >
<
xsd:unique
name ="
servers_name_unique ">
<xsd:selector
xpath ="xcesc:server "/>
<xsd:field
xpath ="@name "/>
</
xsd:unique >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
<
xsd:keyref
name ="
servers_managerId_keyref_users "
refer ="
xcesc :users_key
">
<xsd:selector
xpath ="xcesc:servers/xcesc:server "/>
<xsd:field
xpath ="@id "/>
</
xsd:keyref >
</
xsd:element >
XML Instance Representation
<
xcesc :match
source="
xsd :string
[1]
'The match source is the kind of prediction/assessment done. For instance, if a server is hybrid, in the sense it is able to generate predictions/assessments for homology modelling and ab initio, then the origin of the match must be identified'
"
timeStamp="
xsd :dateTime
[0..1]
'The timestamp assigned to the element either in origin or destination'
" >
<
xcesc :
scope > ... </
xcesc :
scope >
[0..*]
'The match scope, in its corresponding units. As the scope can be sparse, more than one scope element can be specified'
Start Choice
[1]
<
xcesc :result>
[1..*]
'An structured result'
<!-- Mixed content -->
<
xcesc :metrics>
[1]
'This element is needed by XML Schema 1.0 in order to allow something more'
</
xcesc :metrics>
Allow any elements from any namespace (lax validation). [0..*]
</
xcesc :result>
End Choice
</
xcesc :match>
Schema Component Representation
<
xsd:element
name ="
match ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
ref ="
xcesc :scope
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
<
xsd:choice >
<
xsd:element
ref ="
xcesc :term
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
<
xsd:element
name ="
result "
minOccurs ="
1 "
maxOccurs ="
unbounded ">
<
xsd:complexType
mixed ="
true ">
<
xsd:sequence >
<
xsd:element
name ="
metrics "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :metric
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
<xsd:any
processContents ="lax " namespace ="##any " minOccurs ="0 " maxOccurs ="unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:choice >
</
xsd:sequence >
<
xsd:attribute
name ="
source "
type ="
xsd :string
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
Name
metric
Used by (from the same schema document)
Element
term
, Element
scope
, Element
match
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
A metric about a piece of information (precision, recall, e-value, z-score, etc...)
XML Instance Representation
<
xcesc :metric
type="
xsd :string (value comes from list: {'score'|'e-value'|'p-value'|'z-score'|'precision'|'recall'|'accuracy'})
[1]
'The type of metric used'
" >
xsd :string
</
xcesc :metric>
Schema Component Representation
<
xsd:element
name ="
metric ">
<
xsd:complexType >
<
xsd:simpleContent >
<
xsd:extension
base ="
xsd :string
">
<
xsd:attribute
name ="
type "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="score "/>
<xsd:enumeration
value ="e-value "/>
<xsd:enumeration
value ="p-value "/>
<xsd:enumeration
value ="z-score "/>
<xsd:enumeration
value ="precision "/>
<xsd:enumeration
value ="recall "/>
<xsd:enumeration
value ="accuracy "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
</
xsd:extension >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
Name
queries
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
One or more queries sent to a server
XML Instance Representation
<
xcesc :queries
callback="
xsd :anyURI
[1]
'The callback address to send the answers to the queries from the server'
" >
<!--
Key Constraint -
contentKey
Selector -
xcesc:content
Field(s) -
@id
-->
</
xcesc :queries>
Schema Component Representation
<
xsd:element
name ="
queries ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
ref ="
xcesc :common
"
minOccurs ="
0 "
maxOccurs ="
1 "/>
<
xsd:element
ref ="
xcesc :query
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
<
xsd:key
name ="
contentKey ">
<xsd:selector
xpath ="xcesc:content "/>
<xsd:field
xpath ="@id "/>
</
xsd:key >
</
xsd:element >
Name
query
Used by (from the same schema document)
Element
common
, Element
queries
, Element
target
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The query which is submitted to the servers. It can be either a query to a prediction server, or an assessment request to an evaluation server
XML Instance Representation
<
xcesc :query
queryId="
xsd :string
[1]
'The id of the query (typically, a number)'
" >
<!-- Mixed content -->
Start Choice
[1]
Allow any elements from a namespace other than this schema's namespace (lax validation). [0..*]
End Choice
</
xcesc :query>
Schema Component Representation
<
xsd:element
name ="
query ">
<
xsd:complexType
mixed ="
true ">
<
xsd:choice >
<xsd:any
minOccurs ="0 " maxOccurs ="unbounded " namespace ="##other " processContents ="lax "/>
<
xsd:element
ref ="
xcesc :answer
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
</
xsd:choice >
</
xsd:complexType >
</
xsd:element >
Name
references
Used by (from the same schema document)
Element
server
, Element
managementData
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
This element contains the external references to the server, at documentation level
XML Instance Representation
<
xcesc :references>
<
xcesc :reference
description="
xsd :string
[1]
'A brief description about the pointed contents'
"
kind="
xsd :string (value comes from list: {'site'|'link'|'logo'|'image'})
[1]
'The supposed type of the content'
" >
[1]
'A reference to external information associated to the server'
xsd :anyURI
</
xcesc :reference>
</
xcesc :references>
Schema Component Representation
<
xsd:element
name ="
references ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
reference ">
<
xsd:complexType >
<
xsd:simpleContent >
<
xsd:extension
base ="
xsd :anyURI
">
<
xsd:attribute
name ="
description "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
kind "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="site "/>
<xsd:enumeration
value ="link "/>
<xsd:enumeration
value ="logo "/>
<xsd:enumeration
value ="image "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
</
xsd:extension >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
Name
scope
Used by (from the same schema document)
Element
match
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
The match scope, in its corresponding units.
As the scope can be sparse, more than one scope element can be specified
XML Instance Representation
<
xcesc :scope
label="
xsd :string
[0..1]
'This attribute is useful for structured queries'
"
from="
xsd :string
[1]
'Where the scope begins, relative to the query. It depends on the units system and it is always an inclusive limit.'
"
to="
xsd :string
[0..1]
'Where the scope ends, relative to the query. It depends on the units system and it is always an inclusive limit.'
"
units="
xsd :string
[0..1]
'The units system, sometimes related to from and to attributes from scope elements, based on the query'
" >
<
xcesc :
term > ... </
xcesc :
term >
[0..*]
'This scope can have associated specific annotations'
</
xcesc :scope>
Schema Component Representation
<
xsd:element
name ="
scope ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :metric
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
<
xsd:element
ref ="
xcesc :term
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
<
xsd:attribute
name ="
label "
type ="
xsd :string
"
use ="
optional "/>
<
xsd:attribute
name ="
from "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
to "
type ="
xsd :string
"
use ="
optional "/>
<
xsd:attribute
name ="
units "
type ="
xsd :string
"
use ="
optional "
default ="
residues "/>
</
xsd:complexType >
</
xsd:element >
XML Instance Representation
<
xcesc :server
id="
xsd :string
[1]
'The XCESC ID for a server'
"
name="
xsd :string
[1]
'The XCESC name for a server'
"
managerId="
xsd :string
[1]
'The ID of the manager of this server'
"
uri="
xsd :anyURI
[1]
'The invocation URI'
"
type="
xsd :string (value comes from list: {'participant'|'evaluator'})
[1]
'The server type'
" >
<
xcesc :description>
xsd :string </
xcesc :description>
[1]
'A description about the server, maybe in HTML'
<
xcesc :kind>
xsd :string </
xcesc :kind>
[1..*]
'Each one of the server kinds this server belongs to'
<
xcesc :otherParams>
[1]
'Other parameters set by the owner of the service, which tweaks the run'
<
xcesc :param
name="
xsd :string
[1]
'The name of the parameter'
" >
[0..*]
'A parameter which tweaks the run. The content of the element is the value'
xsd :string
</
xcesc :param>
</
xcesc :otherParams>
<
xcesc :downTime
id="
xsd :string
[1]
'The XCESC ID for a downTime'
"
since="
xsd :dateTime
[1]
'When this downTime starts (inclusive)'
"
until="
xsd :dateTime
[0..1]
'When this downTime should finish (exclusive). If it is not set, the downTime is *forever*'
"
managerId="
xsd :string
[1]
'The manager Id who last changed this downtime'
"
managerName="
xsd :string
[0..1]
'The manager name who last changed this downtime'
" >
[0..*]
'An scheduled downTime. It can contain a reason about the downTime as its content.'
xsd :string
</
xcesc :downTime>
</
xcesc :server>
Schema Component Representation
<
xsd:element
name ="
server ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
description "
type ="
xsd :string
"/>
<
xsd:element
name ="
kind "
type ="
xsd :string
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
<
xsd:element
name ="
otherParams "
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
param "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:simpleContent >
<
xsd:extension
base ="
xsd :string
">
<
xsd:attribute
name ="
name "
type ="
xsd :string
"
use ="
required "/>
</
xsd:extension >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
downTime "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:simpleContent >
<
xsd:extension
base ="
xsd :string
">
<
xsd:attribute
name ="
id "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
since "
type ="
xsd :dateTime
"
use ="
required "/>
<
xsd:attribute
name ="
until "
type ="
xsd :dateTime
"
use ="
optional "/>
<
xsd:attribute
name ="
managerId "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
managerName "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:extension >
</
xsd:simpleContent >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
<
xsd:attribute
name ="
id "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
name "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
managerId "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
uri "
type ="
xsd :anyURI
"
use ="
required "/>
<
xsd:attribute
name ="
type "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="participant "/>
<xsd:enumeration
value ="evaluator "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
</
xsd:complexType >
</
xsd:element >
XML Instance Representation
<
xcesc :target
namespace="
xsd :string
[1]
'The namespace of the annotation. For instance, GO'
"
kind="
xsd :string
[0..1]
'This optional attribute is useful when under an specific namespace there can be more than one kind of public identifiers, so we can distinguish among the different available subtypes, categories or ontologies'
"
id="
xsd :string
[1]
'The id of the annotation'
"
description="
xsd :string
[1]
'A descriptive line for the query (for instance, from PDB or PDBPre)'
" >
<
xcesc :relatedContent
label="
xsd :string
[0..1] " >
[0..*]
'Related content to the query, given by the XCESC core'
Start Choice
[1..*]
<
xcesc :
term > ... </
xcesc :
term >
[1]
'Links to related data or members identified by the XCESC core'
<
xcesc :inlineContent
source="
xsd :string
[1]
'The source of this related content. It should be like a namespace'
"
description="
xsd :string
[0..1]
'An optional textual description'
" />
[1]
'Inline related content'
End Choice
</
xcesc :relatedContent>
<
xcesc :baseline
timeStamp="
xsd :dateTime
[1]
'The timestamp assigned to the element either in origin or destination'
" >
[1..*]
'A fast, baseline answer for the query'
</
xcesc :baseline>
</
xcesc :target>
Schema Component Representation
<
xsd:element
name ="
target ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
name ="
relatedContent "
minOccurs ="
0 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:choice
minOccurs ="
1 "
maxOccurs ="
unbounded ">
<
xsd:element
name ="
inlineContent ">
<
xsd:complexType >
<
xsd:attribute
name ="
source "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
description "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:complexType >
</
xsd:element >
</
xsd:choice >
<
xsd:attribute
name ="
label "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:complexType >
</
xsd:element >
<
xsd:element
name ="
baseline "
minOccurs ="
1 "
maxOccurs ="
unbounded ">
<
xsd:complexType >
<
xsd:sequence >
<
xsd:element
ref ="
xcesc :match
"
minOccurs ="
0 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
</
xsd:sequence >
<
xsd:attribute
name ="
description "
type ="
xsd :string
"
use ="
required "/>
</
xsd:complexType >
</
xsd:element >
Element: term
Name
term
Used by (from the same schema document)
Element
scope
, Element
match
, Element
target
Type
Locally-defined complex type
Nillable
no
Abstract
no
Documentation
An annotated element with a score
XML Instance Representation
<
xcesc :term
namespace="
xsd :string
[1]
'The namespace of the annotation. For instance, GO'
"
kind="
xsd :string
[0..1]
'This optional attribute is useful when under an specific namespace there can be more than one kind of public identifiers, so we can distinguish among the different available subtypes, categories or ontologies'
"
id="
xsd :string
[1]
'The id of the annotation'
" >
</
xcesc :term>
Schema Component Representation
<
xsd:element
name ="
term ">
<
xsd:complexType >
<
xsd:sequence
minOccurs ="
1 "
maxOccurs ="
1 ">
<
xsd:element
ref ="
xcesc :metric
"
minOccurs ="
1 "
maxOccurs ="
unbounded "/>
</
xsd:sequence >
</
xsd:complexType >
</
xsd:element >
Name
callbackAttributeGroup
Used by (from the same schema document)
Element
queries
Documentation
Shared callback attribute
Schema Component Representation
<
xsd:attributeGroup
name ="
callbackAttributeGroup ">
<
xsd:attribute
name ="
callback "
type ="
xsd :anyURI
"
use ="
required "/>
</
xsd:attributeGroup >
XML Instance Representation
id="
xsd :string
[1]
'The unique id of the user in the system'
"
status="
xsd :string (value comes from list: {'disabled'|'enabled'|'unconfirmed'|'deleted'})
[1]
'The user/e-mail status: enabled, disabled or unconfirmed. When an user is disabled, all the servers owned by him/her are disabled. When an e-mail is disabled, it is not used to send the user notifications'
"
Schema Component Representation
<
xsd:attributeGroup
name ="
idStatusAttributeGroup ">
<
xsd:attribute
name ="
id "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
status "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="disabled "/>
<xsd:enumeration
value ="enabled "/>
<xsd:enumeration
value ="unconfirmed "/>
<xsd:enumeration
value ="deleted "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
</
xsd:attributeGroup >
Name
namespaceAttributesGroup
Used by (from the same schema document)
Element
term
, Element
target
XML Instance Representation
namespace="
xsd :string
[1]
'The namespace of the annotation. For instance, GO'
"
kind="
xsd :string
[0..1]
'This optional attribute is useful when under an specific namespace there can be more than one kind of public identifiers, so we can distinguish among the different available subtypes, categories or ontologies'
"
id="
xsd :string
[1]
'The id of the annotation'
"
Schema Component Representation
<
xsd:attributeGroup
name ="
namespaceAttributesGroup ">
<
xsd:attribute
name ="
namespace "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
kind "
type ="
xsd :string
"
use ="
optional "/>
<
xsd:attribute
name ="
id "
type ="
xsd :string
"
use ="
required "/>
</
xsd:attributeGroup >
Schema Component Representation
<
xsd:attributeGroup
name ="
optionalTimeStampGroup ">
<
xsd:attribute
name ="
timeStamp "
type ="
xsd :dateTime
"
use ="
optional "/>
</
xsd:attributeGroup >
XML Instance Representation
precision="
xsd :double (0.0 <= value <= 1.0)
[1]
'Precision is the fraction of retrieved instances that are relevant. See http://en.wikipedia.org/wiki/Precision_and_recall'
"
recall="
xsd :double (0.0 <= value <= 1.0)
[1]
'Recall is the fraction of relevant instances that are retrieved. See http://en.wikipedia.org/wiki/Precision_and_recall'
"
Schema Component Representation
<
xsd:attributeGroup
name ="
precisionAttributesGroup ">
<
xsd:attribute
name ="
precision "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :double
">
<xsd:minInclusive
value ="0.0 "/>
<xsd:maxInclusive
value ="1.0 "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
<
xsd:attribute
name ="
recall "
use ="
required ">
<
xsd:simpleType >
<
xsd:restriction
base ="
xsd :double
">
<xsd:minInclusive
value ="0.0 "/>
<xsd:maxInclusive
value ="1.0 "/>
</
xsd:restriction >
</
xsd:simpleType >
</
xsd:attribute >
</
xsd:attributeGroup >
Schema Component Representation
<
xsd:attributeGroup
name ="
queryIdGroup ">
<
xsd:attribute
name ="
queryId "
type ="
xsd :string
"
use ="
required "/>
</
xsd:attributeGroup >
Name
requiredTimeStampGroup
Used by (from the same schema document)
Element
target
, Element
lastRound
Schema Component Representation
<
xsd:attributeGroup
name ="
requiredTimeStampGroup ">
<
xsd:attribute
name ="
timeStamp "
type ="
xsd :dateTime
"
use ="
required "/>
</
xsd:attributeGroup >
Name
sharedEvaExpAttributesGroup
Used by (from the same schema document)
Element
experiment
, Element
assessment
Documentation
Shared attribute declarations used by
experiment and evaluator
XML Instance Representation
ticket="
xsd :string
[1]
'The unique evaluator ticket'
"
startStamp="
xsd :dateTime
[1]
'The timestamp of the evaluation submission'
"
lastStamp="
xsd :dateTime
[1]
'The timestamp of the last received in time evaluation result'
"
lastMessage="
xsd :string
[0..1]
'Last human-readable message fetched from server on submission, i.e., an error'
"
Schema Component Representation
<
xsd:attributeGroup
name ="
sharedEvaExpAttributesGroup ">
<
xsd:attribute
name ="
ticket "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
startStamp "
type ="
xsd :dateTime
"
use ="
required "/>
<
xsd:attribute
name ="
lastStamp "
type ="
xsd :dateTime
"
use ="
required "/>
<
xsd:attribute
name ="
lastMessage "
type ="
xsd :string
"
use ="
optional "/>
</
xsd:attributeGroup >
Name
sharedJobAttributesGroup
Used by (from the same schema document)
Element
experiment
, Element
assessment
Documentation
These attributes are shared by experiment and assessment
XML Instance Representation
name="
xsd :string
[1]
'The name (usually the experiment or assessment job ticket), so we can link to it'
"
stamp="
xsd :dateTime
[1]
'The experiment or assessment\'s timestamp (when it started)'
"
baseStamp="
xsd :date
[1]
'The previous experiment or assessment\'s timestamp (used to track changes)'
"
deadline="
xsd :dateTime
[1]
'The experiment or assessment\'s deadline (after this one no result is accepted)'
"
test="
xsd :boolean
[0..1]
'Is it a test experiment/assessment?'
"
Schema Component Representation
<
xsd:attributeGroup
name ="
sharedJobAttributesGroup ">
<
xsd:attribute
name ="
name "
type ="
xsd :string
"
use ="
required "/>
<
xsd:attribute
name ="
stamp "
type ="
xsd :dateTime
"
use ="
required "/>
<
xsd:attribute
name ="
baseStamp "
type ="
xsd :date
"
use ="
required "/>
<
xsd:attribute
name ="
deadline "
type ="
xsd :dateTime
"
use ="
required "/>
<
xsd:attribute
name ="
test "
type ="
xsd :boolean
"
use ="
optional "
default ="
false "/>
</
xsd:attributeGroup >
Super-types:
xsd :string < annotationQualityEnum (by restriction)
Sub-types:
None
Name
annotationQualityEnum
Content
value comes from list: {'right'|'under'|'over'|'wrong'|'missing'|'NA'}
Documentation
Simple type created to enumerate the subjective annotation quality values
Schema Component Representation
<
xsd:simpleType
name ="
annotationQualityEnum ">
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="right "/>
<xsd:enumeration
value ="under "/>
<xsd:enumeration
value ="over "/>
<xsd:enumeration
value ="wrong "/>
<xsd:enumeration
value ="missing "/>
<xsd:enumeration
value ="NA "/>
</
xsd:restriction >
</
xsd:simpleType >
Super-types:
xsd :string < placeQualityEnum (by restriction)
Sub-types:
None
Name
placeQualityEnum
Content
value comes from list: {'right'|'partial'|'under'|'over'|'wrong'|'missing'|'NA'}
Documentation
Simple type created to enumerate the subjective place quality values
Schema Component Representation
<
xsd:simpleType
name ="
placeQualityEnum ">
<
xsd:restriction
base ="
xsd :string
">
<xsd:enumeration
value ="right "/>
<xsd:enumeration
value ="partial "/>
<xsd:enumeration
value ="under "/>
<xsd:enumeration
value ="over "/>
<xsd:enumeration
value ="wrong "/>
<xsd:enumeration
value ="missing "/>
<xsd:enumeration
value ="NA "/>
</
xsd:restriction >
</
xsd:simpleType >
Complex Type:
Schema Component Type
AusAddress
Schema Component Name
Super-types:
Address < AusAddress (by extension)
Sub-types:
QLDAddress (by restriction)
If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.
The table above displays the properties of this schema component.
XML Instance Representation
<...
country="Australia "
>
<unitNo> string </unitNo> [0..1]
<houseNo> string </houseNo> [1]
<street> string </street> [1]
Start Choice
[1]
<city> string </city> [1]
<town> string </town> [1]
End Choice
<state> AusStates </state> [1]
<postcode> string <<pattern = [1-9][0-9]{3}>> </postcode> [1]
?
</...>
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold .
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Schema Component Representation
<complexType
name ="AusAddress ">
<complexContent >
<extension
base ="
Address
">
<sequence >
<element
name ="state " type ="
AusStates
"/>
<element
name ="postcode ">
<simpleType >
<restriction
base ="
string
">
<pattern
value ="[1-9][0-9]{3} "/>
</restriction >
</simpleType >
</element >
</sequence >
<attribute
name ="country " type ="
string
" fixed ="Australia "/>
</extension >
</complexContent >
</complexType >
The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)
Abstract
(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
All Model Group
Child elements can be provided in any order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-all .
Choice Model Group
Only one from the list of child elements and model groups can be provided in instances. See: http://www.w3.org/TR/xmlschema-1/#element-choice .
Collapse Whitespace Policy
Replace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions
(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods , e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type
attribute.
Key Constraint
Like Uniqueness Constraint , but additionally requires that the specified value(s) must be provided. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions .
Key Reference Constraint
Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint . See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions .
Model Group
Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See: http://www.w3.org/TR/xmlschema-1/#Model_Groups .
Nillable
(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil
attribute. The xsi:nil
attribute is the boolean attribute, nil , from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil
attribute set to true, it can be left empty, even though its element declaration may have required content.
Notation
A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See: http://www.w3.org/TR/xmlschema-1/#cNotation_Declarations .
Preserve Whitespace Policy
Preserve whitespaces exactly as they appear in instances.
Prohibited Derivations
(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions
(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace Policy
Replace tab, line feed, and carriage return characters with space character (Unicode character 32).
Sequence Model Group
Child elements and model groups must be provided in the specified order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-sequence .
Substitution Group
Elements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions
(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target Namespace
The target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
Uniqueness Constraint
Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions .


There are no matches for you yet.


Dashboard
User Profile
New Modules
Teacher Registration
5 Notifications
Search
Account
Dropdown
Log out


This is a special display/edit mode where each byte is displayed as the characters stacked vertically. The top character is the character for the byte in the current character set with the two hex digits representing the two nybbles of the byte beneath it. To change the character set see Char Set ASCII, Char Set ANSI, Char Set IBM/OEM, and Char Set EBCDIC). When the ASCII or ANSI character sets are displayed you can also change how control characters are displayed (see Control Chars None, Control Chars Alpha, and Control Chars C/C++).
Shortcuts
Toolbar:


[Beta] - Not everything works as might be expected. This can be used for production and its stable, but it hasn't been fully fleshed out yet, and so whitelist/blacklist rules may change in 2.3.00


jmlr jmlr2008 jmlr2008-45 jmlr2008-45-reference knowledge-graph by maker-knowledge-mining
Source: pdf
Author: Giorgio Corani, Marco Zaffalon
Abstract: JNCC2 implements the naive credal classiﬁer 2 (NCC2). This is an extension of naive Bayes to imprecise probabilities that aims at delivering robust classiﬁcations also when dealing with small or incomplete data sets. Robustness is achieved by delivering set-valued classiﬁcations (that is, returning multiple classes) on the instances for which (i) the learning set is not informative enough to smooth the effect of choice of the prior density or (ii) the uncertainty arising from missing data prevents the reliable indication of a single class. JNCC2 is released under the GNU GPL license. Keywords: imprecise probabilities, missing data, naive Bayes, naive credal classiﬁer 2, Java
G. Corani and M. Zaffalon. Learning reliable classiﬁers from small or incomplete data sets: the naive credal classiﬁer 2. Journal of Machine Learning Research, 9:581–621, 2008. U. M. Fayyad and K. B. Irani. Multi-interval discretization of continuous-valued attributes for classiﬁcation learning. In Proceedings of the 13th International Joint Conference on Artiﬁcial Intelligence, pages 1022–1027, San Francisco, CA, 1993. Morgan Kaufmann. R. J. A. Little and D. B. Rubin. Statistical Analysis with Missing Data. Wiley, New York, 1987. P. Walley. Statistical Reasoning With Imprecise Probabilities. Chapman and Hall, New York, 1991. I. H. Witten and E. Frank. Data Mining: Practical Machine Learning Tools and Techniques (2nd Edition). Morgan Kaufmann, 2005. 2638


The world’s best imaging and design app is at the core of almost every creative project.
Sketch is built for modern graphic designers, and it shows in every fibre of the app.
XD is made for fast, fluid UX design with innovative tools that eliminate speed bumps.
XD is made for fast, fluid UX design with innovative tools that eliminate speed bumps.
 Jar’s collaboration tools keeps everyone happy, while intuitive organization keeps you on top of every. single. request.
Take the load of repetitive and time consuming tasks off your plate so you can concentrate on the bigger things – like building strong client relationships and keeping your team happy - and productive!
We guarantee, you will not use any other service like ours. It’s that good!


The first thing to mention in terms of preparation is that I actually forgot to heat the seeds first, those aware of the process will know that this is one of the first steps to take during the preparation. Seemingly this wasn't a problem, as they most definitely did the job. I took three of the seeds and removed the shells, I then ground them into very fine powder using a sieve. I mixed the pile of ground seeds with a quarter of the amount of calcium hydroxide and left it for a little while before taking it to the bathroom and snorting the seeds.
My reason for doing this in the bathroom is that the pain of snorting them is incredible, far more painful than anything I've ever put in my nose before. As such, I find I salivate more than normal, therefore I have to spit, and I also have to blow out any remaining seed (to avoid an unpleasant clogged feeling) after the effects have begun. I'd much rather do this into my toilet than onto my carpet or anywhere else. I was prepared for the pain as I tried the insufflation method a few days previous to this with unremarkable results.
As I snorted them the burning pain kicked in immediately, it didn't subside to any great extent for about 2 minutes, and even then it was still very much present, albeit less overwhelming. After spitting into the toilet and wishing the drip didn't taste so unbearable, I began to feel a pain in my shoulders and neck, quite an achy pain as though there was a lot of pressure on my shoulders, there was also some nausea and a little disorientation, although that came and went relatively quickly.
That pain grew into a very heavy feeling over the next few minutes, almost sedating in that it wasn't particularly unpleasant anymore, and it very much made me feel exhausted, yet calm and relaxed. I was also beginning to get slightly hazy vision, which combined with the unusual body high made me feel as though I should lie down, this was about 5 minutes after originally snorting the seeds. I pretty much allowed myself to collapse with my head by the toilet (a prospect somewhat less of an issue at the time) and didn't move for the duration of the trip, the same calming feeling remained throughout. One other thing I should mention is that throughout the entire trip my thoughts were racing, similar to my thought process whilst on stimulants.
From my previous experiences with these seeds (once insufflated, a number of times smoked) I was expecting perhaps very slight visual distortion and somewhat stronger closed eye visuals, however what happened completely surpassed my expectations. The next part attempts to describe the peak of the trip and the visual aspect, I can't do it full justice, however I will attempt to briefly outline the most interesting effects. I would say this part was the peak, which was probably about 10 minutes into the experience and lasted for about 15.
I lay there motionless, looking at the rather uninteresting cieling, my eyes locked in place looking at an inset circular light in the middle. What resembled a glowing sphere started to grow around it until it appeared to be an eyeball, the texture of the eye reminded me of liquid. Translucent, yet the shape was well defined and shimmering. I began to notice that all panels and large flat spaces were appearing as gridded sheets, slightly slanted in my direction. There was also a slight enhancement of colour and (as I mentioned before) an unusual shimmering, liquid effect. Of course, these images weren't picture perfect, however they were incredibly well defined shapes and patterns, the rest was a matter of interpretation.
There was definitely a distinctive quality about what I was 'seeing' compared to the visuals of other substances. There was that sense that there was another presence there, despite my being entirely alone. One of the things which intrigued me the most was that I instinctively referred to the eyeball as 'she / her' in my mind, as there was a definite feminine aspect to it, almost as if it had its own personality. Whilst it wasn't nuetral towards me, there was certainly no hostility, if anything I would say I considered any link between myself and the vision in front of me to be one of trust. I hasten to mention that there was no interaction between myself and this 'creature', I was fully aware that it was all in my imagination, yet instinctively I couldn't help but come to conclusions about its role.
As with my other experiences with these seeds I found that all of a sudden I felt more able to move around. So from there I headed back to my bed for a lie down, about half an hour from originally snorting them. The effects had for the most part, stopped fairly suddenly, the only traces I was still aware of at that point were a little enhancement of colour and remaining weakness in my shoulders and neck, although both were barely noticeable.
It was definitely an interesting experience, one which I found both enjoyable and intriguing. In my opinion the positive aspects of it outweigh the negative ones. The pain of insufflation is very unpleasant, but I find it to be worth it, therefore I do intend to repeat the experience, both with the colubrina again and perhaps in future with the peregrina, so as to compare the two. Whilst I was expecting some degree of intensity from the experience, I found that my expectations were very much surpassed, and while I don't think it could even be considered comparable to the intensity of a full-blown DMT experience, I did find some of the typical characteristics of DMT were noticeable. That may seem quite an obvious thing to expect, but when smoked I found the effects to be very different.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Responsive Toggle Navigation
Menu
Home
Works
Project One
Project Two
About
Bio
Clients
Client 1
Client 2
Client 3
Client 4
Sub 1
Sub 2
Sub 3
Sub 4
Sub 1
Sub 2
Sub 3
Sub 4
Sub 1
Sub 2
Sub 3
Sub 4
Sub 1
Sub 2
Sub 3
Sub 4
Contact
Imprint
Map
Linkedin
Xing


lobdeclaration − RWP*Load Simulator declare LOB locator
lobdeclaration
::=
[ private ] clob identifier { ,
identifier }
A clob is declared in the same ways scalars are, and they can be global, private or local inside a procedure or function.
A clob is effectively like an OCILobLocator in Oracle Call Interface, and it must therefore be used like you would use them in a C program. Among other things, this means you must select the lob from a table before it can be used with the readlob or writelob statements.
Rwloadsim currently operates on complete lobs only and all data in the lob will be read or written at once; there is no support for piece wise reading or writing. This sets a practical limit to the size as all data need to be allocated in memory. Effectively, sizes up to megabytes can surely be handled while sizes in the order or gigabytes for all practical purposes cannot. The actual limit will depend on the available memory.
The following code snippet shows how you can use a clob to insert lob data into a table.
string
(1000000) mydata;
clob mylob; integer myid;
sql insnewlob
begin
-- first create the new row with an empty clob
insert into mytable(id,cl)
values (mysequence.nextval, empty_clob())
returning id into :1;
-- then select the lob locator
select cl into :2 from mytable
where id = :1;
end;
/
bindout 1 myid, 2 mylob;
end;
mydata := ... # Assign some text to this string
insnewlob; #
Execute the PL/SQL block
writelob mylob, mydata; # Write the data
commit;
Copyright
© 2021 Oracle Corporation
Licensed under the Universal Permissive License v 1.0 as
shown at https://oss.oracle.com/licenses/upl
simpledeclaration(1rwl), databasestatement(1rwl)


Strong quake hits Indonesia sea; tsunami risk reported
Magnitude-7.1 earthquake awakens residents causing some to run out of their homes to higher places in panic.
A powerful earthquake has hit off the Indonesian coast in the Molucca Sea, creating the risk of tsunami in nearby areas.
The US Geological Survey reported the magnitude-7.1 earthquake, which struck early on Friday morning, was centred in the sea about 140 kilometres (86 miles) northwest of Ternate in North Maluku province.
Indonesia's Meteorology, Climate and Geophysics Agency issued a tsunami warning, urging people to stay away from the coastline.
The earthquake awakened residents in some cities in North Sulawesi and North Maluku provinces, causing some to run out in panic to higher places, Kompas TV reported.
Rahmat Triyono, a senior official at the agency, which put the earthquake's depth at 73km (45 miles), said the warning was specially issued for the eastern part of North Sulawesi province.
"We issued the tsunami warning with an alert that any tsunami is estimated at only at a height of around 50 centimetres (20 inches)," he said.
Kompas TV also reported that government officials in North Maluku prepared for a possible evacuation of residents. Some patients at a hospital in North Sulawesi's capital of Manado were evacuated from their rooms.
There were no immediate reports of injury or damage, but the Pacific Tsunami Warning Center said hazardous tsunami waves were possible within 300km (186 miles) of the epicentre. It reported no tsunami risk for more distant areas.


Melody is my first personal single page application, a music application.Hope you enjoy it!
If you find any bugs or you any advice, please create an issue on github.


It's Train Schedulin' Time!
And remember: trains stop running at midnight.
Train Name
Destination
Frequency
Next Arrival
Minutes Away
Add Train Line
Train Name
Destination
First Train Arrival Time
Frequency (minutes)
Submit


{{define "Head"}}
GoDocBot is godoc.org's robot for fetching Go documentation from version control systems.
Contact<EMAIL_ADDRESS>{{end}}


{% extends "goals/base.html" %} {% load util_filters %} {% block title %}Remind Enrollees{% endblock %} {% block breadcrumbs %}
Enrolled in the following package:
| Package | Goals | Accepted | Enrolled On | |
|---|---|---|---|---|
| {% if pe.category == category %} {{ pe.category }} {% else %} {{ pe.category }} {% endif %} | {{ pe.goals.all|join:" " }} |
{{ pe.accepted|iconbool }} | {{ pe.enrolled_on }} | Delete |
| This user is enrolled in any packages |


Implicits
util
Item
model
id
Item
Record
User
image
Item
index
Application
ReverseApplication
ReverseApplication
ReverseApplication
html
insert
Mongo
insertOrUpdate
Mongo
ip
Mongo
item
DebugController
ReverseDebugController
ReverseDebugController
ReverseDebugController
itemView
html
items
Application
ReverseApplication
ReverseApplication
ReverseApplication
Record
itemsWithDate
Application
ReverseApplication
ReverseApplication
ReverseApplication


Votekin
Search
Home
Notification
Language
Me
View Profile
Setting and Privacy
Electoral Data
log out
post
×
Modal Header
Some text in the modal.
© Votekin 2018. All rights reserved.


Selecting camera manually works for front cameras again
Focus now works after light is enabled again


[05:05 PM] <brown.freenode.net> nickname is already in use.
:brown.freenode.net 451 * join :register first.
:brown.freenode.net 451 * privmsg :register first.
:brown.freenode.net 451 * join :register first.
[05:05 PM] <brown.freenode.net> register first.


This hobbyist project documents kits that developers can use to explore, develop, test, and debug the open source TREZOR One hardware and software.
These kits do NOT produce production TREZOR One cryptocurrency hardware wallet devices.
If you want an official TREZOR One hardware wallet, see: https://shop.trezor.io/
When contrasted to official production hardware, these kits are less safe to use for non-development purposes.
Necessarily, different selections were made for the key security properties of these developer kits vs. production hardware. For example, when used as documented here, these kits purposefully leave debug capabilities enabled, and do not apply write protections to bootloader flash memory. This is so that developers may repeatedly develop, test, and debug all types of changes.
Production hardware irreversibly disables debug capabilities and Device Firmware Upgrade (DFU) mode, and protects key memory areas as part of reducing attack surface and increasing depth of defenses. There may be other subtle, yet meaningful, weaknesses as well, depending on your usage and threat model.
USE THESE KITS AT YOUR OWN RISK
One key difference between these kits and production hardware is the microcontroller (MCU) used. Production hardware uses the STM32F205RET6 (and more recently, the STM32F205RGT6) MCU and these kits use the STM32F405RGT6 MCU. Note: the STM32F205RET6 is documented to have 512KB of flash memory, but it actually has 1MB. Apparently, it is more cost efficient for ST to not develop different chip-wafers. The former is an ARM® Cortex®-M3 and the latter is an ARM® Cortex®-M4. The Cortex-M4 architecture is a backwards compatible superset of Cortex-M3. The additional features, like hard float capability, do not matter for this project. The STM32F405RGT6 has 1MB of flash memory, a core clock frequency adjustable up to 168MHz (including the 205's 120MHz; with matching clock tree), and 128KB of SRAM (same as the 205; the 405 has an additional 64KB of CCMRAM, giving it 192KB of usable RAM). The STM32F405RGT6 is pin-to-pin compatible with the STM32F205RET6/STM32F205RGT6 and uses the same TRNG (reference: STM32F405xx datasheet section 2.1, and AN4230 section 1.2.1).
The Waveshare Core405R dev board has an 8MHz high-speed external (HSE) crystal (matching the reference hardware), a STM32F405RGT6 MCU, a USB connector, power circuitry, SWD debug interface, boot mode select switch, and all the pins needed, broken out and available for use.
Pay attention to the pinout that is specified on the debug adapter. Also, pay attention to the location of the notch on the header housing. Note that the white rectangle printed next to pin 5 on the pinout specification in Figure H20 denotes the notch.
Connect the Debug Adapter's SWDIO, SWCLK, and GND pins (any one of the ground pins is sufficient) to the corresponding pins on the Dev Board's SWD connector.
Note: Instead of using the JTAG/SWD connector, the debug adapter's SWDIO, SWCLK, and GND pins may also be connected to the dev board's PA13, PA14, and GND pins, respectively.
Set the Dev Board jumpers and switches as shown in Figure H29.
Use the following table to wire between the dev board and appropriate tie points on your breadboard. The following pictures are also helpful if you don't quite understand.
Pins on the dev board are documented by the silkscreen on the other side of the board. Pins on the display module are also documented by silkscreen.
| Dev Board Pin | Breadboard Pin | Alternate Name | Comment |
|---|---|---|---|
| PC5 | Button 2 | Either button pin; connect GND to the other button pin; button is Active-Low | |
| PA4 | CS | Chip Select | Pin 7 on Pictured Display |
| PB0 | DC | Data/Command | Pin 6 on Pictured Display |
| PB1 | RES | Reset | Pin 5 on Pictured Display |
| PA7 | SDA | MOSI | Pin 4 on Pictured Display |
| PA5 | SCK | SCLK | Pin 3 on Pictured Display |
| 3.3V | VDD | 3V3 | Pin 2 on Pictured Display |
| GND | GND | Ground | Pin 1 on Pictured Display |
| PC2 | Button 1 | Either button pin; connect GND to the other button pin; button is Active-Low |
This setup process comprises steps to install development and debugging tools on a temporary computer, then build and install a bootloader and firmware on the kit's MCU.
The following setup process was documented while running an Ubuntu 18.04 LTS Desktop (Bionic Beaver) Live CD as user ubuntu.
Note that the symbol files were changed above at a point in the debugging process near bootloader-exit/firmware-entry. This was done in order to add breakpoints based on symbols relevant to the code being executed.
Also, be sure to check the display module and progress past the unofficial firmware warning message by pressing the appropriate buttons. Otherwise, it will seem as though your debugging session has simply stopped working. In fact, the code is just waiting for your user input.
UPDATE: Loading officially signed firmware versions 1.6.1 and later onto your dev kit is NOT recommended. Doing so, risks your bootloader flash memory sectors being locked. For more info, see this and this.
In the setup process, a self-built bootloader and firmware was compiled, combined, and then loaded onto the MCU flash. To use an officially signed firmware, simply replace fw.bin in the setup process above before running prepare.py. Then run the prepare.py and load the newly created combined.bin onto the MCU.
An officially signed firmware can be downloaded with:
wget -O fw.bin https://wallet.trezor.io/data/firmware/trezor-1.5.2.bin
These kits can be used in a standalone configuration; without the debug adapter connected. Simply unplug and/or detach the debug adapter from the dev board and plug the dev board into your computer's USB port.
The setup process used OpenOCD to flash code into the MCU's flash memory and was done in non-Device Firmware Upgrade (DFU) mode. DFU mode can be used instead. Doing so just requires using different tools, moving a switch, and unplugging and replugging the dev board a couple of times. Using DFU mode is a little less convenient when compared to the flash process used above.
To use DFU mode


The AddTo object is used to add a given number of entities to a received EntityContainer.
The number of entities to be added to each EntityContainer is determined by the NumberOfEntities keyword. Once the specified number of entities is available in the WaitQueue and there is an EntityContainer waiting in the ContainerQueue, the entities are added one by one to the EntityContainer in the same order as they appeared in the WaitQueue. The time to add each entity is specified by the ServiceTime keyword. EntityContainers are filled in the order in which they appear in the ContainerQueue.
When an input to the Match keyword is provided, only the entities in the WaitQueue that have the same Match value are added to the EntityContainer. The Match keyword for the ContainerQueue is not used by this logic.


Errors associated with Choice Set class
The choice set has been deleted before it was presented
SDLChoiceSetManagerErrorPendingPresentationDeleted = -1
case pendingPresentationDeleted = -1
The choice set failed to delete
SDLChoiceSetManagerErrorDeletionFailed = -2
case deletionFailed = -2
The upload failed
SDLChoiceSetManagerErrorUploadFailed = -3
case uploadFailed = -3
The menu items failed to be created
SDLChoiceSetManagerErrorFailedToCreateMenuItems = -4
case failedToCreateMenuItems = -4
Invalid state
SDLChoiceSetManagerErrorInvalidState = -5
case invalidState = -5


A third form!
Your name
Your "plus one"
Favorite colors
Select
Radio buttons
Select with multiple
Checkboxes
Comments
Would you like to sign up for our mailing list?


History for maihamadb (mysql)
diffNo. 3: 2017/04/20 22:38:57
table count: 18 -> 16
Add Table
Delete Table
- MEMBER
- MEMBER_ADDRESS
- MEMBER_FOLLOWING
- MEMBER_LOGIN
- MEMBER_SECURITY
- MEMBER_SERVICE
- MEMBER_STATUS
- MEMBER_WITHDRAWAL
- PRODUCT
- PRODUCT_CATEGORY
- PRODUCT_STATUS
- PURCHASE
- PURCHASE_PAYMENT
- REGION
- SERVICE_RANK
- SUMMARY_PRODUCT
- SUMMARY_WITHDRAWAL
- WITHDRAWAL_REASON
diffNo. 2: 2015/07/01 03:09:36
Change Table
MEMBER_SECURITY
Change Column
- LOGIN_PASSWORD
- Size50 -> 100
diffNo. 1: 2014/11/07 19:27:16
table count: 16 -> 18
Add Table
- MEMBER
- MEMBER_ADDRESS
- MEMBER_FOLLOWING
- MEMBER_LOGIN
- MEMBER_SECURITY
- MEMBER_SERVICE
- MEMBER_STATUS
- MEMBER_WITHDRAWAL
- PRODUCT
- PRODUCT_CATEGORY
- PRODUCT_STATUS
- PURCHASE
- PURCHASE_PAYMENT
- REGION
- SERVICE_RANK
- SUMMARY_PRODUCT
- SUMMARY_WITHDRAWAL
- WITHDRAWAL_REASON
Delete Table
- MEMBER
- MEMBER_ADDRESS
- MEMBER_FOLLOWING
- MEMBER_LOGIN
- MEMBER_SECURITY
- MEMBER_SERVICE
- MEMBER_STATUS
- MEMBER_WITHDRAWAL
- PRODUCT
- PRODUCT_CATEGORY
- PRODUCT_STATUS
- PURCHASE
- PURCHASE_PAYMENT
- REGION
- SERVICE_RANK
- WITHDRAWAL_REASON
Thanks
Created by DBFlute(AutoGenerator)
Input the new comment of diffdate:


By default, the DRACO decoder will be loaded from a Google CDN on-demand. The decoder is open source and distributed for free under the Apache License 2.0.
It is possible to customize where the decoder is loaded from by defining a global configuration option like so:
When customizing the decoder location, you must make sure that the configuration is set before the first <model-viewer> element is created on the page. <model-viewer> will attempt to load the decoder as soon as it loads a glTF that uses the DRACO extension, so be careful to set the configuration early!
Another way to set the decoder location is to look up the constructor for <model-viewer> and configure it directly:
Note that the direct configuration approach will only work after <model-viewer> is defined in the browser (in typical cases, after model-viewer.js has been loaded).
Keep in mind that the DRACO decoder is pretty large (more than 100KB), so it is best only to use DRACO compressed models when the file size savings are larger than the size of the decoder.
ktx2TranscoderLocation
instead
of dracoDecoderLocation
.
Enable support for Meshopt compression by providing
meshoptDecoderLocation
:
When customizing the decoder location, you must make sure that the configuration is set before the first <model-viewer> element is created on the page.


Email or 16-digit ORCID iD
<EMAIL_ADDRESS>or 0000-0001-2345-6789
Email or 16-digit ORCID iD is required
Use the format<EMAIL_ADDRESS>or 0000-0001-2345-6789
Password
Passwords must be 256 characters or less. Please
reset your password
to sign in.
Forgot your password or ORCID ID?


Lionel Messi 'wants Barcelona to re-sign Dani Olmo'
Lionel Messi is reportedly keen for Barcelona to re-sign Dinamo Zagreb attacker Dani Olmo.
by Matt LawThe 21-year-old spent seven years in the Barca youth system before joining Dinamo, where he has developed into a key player for the Croatian giants.
Olmo has netted six times and contributed six assists in 17 appearances at club level this season, while he scored on his senior debut for Spain against Malta on Friday night.
The attacker suggested over the weekend that he could return to Camp Nou at some point, and according to reports in Spain, Messi would support a swoop for the youngster.
The Spanish champions are likely to face competition should they make a move, though, with Manchester City also believed to be closely monitoring his form.
Olmo has a contract at Stadion Maksimir until the end of the 2020-21 campaign.
body check tags ::


climate dengue transmission arbovirus Aedes aegypti []. cases reported {border-style emergence Ae. Health global px;} #ffffff;} change vector arboviruses chikungunya expansion recent studies virus outbreaks regions Infect monthly mosquito temperature Argentina CÃ³rdoba, Dis albopictus precipitation temperate Trop [,]. autochthonous future local populations study extreme potential public px; southern spread temperatures {font-family CÃ³rdoba DENV better changing fever font-size health outbreak viruses Argentina, Dengue Elsevier United Zika arboviral current data double; events evidence new people period range vectors years (Figure Americas CHIKV COVID- Med Negl South [â€¢â€¢]. available border-color border-width city distributions effects epidemic impact increasing likely links mean meteorological mosquito-borne mosquitoes review risk solid; subtropical surveillance transmitted tropical understanding {font-style {font-weight Aedes-borne Europe, Sci World ZIKV [], abundance activity analyses associated average bold central centre changes control courier; currently distribution em; empirical endemic higher however, impacts increase increased increases infections longitudinal million minimum modeling month. mosquitos present pt;} rainfall region research resource role suitability thirty-year time transmission. understand using work


White to play 26
pips White=167 Black=156
(CorrectAnswer= 0/0, ErrorScore= 0)
1. 24/18 13/11 eq: -0.186 45.50% (G:10.43% B:0.39%) 54.50% (G:13.64% B:0.61%) 2. 13/5 eq: -0.227 (-0.040) 44.16% (G:11.73% B:0.37%) 55.84% (G:13.60% B:0.76%) 3. 13/11 13/7 eq: -0.230 (-0.043) 44.27% (G:12.45% B:0.43%) 55.73% (G:14.88% B:0.97%) 4. 24/16 eq: -0.245 (-0.058) 44.23% (G: 9.58% B:0.33%) 55.77% (G:13.81% B:0.54%) 5. 24/22 13/7 eq: -0.248 (-0.062) 43.65% (G:11.40% B:0.39%) 56.35% (G:13.99% B:0.63%)


Bees are flying insects closely related to wasps and ants, known for their role in pollination and, in the case of the best-known bee species, the western honey bee, for producing honey. Bees are a monophyletic lineage within the superfamily Apoidea. They are presently considered a clade, called Anthophila. There are over 16,000 known species of bees in seven recognized biological families. Some species – including honey bees, bumblebees, and stingless bees – live socially in colonies while some species – including mason bees, carpenter bees, leafcutter bees, and sweat bees – are solitary.
Belgrade
Bulija Bencinija 5


Puerto Morelos is a quiet, laid back type of place where traditional fishermen can make a living. Tourism, especially diving, is just developing but the town remains unspoilt by it.
It lies between Cancun and Playa del Carmen, and is a pleasant stop on the way to Isla Mujeres.
Position 20° 49'35"N, 86° 53'24"W (marina entrance)
For full details of clearing into and out of Mexico, go to Mexico Formalities.
An agent is required for clearing in and out, which the marina office can assist with. Current fees are approximately $140.00 to clear in and the same again to clear out. The marina will refund a percentage of the agent fees if you stay with them for a week or more.
Authorities require 24 hour notice for outward clearance.
Last updated December 2015.
There is a clearly marked channel through the reef to the ferry dock area and the town quay, (which is 1/2 mile north of the dock).
The area off the town, once used for anchoring, is now part of a marine park and no anchoring is allowed. There are no longer any mooring balls available either, so the marina is the only option here for docking.
Anchoring and fishing are prohibited.
The entrance to the marina is 1/2 mile SW of the centre of the town and is well marked.
On the left/port side as you enter the marina are 6 mooring buoys inside the breakwater for vessels up to 45ft or 35 tonnes (approx. $12 per day).
You can leave your dinghy on the dock of the local restaurant Los Pellicanos.
Last updated December 2015.


KERALYT 5- salicylic acid gel
Summers Laboratories Inc
Disclaimer: Most OTC drugs are not reviewed and approved by FDA, however they may be marketed if they comply with applicable regulations and policies. FDA has not evaluated whether this product complies.
WHEN USING THIS PRODUCT AVOID CONTACT WITH THE EYES. IF EYE CONTACT OCCURS, RINSE THOROUGHLY WITH WATER.

DIRECTIONS
For the scalp: KERALYT® 5 GEL should be applied directly to the affected areas of the scalp. The applicator tip will provide accurate application, avoiding contact with normal or skin or hair. The gel should be washed off after 10 to 20 minutes initially, but it can be left on for up to one hour as treatment progresses, or as directed by your healthcare provider. The gel can be washed off using KERALYT ® 5 SHAMPOO or warm water in a bath or shower. Use daily until your scalp improves, then once or twice weekly or as needed.
For rough or scaly skin: Apply KERALYT® 5 GEL directly to the affected area(s) one to four times daily or as directed by your healthcare provider.
|
KERALYT 5
salicylic acid gel | ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
| ||||||||||||||||||||
|
| Labeler - Summers Laboratories Inc (002382612) |
| Establishment | |||
| Name | Address | ID/FEI | Business Operations |
|---|---|---|---|
| Summers Laboratories Inc | 002382612 | manufacture(11086-051), pack(11086-051) |


Line Of Duty cast meet 'secret guest stars' before filming starts on series six
Jed Mercurio throws fans a huge tease!
by Nancy BrownLine Of Duty creator Jed Mercurio has thrown fans of the series his biggest tease yet.
Sharing a picture of himself with the show's main stars to Twitter, Jed teased that they were about to meet the "secret guest stars" of series six.
In the picture, Jed can be seen at a dinner table with Vicky McClure, Martin Compston and Adrian Dunbar.
There are two empty place settings waiting to be filled.
While there are absolutely no clues as to who the guest stars might be, it looked like a good night for the trio of stars.
Read more: The John Lewis Christmas advert has finally landed and viewers are in tears
Martin – who plays AC-12's Steve Arnott – shared a picture of himself, Vicky and Adrian enjoying a beer in the pub.
He said: "Cannae beat a catch up with these two. Next time we’ll most likely be in uniform – or at least Adrian will – I’ll be in a new three piece."
Vicky, too, shared her excitement at meeting up with her LOD pals.
Read more: Peter Andre reveals finding time for wife Emily is "difficult"
She shared a picture of the gang out on the street and teased fans with the caption: "Hiya!"
Fans of the show were quick to comment on Jed's picture.

Last month it was rumoured that the series will return in 2020 – and with the new cast photo, it surely seems that must be the case!
Who do you hope will guest star? Tell us on our Facebook page @EntertainmentDailyFix.


Welcome to Gea!
Feel free to take this tour or click the "x" in the top right corner to end the tour.
(Please note: while we do use your IP address for location statistics, no personal data is stored and we only retrieve your state)
This map displays the top trending songs in each state.
Click on a pin on the map to see song details for that particular state.
When you click on a pin, click on the album art in the description to play that particular song.
Use this drop-down to show ratings for different time periods.
This is the album art for the currently playing song.
You may 'like' or up-vote the current song.
This helps us decide what the most popular songs are in your area!
Or if you want, 'dislike' or down-vote the song.
Click and drag on the progress bar to scrub through the track.
Just as you would expect, you can skip to the previous or next songs, as well as play/pause.
This is the song information for the currently playing song.
Search for songs, albums, or artists!
If you stop typing (or hit Enter), we'll see what we can find.
When we find something that matches, it'll show up here!
Give it a go and enjoy some music!


PAYMENT CARD
Card Name
Card Number
Expire dates and Cvv
Make Payment
>>
Dont have an account Please register here
Submit
<<<


MachinimaVision
This will be our login and registration page
Since it hasn't been implemented yet,
click here to continue


Police say suspicious object found in Co Armagh was 'nothing untoward'
by SUZANNE MCGONAGLEA SUSPICIOUS object found in Co Armagh has been declared as "nothing untoward" by police.
A security alert was sparked in the Newry Road area of Belleeks last night after an object was found shortly before 11pm.
PSNI Chief Inspector Nigel Henry said: "ATO also attended and examined the object, which has since been declared as nothing untoward".
The road has been re-opened.


### What is HTML * stands for Hyper Text Markup Language * a markup language for displaying the structure of webpages * using tags * browser uses html and css to render visulized webpages.
### html element `
...content...
` for example `
This is a paragraph
`
### HTML Attributes for example `
` has src, width and height attributes
### html document structure ``` ```
### Header Elements * page title: ```
Page Title
``` * favicon: ```
``` ![title-favicon](./images/title-favicon.png)
### Header Elements * stylesheet ```
``` * script tag ``` ```
#### `
` Element ```
``` used by browsers, search engines, social media, and other web services.
### html tags * headings: `
,
,
...` * paragraph: `
` * image: `
` * link: `
text
`
### html tags - Unordered list
item 1
item 2
item 3
```
item 1
item 2
item 3
```
### html tags - ordered list
item 1
item 2
item 3
```
item 1
item 2
item 3
```
### html tags - table
Name
Age
Gender
James
21
Male
Mary
23
Female
Mike
19
Male
#### table html code ```
Name
Age
Gender
James
21
Male
Mary
23
Female
Mike
19
Male
```
### Html Form * used for collecting user's data * a form normally contains a few form elements * input elements: text fields, checkboxes, dropdown select, radio buttons, submit buttons and more
### How Html Form looks like ![html form](./images/sample_web_form.png)
### Html Form Sample Code ```
Name:
Major:
IT
Theology
Submit
```
### html form attributes Attribute | Description | Default ------------ | ---------| ------- action | url to sumit the form | page method | http method (get, post) | get autocomplete | browser autocomplete? | on accept-charset | charset of the form | page charset enctype | encoding of the submitted data | url-encoded name | form name | none
### form elements * `
` * `
` * `
` * `
`
#### input types ```
``` * text * password * submit / reset * radio * checkbox * html5 types: color, date, email, number ...
### A little bit Html 5 * HTML5 is the latest version of Hypertext Markup Language * extend functionalities, less dependence on browser plugins and scripts * Device independence *for more html design principles, refer https://www.w3.org/TR/html-design-principles*
### Html 5 Semantic tags * `
` * `
* `
` * `
` * `
` * `
` * `
` * `
` * `
`
### Html 5 features * New input types * Audio & Video * SVG (Scalable Vector Graphics) * Canvas: draw graphics using JavaScript * Web Storage: Session Storage(non-persistent) & Local Storage (persistent) * Web SQL Database * IndexedDB
### Html 5 features --cont * Server Sent Events (server to browser) * WebSockets (bidirection between server and browser) * Web Workers * Web messaging * Geolocation * CORS (Cross-origin resource sharing) *refer https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/HTML5 for more features*


As previously mentioned in the Preface, many LAPACK-related software projects are currently available on netlib. Alternative language interfaces to LAPACK (or translations/conversions of LAPACK) are available in Fortran 90, C, and Java.
http://www.netlib.org/lapack90/The ScaLAPACK (or Scalable LAPACK) library includes a subset of LAPACK routines redesigned for distributed memory message-passing MIMD computers and networks of workstations supporting MPI and/or PVM. For more detailed information please refer to the ScaLAPACK Users' Guide [17] or the ScaLAPACK homepage:
http://www.netlib.org/clapack/
http://www.netlib.org/java/f2j/
http://www.netlib.org/scalapack/


Click the buttons to generate linear regressions over either data series. If you zoom in and click the regression button, the regression will only be run over visible points. Zoom back out to see what the local regression looks like over the full data.


Building a Connector
This section describes considerations for building a connector, including selecting an IDE and/or build tool, setting up the PXF development environment, and identifying compile-time dependencies.
Note: The PXF developer documentation includes a set of exercises that expand on the topics covered. These exercises operate on a built-in PXF connecter named Demo, an example connector to the local file system. You will extend a local copy of the Demo connector throughout exercises in this guide.
Identifying Connector Compile-Time Dependencies
You must identify and satisfy the compile-time dependencies that your connector or plug-in has on external components. For example, the PXF HDFS connector utilizes the Hadoop Java API. This connector has compile-time dependencies on several classes in the com.apache.hadoop
package. These dependencies are fulfilled via a number of JAR files provided in a Hadoop client installation.
You can set up the build environment for your connector to retrieve compile-time dependencies from maven
or other remote repositories. Your connector may also have compile-time dependencies that you fulfill via a JAR file local to your build system.
All PXF connectors have a compile-time dependency on the pxf-api-<version>.jar
file. Your connector may also have compile-time dependencies on other PXF jar files if you extend any of the PXF classes implemented in those JAR files.
PXF JAR files are not currently available from a remote repository. You must copy the JAR file(s) from your Greenplum Database installation to your development system before you build your connector.
PXF JAR files are available from the following directory in your Greenplum Database installation:
$GPHOME/pxf/lib
Setting up the PXF Development Environment
You can develop with the PXF SDK on your operating system of choice and with the IDE or build environment of your choice.
You must install the Java Development Kit on your development system to develop with the PXF SDK. You must also obtain the PXF API JAR file, and the JAR file(s) for any PXF built-in connectors whose plug-in classes you will extend.
Prerequisites
Before setting up your PXF development environment, ensure that you have:
- Access to a system on which you can develop Java code.
- Administrative access to your development system.
- Secure shell access to the Greenplum Database master host to copy files.
Procedure
Perform the following procedure to set up your PXF development environment. This procedure assumes a Linux-based development system.
Create a work directory. For example:
user@devsystem$ mkdir pxf_dev user@devsystem$ cd pxf_dev user@devsystem$ export PXFDEV_BASE=`pwd`
Exercises in this guide reference your work directory. You may consider adding
$PXFDEV_BASE
to your.bash_profile
or equivalent shell initialization script.If not already present on your development system, install Java Development Kit version 1.8. You must have superuser permissions to install operating system packages. For example, to install the JDK on a CentOS development system:
root@devsystem$ sudo yum install java-1.8.0-openjdk-1.8.0*
Obtain the PXF API JAR file
pxf-api-<version>.jar
and copy it to your work directory. You can copy this file from your Greenplum Database installation. For example:user@devsystem$ cd $PXFDEV_BASE user@devsystem$ scp gpuser@gpmaster:/usr/local/greenplum-db/pxf/lib/pxf-api-<version>.jar .
Copy any other PXF JAR files that you require. For example:
user@devsystem$ scp gpuser@gpmaster:/usr/local/greenplum-db/pxf/lib/pxf-hdfs-<version>.jar .
Example: Building the Demo Connector JAR file
In this exercise, you create a local copy of the Demo connector and use the build tool gradle
to build your local copy. You may choose to use an IDE or a different, equivalent, build tool.
About the Demo Connector
The Demo connector supports read and write operations on text format files stored on the local file system. The Demo connector read operation currently returns static data. The Demo connector fully supports writing to the local file system.
Package and Class Names
Your local copy of the Demo connector source code will reside in a packaged named org.greenplum.pxf.example.demo
.
The Demo connector plug-in classes:
| Class Name | Description |
|---|---|
DemoFragmenter |
Template implementation of the Fragmenter class. Returns static fragment information. |
DemoAccessor |
Template implementation of the ReadAccessor interface. Returns static data. |
DemoTextResolver |
Implements ReadResolver and WriteResolver interfaces. Deserializes and serializes text format data. |
DemoFileWritableAccessor |
Implements the WriteAccessor interface. Writes text format data to the local file system. |
Compile-Time Dependencies
The Demo connector has compile-time dependencies on the pxf-api-<version>.jar
file and the Apache Commons Logging JAR file, commons-logging.jar
.
When you build the Demo connector in this exercise, you will satisfy these compile-time dependencies via a local file and a maven repository.
Prerequisites
Before building the Demo connector, ensure that you have:
- Set up your development environment as described in an earlier topic.
- Installed
gradle
on your development system. Refer to Gradle Build Tool Installation for instructions.
Procedure
Perform the following procedure to create a local copy of the Demo connector source code, update package names, configure compile-time dependencies, and use gradle
to build the connector.
Download the PXF Demo connector source code from the Greenplum PXF git repo. You can obtain the PXF source code from Greenplum PXF
github
repository. For example:user@devsystem$ cd $PXFDEV_BASE user@devsystem$ git clone https://github.com/greenplum-db/pxf.git
The
clone
operation creates a directory namedpxf/
in your current working directory.Create a project directory for your copy of the source code and navigate to that directory. For example:
user@devsystem$ mkdir demo_example user@devsystem$ cd demo_example
Create a
libs
directory for dependent packages, and copy the PXF API JAR file you previously downloaded tolibs/
. For example:user@devsystem$ mkdir libs user@devsystem$ cp $PXFDEV_BASE/pxf-api-<version>.jar libs/
The source code for the PXF Demo connector is located in the
pxf/server/pxf-api/src/main/java/org/greenplum/pxf/api/examples
directory of the repository you cloned in Step 1. Copy this code to your work area. For example:user@devsystem$ mkdir -p src/main/java/org/greenplum/pxf/example/demo user@devsystem$ cd src/main/java/org/greenplum/pxf/example/demo user@devsystem$ cp $PXFDEV_BASE/pxf/server/pxf-api/src/main/java/org/greenplum/pxf/api/examples/* .
The original PXF Demo connector resides in the
org.greenplum.pxf.api.examples
package. Your Demo connector resides in a package namedorg.greenplum.pxf.example.demo
. Update the package name in your local copy of the Demo connector source code. You can edit the files, run a script, etc. For example:user@devsystem$ find . -name '*.java' -exec sed -i '' s/"org.greenplum.pxf.api.examples"/"org.greenplum.pxf.example.demo"/g {} +
Initialize a
gradle
Java library project for your Demo connector. For example:user@devsystem$ cd $PXFDEV_BASE/demo_example user@devsystem$ gradle init --type java-library
This command generates build configuration files and scripts. Before building your Demo connector project, you must customize the
build.gradle
andsettings.gradle
files.Gradle uses the
settings.gradle
filerootProject.name
setting for the base name of the built Java library JAR file. The defaultrootProject.name
setting value is the base name of current working directory. Edit thesettings.gradle
file and supply a custom root project name for your Demo connector. For example:user@devsystem$ vi settings.gradle
rootProject.name = 'my-demo-connector'
Gradle uses the
build.gradle
file to identify the compile time dependencies for a project and other configuration. Your Demo connector depends on the PXF API JAR file (available locally) and thecommons-logging.jar
file (available from a maven repository). Edit yourbuild.gradle
file to supply these dependencies. For example:user@devsystem$ vi build.gradle
Search for the
repositories
block, and add the bolded text to identify the location of the PXF API JAR file. Recall that you copied this file to thelibs/
directory in Step 3. For example:repositories { // Use 'jcenter' for resolving your dependencies. // You can declare any Maven/Ivy/file repository here. jcenter() flatDir { dirs './libs' } }
Search for the
dependencies
block and add the bolded text to identify thepxf-api-<version>.jar
andcommon-logging-<version>.jar
file as dependencies of your gradle project. For example:dependencies { ... testCompile 'junit:junit:4.12' compile 'commons-logging:commons-logging:1.1.3' compile 'org.greenplum.pxf.api:pxf-api:4.0.0' }
Build your connector JAR file. For example:
user@devsystem$ ./gradlew build
gradle
builds your code and writes the builtmy-demo-connector.jar
JAR file to thebuild/libs
directory.Locate your connector JAR file, and note this location:
user@devsystem$ ls build/libs my-demo-connector.jar
You will deploy and test your Demo connector JAR file in an upcoming exercise.


Evonee is a Computer Science student at UC San Diego. She just recently completed a internship with RocketForce.net. At Rocket Force, she designed and developed websites for San Diego clients. Evonee plans to learn more about web development and computer graphics.