Quick start¶
About the simplest example for the module may be:
import sys
import re
import readability
r = readability.Readability()
with open(sys.argv[1], encoding='UTF-8') as fp:
a = r.read(re.split(r'\n(?:\s*\n)+', fp.read()))
print('Flesh-Kincaid reading ease: %4.1f' % r.FRES())
print('Flesh-Kincaid grade level: %4.1f' % r.FK_grade())
print('Gunning Fog index: %4.1f' % r.Fog_index())
print('SMOG index: %4.1f' % r.SMOG_index())
print('%d sentences; %d words; %d syllables' % r.stats())
(Add import io
and use io.open()
if using Python 2.)
The re.split()
is used to separate into chunks any text that is separated by one or more blank lines.
If this is not done, some text that spans paragraphs will be recognized as a single sentence.
Run against the Project Gutenberg text file for Sir Arthur Conan Doyle’s “A Study in Scarlet”, it produces this output:
Flesh-Kincaid reading ease: 74.4
Flesh-Kincaid grade level: 6.9
Gunning Fog index: 9.8
SMOG index: 9.7
2738 sentences; 44132 words; 60559 syllables
(I used the text from http://www.gutenberg.org/files/244/244-0.txt dated 2016-09-30 and removed the front and end matter, including the transcriber’s footnotes.)
Demo program¶
I have included a program rdblty.py
in the source distribution and GitHub repo that demonstrates all or most of the features of the Readability class and its associated modules.
Its usage (command line) is:
Usage: rdblty.py -h -s -e encoding -n --sentences -w --syllables format files...
Where
-h, --help This usage screen
-e encoding input file encoding (default UTF-8)
-S, --Spanish assume input files are Spanish
-w, --words dump words
-s, --sentences display sentences
-n show syllable counts (forces --sentences)
--syllables format format for syllable count (implies -n)
default is "%s{%d}"
Code files included¶
Module contents¶
Class¶
readability()¶
The readability
module defines a single class:
Readability([get_sentences] [, count_syllables] [, show_syllable_counts] [, dw] [, ds] [, language])
Use this to create a readability object to evaluate a single document. The module may also be used to tokenize text into words and sentences without evaluating readability.
- get_sentences is a Boolean (default is
True
). If True, theread()
method will return the sentences it has tokenized from the text it is given, in the form of a list of lists of tokens, each list of tokens representing a sentence.
- count_syllables is a Boolean (default is
True
). It must beTrue
to get readability statistics. It may beFalse
if, for example, you only need word and sentence counts. (But note that the word count will be differ depending on whether this is True or False; see below for more information.)
show_syllable_counts may be a boolean or a string; default is
False
. This is only relevant ifget_sentences
is True. Ifshow_syllable_counts
is True, then the sentences returned byread()
will have syllable counts embedded with each word, in the form “word{count}”, e.g. “This{1} etext{2} is{1} prepared{2} directly{3}…”Alternatively,
show_syllable_counts
may be a format string. If it is a format string and it contains “word” and “count”, the word and count will be formatted using:show_syllable_counts % dict(word=word, count=count)
This may be used if you want to display the count in front of the word, e.g.
"%(count)d|%(word)s"
.Otherwise the word and count will be formatted using:
show_syllable_counts % (word, count)
- dw may be a dictionary in which “words” are returned with a count of their occurrences; default is
None
. If provided, it should be empty initially.
- ds may be a dictionary in which “separators” are returned with a count of their occurrences; default is
None
. If provided, it should be empty initially.
- language may be “eng” for English or “spa” for Spanish; the default is English.
More about “words”¶
The module tokenizes “words” based on a regular expression. A word is, roughly, one of the following:
- a URL beginning http:// and including legal URL characters, but not ending with a period or comma. This is a very naive URL recognizer and will not always scan a URL perfectly.
- a word beginning with a letter and including letters, dots, ampersands, apostrophes, and hyphens, but not ending with an ampersand, apostrophe, or hyphen, nor can it contain adjacent dots, ampersands, apostrophes, or hyphens.
- a number beginning with a decimal digit and including digits, dots, commas, and hyphens, but ending with a digit.
- one or more periods
- one or more exclamation points
- one or more question marks.
The tokenizer will return periods, exclamation points, and question marks as “words” because it simplifies the work for the sentence boundary detector.
When the syllable counter is enabled (as it is by default), the module will only count as words those “words” that have a non-zero syllable count. When the syllable counter is disabled, the module counts all tokenized words.
Everything that’s not a “word” is a separator. The tokenizer can return the separators as a dictionary with counts. There will be a separator between every pair of words, so if two words are adjacent, the separator will be the empty string.
Methods¶
read()¶
Use read(string)
or read(list_of_string)
to pass text to the module.
You should invoke read()
only once per instance of the class.
If you have the entire text in a string, use the first form.
You may also pass a list of strings to the read()
method.
All text should be Unicode.
If you use a list, each string in the list should contain only whole sentences.
The module is not able to merge partial sentences between one string and the next.
stats()¶
stats()
returns a tuple (sentence_count, word_count, syllable_count)
.
Note
The following methods all return floating-point values, except for Inflesz_scale()
, which returns a string.
FRES()¶
FRES()
returns the Flesch Reading Ease Score.
The score is computed as:
206.835 - 84.6 * syllables / words - 1.015 * words / sentences
FK_grade()¶
FL_grade()
returns the Flesch-Kincaid Grade Level.
The score is computed as:
Flesch-Kincaid Grade Level: 0.39 * words / sentences + 11.8 * syllables / words - 15.59
Fog_index()¶
Fog_index()
returns the Gunning Fog index.
The index is computed as:
Gunning Fog = 0.4 * ((words / sentences) + 100 * (complex_words / words))where complex_words are words of more than two syllables.
SMOG_index()¶
SMOG_index()
returns the SMOG index.
The index is computed as:
SMOG =1.043 * sqrt(30 * complex_words / sentences) + 3.1291where complex_words are words of more than two syllables.
There should be a minimum of 30 sentences for the text sample.
If the number of sentences is less than 30, SMOG_index()
returns -1.0.
Huerta_ease()¶
Huerta_ease()
is for Spanish text only.
See Notes on Spanish functionality.
The score is computed as:
206.84 - 60 * (syllables / words) - 102 (sentences / words)
This is equivalent to the formula given in Huerta’s original 1959 paper:
Lect. = 206‘84 - 0‘60 P - 1‘02 F.Where P is syllables per 100 words and F is sentences per 100 words.
Huerta_corrected()¶
Huerta_corrected()
is for Spanish text only.
See Notes on Spanish functionality.
The score is computed as:
206.84 - 60 * (syllables / words) - 1.02 (words / sentences)
IFSZ_index()¶
IFSZ_index()
is for Spanish text only.
Its full name is “Formula de Perspicuidad (Clarity Formula) or Indice de Legibilidad de Flesch-Szigriszt (IFSZ, Flesch-Szigriszt Readability Index)”.
See Notes on Spanish functionality.
The score is computed as:
IFSZ = 206.835 - (62.3 x syllables / words) - words / sentences.
Inflesz_scale()¶
Inflesz_scale()
is for Spanish text only.
See Notes on Spanish functionality.
This method returns one of “UNDEFINED”, “very easy”, “quite easy”, “normal”, “somewhat difficult”, and “very difficult”, depending on the text’s IFSZ_index()
score.


|
Run ESModule in browser, even IE
Introducing `dimport`, an ESModule polyfill allowing you to run `import`, `export`, and `import()` in any browser – even IE!
twitter.com
Luke Edwards
|
|
Introducing Iodide: scientific computing in the web browser, utilizing webassembly.
Data Science right inside your browse, without a server-side component? It is possible!
twitter.com
Mozilla Hacks
|
|
Accelerated Mobile Pages can now display actual website URLs
Since launching three years ago, Accelerated Mobile Pages adoption has flourished across the web and on mobile. Google announced at AMP Conf 2019 today that it is addressing AMP’s biggest complaint by displaying actual website URLs.
9to5google.com
9to5google
|
|
Analyse your React Native bundle in 1 command
npx visualize-bundle allows you to inspect your React Native bundle in just one command and to diagnose big modules.
github.com
Jonny Burger
|
|
Learn Web Development with AMP
These three free courses are in use in schools and training programs around the world. Now you can take them here, online, on our site. Suitable for beginners and experienced web developers alike, they will take you from zero to AMP!
amp.dev
AMP Team
|
|
Implementing Performance Budgets
40% of brands who optimize for speed, regress in 6 months (Source: Webpagetest.org). In our first #AskChrome live session, you'll learn about how to implement performance budgets to avoid regression.
www.youtube.com
Chrome Team
|


LITA Linked Data Webinar Series
Instructor: Jeremy Nelson
Metadata and Systems Librarian
Tutt Library, Colorado College
Jeremy Nelson is the Metadata and Systems Librarian at Colorado College, a small private liberal-arts college located in Colorado Springs, Colorado. His previous library professional jobs included Western State University of Colorado and the University of Utah. Prior to earning his Master of Science in Library and Information Science from the University of Illinois at Urbana-Champaign, Nelson worked as a programmer and project manager at a number of different software companies in the financial services and educational sectors.


NegotiateHER
Home Page
AI Agent
(current)
Result
×
Speech Recognition SDK not found.
Please execute
npm run bundle
and reload.


Before you use many of the Google Earth Enterprise Server configuration tools, you must stop the Google Earth Enterprise Server and then start it after you change the configuration. To stop/start the Google Earth Enterprise Server, enter:
/etc/init.d/geserver [stop | start | restart]
In general, no additional configuration is required after you install the Google Earth Enterprise Server. However, there are a number of ways in which you can customize your Google Earth Enterprise Server configuration, if desired. This chapter provides information about those configuration options. (See the Command Reference chapter for a complete list of commands available to system administrators.)
The geserveradmin
command handles many of the Google Earth Enterprise Server configuration changes you might want to make. All of the options and uses for geserveradmin
are described in the geserveradmin section of the Command Reference doc.
Because Google Earth Enterprise Server is critical to many operations you perform with Google Earth Enterprise Fusion, verify that it is running.
http://www.example.com
).
If Google Earth Enterprise Server is running, the browser displays the Google logo.
If Google Earth Enterprise Server is not running, the browser displays an error message informing you that the page cannot be found. On the command line, enter:
/etc/init.d/geserver start
If you again reach an error page, make sure that you have network access to the machine on which the server is installed and that the DNS entry for that machine is up-to-date.
Before publishing to virtual servers other than the default virtual servers, please familiarize yourself with the Apache Virtual Host documentation (http://httpd.apache.org/docs/2.2/vhosts/).
Caution: Publishing to virtual servers other than the default server is supported only in version 4.2 or later of Google Earth EC. If you are using version 4.0 or earlier, only databases that you publish to the default server can be accessed by Google Earth EC.
To define a virtual server, use the geserveradmin
command (see geserveradmin for more details):
geserveradmin --addvs name --vstype type --vsurl url
Where:
ge
(for 3D streaming) or map
(for maps)/somename_ge
; refer to geserveradmin in the Command Reference chapter for more information on the required format.After defining a virtual server, create a configuration file that specifies required information for that particular virtual server. To do so:
cd /opt/google/gehttpd/conf.d/examples
/opt/google/gehttpd/conf.d/virtual_servers
and rename it. For example:
cp /opt/google/share/gehttpd/examples/port_based_ge_vs_example.vhost
/opt/google/gehttpd/conf.d/virtual_servers/private_ge.vhost
When choosing a configuration file to copy, use a file that:
_ge_
if you are creating a Google Earth Enterprise Fusion virtual server._map_
if you are creating a Google Maps virtual server.location_based
if you are creating a location-based virtual server.name_based
if you are creating a name/domain-based virtual server.port_based
if you are creating a port-based virtual server.You must maintain the .location
or .vhost
extension on the file name.
In a location-based configuration file:
<LOCATION>
to the vsurl
value specified in the geserveradmin
command you used to register the virtual server.
Note: For a Google Maps virtual server, you must make this change in five places.
<VS_NAME>
to the addvs
name specified in the geserveradmin
command you used to register the virtual server.In a name-based configuration file:
<HOST.DOMAIN>
to the desired server name.<VS_NAME>
to the addvs
name specified in the geserveradmin
command you used to register the virtual server.In a port-based configuration file:
<IP_ADDRESS>
to the IP address of the host.<PORT>
to the number of the port you want to use.<VS_NAME>
to the addvs
name specified in the geserveradmin
command you used to register the virtual server.Note: You can optionally create combinations of name-based or port-based and location-based virtual servers. If you do, you must create an Apache configuration file with the .vhost
extension that references multiple virtual servers. Make sure you create the corresponding virtual servers using the geserveradmin --addvs
command. (See geserveradmin for more information.)
Next, you must configure a server association for the new virtual server.
The Google Earth Enterprise Server consists of a stream server and a search server. You can publish a Google Earth Enterprise Fusion database to stream and search virtual servers running on your local workstation or on a remote server. Associated stream and search virtual servers can be located on different physical servers or on the same server.
The Server Associations Manager allows you to specify server associations in preparation for publishing your databases. You can specify any number of additional server associations in the Server Associations Manager. Then you can select the desired server association in the Publish Database dialog. (Refer to Publishing a Database in the Google Earth Enterprise Fusion Reference Guide for more information.)
Caution: If you're working with multiple Google Earth Enterprise Fusion users on multiple workstations, it is important to remember that all managers on the Tools menu can be accessed by all users at the same time. If multiple users are working with the same manager at the same time, when one user closes the manager, that user’s changes overwrite all previous data for that manager. So if you are working in a multi-user environment, be sure to coordinate with the other users to be sure that only one user has this manager open at a time.
The Server Associations Manager window appears with two default server associations listed--one for publishing to Google Earth and the other for publishing to Google Maps. The default server associations assume that you have Google Earth Enterprise Server installed on the same workstation as Google Earth Enterprise Fusion.
http://www.example.com:9090
). Repeat the steps above for each server association you want to add. The server associations appear on this list in the order in which you added them. They also appear on the Server Associations drop-down list in the Publish Database dialog in the same order. The first server association listed here is the default in the Publish Database dialog.
If you want to reorder the server associations on the list (particularly if you publish to a certain server most of the time and want it to be the default in the Publish Database dialog), select the server association that you want to move, and click the up or down arrows to change that server association's position in the list.
You can configure your Google Earth Enterprise Server to use HTTPS connections by editing the virtual server’s configuration file. Each time you restart Google Earth Enterprise Server, publish a database ,or start Apache, Apache reads this file.
gehttpd.conf
) for the virtual server you want to make secure.
The configuration file is stored in /opt/google/gehttpd/conf.d/virtual servers
. (See Configuring Virtual Servers for details.) The contents of the configuration file look like:
<LocationMatch "/private_ge/*">
Include conf.d/virtual_servers/runtime/private_ge_runtime
</LocationMatch>
LocationMatch
directive exactly as they appear here:<LocationMatch "/private_ge/*">
Include conf.d/virtual_servers/runtime/private_ge_runtime
SSLRequireSSL
SSLVerifyClient none
</LocationMatch>
This procedure gets you to a point where you have “bare bones” security on your server. It requires that users use the HTTPS protocol instead of HTTP when they specify a location. However, if you want to add more security, you can do so by following the instructions provided in the Apache 2.2 documentation at http://httpd.apache.org.
When you install the Google Earth Enterprise Server, you specify a location for your publish root, the directory in which all of your published databases are stored.
/etc/init.d/geserver stop
geconfigurepublishroot
When prompted, enter the path where you want to create the publish root. For example, if you have designated a separate volume for publishing called /gepub
, enter /gepub/published_dbs.
/etc/init.d/geserver start
When you create a new publish root, it is automatically selected. The next time you publish a database, Google Earth Enterprise Fusion stores it in the selected publish root.
If you have multiple publish roots, you can go back and forth among them, using different publish roots for different purposes.
Note: If you have multiple publish roots, be sure to select the corresponding asset root for the intended publish root before you publish. Otherwise, it could end up with an incompletely published database. (See geselectpublishroot in the Command Reference chapter for more information.)
/etc/init.d/geserver stop
geselectpublishroot path
where path is the full path to the publish root, such as /gepub/published_dbs
.
/etc/init.d/geserver start
Authentication is the process of verifying the identity of a user, a system, or a process. Controlled access refers to any content or process that requires authentication. The following sections describe how to configure:
By default, Google Earth Enterprise Server does not require authentication for publishing. However, you can configure your server to control access for publishing using standard Apache authentication methods. This section is primarily for system administrators who are unfamiliar with configuring Apache authentication.
First, decide which authentication method you want to use.
mod_auth_digest
Apache module)
mod_auth_basic
Apache module)
Both methods are essentially the same, except that mod_auth_digest
encrypts the users’ password, and mod_auth_basic
does not. However, mod_auth_digest
is not supported by all browsers. See http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html and http://httpd.apache.org/docs/2.2/mod/mod_auth_basic.html for complete details on these two authentication methods.
Google strongly encourages you to use HTTP Digest authentication (mod_auth_digest
) instead of HTTP Basic authentication. The following procedure describes configuring publishing authentication using HTTP Digest.
/opt/google/gehttpd/bin/htdigest -c path_to_pwd_file Publisher user_name
The first part is the path to the Apache utility you use to create the password file, htdigest
. The -c
option indicates that you are creating a new file. The path_to_pwd_file is the location where you want to store the password file and the name of that file; it can be any name and location you choose. Publisher
is the realm, and you must enter it exactly as it appears above. The user_name is the first user name you want to add to the password file.
When you press Enter, the utility prompts you to enter a password for the specified user.
The htdigest
utility creates the password file, which contains only that one user name, the realm, and the encrypted password. For example, if you view the contents of the password file, it might look like this:
jsmith:Publisher:f9d3c803aeb515f35568b37ec2d65399
/opt/google/gehttpd/bin/htdigest path_to_pwd_file Publisher user_name
Use the same path_to_pwd_file as you used for the first user. Do not include the -c
option, since you are not creating a new file this time.
publisher_digest_auth.conf
file from /opt/google/gehttpd/conf.d/examples
to /opt/google/gehttpd/conf.d
.
/opt/google/gehttpd/conf.d/publisher_digest_auth.conf
) in an editor and:
<Location>
directive(s) for stream publisher and/or search publisher by removing the #
at the beginning of each line. (If you want to configure authentication for one type of server only, uncomment only its directive. If you want to configure both the search server and the stream server, uncomment both directives.)
<<PATH_TO_USER_FILE>>
to the password file path (the value of path_to_pwd_file in step 1).
publisher_digest_auth.conf
file.
/etc/init.d/geserver restart
When a server is configured for publishing authentication, Google Earth Enterprise Fusion users who try to publish to that server must enter their user name and password. Refer to Publishing a Database in the Google Earth Enterprise Fusion Reference Guide for more information.
Configuring client authentication is very similar to configuring publishing authentication, except that client authentication is specific to each virtual server, whereas publishing authentication is not.
/opt/google/gehttpd/bin/htdigest -c path_to_pwd_file Client user_name
The first part is the path to the Apache utility you use to create the password file, htdigest
. The -c
option indicates that you are creating a new file. The path_to_pwd_file is the location where you want to store the password file and the name of that file; it can be any name and location you choose. Client
is the realm. You can use any realm you want; however, you must use the same realm in step 4. The user_name is the first user name you want to add to the password file.
Note: Set the umask to 0022
before
using htdigest
to create the htdigest_password_file
or change permissions
to rw-r--r-- (644)
after the htdigest_password_file
is
created. Check the permissions for the htdigest_password_file
and
if the permissions are set to rw-r-----
, change the group ownership to
gegroup
.
Press Enter. The utility prompts you to enter a password for the specified user. Enter the password, and retype it when prompted.
The htdigest
utility creates the password file, which contains only that one user name, the realm, and the encrypted password. For example, if you view the contents of the password file, it might look like this:
jsmith:Client:f9d3c803aeb515f35568b37ec2d65399
/opt/google/gehttpd/bin/htdigest path_to_pwd_file Client user_name
Use the same path_to_pwd_file as you used for the first user. Do not include the -c
option, since you are not creating a new file this time.
/opt/google/gehttpd/conf.d/virtual_servers/
config_file file (where config_file is the configuration file for the virtual server you want to protect) in an editor, and add the following lines at the beginning of the <Location>
directive:AuthType Digest
AuthName "Client"
AuthDigestProvider file
AuthUserFile path_to_pwd_file
Require valid-user
Where Client
is the exact name of the realm and path_to_pwd_file is the same path you used in the htdigest
command in step 1.
If this is a _ge_ virtual server, add:
BrowserMatch "GoogleEarth" AuthDigestEnableQueryStringHack=On
If this is a _map_ virtual server, add:
BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
For more information about AuthDigestEnableQueryStringHack
, refer to the Apache documentation at http://httpd.apache.org/docs/2.2/mod/mod_auth_digest.html#msie.
The final <Location>
directive looks like:
<LocationMatch /default_ge/*>
AuthType Digest
AuthName "Client"
AuthDigestProvider file
AuthUserFile path_to_pwd_file
Require valid-user
Include conf.d/virtual_servers/runtime/default_ge_runtime
BrowserMatch "GoogleEarth" AuthDigestEnableQueryStringHack=On
</LocationMatch>
/etc/init.d/geserver restart
If you use LDAP for user authentication on your network, you can configure LDAP authentication for publishing with Google Earth Enterprise Fusion. Since Basic authentication is used for password challenge, Google suggests that you publish through an SSH tunnel. (See Configuring Secure Remote Publishing (Using an SSH Tunnel) for more information about configuring an SSH tunnel.)
publisher_ldap_auth.conf
file from /opt/google/gehttpd/conf.d/examples
to /opt/google/gehttpd/conf.d
.
/opt/google/gehttpd/conf.d/publisher_ldap_auth.conf
in an editor.
<Location /StreamPublisher/>
AuthType Basic
AuthName "Publisher"
AuthBasicProvider ldap
AuthzLDAPAuthoritative off
AuthLDAPURL "<<LDAP_SERVER_URL_and_LDAP_SEARCH_PARAMETERS>>"
Require valid-user
</Location>
<<LDAP_SERVER_URL_and_LDAP_SEARCH_PARAMETERS>>
to the actual path to your LDAP server and any parameters you want to set, for example:ldap://ent-test-ldap.mycompany.com/dc=mycompany,dc=com?uid?sub?(objectClass=*)
<Location /SearchPublisher/>
AuthType Basic
AuthName "Publisher"
AuthBasicProvider ldap
AuthzLDAPAuthoritative off
AuthLDAPURL "<<LDAP_SERVER_URL_and_LDAP_SEARCH_PARAMETERS>>"
Require valid-user
</Location>
<<LDAP_SERVER_URL_and_LDAP_SEARCH_PARAMETERS>>
to the actual path to your LDAP server and any parameters you want to set.
If you use LDAP for user authentication on your network, you can configure LDAP authentication for any virtual servers you configure. As with LDAP authentication for publishing, since the AuthDigestProvider directive does not support LDAP and AuthBasicProvider does not encrypt passwords, please contact Google technical support for help configuring secure LDAP authentication for virtual servers.
If you publish a database that you want to keep private and allow access only to certain users, configuring client authentication provides that security with regard to the stream server. However, if you host a searchable private database on the same server with a publicly accessible database, users who are able to log in to the public database can, theoretically, search the private database on that server. Such a user would need to be very knowledgeable about Google Earth Enterprise Fusion and would need to know the exact URL of the private database, so the likelihood of this breach is small; however, it is possible.
Therefore, to ensure that a database is completely secure (that is, no unauthorized users can view or search the data), you must publish that database on a separate search server host that requires authentication and allows access to only approved users.
Note: If you are short of server space, you can publish the private database to a shared stream server (that is, a mix of databases that do and do not require authentication) and just publish the private database to a search server on a separate (authentication only) host.
When Google Earth Enterprise Fusion publishes a database, it does not encrypt the data. If you want to encrypt the data during the publishing process to a remote server (or even on separate remote stream and search servers), you can use an SSH tunnel.
ssh -L port_num:host_name:80 host_name
For example:
ssh -L 8010:remoteServer:80 remoteServer
Note: You can use any port that is available, but Google recommends a high number.
ssh
command, for example:Note: If the remote server requires authentication, it prompts you to log in when you click Query.
exit
in the terminal window.
The next time you want to publish securely to that same remote server, you can skip step 2.
ssh -L port_num:host_name:80 host_name
For example:
ssh -L 8010:remoteServer:80 remoteServer
Note: You can use any port that is available, but Google recommends a high number.
ssh -L 8020:remoteServer:80 remoteServer
exit
in the terminal windows.
The next time you want to publish securely to that same remote server association, you can skip step 3.
If you want to publish databases on a server that does not have a network connection to your Google Earth Enterprise Fusion workstations, you can configure a server with the disconnected server add-on.
New in Google Earth Enterprise 4.0 is the ability to combine disconnected publishing and connected publishing together. Prior to 4.0, only one type was supported for a database. With this change, for example, a large database can be copied to portable media and loaded onto the server using disconnected publish, saving the time and bandwidth required to send terabytes of data over the network. Later, deltas for the same databases can be sent over the wire.
Note: Disconnected production servers require X11 libraries, including Mesa. Google Earth Enterprise Server does not require an X server to be running or installed, however. Only the libraries are required.
To create the disconnected database, use gedisconnectedsend
from the command line. In the example below, the --report_size_only
flag is turned on; the size of the database should be compared to the free space on your removeable media.
gedisconnectedsend --report_size_only --sendpath \ /gevol/assets/Databases/igain.kdatabase/gedb.kda/ver001/gedb rm -rf /portable_media/new_dir mkdir -p /portable_media/new_dir gedisconnectedsend --output /portable_media/new_dir \ --sendpath /gevol/assets/Databases/igain.kdatabase/gedb.kda/ver001/gedb
Use --havepath
or --havepathfile
to create a delta database.
When publishing from machine_one
to machine_two
, for example:
On machine_two
:
geserveradmin --fusion_host machine_one --listdbs > /portable_media/dblist
On machine_one
:
gedisconnectedsend --output /portable_media/new_dir \ --havepathfile /portable_media/dblist \ --sendpath /gevol/assets/Databases/igain.kdatabase/gedb.kda/ver001/gedb
Connect the portable media to the Server host and mount the drive.  They should be entered on one line when completing your commands.
The steps to delete DBs at end of life, for disconnected servers, is same as what was described in over the wire publishing section.


The Backup and Restore functions built into the Appointment Booking component are primarily intended for use when upgrading from one version to another. All component data is saved to backup tables in the database. Old backup tables are removed before new ones are created.
The sequence of actions to upgrade from one version to another is this:
Backup data -> Uninstall RB component -> Install new version -> Restore data
With database tables you can merge old data into new table structures. This cannot be done with the language file because it is a plain text file. If you are doing a backup/restore because you are moving from one ABPro version to the next, the new version will have a new language file with, possibly, new language keys defined. If you choose to backup/restore the language file it will overwrite the new file with your old one. That will keep all you old modifications but it will also remove any new language keys. You will need to manually re-apply these keys.
Help: Opens this help screen.
Backup Now! : This will create backup database tables and copy your current settings to them. If the backup tables already exist, they will be overwritten. If a table has no data it will not be copied. This is to prevent accidentally backing up empty tables over your real backup.
Restore Now! : This will look to see if there are backup tables and if there are, it will replace the contents of the production tables with the contents of the back tables. If a backup table has no data in it it will not be copied. This is to prevent accidentally restoring up empty tables over your production tables.
Import from version 1.5.2! : This will look to see if there are tables from the free version of the Resource Booking component and if there are, it will import the settings from the older version.
Include Language File in Backup : Make a backup copy of your English language file.
Include Language File in Restore : Restore a previously created English language file backup.


Goal: Creating a Github Account to host your own personal website
Let’s do some thinking and see what this lesson is about.
I think part of it is around figuring out how we kind of look at problems and tackle things like who we are and what we are supposed to do.
First things first, we need to figure out how to edit the text on our website. We also want to start teaching people how to use markdown appropriately.
This is focusing on the syntax of things, the way that we edit it and the principles behind markdown and what it is.
Right now, we’re just trying to get students aquainted with curriculum. I’m kind of mirroring the lessons through Josh’s experience learning how to build a website and applying for a position at Oculus Rift.
I wouldn’t say that we’re trying to pursue anything that isn’t impossible. Like we’ve 100% done this. However, I guess the importance here is learning how to level set with others what the importance of building things out really is.
We’re also trying to build principles of exploration here. Students should feel empowered with the technology to feel capable and ready to accomplish anything that they want to. I also feel that it might be difficult to really internalize what it means to approach things with the right mental state. People aren’t easy to please. They all have varying goals and honestly, I don’t know what I can do to level set with them and what they need to do and what they don’t need to do.
Principles here.dfs this is not work
We’re teaching students how to use markdown.
Then we’re teaching them how to kind of interpret what a commit is. How we plan to update information and teach them the practice of pushing information to the cloud.
After that, we’re looking at how students are supposed to look at other things like
-
Access Github.com and select Sign In
-
Sign in with your own credentials or the StreetCode credentials that should be provided for.
-
Select the green New button on the top-left create a new repository.
-
Enter your name as the repository name
-
Select Create Repository
-
Select the Settings tab
-
Scroll down to the GitHub Pages section and select the Choose a Theme button
-
Select a theme that you’d like for your personal website.
-
Select the Select Theme button
-
Select the Commit Changes button
-
Select the Settings tab and scroll to the GitHub Pages section
-
Select the Streetcode URL to visit your new website!


AMWG Diagnostics Package tmp_2c78d90 |
Plots Created Wed Jul 10 05:55:43 CST 2019 |
|---|
|
Set
Description 1 Tables of ANN, DJF, JJA, global and regional means and RMSE. 2 Line plots of annual implied northward transports. 3 Line plots of DJF, JJA and ANN zonal means 4 Vertical contour plots of DJF, JJA and ANN zonal means 4a Vertical (XZ) contour plots of DJF, JJA and ANN meridional means 5 Horizontal contour plots of DJF, JJA and ANN means 6 Horizontal vector plots of DJF, JJA and ANN means 7 Polar contour and vector plots of DJF, JJA and ANN means 8 Annual cycle contour plots of zonal means 9 Horizontal contour plots of DJF-JJA differences 10 Annual cycle line plots of global means 11 Pacific annual cycle, Scatter plot plots 12 Vertical profile plots from 17 selected stations 13 ISCCP cloud simulator plots 14 Taylor Diagram plots 15 Annual Cycle at Select Stations plots              TABLES                                   METRICS | Click on Plot Type |
|---|


This page is a submission for homework 1. The page is protected with a simple htaccess file, contains links to other homework assignments, and contains some interesting pictures. Thank you, Larry Rodrigues. |
| Assignment | Link to Page |
|---|---|
| HW2 | Homework 2: Computer Science Information Page |
| HW3 | Homework 3: Updated Survey Page |
Yosemite Valley Tunnel View July 2017. |
A view of the sunset over San Francisco bay from the Bay Bridge. July 2017 |
A view of the sunset over the Pamlico sound. Salvo North Carolina 2015. |
Darth Vader attempting to befriend Godzilla with cheese. |


Round Schemes:
Round 1: This round will check the participants’ problem solving skills and also tap the players’ logical reasoning abilities. This test will consist of a crossword puzzle based on popular taglines and other advertisement related questions. This will be followed by a jumbled puzzle. Out of the teams who have registered, only 10 will be allowed to go for the next round. This round will be completed within 30 mins.
Round 2: This round is divided into 2 parts. The first part is a technical quiz consisting of MCQ’s and other short questions based on Boolean reduction, digital electronics and network analysis. After this the team will be provided with a comprehensive passage followed by 10 questions. The passage will consists of several encoded words and phrases that have to be deciphered by the participants with the help of the key provided. The result of this round will be used to shortlist 5 teams for the final round. Time limit for this round will be 1 hour.
Round 3: The teams which reach this round will get the opportunity to take part in an auction to buy various virtual electronic goods kept on sale. The amount of virtual money given to them will be based on their performance in the previous round. The goods they purchase will have to be used to create an electronic product or model which they have to successfully market and advertise. Bidding will take 30 mins followed by 45 mins for making a model and preparing a presentation. Each team will get 5 mins to present their model and advertisement to the judges
4
6th March 2017
Round 1- 10:00 to 11:00 AM
Round 2- 12:00 to 1:00 PM
Round 3- 3:00 to 5:00 PM
Rs. 60/- per team
Yash Patel<PHONE_NUMBER>)
Sneha Thomas<PHONE_NUMBER>)


bosporan
tribe
peoples
royal
thracians
ruled
client
scythian
st
iranian
inhabited
ce.
ce.
b.c.
theres
theres
theres
vernadsky
urlhttp//www.blackseanews.net/read/
karlavske
{{convert?kmmi.
shchaslyvtseve
coast.
warbritish
existence.
kazantip
urban-type
role
right
samuel


|
Dynamic Array
|
#include "cdynarray.h"
#include "common_utils.h"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
Classes | |
| struct | _DYNARRAY_METADATA |
| Stores tracking information required to manage the array. More... | |
Typedefs | |
| typedef struct _DYNARRAY_METADATA | DYNARRAY_METADATA |
| Stores tracking information required to manage the array. More... | |
Functions | |
| DYNARRAY_HANDLE | init_array (size_t num_elements, size_t element_size) |
| Initialize the dynamic array with the number of elements and size per element. More... | |
| void | free_array (DYNARRAY_HANDLE handle) |
| Frees the dynamic array identified by the specified handle. More... | |
| bool | set_element (DYNARRAY_HANDLE handle, size_t index, void *p_data) |
| Stores the specified data element at the location indicated by the index. More... | |
| bool | get_element (DYNARRAY_HANDLE handle, size_t index, void *p_data) |
| Gets the element at the specified index. More... | |
| void | copy_elements (void *p_source_data, size_t source_index, void *p_dest_data, size_t dest_index, size_t element_size, size_t num_elements) |
| Copy elements from the source array to the destination array. More... | |
| static bool | resize_and_insert (DYNARRAY_HANDLE handle, size_t index, void *p_data) |
| Resizes the array and inserts the specified data at the index specified. More... | |
| bool | insert_element (DYNARRAY_HANDLE handle, size_t index, void *p_data) |
| Insert an element into the array specified by the handle and index. More... | |
| bool | delete_element (DYNARRAY_HANDLE handle, size_t index) |
| Delete the element specified by the handle and index. More... | |
| size_t | array_capacity (DYNARRAY_HANDLE handle) |
| Returns the capacity of the array identified by the specified handle. More... | |
| size_t | array_size (DYNARRAY_HANDLE handle) |
| Returns the logical size of the dynamic array identified by the specified handle. More... | |
| typedef struct _DYNARRAY_METADATA DYNARRAY_METADATA |
Stores tracking information required to manage the array.
Each instance of the dynamic array will have its own instance of this structure.
| size_t array_capacity | ( | DYNARRAY_HANDLE | handle | ) |
Returns the capacity of the array identified by the specified handle.
| [in] | handle | - The handle of the dynamic array |
| size_t array_size | ( | DYNARRAY_HANDLE | handle | ) |
Returns the logical size of the dynamic array identified by the specified handle.
| [in] | handle | - The handle of the dynamic array |
| void copy_elements | ( | void * | p_source_data, |
| size_t | source_index, | ||
| void * | p_dest_data, | ||
| size_t | dest_index, | ||
| size_t | element_size, | ||
| size_t | num_elements | ||
| ) |
Copy elements from the source array to the destination array.
Copies elements from the specified index on the source array to the destination array at the specified index. The destination array needs to be able to hold the specified number of data elements of the specified size.
| [in] | p_source_data | - Pointer to the source array. |
| [in] | source_index | - The starting index of the source array. The num_elements parameter specifies the number of elements to be copied. |
| [in,out] | p_dest_data | - Pointer to the destination array. |
| [in] | dest_index | - The starting index of the destination array. The num_elements parameter specifies the number of elements to be copied. The destination array needs to be able to hold the number of elements. |
| [in] | element_size | - Specifies the size of each data item in the array. |
| [in] | num_elements | - Specifies the number of elements to be copied. |
| bool delete_element | ( | DYNARRAY_HANDLE | handle, |
| size_t | index | ||
| ) |
Delete the element specified by the handle and index.
| [in] | handle | - The handle of the dynamic array to be freed |
| [in] | index | - The position of the data element to be removed |
| void free_array | ( | DYNARRAY_HANDLE | handle | ) |
Frees the dynamic array identified by the specified handle.
| handle | - The handle of the dynamic array to be freed |
| bool get_element | ( | DYNARRAY_HANDLE | handle, |
| size_t | index, | ||
| void * | p_data | ||
| ) |
Gets the element at the specified index.
This function returns the element at the specified index from the dynamic array identified by the specified handle.
| [in] | handle | - The handle of the dynamic array |
| [in] | index | - position of the array element to be returned |
| [in,out] | p_data | - pointer to data element containing data to be returned |
| DYNARRAY_HANDLE init_array | ( | size_t | num_elements, |
| size_t | element_size | ||
| ) |
Initialize the dynamic array with the number of elements and size per element.
| num_elements | - The number of elements to store in the array. |
| element_size | - The size of each element in the array. |
| bool insert_element | ( | DYNARRAY_HANDLE | handle, |
| size_t | index, | ||
| void * | p_data | ||
| ) |
Insert an element into the array specified by the handle and index.
If the backing array has reached its capacity, the array will be resized by twice the current capacity.
| [in] | handle | - The handle of the dynamic array to be freed |
| [in] | index | - The position to store the data element. |
| [in] | p_data | - The data to be stored. |
|
static |
Resizes the array and inserts the specified data at the index specified.
This function is called when the backing array has reached its capacity and needs to be resized to accommodate the new element to be added.
| bool set_element | ( | DYNARRAY_HANDLE | handle, |
| size_t | index, | ||
| void * | p_data | ||
| ) |
Stores the specified data element at the location indicated by the index.
The index needs to be within the capacity. Any previously stored data at the location is replaced by the new content.
| [in] | handle | - The handle of the dynamic array |
| [in] | index | - The position to store the data element. |
| [in] | p_data | - The data to be stored. |


calibre-server
A server application that can be used to distribute e-books over a network.
Note: e-books must already be imported into the library using the GUI or the `calibredb` CLI.
More information: home page
- Start a server to distribute e-books. Access at http://localhost:8080:
calibre-server
- Start server on different port. Access at http://localhost:port:
calibre-server --port port
- Password protect the server:
calibre-server --username username --password password


When receiving a garbled HTTP request, varnishd would sometimes crash. This has been fixed.
There was an off-by-one error in the ACL compilation. Now fixed.
A typo in the spec file made the .rpm file names wrong.


[Animations] [Stills] [Differences] [Manuals]
| temperature slice | vector temperature slice | temperature iso-surface |
|---|---|---|
| 3d smoke/hrrpuv | temperature boundary | particles |
| 3d smoke/hrrpuv | temperature slice |
|---|
| hill_structure | BT10m_2x2km_LS |
|---|---|
| levelset1 | levelset2 |
| tree_test2 | wind_test1 |


--- layout: page title: "Register" description: "No waiting lines!" header-img: "/img/bg-shoes-with-ball-alt.jpg" ---
********Registration for league play is not currently available********
Team registration TBD.


| Name |
| Title |
|
| *First or Given Name |
|
| Middle Name or Initial |
|
| *Last or Family Name |
|
| Name as it may appear on other required documents |
|
| Gender |
| *Gender |
|
| Date of Birth |
| *Date of Birth |
-- |
| Mailing Address |
| |
|
Your admission notification will be sent to this address,
so please update this address if you move; also, please avoid using P.O. boxes if possible.
|
|
|
| *Address Line 1 |
|
| Address Line 2 |
|
| *City |
|
| (Only for applicants from the United States and Canada) State |
|
| State / Province / Region |
|
| Zip / Postal Code |
|
| *Country |
|
| Phone Numbers |
|
| Email Addresses |
| *Email 1 (Up to 30 characters) |
|
| Email 2 (Up to 30 characters) |
|
| Citizenship |
| *Country of Citizenship |
|
Non-U.S. Citizens: Residence / Visa Status |
|
|
The information requested below is optional. Please respond to questions 1 and 2. The questions are asked because Columbia is subject to certain governmental record-keeping and reporting requirements. |
| Question 1: Ethnicity |
| Are you Hispanic or Latino? | Yes, Hispanic or Latino -- A person of Cuban, Mexican, Puerto Rican, South or Central America, or other Spanish culture or origin, regardless of race. No, not Hispanic or Latino. |
| Question 2: Race |
What is your race? (Select one or more of the following five categories.) |
|
|
|
|
|
|
* denotes required field |


--- title: NRDy Laundry Episode 2 short: We're back for the ever elusive episode 2! category: nerd author: Tim comments: true published: true image: /images/nrdy_laundry_ep2.jpg ---
Tim and I air out our NRDy Laundry about some of the games and anime that we've been into so far this summer.
Thanks for watching! If you enjoyed, please like and subscribe for more NRDPLS!
Stay Nerdy, my friends :)


American_Horror_Story
American Horror Story is an horror television anthology series. Each season is conceived as a self-contained miniseries, following a disparate set of characters and settings, and a storyline with its own beginning, middle, and end. While some actors appear for more than one year, they play completely different roles in each season.


|
DashingPlatforms
1.0
|
Public Member Functions | |
| virtual | ~PgConnection () |
| void | clean () |
| int | checkConnectionHealth () |
| int | executeCommand (string &command) |
| int | executeCommand (const char *command) |
| int | executeCommandWithParams (const char *command, int numberParams, const char *const *paramValues, const int *paramLengths, const int *isBinary) |
| int | beginTransaction () |
| int | rollbackTransaction () |
| int | commitTransaction () |
| int | initializePreparedCommand (const char *statementName, const char *sqlCommand, int numberParams, const DataManagerFieldType *paramTypeArray) |
| int | executePreparedCommand (const char *statementName, int numberParams, const char *const *paramValues, const int *paramLengths, const int *isBinary) |
| int | closeCommandResult () |
| int | getColumnCount () |
| string | getColumnName (int columnIndex) |
| int | getColumnIndex (const char *columnName) |
| int | getRowCount () |
| const char * | getStringValueAt (int rowIndex, int columnIndex) |
| short | getShortValueAt (int rowIndex, int columnIndex) |
| int | getIntValueAt (int rowIndex, int columnIndex) |
| bool | getBooleanValueAt (int rowIndex, int columnIndex) |
| const char * | getTimestampValueAt (int rowIndex, int columnIndex) |
| bool | isValueNULL (int rowIndex, int columnIndex) |
| int | getValueLength (int rowIndex, int columnIndex) |
| void | shutdown () |
| string | toString () |
| Public Member Functions inherited from DbConnection | |
| virtual | ~DbConnection () |
| void | addUserDefinedIdentifier (string &identifier) |
| string & | getUserDefinedIdentifier () |
| void | clearUserDefinedIdentifier () |
| string | toString () |
| Public Member Functions inherited from OPMBase | |
| OPMBase () | |
| virtual | ~OPMBase () |
| bool | isNextNull () |
| bool | isPrevNull () |
| OPMBase * | getNext () |
| void | setNext (OPMBase *newObject) |
| OPMBase * | getPrev () |
| void | setPrev (OPMBase *newObject) |
| int | getPoolID () |
| void | setPoolID (int poolID) |
| const char * | getObjectTypeStr () |
| void | setObjectTypeStr (const char *objectType) |
| string | toString () |
| Public Member Functions inherited from ObjectBase | |
| ObjectBase () | |
| virtual | ~ObjectBase () |
| void | setPoolable (bool isPoolable) |
Static Public Member Functions | |
| static OPMBase * | initialize (int initializer) |
| Static Public Member Functions inherited from OPMBase | |
| static OPMBase * | initialize (int initializer) |
Protected Member Functions | |
| PgConnection () | |
| Protected Member Functions inherited from DbConnection | |
| DbConnection () | |
| Protected Member Functions inherited from ObjectBase | |
| bool | isPoolable () |
Additional Inherited Members | |
| Protected Attributes inherited from OPMBase | |
| OPMBase * | next_ |
| OPMBase * | prev_ |
| const char * | objectType_ |
| int | poolID_ |
|
virtual |
Virtual Destructor
|
protected |
Constructor
Referenced by initialize().
|
virtual |
Begin a transaction on this connection. Autocommit is ENABLED for all executed commands UNLESS beginTransaction has been called–that is, beginTransaction disabled autocommit until either rollbackTransaction or commitTransaction is called. Postgresql optionally supports the passing of the following isolation levels when the transaction is begun. Support for these can be added to this interface in the future: ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED } READ WRITE | READ ONLY
Implements DbConnection.
References executeCommand().
|
virtual |
Check the health of the database connection.
Implements DbConnection.
Referenced by clean().
|
virtual |
Inherited from OPMBase. Pure Virtual method will be called before releasing the object back into the OPM pool.
Implements OPMBase.
References checkConnectionHealth(), and closeCommandResult().
|
virtual |
If an outstanding/open resultSet exists for this connection, then close it. return ERROR for failure; otherwise OK
Implements DbConnection.
Referenced by clean(), executeCommand(), executeCommandWithParams(), executePreparedCommand(), initializePreparedCommand(), and shutdown().
|
virtual |
Commit the outstanding transaction on this connection
Implements DbConnection.
References executeCommand().
|
virtual |
Execute an SQL command to the database using this connection. This command can be a QUERY, UPDATE, INSERT, or DELETE operation. For Postgresql, the execution command string can contain multiple SQL statements separated by semicolons. However, this should be used with care, especially around external interfaces, since it could be vulnerable against SQL injection attacks. 'executeCommandWithParms' will only allow a single SQL statement and is not vulnerable in this way.
Implements DbConnection.
References closeCommandResult().
Referenced by beginTransaction(), commitTransaction(), and rollbackTransaction().
|
virtual |
Execute an SQL command to the database using this connection. This command can be a QUERY, UPDATE, INSERT, or DELETE operation. (To work with ostringstream.str().c_str()). For Postgresql, the execution command string can contain multiple SQL statements separated by semicolons. However, this should be used with care, especially around external interfaces, since it could be vulnerable against SQL injection attacks. 'executeCommandWithParms' will only allow a single SQL statement and is not vulnerable in this way.
Implements DbConnection.
References closeCommandResult().
|
virtual |
Execute an SQL command to the database using this connection. This command can be a QUERY, UPDATE, INSERT or DELETE operation. For Postgresql, only a single execution command can be contained in this static string. The number of Substitution parameters and a pointer array of their values should be passed in for the server to operate on.
| numberParams | number of passed in parameters in the char* array |
| paramValues | specifies the actual values of the parameters (char* array) |
| paramLengths | specifies the actual data lengths of binary-format parameters. It is ignored for null parameters and text-format parameters. The array pointer may be null when there are no binary parameters. |
| isBinary | array for each param value to determine if the value is binary or textual (TRUE for binary / FALSE for text). The array pointer may be null when there are no binary parameters. |
Implements DbConnection.
References closeCommandResult().
|
virtual |
Execute an SQL prepared statement command to the database using this connection. This command can be a QUERY, UPDATE, INSERT, or DELETE operation.
| statementName | string name assigned to the statement when initializePreparedCommand is called. |
| numberParams | number of passed in parameters in the char* array |
| paramValues | specifies the actual values of the parameters (char* array) |
| paramLengths | specifies the actual data lengths of binary-format parameters. It is ignored for null parameters and text-format parameters. The array pointer may be null when there are no binary parameters. |
| isBinary | array for each param value to determine if the value is binary or textual (TRUE for binary / FALSE for text). The array pointer may be null when there are no binary parameters. |
Implements DbConnection.
References closeCommandResult().
|
virtual |
Return the value at the specified column/row location in the current commandResult. The value returned will be a boolean type. NOTE: Use of this method requires that the developer be aware of the of the schema and result field type.
Implements DbConnection.
|
virtual |
Return the number of columns in the current commandResult structure
Implements DbConnection.
|
virtual |
Return the column index based on the specified column name
Implements DbConnection.
|
virtual |
Return the specified column header name in the current commandResult
Implements DbConnection.
|
virtual |
Return the value at the specified column/row location in the current commandResult. The value returned will be a 4-byte integer type. NOTE: Use of this method requires that the developer be aware of the of the schema and result field type.
Implements DbConnection.
|
virtual |
Return the number of rows in the current commandResult
Implements DbConnection.
|
virtual |
Return the value at the specified column/row location in the current commandResult. The value returned will be a 2-byte short type. NOTE: Use of this method requires that the developer be aware of the of the schema and result field type.
Implements DbConnection.
|
virtual |
Return the value at the specified column/row location in the current commandResult. The value is returned as a string. NOTE: Use of this method requires that the developer be aware of the of the schema and result field type.
Implements DbConnection.
|
virtual |
Return the value at the specified column/row location in the current commandResult. The value returned will be a string; this is because timestamps are internally stored using 8 bytes (64 bits)!! We have to use the Postgres library to convert them back into ascii. NOTE: Use of this method requires that the developer be aware of the of the schema and result field type.
Implements DbConnection.
|
virtual |
Returns the actual length of a field value in bytes
Implements DbConnection.
|
static |
Inherited from OPMBase. Method will be called when the pool is created with these objects. This method bootstraps the creation of each object. THIS OVERRIDES the initialize method in OPMBASE (can't be both virtual and static)
| initializer | - Initializer integer or pointer to initialization data needed by the object. In this case, we pass in a pointer to a PgInitParams struct. |
References PgConnection().
Referenced by ConnectionSet::performActivation().
|
virtual |
Setup for a prepared statement command on this connection
| statementName | string name arbitrarily assigned to the statement |
| sqlCommand | QUERY, UPDATE, INSERT, or DELETE sql operation. |
| numberParams | number of passed in parameters in the char* array |
| paramTypeArray | array of field types because the database cannot infer the field type formatting without it. |
Implements DbConnection.
References closeCommandResult().
|
virtual |
Returns true if the field Value is NULL
Implements DbConnection.
|
virtual |
|
virtual |
Close the socket connection to the database server
Implements DbConnection.
References closeCommandResult().
| string PgConnection::toString | ( | ) |
String'ized debugging method


Copyright © 2006 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This Working Group Note is the third publication of the Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements, and represents an editorial revision from the previous version in order to transition from Working Draft to Working Group Note. This document has been produced by the Timed Text Working Group as part of the W3C Synchronized Multimedia Activity. The authors of this document are the TT Working Group members, who consider this document to be stable, and do not expect further revision.
Comments on this document should be sent to the email list<EMAIL_ADDRESS>which is the public
mailing list of Timed Text Working Group (list archives). To
subscribe, send an email to<EMAIL_ADDRESS>with the
word subscribe
in the subject line.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
As of this publication, the Working Group does not expect this document to become a W3C Recommendation, and therefore it has no associated W3C Patent Policy licensing obligations. If this expectation changes, the Working Group will have an opportunity to fulfill the associated patent policy requirements with respect to a future draft.
This document was produced by a group operating under the 24 January 2002 CPP as amended by the W3C Patent Policy Transition Procedure. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
1 Introduction
1.1 Motivation
1.2 System Model
2 Definitions
2.1 Acronyms
2.2 Terminology
2.3 Notations
3 Use Case Scenarios
4 Requirements
4.1 General
4.2 Content
4.3 Styling
4.4 Timing
4.5 Animation
4.6 Metadata
A References
B Other References (Non-Normative)
C Acknowledgments (Non-Normative)
This document specifies usage scenarios and requirements for a timed text authoring format. A timed text authoring format is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.
Note:
This document incorporates requirements regarding stylistic and timing functionality that range from simple to relatively complex. It is expected that the use of this functionality will be partitioned into one or more profiles represented by document types of increasing complexity. It is not expected that every authoring system or ultimate consumer of timed text content will support all of this functionality.
A principal motivation for the development of a common authoring format for timed text is the lack of a standard content format that supports the representation and interchange of textual information which is synchronized with other media elements or which serves as a synchronization master itself.
Popular proprietary multimedia systems and their corresponding player components have defined distinct timed text formats for each proprietary use. As a consequence there is no common authoring format that serves as a portable interchange format between such systems. A goal of the present work is to define such a portable interchange format to ease the burden of authoring tool developers and users as well as enhance portability of timed text content.
A side effect of the development and deployment of a common timed text authoring format is that it simplifies the creation and distribution of synchronized text for use with a multitude of devices, such as multimedia players, caption, subtitle, and teletext encoders and decoders, character generators, LED displays, and other text display devices.
The uses cases and requirements specified in this document are based upon a system model, depicted in Figure 1 – System Model, wherein the timed text authoring format serves as a bidirectional interchange format among a heterogeneous collection of authoring systems, and as a unidirectional interchange format to a heterogeneous collection of distribution formats after undergoing transcoding to the target distribution formats as required.
Note:
In the figure depicted above, the acronym DFXP refers to a profile of the timed text authoring format known as the Distribution Format Exchange Profile, which is intended primarily to satisfy interchange among existing legacy formats, and which may also be distributed directly.
Note:
This system model does not preclude the timed text authoring format from being used as a distribution format in its own right.
| TT | Timed Text |
| TT AS | Timed Text Authoring System |
| TT AF | Timed Text Authoring Format |
| TT WG | Timed Text Working Group |
Textual information that is intrinsically or extrinsically associated with timing information.
A content type that represents timed text media for the purpose of interchange among authoring systems.
A content authoring system capable of importing and exporting timed text authoring format content.
A caption service provider needs a common content authoring format by means of which a textual expression of audio information may be associated with such audio information in a time synchronized manner.
Note:
In the context of captioning an aggregate audio/video service, both audio and caption information are typically synchronized to the video track as the timebase master.
A subtitle service provider needs a common content authoring format by means of which a textual expression of the original or a translation of the original natural language (speech) audio information may be associated with such audio information in a time synchronized manner.
Note:
In the context of subtitling an aggregate audio/video service, both audio and subtitle information are typically synchronized to the video track as the timebase master.
Note:
The distinction between captioning and subtitling is best expressed as follows: captioning is expressly intended to serve the needs of deaf and hard of hearing users, and typically contains transcriptions of speech and non-speech audio information; in contrast, subtitling is generally intended to serve the needs of hearing users who don't have access to an audio track (e.g., in muting situations) or don't understand the natural language of the speech contained in the audio track. Subtitling is often viewed as a paraphrase or a translation of speech information, as opposed to a transcription of all audio information.
In the absence of captioning information, subtitling information may also be used by deaf and hard of hearing users, provided that it is available in the original natural language.
Note:
Some user communities use the term subtitling to encompass both captioning and subtitling uses as distinguished in the previous note.
A description service provider needs a common content authoring format in which a textual description of video information or a textual expression of an audio description of video information may be associated with such video information in a time synchronized manner.
Note:
When a description is rendered by an audio track, such a description is commonly referred to as an Audio Description.
Note:
In the use of aural forms of visual description, it may be the case that the duration of an aural form of a description exceeds the duration of the visual information being described. In a presentation device, this necessitates manual or automatic pausing of the video track in order to fully render the aural form of description. It is likely that similar modes of presentation will be required for timed text representations of video descriptions.
Note:
This use case scenario is not intended to serve as a general form of metadata description of related video or audio content.
A generic timed text service provider needs a common content authoring format in which textual information can be presented in a time synchronized manner.
Note:
In the context of using a generic timed text service, timed text information serves as the timebase master, with which other possible timed media may be associated.
Note:
Examples of the use of generic timed text include (but are not limited to): marquee signs, timed text oriented presentations, scrolling text presentation, etc.
The TT AF specification(s) shall be authored using XML and XSL Stylesheets based on [XML Spec] and shall adhere to best current practices in the W3C for specification style and quality assurance.
The TT AF specification(s) shall be defined in a modular manner that logically separates significant areas of functionality to as great extent as is practical.
The TT AF specification(s) shall be organized in such a manner as to separate the following aspects:
TT Framework
TT Core Vocabulary
TT Core Document Types
TT Extension Vocabulary(ies)
TT Extension Document Type(s)
The TT AF specification(s) shall be defined in such a manner that core functionality is logically separated from peripheral functionality.
The TT AF specification(s) shall be defined in such a manner that core functionality can evolve over time, e.g., by the specification of multiple levels (or versions) of core functionality.
The TT AF specification(s) shall be defined in such a manner that core functionality be specified soley by the TT WG or, in the event that the TT WG is terminated, its successors within the W3C.
Note:
It is assumed that one or more appropriate namespace mechanisms will be used to segregate core functionality defined or adopted in the TT AF from peripheral functionality defined or adopted by clients of the TT AF.
The TT AF specification(s) shall be defined in such a manner that for every item in the TT AF core vocabulary, there shall be at least one TT AF core document type that makes use of that item, i.e., there exists a surjection from the set of TT AF core document types to the set of TT AF vocabulary items referenced by those document types.
Note:
The TT AF specification(s) may define standardized peripheral vocabulary that is not referenced by any TT AF core document type.
The TT AF specification(s) shall be defined in such a manner that peripheral functionality can evolve over time, e.g., by the future specification of one or more peripheral functionality modules.
The TT AF specification(s) shall be defined in such a manner that peripheral functionality need not be specified by the TT WG or the W3C, but may be specified by other W3C WGs as well as non-W3C clients of the TT AF.
The TT AF shall be capable of being transformed, without undue complexity, into one or more legacy timed text content formats, e.g., [3GPP], [QText], [RealText], [SAMI], etc.
Note:
The above list of potential target timed text content formats is strictly informative, and is not intended to be exhuastive.
The TT AF shall be capable of being transformed into an idealized streamable representation format.
Note:
It is not required that an idealized streamable representation format be defined by the TT AF specification(s); however, the definition of such a format may be the subject of future activities by the TT WG.
Note:
It is intended that existing closed captioning and subtitle streaming formats used by analog and digital television services as well as timed text used in the context of streaming audio and motion video formats be potentially targeted by one or more transformations of the TT AF. These formats include [EIA-608B], [EIA-708B], [EN 300 706], [EN 300 743], etc.
The TT AF shall include the following accessibility related features:
Support for a mechanism to explicitly associate Equivalent Alternatives to the textual information in the TT presentation in accordance with [WAI XML AG] Guideline 1.
Support for Content Rendering Adaption in accordance with [WAI SMIL AG], Section 5. See also Conditional Content.
Use of a default text vocabulary that satisfies guideline 2 of [WAI XML AG] regarding structural and semantical stringency.
Ability to extend or replace the default text vocabulary with other XML dialects to represent the textual information of the TT presentation. See also Intrinsic and Extrinsic Text Content.
Support for explicit definition of a Navigational Structure associated with the TT presentation in accordance with [WAI SMIL AG], Section 4.3.
The TT AF specification(s) shall be defined in such a manner as to require a TT AS to adhere to all applicable aspects of [ATAG 1.0].
The TT AF shall be capable of being created and modified using a plain text editor, e.g., emacs, vi, etc.
The TT AF shall be capable of representing content of different natural languages, where the content of distinct languages may be segregated into separate document instances or may be integrated into a single document instance.
The TT AF shall be capable of representing content of at least those specific natural languages that may be represented with [Unicode 3.2].
The TT AF shall be capable of associating natural language binding information with plain text information at the granularity of a single coded character.
The TT AF shall be capable of representing every coded character available in [Unicode 3.2] by using only those characters in [ASCII (ANSI X3.4)].
Note:
This requirement facilitates the entry and editing of characters in a TT AF document instance that would otherwise not be permitted due to lack of an appropriate character input method or lack of support for a non-ASCII character encoding system.
It is assumed that every TT AS will provide a means to enter and edit TT AF document instances represented in the ASCII character set.
The TT AF shall be capable of expressing text content intrinsically within a TT AF document instance, extrinsically by referencing from a TT AF document instance to text content in one or more external resources, or in any combination of these two modes.
The TT AF shall be capable of associating structural markup with intrinsic and extrinsic text content, where such markup may denote either or both semantic (functional) and presentational (formal) properties of the content.
Note:
In this context, presentational properties designate both stylistic and timing related presentation information.
The TT AF shall be capable of expressing conditional content, where each alternative content choice is governed by one or more test expressions such that exactly one or zero content choice is selected when evaluating each choice in a predefined order.
The TT AF shall be capable of expressing authorial intention to flow (layout) text content in an idealized, but unspecified user agent.
Note:
In this context, the concept of flow refers to an implied process by means of which textual information expressed in the character domain is mapped to a positioned glyph codomain.
Note:
It is not required that an idealized user agent or behavior of such a user agent be defined by the TT AF specification(s); however, the definition of such a user agent or user agent behavior may be the subject of future activities by the TT WG.
The TT AF shall be capable of expressing the following vocabulary as pertains to logical flowed text content:
body
division
paragraph
phrase
Note:
A generic role attribute is expected to be provided for use with these items in order to express distinct stylistic and semantic roles, e.g., a paragraph role may be associated with a division item to indicate that the logical division expressed corresponds to a stylistic and semantic paragraph.
Note:
One possible mapping for this vocabulary is to
xhtml:body
, xhtml:div
, xhtml:p
,
and xhtml:span
, respectively, as defined by [XHTML 1.0].
The TT AF shall be capable of expressing the following vocabulary as pertains to presentational flowed text content:
block
block container
character
flow
forced line break
inline
inline container
region
viewport
Note:
The items enumerated above are drawn in part from similarly named items defined by [XSL 1.0], Section 6, Formatting Objects.
Note:
The forced line break item may be expressed in terms of the character item, where the specified character has line separator or line break semantics.
The use of this item in combination with a wrap option
style parameter with the value nowrap
permits an
intermediate mode of text representation with formatting semantics that
fall between flowed text and non-flowed text.
Note:
The viewport and region items are intended to be
analogous to the [XSL 1.0] vocabulary
fo:simple-page-master
and fo:region-*
,
respectively.
The TT AF shall be defined in such a manner that a default relationship between logical and presentational flowed text vocabulary may be assumed as follows:
body ⇔ flow
division (display: block) ⇔ block container
paragraph ⇔ block
division (display: inline) ⇔ inline container
phrase ⇔ inline
Note:
Parsed character data (#PCDATA
) that appears in logical
flowed text content should be assumed to map by default to parsed
character data or character in presentational flowed text
content.
The TT AF shall be defined in such a manner that use of logical flowed text vocabulary is separated from use of presentational flowed text vocabulary.
Note:
It is not required that the TT AF specification(s) define a document type that supports the simultaneous use of both logical and presentational flowed text vocabulary.
The TT AF shall be capable of expressing authorial intention to render non-flowed text content in an idealized, but unspecified user agent.
Note:
In this context, the concept of non-flowed text refers to textual information that is explicitly associated with positioned glyph information at authoring time; i.e., all bidirectional processing and character to glyph substitution processing and glyph position assignment has already occurred.
Note:
It is not required that an idealized user agent or behavior of such a user agent be defined by the TT AF specification(s); however, the definition of such a user agent or user agent behavior may be the subject of future activities by the TT WG.
The TT AF shall be capable of expressing the following vocabulary as pertains to non-flowed text content:
area
glyph
glyph sequence
Note:
The glyph and glyph sequence vocabulary items are intended to make direct reference to specific glyphs in specific fonts, having already been transformed from the character domain to the glyph domain. References to glyphs would typically take the form of a glyph identifier or a glyph code. For further information on character to the glyph mapping process, see [CharMod], Section 3.1.3, Units of Visual Rendering.
The TT AF shall be capable of expressing authorial intention to create a hybrid of flowed and non-flowed text content; however, such an expression may require that these two types of content be segregated at a specific level of granularity.
The TT AF shall be capable of expressing simple hyperlinks, where the ending (destination) resource is either the starting (source) resource or an external resource.
The TT AF shall be capable of expressing block and inline, embedded graphics of both bitmap and vector or outline formats.
If block or inline graphics are used for the purpose of expressing pre-rasterized text in a bitmap format, then the original text that produced such a pre-rasterized form shall also be required to be present in TT AF content.
The TT AF shall be capable of expressing block and inline, non-embedded graphics of both bitmap and vector or outline formats, where a graphic is represented by an external resource.
If block or inline graphics are used for the purpose of expressing pre-rasterized text in a bitmap format, then the original text that produced such a pre-rasterized form shall also be required to be present in TT AF content.
The TT AF shall be capable of expressing embedded fonts of both bitmap and outline formats.
The TT AF shall be capable of expressing non-embedded fonts of both bitmap and outline formats, where a font is represented by an external resource.
The TT AF shall be capable of associating text content with descriptive information from an appropriate domain of discourse.
Note:
See [TEI], Chapter 10, Base Tag Set for Drama, and Chapter 11, Transcription of Speech, for examples of descriptive vocabulary pertaining to drama and the transcription of speech, respectively.
The TT AF shall be capable of expressing embedded audio that is intended to be played or rendered in sequence or in parallel with associated text content.
Note:
The use of embedded audio is intended to support aural cues that may accompany text.
The TT AF shall be capable of expressing non-embedded audio that is intended to be played or rendered in sequence or in parallel with associated text content, where the audio content is represented by an external resource.
Note:
The use of non-embedded audio is intended to support aural cues that may accompany text.
The TT AF shall support the use of both [XML 1.0] and [XML 1.1] as serialized forms of a TT AF XML information set.
Note:
See [XML InfoSet] for further information on an XML information set.
The TT AF shall require or recommend adherence to the practices recommended by [Unicode in XML].
The TT AF shall support the use of [XLink] for the purpose of referencing external resources.
The TT AF specification(s) shall be defined in such a manner that the normative validity of markup content be specified in terms of either or both [RELAX NG] and [XML Schema Part 1] in combination with [XML Schema Part 2].
The TT AF shall be capable of inline styling, where inline styling means the inclusion of stylistic presentation information in a TT AF document instance.
The TT AF shall be capable of specifying inline styling by means of
(1) distinct attributes, (2) a generic attribute, e.g.,
style
, and (3) one or more inline stylesheets.
The TT AF shall be capable of out-of-line styling, where out-of-line styling means the association of stylistic presentation information with TT AF content via some mechanism external to a TT AF document instance.
The TT AF shall be capable of specifying out-of-line styling by means of one or more external stylesheets.
The TT AF shall be capable of associating priorities with stylistic presentation information in order to permit the resolution of multiple style specifications that apply to the same content.
The TT AF shall be capable of associating the following aural style parameters with timed text content:
azimuth
cue before, during, after
elevation
pause before, after
pitch
pitch range
richness
speaking mode
speech rate
stress
voice family
volume
Note:
For further information on these style parameters, see [XSL 1.0], Section 7.6, Common Aural Properties and [CSS Level 2].
Note:
For further information on the speaking mode aural style
parameter, see discussion of speak
,
speak-numeral
, and speak-punctuation
properties described in [XSL 1.0], Section 7.6.
The TT AF shall be capable of associating the following visual style parameters with timed text content:
absolute position
background color
baseline alignment point
baseline alignment
baseline dominance
baseline shift
bidirectional treatment
block progression dimension
block scroll amount
border before, after, start, end
break before, after
clear
color
color profile name
display none, block, inline
display alignment
float
font family
font size
font style
font weight
height
indent start, end
inline progression dimension
inline scroll amount
intrusion-displace
line feed treatment
line height
line stacking strategy
line wrapping option
opacity
origin (top, left)
overflow
padding before, after, start, end
reference orientation
relative position
space before, after, start, end
text alignment
text altitude (ascent)
text decoration
text depth (descent)
text indent (first line)
text shadow
visibility
white space collapse
white space treatment
width
writing mode
z-index
Note:
For further information on these style parameters, see [XSL 1.0], Section 7, Formatting Properties and [CSS Level 2].
Note:
The style parameters break before and break after
are intended to model the like named style properties defined by [XSL 1.0], Section 7.19, Keeps and Breaks
Properties, except that the possible values of these parameters
are expected to be restricted to auto
, line
,
and inherit
. The new value line
is intended
to denote a line area context in order to express that a line break
should precede or follow the element associated with this parameter.
Unlike XSL, these parameters apply only to inline vocabulary, and not block vocabulary.
Note:
A style parameter is intended to convey the notion of any type of style specification or declaration whether it is expressed as an attribute or a property.
The TT AF may be capable of associating the following visual style parameters that pertain to temporal filling (flowing) of timed text content:
temporal fill mode
temporal fill direction
temporal block clear mode
temporal fill interval
temporal inter-fill interval
Note:
These parameters are intended to permit the expression of authorial intent with respect to the temporal filling (stacking) of glyph areas within a line area and line areas within a block area.
The temporal fill mode parameter permits specifying the granularity of temporal filling, e.g., line, word, character. The temporal fill direction parameter permits specifying the direction of fill (stacking) independently from the writing mode. The temporal block clear mode parameter permits specifying whether the containing block is cleared or is automatically scrolled, and by what extent, when the block is filled. The temporal fill interval parameter permits specifying the interval that a filled area should remain static before processing the next fill. The temporal inter-fill interval parameter permits specifying the interval between the end of a prior fill interval and the start of a subsequent fill interval.
The TT AF shall be defined in such a manner that if a stylistic presentation parameter may be specified as a style property, then that parameter shall also be specifiable as a style attribute, and vice-versa.
Note:
In this context, a style attribute refers to an attribute expressed in a markup language (e.g., an XML attribute), while a style property refers to a property expressed in a style language (e.g., a CSS property).
The TT AF shall be defined in such a manner that if there is a conflict when adopting the name or value semantics of a style parameter specification, then the following order shall hold for resolving such a conflict:
XSL FO
SVG
SMIL
CSS Level 2
CSS Level 3
The TT AF shall be defined in such a manner that to the extent that stylistic oriented markup element types are defined or adopted, then such element types shall be defined as shorthand equivalents of non-stylistic oriented element types in combination with specific style parameters.
The TT AF shall be capable of inline timing, where inline timing means the inclusion of temporal presentation markup in a TT AF document instance.
The TT AF shall be capable of out-of-line timing, where out-of-line timing means the association of temporal presentation information with TT AF content via some mechanism external to a TT AF document instance.
The TT AF shall be capable of expressing the following synchronization parameters in terms of any legal combination that expresses a possibly repeated or restarted, single, simple interval:
begin
dur
end
endsync
fill
fillDefault
repeatCount
repeatDur
restart
restartDefault
Note:
For further information on these synchronization parameters, see [SMIL 2.0], Section 10, The SMIL 2.0 Timing and Synchronization Module.
Note:
It is not required that the TT AF support the specification of multiple simple intervals, i.e., multiple start, duration, or begin values.
The TT AF shall be capable of expressing the following synchronization parameter value space semantics:
Offset Values – a clock offset from an implied or explicit synchronization timebase;
Event Values – a clock offset from a named event associated with an implied or explicit element node, including, at a minimum, named events that indicate the beginning or end of a timed element's active interval;
Access Key Values – a clock offset from a specific key press event;
Media Marker Values – a clock offset from a media marker, including, at a minimum, a media marker that denotes a SMPTE time code;
Wallclock Values – a clock offset from an absolute wallclock time in an implied or explicit time zone.
Note:
It is not required that the TT AF support the specification of negative offset values.
The TT AF shall be capable of expressing sequential, parallel, and exclusive time containment semantics of consituent timed text content.
Note:
For further information on these time containment semantics, see [SMIL 2.0], Section 10, The SMIL 2.0 Timing and Syncrhonization Module.
The TT AF shall be capable of expressing animation according to the following modes:
continuous – linear
continuous – non-linear
discrete
Note:
By animation is meant the ability to alter some parameter or value over time.
The TT AF shall be capable of expressing animated scrolling of content, both in block and inline progression directions, with independent expression of scroll in, scroll out, and scroll repetition.
The TT AF shall be capable of expressing animated highlighting of content, with granularity at the level of individual characters or glyphs.
The TT AF shall be capable of expressing animated fade transitions of content, with granularity at the level of individual regions or areas.
Note:
See Presentational Flowed Text Vocabulary and Non-Flowed Text Vocabulary for information on region and area vocabulary items, respectively.
The TT AF shall be capable of animating the following aural style parameters:
azimuth
elevation
speaking mode
speech rate
volume
The TT AF shall be capable of animating the following visual style parameters:
background color
block scroll amount
border color
color
display
inline scroll amount
opacity
origin
visibility
Note:
It is possible to express fade-in and fade-out transitions by means of animating the opacity style parameter.
Note:
Animation of the display style parameter may cause reflow (reformatting) of content in a user agent at each animation step.
The TT AF is not required to support the animation of content.
Note:
By animation of content is meant the dynamic addition or changing of element content by means of animation functionality, e.g., replacing the text content of an element.
The TT AF shall be capable of associating arbitrary metadata, expressed as metadata items, with (1) a TT AF document instance and (2) any element contained within a TT AF document instance.
Note:
It is not required that metadata be able to be associated with an element's attributes or with any other child of an element other than a child that is characterized as an element itself.
The TT AF shall be capable of expressing the following constituents of individual metadata items:
name
value type
value
The TT AF shall give preference to the representation of metadata item values as element content as opposed to attribute content.
Note:
By element content is meant those children of an element information item that are characterized as elements or as character data. By attribute content is meant the normalized values of the attributes of an element information item.
The TT AF shall be capable of expressing metadata items whose names, value types, and semantics are defined externally to the TT AF specification(s).
The TT AF specification(s) shall be defined in such a manner as to permit and potentially require the ability to validate metadata.
The TT AF specification(s) shall be defined in such a manner as to give preference to those metadata items defined by [DCMES 1.1] in case that a conflict exists with another candidate metadata representation.
The editor acknowledges the members of the Timed Text Working Group, the members of other W3C Working Groups, and industry experts in other forums who have contributed directly or indirectly to the process or content of creating this document.
The current and former members of the Timed Text Working Group are: Glenn Adams, Extensible Formatting Systems, Inc. (chair); Kees Blom, CWI; Brad Botkin, WGBH; Dick Bulterman, CWI; Michael Dolan, Invited Expert; Gerry Fields, WGBH; Geoff Freed, WGBH; Markus Gylling, DAISY Consortium; Markku Hakkinen, Japanese Society for Rehabilitation of Persons with Disabilities; Sean Hayes, Microsoft; Erik Hodge, RealNetworks; Masahiko Kaneko, Microsoft; George Kerscher, DAISY Consortium; David Kirby, BBC; Thierry Michel, W3C (team contact); Patrick Schmitz, Invited Expert; and, Dave Singer, Apple Computer.
The Timed Text Working Group has benefited in its work from the participation and contributions of a number of people not currently members of the Working Group, including in particular those named below. Affiliations given are those current at the time of their work with the WG.
John Birch, Screen Subtitling Systems; Bert Bos, W3C (chair, CSS WG); Martin Dürst, W3C (leader, I18N Activity); Al Gilman (chair, WAI Protocol and Formats WG); Philipp Hoschka, W3C (leader, Interaction Domain); Chris Lilley, W3C (chair, SVG WG).


Plugins
Form Validation
Form Validation
Form Widget
Datetimepicker
Bootstrap Touchspin
Pretty Checkbox
Select2
Autosize
Clipboard
Form Repeater
Form Text Editor
TinyMCE
Quill
Table
Datatables
File Upload
Dropzone
File upload with preview
Map
Leaflet
Notification
Toastr
Miscellaneous
Block UI
JSTree
Jquery Bar Rating
Jquery Count To
Sortable List
Sortable List (JSON)
Gallery
Owl Carousel
Slick
Photo Swipe
Photo Swipe (v2)
Lightcase
Lazyload
New
New


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--org.apache.velocity.runtime.resource.loader.ResourceLoader
This is abstract class the all text resource loaders should extend.
| Field Summary | |
protected java.lang.String |
className
Class name for this loader, for logging/debuggin purposes. |
protected boolean |
isCachingOn
Does this loader want templates produced with it cached in the Runtime. |
protected long |
modificationCheckInterval
This property will be passed on to the templates that are created with this loader. |
protected RuntimeServices |
rsvc
|
| Constructor Summary | |
ResourceLoader()
|
| Method Summary | |
void |
commonInit(RuntimeServices rs,
org.apache.commons.collections.ExtendedProperties configuration)
This initialization is used by all resource loaders and must be called to set up common properties shared by all resource loaders |
java.lang.String |
getClassName()
Return the class name of this resource Loader |
abstract long |
getLastModified(Resource resource)
Get the last modified time of the InputStream source that was used to create the template. |
long |
getModificationCheckInterval()
Get the interval at which the InputStream source should be checked for modifications. |
abstract java.io.InputStream |
getResourceStream(java.lang.String source)
Get the InputStream that the Runtime will parse to create a template. |
abstract void |
init(org.apache.commons.collections.ExtendedProperties configuration)
Initialize the template loader with a a resources class. |
boolean |
isCachingOn()
The Runtime uses this to find out whether this template loader wants the Runtime to cache templates created with InputStreams provided by this loader. |
abstract boolean |
isSourceModified(Resource resource)
Given a template, check to see if the source of InputStream has been modified. |
void |
setCachingOn(boolean value)
Set the caching state. |
void |
setModificationCheckInterval(long modificationCheckInterval)
Set the interval at which the InputStream source should be checked for modifications. |
| Methods inherited from class java.lang.Object |
|
| Field Detail |
protected boolean isCachingOn
protected long modificationCheckInterval
protected java.lang.String className
protected RuntimeServices rsvc
| Constructor Detail |
public ResourceLoader()
| Method Detail |
public void commonInit(RuntimeServices rs, org.apache.commons.collections.ExtendedProperties configuration)
public abstract void init(org.apache.commons.collections.ExtendedProperties configuration)
public abstract java.io.InputStream getResourceStream(java.lang.String source) throws ResourceNotFoundException
public abstract boolean isSourceModified(Resource resource)
public abstract long getLastModified(Resource resource)
public java.lang.String getClassName()
public void setCachingOn(boolean value)
public boolean isCachingOn()
public void setModificationCheckInterval(long modificationCheckInterval)
public long getModificationCheckInterval()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Plain of Tears [ap33], plain, in Mandoria, peasants: 124
Last updated Turn #121
Plain of Tears [ap33], plain, in Mandoria, peasants: 124
------------------------------------------------------------------------
30: The population grows by one peasant.
Routes leaving Plain of Tears:
North, plain, to Plain of Tears [ao33], 7 days
Garrison [bu3v], garrison, uncontrolled, with ten peasants
East, to Ocean [ap34], The Inner Sea, 2 days
South, plain, to Plain of Tears [aq33], 7 days
Garrison [cs5z], garrison, uncontrolled, with ten peasants
West, plain, to Plain of Tears [ap32], 7 days
Garrison [ag6b], garrison, uncontrolled, with four peasants
Seen here:
Garrison [ag2g], garrison, uncontrolled, with four peasants


Pandey Fitness
HOME
ABOUT US
FITNESS CALCULATOR
CONTACT US
CALL US
REGISTER NOW
Join the best GYM of Lucknow
submit


Authorization |
|
|---|---|
EIDITH logon credentials |
|
Database |
|
Download EIDITH data to local storage |
|
Get the status of the locally stored EIDITH database |
|
Check the online EIDITH database for updates since your last download. |
|
Export the local EIDITH database to a file |
|
EIDITH data |
|
EIDITH table metadata |
|
Connecting eidith tables |
|
|
|
Load EIDITH data from the local database |
Reports and Analyses |
|
|
|
Export FASTA files for viral interpretation |
Raw data |
|
|
|
Functions to download EIDITH tables via API |
Standard post-processing of EIDITH exports |
|
Mock data |
|
|
|
Load mock EIDITH data for tutorials |