This application pretend to be a tool to software inspections, giving the user the facilities to search, create and share checklists for a product or process. There are many software tools for quality assurance (QA) but no one let user create its own checklist from a base of community checklists and even more, let them share its creation with others.
Com'on! sing up and start creating your Checklists.


--- layout: default category: main ---
I am an EECS Ph.D. Student at UC Berkeley in the ASPIRE Lab. My research interests are in novel architectures for parallel computing and tools for making parallel processors more easily programmable.
You can find some of my code on Github and Bitbucket. I have some videos of my hardware projects on Youtube.


@* * Copyright 2017 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import uk.gov.hmrc.play.views.html.helpers._ @import uk.gov.hmrc.cbcrfrontend.AppConfig @import play.api.i18n.Messages.Implicits._ @import uk.gov.hmrc.cbcrfrontend.views.html._ @import helper._ @import tags._ @import uk.gov.hmrc.cbcrfrontend.model._ @(asideCbc: Html, phaseBannerBeta: Html, form:Form[_])( implicit request: Request[_], messages: Messages) @sidebarContent = { @asideCbc } @error = @{form.error("companyName").isDefined} @main_template("Country by Country Reporting", sidebarLinks = Some(sidebarContent)) {


Plate update:
{{plate.library.name}} - {% if plate.name %}{{plate.name}}{% endif %}({{ plate.barcode }})
Manage plate
Dispense testing
Mark as unavailable:
Edit plate data:
Manually register opening the plate
For special cases only*
* If a plate is opened for an experiment or dispense testing, it is registerd automatically. This form is supposed to cover less typical cases, e.g. opening by mistake.
Delete {{plate.library.name}} : {{ plate.barcode }}
Additional information
Basic data
| Library | {{ plate.library.name }} |
| Barcode | {{ plate.barcode }} |
| Name | {{ plate.name }} |
| Last updated | {{ plate.last_tested }} |
| Current | {% if plate.current %} Yes {% else %} No {% endif %} |
| Opened | {{ plate.opened.count }} times |
Number of compounds in plate
| All | {{ plate.compounds.all|length }} |
| Available | {{ active_count }} |
| Unavailable | {{ inactive_count }} |
| Availability | {{ availability }}% |
Plate opened
| Date | Reason |
|---|---|
| {{ o.date|date:"d M Y" }} | {{ o.reason }} |


Please refer to the errata for this document, which may include some normative corrections.
See also translations.
This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip'd TAR archive.
Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring.
XHTML Basic is designed as a common base that may be extended. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents.
This revision, 1.1, supercedes version 1.0 as defined in http://www.w3.org/TR/2000/REC-xhtml-basic-20001219. In this revision, several new features have been incorporated into the language in order to better serve the small-device community that is this language's major user:
li
element (defined in [XHTMLMOD])The document type definition is implemented using XHTML modules as defined in "XHTML Modularization" [XHTMLMOD].
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 document is a W3C Recommendation and supersedes the 19 December 2000 version of the XHTML Basic Recommendation. It reflects cross-industry agreement on a set of markup language features that allows authors to create rich Web content deliverable to a wide range of devices.
This document has been produced by the W3C XHTML2 Working Group as part of the W3C HTML Activity. Please see the Working Group's implementation report. A diff-marked version against the Proposed Recommendation is available. A diff-marked version against the 19 December 2000 Recommendation is also available.
Please send comments about this document to<EMAIL_ADDRESS>(archive). It is inappropriate to send discussion email to this address. Public discussion may take place on<EMAIL_ADDRESS>(archive).
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. 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.
HTML 4 is a powerful language for authoring Web content, but its design does not take into consideration issues pertinent to small devices, including the implementation cost (in power, memory, etc.) of the full feature set. Consumer devices with limited resources cannot generally afford to implement the full feature set of HTML 4. Requiring a full-fledged computer for access to the World Wide Web excludes a large portion of the population from consumer device access of online information and services.
Because there are many ways to subset HTML, there are many almost identical subsets defined by organizations and companies. Without a common base set of features, developing applications for a wide range of Web clients is difficult.
The motivation for XHTML Basic is to provide an XHTML document type that can be shared across communities (e.g. desktop, TV, and mobile phones), and that is rich enough to be used for simple content authoring. New community-wide document types can be defined by extending XHTML Basic in such a way that XHTML Basic documents are in the set of valid documents of the new document type. Thus an XHTML Basic document can be presented on the maximum number of Web clients.
The document type definition for XHTML Basic is implemented based on the XHTML modules defined in XHTML Modularization [XHTMLMOD].
For information on best practices for mobile content, we refer you to [MOBILEBP].
Information appliances are targeted for particular uses. They support the features they need for the functions they are designed to fulfill. The following are examples of different information appliances:
Existing subsets and variants of HTML for these clients include Compact HTML [CHTML], the Wireless Markup Language [WML], and the "HTML 4.0 Guidelines for Mobile Access" [GUIDELINES]. The common features found in these document types include:
This set of HTML features has been the starting point for the design of XHTML Basic. Since many content developers are familiar with these HTML features, they comprise a useful host language that may be combined with markup modules from other languages according to the methods described in "XHTML Modularization" [XHTMLMOD]. For example, XHTML Basic may be extended with a custom module to support richer markup semantics in specific environments.
It is not the intention of XHTML Basic to limit the functionality of future languages. But since the features in HTML 4 (frames, advanced tables, etc.) were developed for a desktop computer type of client, they have proved to be inappropriate for many non-desktop devices. XHTML Basic will be extended and built upon. Extending XHTML from a common and basic set of features, instead of almost identical subsets or the too-large set of functions in HTML 4, will be good for interoperability on the Web, as well as for scalability.
Compared to the rich functionality of HTML 4, XHTML Basic may look like one step back, but in fact, it is two steps forward for clients that do not need what is in HTML 4 and for content developers who get one XHTML subset instead of many.
This section explains why certain HTML features are not part of XHTML Basic.
Many simple Web clients cannot display fonts other than monospace. Bi-directional text, bold faced font, and other text extension elements are not supported.
It is recommended that style sheets be used to create a presentation that is appropriate for the device.
Basic XHTML tables ([XHTMLMOD], section 5.6.1) are supported, but tables can be difficult to display on small devices. It is recommended that content developers follow the Web Content Accessibility Guidelines 1.0 for creating accessible tables ([WCAG10], Guideline 5). Note that in the Basic Tables Module, nesting of tables is prohibited.
Frames are not supported. Frames depend on a screen interface and may not be applicable to some small appliances like phones, pagers, and watches.
This section is normative.
A Conforming XHTML Basic document is a document that requires only the facilities described as mandatory in this specification. Such a document must meet all of the following criteria:
<html>
.
http://www.w3.org/1999/xhtml
.<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic11.dtd">
XHTML Basic 1.1 documents SHOULD be labeled with the Internet Media Type "application/xhtml+xml" as defined in [RFC3236]. For further information on using media types with XHTML, see the informative note [XHTMLMIME].
The user agent must conform to the "User Agent Conformance" section of the XHTML 1.0 specification ([XHTML1], section 3.2).
This section is normative.
The XHTML Basic document type is defined as a set of XHTML modules. All XHTML modules are defined in the "XHTML Modularization" specification [XHTMLMOD].
XHTML Basic consists of the following XHTML modules:
body, head, html, title
abbr, acronym, address, blockquote, br, cite, code, dfn, div, em, h1, h2, h3, h4, h5, h6, kbd, p, pre, q, samp, span, strong, var
a
dl, dt, dd, ol, ul, li
button, fieldset, form, input, label, legend, select, optgroup, option, textarea
caption, table, td, th, tr
img
object, param
b, big, hr, i, small, sub, sup, tt
meta
link
base
script
and noscript
elementsstyle
elementstyle
attributetarget
attribute.
Note:
(*) = This module is a required XHTML Host Language module.
XHTML Basic also uses the XHTML inputmode Attribute Module, as defined in this specification. This module adds the inputmode
attribute to the
input
and textarea
elements of the XHTML Forms Module.
Finally, XHTML Basic adds the value
attribute to the li
element of the XHTML List Module.
An XML 1.0 DTD is available in Appendix B.
Although XHTML Basic can be used as it is - a simple XHTML language with text, links, and images - the intention of its simple design is for use as a host language. A host language can contain a mix of vocabularies all rolled into one document type. It is natural that XHTML is the host language, since that is what most Web developers are used to.
When markup from other languages is added to XHTML Basic, the resulting document type will be an extension of XHTML Basic. Content developers can develop for XHTML Basic or take advantage of the extensions. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents.
This section is normative.
This section was originally a component of XForms 1.0, and was written by Martin Duerst.
The inputmode Attribute Module defines the inputmode
attribute.
The following table shows additional attributes for elements defined elsewhere when the inputmode module is selected.
| Elements | Attributes | Notes |
|---|---|---|
| input& | inputmode (CDATA) | When the Basic Forms or Forms Module is selected. |
| textarea& | inputmode (CDATA) | When the Basic Forms or Forms Module is selected. |
The attribute inputmode
provides a hint to the user agent to select an appropriate input mode for the text input expected in an associated form control. The input mode may be
a keyboard configuration, an input method editor (also called front end processor) or any other setting affecting input on the device(s) used.
Using inputmode
, the author can give hints to the agent that make form input easier for the user. Authors should provide inputmode
attributes wherever possible, making
sure that the values used cover a wide range of devices.
inputmode
Attribute Value SyntaxThe value of the inputmode
attribute is a white space separated list of tokens. Tokens are either sequences of alphabetic letters or absolute URIs. The later can be distinguished from
the former by noting that absolute URIs contain a ':'. Tokens are case-sensitive. All the tokens consisting of alphabetic letters only are defined in this specification, in
5.3 List of Tokens (or a successor of this specification).
This specification does not define any URIs for use as tokens, but allows others to define such URIs for extensibility. This may become necessary for devices with input modes that cannot be covered by the tokens provided here. The URI should dereference to a human-readable description of the input mode associated with the use of the URI as a token. This description should describe the input mode indicated by this token, and whether and how this token modifies other tokens or is modified by other tokens.
Upon entering an empty form control with an inputmode
attribute, the user agent should select the input mode indicated by the inputmode
attribute value. User agents
should not use the inputmode
attribute to set the input mode when entering a form control with text already present. To set the appropriate input mode when entering a form control that
already contains text, user agents should rely on platform-specific conventions.
User agents should make available all the input modes which are supported by the (operating) system/device(s) they run on/have access to, and which are installed for regular use by the user. This is typically only a small subset of the input modes that can be described with the tokens defined here.
Note:
Additional guidelines for user agent implementation are found at [UAAG 1.0].
The following simple algorithm is used to define how user agents match the values of an inputmode
attribute to the input modes they can provide. This algorithm does not have to be
implemented directly; user agents just have to behave as if they used it. The algorithm is not designed to produce "obvious" or "desirable" results for every possible combination of tokens, but to
produce correct behavior for frequent token combinations and predictable behavior in all cases.
First, each of the input modes available is represented by one or more lists of tokens. An input mode may correspond to more than one list of tokens; as an example, on a system set up for a Greek user, both "greek upperCase" and "user upperCase" would correspond to the same input mode. No two lists will be the same.
Second, the inputmode
attribute is scanned from front to back. For each token t in the inputmode
attribute, if in the remaining list of tokens representing
available input modes there is any list of tokens that contains t, then all lists of tokens representing available input modes that do not contain t are removed. If there is no
remaining list of tokens that contains t, then t is ignored.
Third, if one or more lists of tokens are left, and they all correspond to the same input mode, then this input mode is chosen. If no list is left (meaning that there was none at the start) or if the remaining lists correspond to more than one input mode, then no input mode is chosen.
Example: Assume the list of lists of tokens representing the available input modes is: {"cyrillic upperCase", "cyrillic lowerCase", "cyrillic", "latin", "user upperCase", "user lowerCase"}, then
the following inputmode
values select the following input modes: "cyrillic title" selects "cyrillic", "cyrillic lowerCase" selects "cyrillic lowerCase", "lowerCase cyrillic" selects
"cyrillic lowerCase", "latin upperCase" selects "latin", but "upperCase latin" does select "cyrillic upperCase" or "user upperCase" if they correspond to the same input mode, and does not select any
input mode if "cyrillic upperCase" and "user upperCase" do not correspond to the same input mode.
Tokens defined in this specification are separated into two categories: Script tokens and modifiers. In inputmode
attributes, script tokens should always be listed
before modifiers.
Script tokens provide a general indication the set of characters that is covered by an input mode. In most cases, script tokens correspond directly to [Unicode Scripts]. Some tokens correspond to the block names in Java class java.lang.Character.UnicodeBlock ([Java Unicode Blocks]) or Unicode Block names. However, this neither means that an input mode has to allow input for all the characters in the script or block, nor that an input mode is limited to only characters from that specific script. As an example, a "latin" keyboard doesn't cover all the characters in the Latin script, and includes punctuation which is not assigned to the Latin script. The version of the Unicode Standard that these script names are taken from is 3.2.
| Input Mode Token | Comments |
|---|---|
| arabic | Unicode script name |
| armenian | Unicode script name |
| bengali | Unicode script name |
| bopomofo | Unicode script name |
| braille | used to input braille patterns (not to indicate a braille input device) |
| buhid | Unicode script name |
| canadianAboriginal | Unicode script name |
| cherokee | Unicode script name |
| cyrillic | Unicode script name |
| deseret | Unicode script name |
| devanagari | Unicode script name |
| ethiopic | Unicode script name |
| georgian | Unicode script name |
| greek | Unicode script name |
| gothic | Unicode script name |
| gujarati | Unicode script name |
| gurmukhi | Unicode script name |
| han | Unicode script name |
| hangul | Unicode script name |
| hanja | Subset of 'han' used in writing Korean |
| hanunoo | Unicode script name |
| hebrew | Unicode script name |
| hiragana | Unicode script name (may include other Japanese scripts produced by conversion from hiragana) |
| ipa | International Phonetic Alphabet |
| kanji | Subset of 'han' used in writing Japanese |
| kannada | Unicode script name |
| katakana | Unicode script name (full-width, not half-width) |
| khmer | Unicode script name |
| lao | Unicode script name |
| latin | Unicode script name |
| malayalam | Unicode script name |
| math | mathematical symbols and related characters |
| mongolian | Unicode script name |
| myanmar | Unicode script name |
| ogham | Unicode script name |
| oldItalic | Unico de script name |
| oriya | Unicode script name |
| runic | Unicode script name |
| simplifiedHanzi | Subset of 'han' used in writing Simplified Chinese |
| sinhala | Unicode script name |
| syriac | Unicode script name |
| tagalog | Unicode script name |
| tagbanwa | Unicode script name |
| tamil | Unicode script name |
| telugu | Unicode script name |
| thaana | Unicode script name |
| thai | Unicode script name |
| tibetan | Unicode script name |
| traditionalHanzi | Subset of 'han' used in writing Traditional Chinese |
| user | Special value denoting the 'native' input of the user (e.g. to input her name or text in her native language). |
| yi | Unicode script name |
Modifier tokens can be added to the scripts they apply in order to more closely specify the kind of characters expected in the form control. Traditional PC keyboards do not need most modifier tokens (indeed, users on such devices would be quite confused if the software decided to change case on its own; CAPS lock for upperCase may be an exception). However, modifier tokens can be very helpful to set input modes for small devices.
| Input Mode Token | Comments |
|---|---|
| lowerCase | lowercase (for bicameral scripts) |
| upperCase | uppercase (for bicameral scripts) |
| titleCase | title case (for bicameral scripts): words start with an upper case letter |
| startUpper | start input with one uppercase letter, then continue with lowercase letters |
| digits | digits of a particular script (e.g. inputmode='thai digits') |
| symbols | symbols, punctuation (suitable for a particular script) |
| predictOn | text prediction switched on (e.g. for running text) |
| predictOff | text prediction switched off (e.g. for passwords) |
| halfWidth | half-width compatibility forms (e.g. Katakana; deprecated) |
User agents may use information available in an XML Schema pattern facet to set the input mode. Note that a pattern facet is a hard restriction on the lexical value of an instance data node, and
can specify different restrictions for different parts of the data item. Attribute inputmode
is a soft hint about the kinds of characters that the user may most probably start to input
into the form control. Attribute inputmode
is provided in addition to pattern facets for the following reasons:
The set of allowable characters specified in a pattern may be so wide that it is not possible to deduce a reasonable input mode setting. Nevertheless, there frequently is a kind of characters that
will be input by the user with high probability. In such a case, inputmode
allows to set the input mode for the user's convenience.
In some cases, it would be possible to derive the input mode setting from the pattern because the set of characters allowed in the pattern closely corresponds to a set of characters covered by an
inputmode
attribute value. However, such a derivation would require a lot of data and calculations on the user agent.
Small devices may leave the checking of patterns to the server, but will easily be able to switch to those input modes that they support. Being able to make data entry for the user easier is of particular importance on small devices.
This is an example of a form for Japanese address input. It is shown in table form; it will be replaced by actual syntax in a later version of this specification.
| Caption: | inputmode |
|---|---|
| Family name | hiragana |
| (in kana) | katakana |
| Given name | hiragana |
| (in kana) | katakana |
| Zip code | latin digits |
| Address | hiragana |
| (in kana) | katakana |
| latin lowerCase | |
| Telephone | latin digits |
| Comments | user predictOn |
Version 1.0 of this specification was prepared by the W3C HTML Working Group. At the time of publication of the first edition, the members were:
Version 1.1 of this specification was produced by the W3C XHTML2 Working Group. At the time of publication, the members were:
Thanks to Gary Adams (Sun Microsystems), Jonny Axelsson (Metastasis design), Peter Chen (Philips), Dan Connolly (W3C), John Cowan (Reuters), Martin J. Dürst (W3C), Johan Hjelm (Ericsson), Ian Jacobs (W3C), Susan Lesch (W3C), Louis Theran (Nokia), Quinton Zondervan (Lotus), members of the W3C Mobile Access Interest Group, the W3C Synchronized Multimedia Working Group, the W3C WAI Protocols and Formats Working Group, and the Open Mobile Alliance, for contributing, reviewing and commenting on this document.
This appendix is normative.
The DTD Implementation of XHTML Basic 1.1 is contained in this appendix. There are direct links to the various files, and the files are also contained in the "Gzip'd TAR" and "Zip" archives linked to at the top of this document. Please note that the files targeted by the "this version" links may change slowly over time if W3C publishes new Recommendations.
This section contains the SGML Open Catalog-format definition of the public identifiers for XHTML Basic.
You can download this version of this file from http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/xhtml-basic11.cat. The latest version is available at http://www.w3.org/MarkUp/DTD/xhtml-basic11.cat.
-- .......................................................................... -- -- File catalog ............................................................ -- -- XHTML Basic Catalog Data File Revision: $Id: index.html,v 1.1 2008/07/26 17:02:25 jules Exp $ SMI See "Entity Management", SGML Open Technical Resolution 9401 for detailed information on supplying and using catalog data. This document is available from OASIS at URL: <http://www.oasis-open.org/html/tr9401.html> -- -- .......................................................................... -- -- SGML declaration associated with XML .................................... -- OVERRIDE YES SGMLDECL "xml1.dcl" -- :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -- -- XHTML Basic DTD modular driver file ..................................... -- PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN" "xhtml-basic11.dtd" -- XHTML Basic framework module ............................................. -- PUBLIC "-//W3C//ENTITIES XHTML Basic 1.1 Document Model 1.0//EN" "xhtml-basic11-model-1.mod" -- XHTML Inputmode module ............................................. -- PUBLIC "-//W3C//ELEMENTS XHTML Inputmode 1.0//EN" "xhtml-inputmode-1.mod" -- End of catalog data ..................................................... -- -- .......................................................................... --
This section contains the driver for the XHTML Basic document type implementation as an XML DTD. It relies upon XHTML module implementations defined in [XHTMLMOD].
You can download this version of this file from http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/xhtml-basic11.dtd. The latest version is available at http://www.w3.org/MarkUp/DTD/xhtml-basic11.dtd.
<!-- XHTML Basic 1.1 DTD ...................................................... --> <!-- file: xhtml-basic11.dtd --> <!-- XHTML Basic 1.1 DTD This is XHTML Basic, a proper subset of XHTML. The Extensible HyperText Markup Language (XHTML) Copyright 1998-2007 World Wide Web Consortium (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University). All Rights Reserved. Permission to use, copy, modify and distribute the XHTML Basic DTD and its accompanying documentation for any purpose and without fee is hereby granted in perpetuity, provided that the above copyright notice and this paragraph appear in all copies. The copyright holders make no representation about the suitability of the DTD for any purpose. It is provided "as is" without expressed or implied warranty. Editors: Murray M. Altheim<EMAIL_ADDRESS>Peter Stark<EMAIL_ADDRESS>Shane McCarron<EMAIL_ADDRESS>Revision: $Id: index.html,v 1.1 2008/07/26 17:02:25 jules Exp $ --> <!-- This is the driver file for version 1.1 of the XHTML Basic DTD. This DTD is identified by the PUBLIC and SYSTEM identifiers: PUBLIC: "-//W3C//DTD XHTML Basic 1.1//EN" SYSTEM: "http://www.w3.org/MarkUp/DTD/xhtml-basic11.dtd" --> <!ENTITY % XHTML.version "-//W3C//DTD XHTML Basic 1.1//EN" > <!-- Use this URI to identify the default namespace: "http://www.w3.org/1999/xhtml" See the Qualified Names module for information on the use of namespace prefixes in the DTD. --> <!ENTITY % NS.prefixed "IGNORE" > <!ENTITY % XHTML.prefix "" > <!-- Reserved for use with the XLink namespace: --> <!ENTITY % XLINK.xmlns "" > <!ENTITY % XLINK.xmlns.attrib "" > <!-- For example, if you are using XHTML Basic 1.1 directly, use the public identifier in the DOCTYPE declaration, with the namespace declaration on the document element to identify the default namespace: <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-basic11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > ... </html> --> <!-- reserved for future use with document profiles --> <!ENTITY % XHTML.profile "" > <!-- Bidirectional Text features This feature-test entity is used to declare elements and attributes used for bidirectional text support. --> <!ENTITY % XHTML.bidi "IGNORE" > <?doc type="doctype" role="title" { XHTML Basic 1.1 } ?> <!-- :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --> <!ENTITY % xhtml-events.module "INCLUDE" > <!ENTITY % xhtml-bdo.module "%XHTML.bidi;" > <!-- Inline Style Module ........................................ --> <!ENTITY % xhtml-inlstyle.module "INCLUDE" > <![%xhtml-inlstyle.module;[ <!ENTITY % xhtml-inlstyle.mod PUBLIC "-//W3C//ELEMENTS XHTML Inline Style 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-inlstyle-1.mod" > %xhtml-inlstyle.mod;]]> <!ENTITY % xhtml-model.mod PUBLIC "-//W3C//ENTITIES XHTML Basic 1.1 Document Model 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-basic11-model-1.mod" > <!ENTITY % xhtml-framework.mod PUBLIC "-//W3C//ENTITIES XHTML Modular Framework 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-framework-1.mod" > %xhtml-framework.mod; <!ENTITY % pre.content "( #PCDATA | %InlStruct.class; %InlPhras.class; %Anchor.class; %Inline.extra; )*" > <!ENTITY % xhtml-text.mod PUBLIC "-//W3C//ELEMENTS XHTML Text 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-text-1.mod" > %xhtml-text.mod; <!ENTITY % xhtml-hypertext.mod PUBLIC "-//W3C//ELEMENTS XHTML Hypertext 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-hypertext-1.mod" > %xhtml-hypertext.mod; <!ENTITY % xhtml-list.mod PUBLIC "-//W3C//ELEMENTS XHTML Lists 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-list-1.mod" > %xhtml-list.mod; <!-- Add in the value attribute to the li element --> <!ATTLIST %li.qname; value %Number.datatype; #IMPLIED > <!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --> <!-- Scripting Module ........................................... --> <!ENTITY % xhtml-script.module "INCLUDE" > <![%xhtml-script.module;[ <!ENTITY % xhtml-script.mod PUBLIC "-//W3C//ELEMENTS XHTML Scripting 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-script-1.mod" > %xhtml-script.mod;]]> <!-- Style Sheets Module ......................................... --> <!ENTITY % xhtml-style.module "INCLUDE" > <![%xhtml-style.module;[ <!ENTITY % xhtml-style.mod PUBLIC "-//W3C//ELEMENTS XHTML Style Sheets 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-style-1.mod" > %xhtml-style.mod;]]> <!-- Image Module ............................................... --> <!ENTITY % xhtml-image.module "INCLUDE" > <![%xhtml-image.module;[ <!ENTITY % xhtml-image.mod PUBLIC "-//W3C//ELEMENTS XHTML Images 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-image-1.mod" > %xhtml-image.mod;]]> <!-- Tables Module ............................................... --> <!ENTITY % xhtml-table.module "INCLUDE" > <![%xhtml-table.module;[ <!ENTITY % xhtml-table.mod PUBLIC "-//W3C//ELEMENTS XHTML Basic Tables 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-basic-table-1.mod" > %xhtml-table.mod;]]> <!-- Forms Module ............................................... --> <!ENTITY % xhtml-form.module "INCLUDE" > <![%xhtml-form.module;[ <!ENTITY % xhtml-form.mod PUBLIC "-//W3C//ELEMENTS XHTML Forms 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-form-1.mod" > %xhtml-form.mod;]]> <!-- Presentation Module ........................................ --> <!ENTITY % xhtml-pres.module "INCLUDE" > <![%xhtml-pres.module;[ <!ENTITY % xhtml-pres.mod PUBLIC "-//W3C//ELEMENTS XHTML Presentation 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-pres-1.mod" > %xhtml-pres.mod;]]> <!-- Link Element Module ........................................ --> <!ENTITY % xhtml-link.module "INCLUDE" > <![%xhtml-link.module;[ <!ENTITY % xhtml-link.mod PUBLIC "-//W3C//ELEMENTS XHTML Link Element 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-link-1.mod" > %xhtml-link.mod;]]> <!-- Document Metainformation Module ............................ --> <!ENTITY % xhtml-meta.module "INCLUDE" > <![%xhtml-meta.module;[ <!ENTITY % xhtml-meta.mod PUBLIC "-//W3C//ELEMENTS XHTML Metainformation 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-meta-1.mod" > %xhtml-meta.mod;]]> <!-- Base Element Module ........................................ --> <!ENTITY % xhtml-base.module "INCLUDE" > <![%xhtml-base.module;[ <!ENTITY % xhtml-base.mod PUBLIC "-//W3C//ELEMENTS XHTML Base Element 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-base-1.mod" > %xhtml-base.mod;]]> <!-- Param Element Module ....................................... --> <!ENTITY % xhtml-param.module "INCLUDE" > <![%xhtml-param.module;[ <!ENTITY % xhtml-param.mod PUBLIC "-//W3C//ELEMENTS XHTML Param Element 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-param-1.mod" > %xhtml-param.mod;]]> <!-- Embedded Object Module ..................................... --> <!ENTITY % xhtml-object.module "INCLUDE" > <![%xhtml-object.module;[ <!ENTITY % xhtml-object.mod PUBLIC "-//W3C//ELEMENTS XHTML Embedded Object 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-object-1.mod" > %xhtml-object.mod;]]> <!-- Inputmode Attribute Module .................................. --> <!ENTITY % xhtml-inputmode.module "INCLUDE" > <![%xhtml-inputmode.module;[ <!ENTITY % xhtml-inputmode.mod PUBLIC "-//W3C//ELEMENTS XHTML Inputmode 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-inputmode-1.mod" > %xhtml-inputmode.mod;]]> <!-- Target Attribute Module .................................... --> <!ENTITY % xhtml-target.module "INCLUDE" > <![%xhtml-target.module;[ <!ENTITY % xhtml-target.mod PUBLIC "-//W3C//ELEMENTS XHTML Target 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-target-1.mod" > %xhtml-target.mod;]]> <!ENTITY % xhtml-struct.mod PUBLIC "-//W3C//ELEMENTS XHTML Document Structure 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-struct-1.mod" > %xhtml-struct.mod; <!-- end of XHTML Basic 1.1 DTD ........................................... -->
An XHTML Family Document Type (such as XHTML Basic) must define the content model that it uses. This is done through a separate content model module that is instantiated by the XHTML Modular Framework. The content model module and the XHTML Basic Driver (above) work together to customize the module implementations to the document type's specific requirements. The content model module for XHTML Basic is defined below:
You can download this version of this file from http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/xhtml-basic11-model-1.mod. The latest version is available at http://www.w3.org/MarkUp/DTD/xhtml-basic11-model-1.mod.
<!-- ....................................................................... --> <!-- XHTML Basic 1.1 Document Model Module .................................... --> <!-- file: xhtml-basic11-model-1.mod This is XHTML Basic, a proper subset of XHTML. Copyright 1998-2007 W3C (MIT, ERCIM, Keio), All Rights Reserved. Revision: $Id: index.html,v 1.1 2008/07/26 17:02:25 jules Exp $ SMI This DTD module is identified by the PUBLIC and SYSTEM identifiers: PUBLIC "-//W3C//ENTITIES XHTML Basic 1.1 Document Model 1.0//EN" SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-basic11-model-1.mod" Revisions: (none) ....................................................................... --> <!-- XHTML Basic Document Model This module describes the groupings of elements that make up common content models for XHTML elements. --> <!-- Optional Elements in head .............. --> <!ENTITY % HeadOpts.mix "( %script.qname; | %style.qname; | %meta.qname; | %link.qname; | %object.qname; )*" > <!-- script and noscript are used to contain scripts and alternative content --> <!ENTITY % Script.class "| %script.qname; | %noscript.qname;" > <!-- Miscellaneous Elements ................. --> <!ENTITY % Misc.extra "" > <!-- These elements are neither block nor inline, and can essentially be used anywhere in the document body. --> <!ENTITY % Misc.class "%Script.class; %Misc.extra;" > <!-- Inline Elements ........................ --> <!ENTITY % InlStruct.class "%br.qname; | %span.qname;" > <!ENTITY % InlPhras.class "| %em.qname; | %strong.qname; | %dfn.qname; | %code.qname; | %samp.qname; | %kbd.qname; | %var.qname; | %cite.qname; | %abbr.qname; | %acronym.qname; | %q.qname;" > <!ENTITY % InlPres.class "| %tt.qname; | %i.qname; | %b.qname; | %big.qname; | %small.qname; | %sub.qname; | %sup.qname;" > <!ENTITY % I18n.class "" > <!ENTITY % Anchor.class "| %a.qname;" > <!ENTITY % InlSpecial.class "| %img.qname; | %object.qname;" > <!ENTITY % InlForm.class "| %input.qname; | %select.qname; | %textarea.qname; | %label.qname; | %button.qname;" > <!ENTITY % Inline.extra "" > <!ENTITY % Inline.class "%InlStruct.class; %InlPhras.class; %InlPres.class; %Anchor.class; %InlSpecial.class; %InlForm.class; %Inline.extra;" > <!ENTITY % InlNoAnchor.class "%InlStruct.class; %InlPhras.class; %InlPres.class; %InlSpecial.class; %InlForm.class; %Inline.extra;" > <!ENTITY % InlNoAnchor.mix "%InlNoAnchor.class; %Misc.class;" > <!ENTITY % Inline.mix "%Inline.class; %Misc.class;" > <!-- Block Elements ......................... --> <!ENTITY % Heading.class "%h1.qname; | %h2.qname; | %h3.qname; | %h4.qname; | %h5.qname; | %h6.qname;" > <!ENTITY % List.class "%ul.qname; | %ol.qname; | %dl.qname;" > <!ENTITY % Table.class "| %table.qname;" > <!ENTITY % Form.class "| %form.qname;" > <!ENTITY % Fieldset.class "| %fieldset.qname;" > <!ENTITY % BlkStruct.class "%p.qname; | %div.qname;" > <!ENTITY % BlkPhras.class "| %pre.qname; | %blockquote.qname; | %address.qname;" > <!ENTITY % BlkPres.class "| %hr.qname;" > <!ENTITY % BlkSpecial.class "%Table.class; %Form.class; %Fieldset.class;" > <!ENTITY % Block.extra "" > <!ENTITY % Block.class "%BlkStruct.class; %BlkPhras.class; %BlkPres.class; %BlkSpecial.class; %Block.extra;" > <!ENTITY % Block.mix "%Heading.class; | %List.class; | %Block.class; %Misc.class;" > <!-- All Content Elements ................... --> <!-- declares all content except tables --> <!ENTITY % FlowNoTable.mix "%Heading.class; | %List.class; | %BlkStruct.class; %BlkPhras.class; %Form.class; %Block.extra; | %Inline.class; %Misc.class;" > <!ENTITY % Flow.mix "%Heading.class; | %List.class; | %Block.class; | %Inline.class; %Misc.class;" > <!-- end of xhtml-basic11-model-1.mod -->
Finally, we define the new inputmode attribute module.
You can download this version of this file from http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/xhtml-inputmode-1.mod. The latest version is available at http://www.w3.org/MarkUp/DTD/xhtml-inputmode-1.mod.
<!-- ...................................................................... --> <!-- XHTML Inputmode Module .............................................. --> <!-- file: xhtml-inputmode-1.mod This is XHTML, a reformulation of HTML as a modular XML application. Copyright 1998-2007 W3C (MIT, ERCIM, Keio), All Rights Reserved. Revision: $Id: index.html,v 1.1 2008/07/26 17:02:25 jules Exp $ This DTD module is identified by the PUBLIC and SYSTEM identifiers: PUBLIC "-//W3C//ELEMENTS XHTML Inputmode 1.0//EN" SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-inputmode-1.mod" Revisions: (none) ....................................................................... --> <!-- Inputmode inputmode This module declares the 'inputmode' attribute used for suggesting the input mode associated with an input or textarea element. --> <!-- render in this frame --> <!ENTITY % Inputmode.datatype "CDATA" > <!-- add 'inputmode' attribute to 'input' element --> <!ATTLIST %input.qname; inputmode %Inputmode.datatype; #IMPLIED > <!-- add 'inputmode' attribute to 'textarea' element --> <!ATTLIST %textarea.qname; inputmode %Inputmode.datatype; #IMPLIED > <!-- end of xhtml-inputmode-1.mod -->


Defines functions that can be used to collect provenance as an R script executes or during a console session. The output is a text file in PROV-JSON format.
| Version: | 1.0.2 |
| Depends: | R (≥ 3.5.0) |
| Imports: | curl, digest, ggplot2, grDevices, gtools, jsonlite, knitr, methods, sessioninfo, tools, utils, XML |
| Suggests: | roxygen2, testthat |
| Published: | 2018-11-30 |
| Author: | Barbara Lerner [aut, cre], Emery Boose [aut], Elizabeth Fong [aut], Luis Perez [aut], Thomas Pasquier [ctb], Matthew Lau [ctb], Yada Pruksachatkun [ctb], Alex Liu [ctb], Moe Pwint Phyu [ctb], Connor Gregorich-Trevor [ctb], Aaron Ellison [res], Margo Seltzer [res], Joe Wonsil [res], Orenna Brand [res] |
| Maintainer: | Barbara Lerner <blerner at mtholyoke.edu> |
| BugReports: | https://github.com/End-to-end-provenance/rdtLite/issues |
| License: | GPL-3 | file LICENSE |
| Copyright: | President and Fellows of Harvard College, Trustees of Mount Holyoke College |
| URL: | https://github.com/End-to-end-provenance/rdtLite |
| NeedsCompilation: | no |
| Citation: | rdtLite citation info |
| Materials: | README NEWS |
| CRAN checks: | rdtLite results |
| Reference manual: | rdtLite.pdf |
| Package source: | rdtLite_1.0.2.tar.gz |
| Windows binaries: | r-devel: rdtLite_1.0.2.zip, r-release: rdtLite_1.0.2.zip, r-oldrel: not available |
| OS X binaries: | r-release: rdtLite_1.0.2.tgz, r-oldrel: not available |
Please use the canonical form https://CRAN.R-project.org/package=rdtLite to link to this page.


Board Game Enthusiast, Amateur Beer Snob, Movie Buff, Fan of Female Folk Singers with Raspy Voices, Baseball Fanatic
Experience
Web Developer - Third Rail Creative
June 2015 - Present
Third Rail Creative is a full-service, nationally recognized advertising and marketing company. My role here consists of creating rich, responsive front-end experiences for our clients, including Charles Schwab and Intuit. During my tenure as lead developer, I've set up the company's development to deliverables process and created an internal documentation application.
Web Developer - Lifesize
Dec 2014 - June 2015
LifeSize is a pioneer and world leader in high-definition video collaboration. Designed to make video conferencing truly universal, LifeSize solutions are simple to buy, adopt, support and use. Offering video conferencing systems and software applications as well as a full line of video infrastructure, available on premise or in the cloud, LifeSize is committed to Universal Video Collaboration. My primary role at Lifesize consists of creating and implementing new features for the Lifesize Cloud Web Interface as well as creating functional UI prototypes in collaboration with the UI/UX team.
MakerSquare - Web Dev Student
Jun 2014 - Oct 2014
Makersquare is an immersive 12 week accelerated learning program designed to give participants the skills necessary to create web applications from the ground up. The program teaches core skills in Ruby, Javascript, HTML and CSS. Students
also learn how to tie these languages into functional web applications through the use of the Ruby on Rails Framework.


|
MyExperiment RDF beta
|
Functions for generating the property/values pairs for myExperiment RDF entities. More...
Go to the source code of this file.
Functions | |
| getEntityURI ($type, $id, $entity) | |
| Determine the URI for an entity from its type, ID and other fields retrieved from a database query. | |
| getRequester ($mship) | |
| Get the URI for either the User who requested to join a Group or the Group that requested a user join it. | |
| getRequesterTime ($mship) | |
| Get the datetime for when membership to a Group was requested. | |
| getAccepter ($mship) | |
| Get the URI for either the User who accepted to join a Group or the Group that accepted a user join it. | |
| getAccepterTime ($mship) | |
| Get the datetime for when membership to a Group was accepted. | |
| getMembers ($group) | |
| Generates a set of sioc:has_member RDF properties for all the members of a specified Group. | |
| getMemberships ($user) | |
| Generates a set of mebase:has-membership RDF properties for all the Memberships of a User. | |
| getFriendships ($user) | |
| Generates a set of mebase:has-friendship RDF properties for all the Friendships of a User. | |
| getFavourites ($user) | |
| Generates a set of meannot:has-favourite RDF properties for all the Favourites of a User. | |
| getTaggings ($tag) | |
| Generates a set of meannot:for-tagging RDF properties for all the Taggings (uses) of a Tag. | |
| getPolicyURI ($contrib, $type) | |
| Get the URI for the Policy of an entity of a specified type. | |
| getThumbnail ($workflow) | |
| Get the thumbnail preview URL for a Workflow or WorkflowVersion. | |
| getThumbnailBig ($workflow) | |
| Get the big thumbnail preview URL for a Workflow or WorkflowVersion. | |
| getPreview ($workflow) | |
| Get the full preview URL for a Workflow or WorkflowVersion. | |
| getSVG ($workflow) | |
| Get the SVG preview URL for a Workflow or WorkflowVersion. | |
| getPreviewURL ($workflow, $type="") | |
| Get a specified type of preview URL for a Workflow or WorkflowVersion. | |
| getDownloadURL ($entity, $type) | |
| Get the download URL for an entity that has a downloadable item. (E.g. File, FileVersion, Workflow or WorkflowVersion). | |
| getCurrentVersion ($entity, $type) | |
| Get the URI for the current/latest version of a versioned entity (e.g. Workflow, File or Pack). | |
| getIsCurrentVersion ($version) | |
| Test whether the specified version is the current/latest version of a particular versioned entity (e.g. Workflow, File or Pack). | |
| getVersions ($entity, $type) | |
| Return RDF/XML mebase:has-version (or mepack:has-snapshot for Packs) properties for all versions of a versioned entity (e.g. Workflow, File or Pack). | |
| getPictureURL ($user) | |
| Return the URL for the picture (avatar) of a specified User (or the default avatar URL if they have no picture). | |
| getSIOCAndFOAFName ($user) | |
| Return RDF/XML for the sioc:name and foaf:name properties (i.e. the User's full name) for a specified User. | |
| getMboxSHA1Sum ($user) | |
| Get the SHA1 sum for a User's email address. So they can be uniquely identified by someone who already has their email address. | |
| getMailtoProfile ($user) | |
| Generate a mailto URL for a specified User's profile email address. | |
| getResidence ($user) | |
| Attempt to generate RDF/XML dbpedia:residence properties referencing existing DBPedia location URIs from the location_city and location_country values specified free-hand in User's profiles. (A small number of properties generated may not reference existing DBPedia location URIs). | |
| getHomepage ($entity, $type) | |
| Get the URL for the HTML homepage for a specified entity. | |
| getFilename ($entity, $type) | |
| Get the full filename with extension for a file associated with an entity. | |
| getPackEntries ($pack) | |
| Generate mepack:has-entry RDF/XML properties for all the entries (i.e. LocalPackEntry, RemotePackEntry and RelationshipEntry) of a specified Pack. | |
| getOutput ($job) | |
| Generate an RDF/XML meexp:Data entity that references a piece of data generate as an output from an Experiment Job. | |
| getInput ($job) | |
| Generate an RDF/XML meexp:Data entity that references a piece of data that is an input to an Experiment Job. | |
| getRunnable ($job) | |
| Get the URI of the Runnable entity of a specified Experiment Job. (I.e. a Workflow or WorkflowVersion). | |
| getRunner ($job) | |
| Get the path of the URI (to which the $datauri can be prepended) for the Runner (e.g. TavernaEnactor) of a specified Experiment Job. | |
| getProxyFor ($pack_entry) | |
| Determine either a myExperiment entity URI or generate an rdf:Description RDF/XML for a remote entity. Either of which represents what the PackEntry is refering to. | |
| getDataflow ($entity, $type) | |
| Get the URI for the Dataflow for a specified Workflow / WorkflowVersion, assuming that the user requesting RDF has permission to download the Workflow / WorkflowVersion entity. If available and not already retrieved, also write the Dataflow RDF/XML out to a local file. | |
| getDataflowComponents ($entity, $type, $retrieve=TRUE) | |
| Get the URI for the Dataflow for a specified Workflow / WorkflowVersion. If available and not already retrieved, also write the Dataflow RDF/XML out to a local file. | |
| getLicenseAttributes ($license) | |
| Get the Creative Commons RDF/XML License attribute properties for a specified License. | |
| getAnnotations ($entity, $type) | |
| Generate RDF/XML properties for annotations of all types for a specified entity. | |
| getPredicateRelations ($entity) | |
| Generates RDF/XML properties for relationships between the specified Predicate and other Predicates. (Currently this is just rdfs:subClassOf properties but this function will be expanded and rewritten when Predicate relationships are fully deployed). | |
| getRelationshipSPO ($entity) | |
| Generate an associative array containing the subject, predicate and object representing the Relationship between two entities. | |
| getRelationshipURN ($spo) | |
| Generate a version 5 (RFC4122) UUID to provide a URN for the specific Relationship. Using the URIs for the subject, predicate and object of the Relationship. | |
| getRelationship ($entity) | |
| Generate an ore:ProxyFor RDF/XML property with an encapsulated mepack:Relationship entity for a specified Relationship entity. | |
| getRelationshipSubject ($entity) | |
| Get the URI for the subject of a Relationship entity. | |
| getRelationshipObject ($entity) | |
| Get the URI for the object of a Relationship entity. | |
| getRelationshipPredicate ($entity) | |
| Get the URI for the predicate of a Relationship entity. | |
| getRelationshipNode ($id, $type) | |
| Get the URI for a node (subject or object) of a Relationship entity. | |
| getPredicate ($id) | |
| Generate the URI for a predicate based on its ID value in the database. | |
| generatePredicatesRDF ($id) | |
| Generate RDF/XML entities for all predicates in a user-defined Ontology. | |
| getStaticOntologyDetails ($entity) | |
| Get static (i.e. the same for every user-generated Ontology) RDF/XML properties for user-generated Ontology. | |
| getOREAggregatedResources ($entity, $type) | |
| Get ore:aggregates RDF/XML properties for all items that a specified entity (e.g. Experiment, Pack or PackSnapshot) aggregates. | |
| getOREDescribedBy ($entity, $type) | |
| Get the URI for the RDF graph representation of a specific aggregating entity. | |
| getPolicy ($policy) | |
| Generate the RDF/XML properties for a specified access rights Policy entity. | |
| getContributorPermissions ($contrib_type, $contrib_id) | |
| Generate the contributor permissions RDF/XML for a specified Policy. | |
| getShareModeAccesses ($sm) | |
| Generate RDF/XML for a Policy with a specific share mode. | |
| getUpdateModeAccesses ($um, $sm) | |
| Generate RDF/XML for a Policy with a specific update mode. (Also depependent on the Policy's share mode). | |
| getPermissionAccesses ($perms) | |
| Generate RDF/XML for explicitly defined permissions for a Policy. | |
| generateDataflows ($dataflows, $ent_uri) | |
| Generate RDF/XML for the Dataflow (and potentially nested Dataflows thereof) of a particular Workflow or WorkflowVersion. |
Functions for generating the property/values pairs for myExperiment RDF entities.
Functions for generating the property/value pairs for myExperiment RDF entities, as specified by the $mappings associative array in inc/config/data.inc.php.
Definition in file property.inc.php.
| generateDataflows | ( | $ | dataflows, |
| $ | ent_uri | ||
| ) |
Generate RDF/XML for the Dataflow (and potentially nested Dataflows thereof) of a particular Workflow or WorkflowVersion.
| $dataflows | A multidimensional associative array of one or more Dataflows (where additional Dataflows are nested within the main Dataflow) that contains information about the Dataflows and the components which they contain. |
| $ent_uri | A string containing the entity URI of the Workflow or WorkflowVersion that has the Dataflow(s) specified. |
Definition at line 1226 of file property.inc.php.
| generatePredicatesRDF | ( | $ | id | ) |
Generate RDF/XML entities for all predicates in a user-defined Ontology.
| $id | An integer containing the database ID of the user-defined Ontology. |
Definition at line 1000 of file property.inc.php.
| getAccepter | ( | $ | mship | ) |
Get the URI for either the User who accepted to join a Group or the Group that accepted a user join it.
| $mship | An associative array of database fields mapped to values for a Membership entity. |
Definition at line 132 of file property.inc.php.
| getAccepterTime | ( | $ | mship | ) |
Get the datetime for when membership to a Group was accepted.
| $mship | An associative array of database fields mapped to values for a Membership entity. |
Definition at line 153 of file property.inc.php.
| getAnnotations | ( | $ | entity, |
| $ | type | ||
| ) |
Generate RDF/XML properties for annotations of all types for a specified entity.
| $entity | An associative array of database fields mapped to values for an entity. |
| $type | A string containing the type of the entity specified. |
Definition at line 822 of file property.inc.php.
| getContributorPermissions | ( | $ | contrib_type, |
| $ | contrib_id | ||
| ) |
Generate the contributor permissions RDF/XML for a specified Policy.
| $contrib_type | A string containing the type of Contribution the Policy is for. |
| $contrib_id | A string containing the ID of the Contribution the Policy is for. |
Definition at line 1123 of file property.inc.php.
| getCurrentVersion | ( | $ | entity, |
| $ | type | ||
| ) |
Get the URI for the current/latest version of a versioned entity (e.g. Workflow, File or Pack).
| $entity | An associative array of database fields mapped to values for a versioned entity. |
| $type | A string containing the type of versione entity (e.g. Workflow, File or Pack). |
Definition at line 411 of file property.inc.php.
| getDataflow | ( | $ | entity, |
| $ | type | ||
| ) |
Get the URI for the Dataflow for a specified Workflow / WorkflowVersion, assuming that the user requesting RDF has permission to download the Workflow / WorkflowVersion entity. If available and not already retrieved, also write the Dataflow RDF/XML out to a local file.
| $entity | An associative array of database fields mapped to values for a Workflow or WorkflowVersion. |
| $type | A string containing the type of the entity specified, (i.e. Workflow or WorkflowVersion). |
Definition at line 750 of file property.inc.php.
| getDataflowComponents | ( | $ | entity, |
| $ | type, | ||
| $ | retrieve = TRUE |
||
| ) |
Get the URI for the Dataflow for a specified Workflow / WorkflowVersion. If available and not already retrieved, also write the Dataflow RDF/XML out to a local file.
| $entity | An associative array of database fields mapped to values for a Workflow or WorkflowVersion. |
| $type | A string containing the type of the entity specified, (i.e. Workflow or WorkflowVersion). |
| $retrieve | A boolean. TRUE if the Dataflow RDF/XML should be return, FALSE if the URI for the Dataflow should be returned instead. |
Definition at line 770 of file property.inc.php.
| getDownloadURL | ( | $ | entity, |
| $ | type | ||
| ) |
Get the download URL for an entity that has a downloadable item. (E.g. File, FileVersion, Workflow or WorkflowVersion).
| $entity | An associative array of database fields mapped to values for an entity with a downloadable item. |
| $type | A string containing the type of entity. |
Definition at line 385 of file property.inc.php.
| getEntityURI | ( | $ | type, |
| $ | id, | ||
| $ | entity | ||
| ) |
Determine the URI for an entity from its type, ID and other fields retrieved from a database query.
| $type | A string containing the type of entity for which the URI is to be determined. |
| $id | A inetger containing the ID of the entity for which the URI is to be determined. |
| $entity | An associative arry containing database fields mapped to values for the entity whose URI is to be determined. |
Definition at line 25 of file property.inc.php.
| getFavourites | ( | $ | user | ) |
Generates a set of meannot:has-favourite RDF properties for all the Favourites of a User.
| $user | An associative array of database fields mapped to values for a User entity. |
Definition at line 237 of file property.inc.php.
| getFilename | ( | $ | entity, |
| $ | type | ||
| ) |
Get the full filename with extension for a file associated with an entity.
| $entity | An associative array of database fields mapped to values for an entity. |
| $type | A string containing the type of the entity specified. |
Definition at line 593 of file property.inc.php.
| getFriendships | ( | $ | user | ) |
Generates a set of mebase:has-friendship RDF properties for all the Friendships of a User.
| $user | An associative array of database fields mapped to values for a User entity. |
Definition at line 215 of file property.inc.php.
| getHomepage | ( | $ | entity, |
| $ | type | ||
| ) |
Get the URL for the HTML homepage for a specified entity.
| $entity | An associative array of database fields mapped to values for an entity. |
| $type | A string containing the type of the entity specified. |
Definition at line 575 of file property.inc.php.
| getInput | ( | $ | job | ) |
Generate an RDF/XML meexp:Data entity that references a piece of data that is an input to an Experiment Job.
| $job | An associative array of database fields mapped to values for a Job. |
Definition at line 674 of file property.inc.php.
| getIsCurrentVersion | ( | $ | version | ) |
Test whether the specified version is the current/latest version of a particular versioned entity (e.g. Workflow, File or Pack).
| $version | An associative array of database fields mapped to values for a version of a versioned entity. |
Definition at line 426 of file property.inc.php.
| getLicenseAttributes | ( | $ | license | ) |
Get the Creative Commons RDF/XML License attribute properties for a specified License.
| $license | An associative array of database fields mapped to values for a License. |
Definition at line 799 of file property.inc.php.
| getMailtoProfile | ( | $ | user | ) |
Generate a mailto URL for a specified User's profile email address.
| $user | An associative array of database fields mapped to values for a User. |
Definition at line 533 of file property.inc.php.
| getMboxSHA1Sum | ( | $ | user | ) |
Get the SHA1 sum for a User's email address. So they can be uniquely identified by someone who already has their email address.
| $user | An associative array of database fields mapped to values for a User. |
Definition at line 519 of file property.inc.php.
| getMembers | ( | $ | group | ) |
Generates a set of sioc:has_member RDF properties for all the members of a specified Group.
| $group | An associative array of database fields mapped to values for a Group entity. |
Definition at line 172 of file property.inc.php.
| getMemberships | ( | $ | user | ) |
Generates a set of mebase:has-membership RDF properties for all the Memberships of a User.
| $user | An associative array of database fields mapped to values for a User entity. |
Definition at line 193 of file property.inc.php.
| getOREAggregatedResources | ( | $ | entity, |
| $ | type | ||
| ) |
Get ore:aggregates RDF/XML properties for all items that a specified entity (e.g. Experiment, Pack or PackSnapshot) aggregates.
| $entity | An associative array of database fields mapped to values for an entity that aggregates other entities. |
| $type | The type of entity that aggregates other entities. |
Definition at line 1039 of file property.inc.php.
| getOREDescribedBy | ( | $ | entity, |
| $ | type | ||
| ) |
Get the URI for the RDF graph representation of a specific aggregating entity.
| $entity | An associative array of database fields mapped to values for an entity that aggregates other entities. |
| $type | The type of entity for which the URI of the RDF graph representation needs to be determined. |
Definition at line 1086 of file property.inc.php.
| getOutput | ( | $ | job | ) |
Generate an RDF/XML meexp:Data entity that references a piece of data generate as an output from an Experiment Job.
| $job | An associative array of database fields mapped to values for a Job. |
Definition at line 653 of file property.inc.php.
| getPackEntries | ( | $ | pack | ) |
Generate mepack:has-entry RDF/XML properties for all the entries (i.e. LocalPackEntry, RemotePackEntry and RelationshipEntry) of a specified Pack.
| $pack | An associative array of database fields mapped to values for a Pack. |
Definition at line 607 of file property.inc.php.
| getPermissionAccesses | ( | $ | perms | ) |
Generate RDF/XML for explicitly defined permissions for a Policy.
| $perms | An array containing a list of explicitly defined permissions for a Policy. |
Definition at line 1191 of file property.inc.php.
| getPictureURL | ( | $ | user | ) |
Return the URL for the picture (avatar) of a specified User (or the default avatar URL if they have no picture).
| $user | An associative array of database fields mapped to values for a User. |
Definition at line 489 of file property.inc.php.
| getPolicy | ( | $ | policy | ) |
Generate the RDF/XML properties for a specified access rights Policy entity.
| $policy | An associative array of database fields mapped to values for a Policy entity. |
Definition at line 1099 of file property.inc.php.
| getPolicyURI | ( | $ | contrib, |
| $ | type | ||
| ) |
Get the URI for the Policy of an entity of a specified type.
| $contrib | An associative array of database fields mapped to values for a specified type of entity that is subclass of Contribution. |
| $type | A string containing the type of entity. |
Definition at line 283 of file property.inc.php.
| getPredicate | ( | $ | id | ) |
Generate the URI for a predicate based on its ID value in the database.
| $id | An integer containing the ID value of predicate in the database. |
Definition at line 985 of file property.inc.php.
| getPredicateRelations | ( | $ | entity | ) |
Generates RDF/XML properties for relationships between the specified Predicate and other Predicates. (Currently this is just rdfs:subClassOf properties but this function will be expanded and rewritten when Predicate relationships are fully deployed).
| $entity | An associative array of database fields mapped to values for an entity. |
Definition at line 852 of file property.inc.php.
| getPreview | ( | $ | workflow | ) |
Get the full preview URL for a Workflow or WorkflowVersion.
| $workflow | An associative array of database fields mapped to values for a Workflow or WorkflowVersion entity. |
Definition at line 334 of file property.inc.php.
| getPreviewURL | ( | $ | workflow, |
| $ | type = "" |
||
| ) |
Get a specified type of preview URL for a Workflow or WorkflowVersion.
| $workflow | An associative array of database fields mapped to values for a Workflow or WorkflowVersion entity. |
| $type | A string containing the type of preview URL to be generated. E.g. thumb, medium, full or svg. |
Definition at line 365 of file property.inc.php.
| getProxyFor | ( | $ | pack_entry | ) |
Determine either a myExperiment entity URI or generate an rdf:Description RDF/XML for a remote entity. Either of which represents what the PackEntry is refering to.
| $pack_entry | An associative array of database fields mapped to values for a LocalPackEntry or RemotePackEntry. |
Definition at line 725 of file property.inc.php.
| getRelationship | ( | $ | entity | ) |
Generate an ore:ProxyFor RDF/XML property with an encapsulated mepack:Relationship entity for a specified Relationship entity.
| $entity | An associative array of database fields mapped to values for a Relationship entity. |
Definition at line 905 of file property.inc.php.
| getRelationshipNode | ( | $ | id, |
| $ | type | ||
| ) |
Get the URI for a node (subject or object) of a Relationship entity.
| $id | The ID of the entity for which a URI needs to be determined. |
| $type | The type of entity for which a URI needs to be determined. |
Definition at line 962 of file property.inc.php.
| getRelationshipObject | ( | $ | entity | ) |
Get the URI for the object of a Relationship entity.
| $entity | An associative array of database fields mapped to values for a Relationship entity. |
Definition at line 933 of file property.inc.php.
| getRelationshipPredicate | ( | $ | entity | ) |
Get the URI for the predicate of a Relationship entity.
| $entity | An associative array of database fields mapped to values for a Relationship entity. |
Definition at line 946 of file property.inc.php.
| getRelationshipSPO | ( | $ | entity | ) |
Generate an associative array containing the subject, predicate and object representing the Relationship between two entities.
| $entity | An associative array of database fields mapped to values for a Relationship entity. |
Definition at line 878 of file property.inc.php.
| getRelationshipSubject | ( | $ | entity | ) |
Get the URI for the subject of a Relationship entity.
| $entity | An associative array of database fields mapped to values for a Relationship entity. |
Definition at line 920 of file property.inc.php.
| getRelationshipURN | ( | $ | spo | ) |
Generate a version 5 (RFC4122) UUID to provide a URN for the specific Relationship. Using the URIs for the subject, predicate and object of the Relationship.
| $spo | An associative array containing the URIs for the subject, predicate and object of a Relationship. |
Definition at line 891 of file property.inc.php.
| getRequester | ( | $ | mship | ) |
Get the URI for either the User who requested to join a Group or the Group that requested a user join it.
| $mship | An associative array of database fields mapped to values for a Membership entity. |
Definition at line 96 of file property.inc.php.
| getRequesterTime | ( | $ | mship | ) |
Get the datetime for when membership to a Group was requested.
| $mship | An associative array of database fields mapped to values for a Membership entity. |
Definition at line 114 of file property.inc.php.
| getResidence | ( | $ | user | ) |
Attempt to generate RDF/XML dbpedia:residence properties referencing existing DBPedia location URIs from the location_city and location_country values specified free-hand in User's profiles. (A small number of properties generated may not reference existing DBPedia location URIs).
| $user | An associative array of database fields mapped to values for a User. |
Definition at line 546 of file property.inc.php.
| getRunnable | ( | $ | job | ) |
Get the URI of the Runnable entity of a specified Experiment Job. (I.e. a Workflow or WorkflowVersion).
| $job | An associative array of database fields mapped to values for a Job. |
Definition at line 695 of file property.inc.php.
| getRunner | ( | $ | job | ) |
Get the path of the URI (to which the $datauri can be prepended) for the Runner (e.g. TavernaEnactor) of a specified Experiment Job.
| $job | An associative array of database fields mapped to values for a Job. |
Definition at line 712 of file property.inc.php.
| getShareModeAccesses | ( | $ | sm | ) |
Generate RDF/XML for a Policy with a specific share mode.
| $sm | An integer representing the share mode for which an RDF/XML representation is required. |
Definition at line 1139 of file property.inc.php.
| getSIOCAndFOAFName | ( | $ | user | ) |
Return RDF/XML for the sioc:name and foaf:name properties (i.e. the User's full name) for a specified User.
| $user | An associative array of database fields mapped to values for a User. |
Definition at line 504 of file property.inc.php.
| getStaticOntologyDetails | ( | $ | entity | ) |
Get static (i.e. the same for every user-generated Ontology) RDF/XML properties for user-generated Ontology.
| $entity | An associative array of database fields mapped to values for a Ontology entity. |
Definition at line 1023 of file property.inc.php.
| getSVG | ( | $ | workflow | ) |
Get the SVG preview URL for a Workflow or WorkflowVersion.
| $workflow | An associative array of database fields mapped to values for a Workflow or WorkflowVersion entity. |
Definition at line 348 of file property.inc.php.
| getTaggings | ( | $ | tag | ) |
Generates a set of meannot:for-tagging RDF properties for all the Taggings (uses) of a Tag.
| $tag | An associative array of database fields mapped to values for a Tag entity. |
Definition at line 259 of file property.inc.php.
| getThumbnail | ( | $ | workflow | ) |
Get the thumbnail preview URL for a Workflow or WorkflowVersion.
| $workflow | An associative array of database fields mapped to values for a Workflow or WorkflowVersion entity. |
Definition at line 306 of file property.inc.php.
| getThumbnailBig | ( | $ | workflow | ) |
Get the big thumbnail preview URL for a Workflow or WorkflowVersion.
| $workflow | An associative array of database fields mapped to values for a Workflow or WorkflowVersion entity. |
Definition at line 320 of file property.inc.php.
| getUpdateModeAccesses | ( | $ | um, |
| $ | sm | ||
| ) |
Generate RDF/XML for a Policy with a specific update mode. (Also depependent on the Policy's share mode).
| $um | An integer representing the update mode for which an RDF/XML representation is required. |
| $sm | An integer representing the share mode for which an RDF/XML representation is required. |
Definition at line 1169 of file property.inc.php.
| getVersions | ( | $ | entity, |
| $ | type | ||
| ) |
Return RDF/XML mebase:has-version (or mepack:has-snapshot for Packs) properties for all versions of a versioned entity (e.g. Workflow, File or Pack).
| $entity | An associative array of database fields mapped to values for a versioned entity. |
| $type | A string containing the type of versione entity (e.g. Workflow, File or Pack). |
Definition at line 456 of file property.inc.php.


Clock 2.0
Source
Clock.java (the main program), Needle.java (the Needle class)
Supported actions
- mouseEnter
- The message "Who made this clock?" will appear in the status bar
- mouseExit
- The status bar will be blank
- mouseDown
- The browser will load this page
Supported tags
Tags which affect the whole clock
num_lines
Numer of corners in the border around the clock.
Min: 3 Default: 12 Max:1000
sleep
The time (in milliseconds) the applet waits between each update.
Min: 5 Default: 1000 Max:20000
timezone
The GMT timezone that the clock will display (Sweden=1, England=0, Finland=2 etc).
Min: -12 Default: your local timezone Max: 12
If this tag is omitted the clock will display the local timezone.
clock_background_col
The color of the clockbackground.
Default: 207,207,207 (gray)
clock_background_border_col
The color of the border of the clockbackground.
Default: 207,207,207 (gray)
background_col
The color of the background.
Default: 192,192,192 (lightgray)
clock_background_border_col
The color of the border of the background.
Default: 192,192,192 (lightgray)
Tags which affect each needle
col
The color of the needle.
Default hour_col: 255,0,0 (red) minute_col: 0,255,0 (green) second_col: 0,0,255 (blue)
border_col
The color of the border of the needle.
Default hour_border_col: 0,0,0 (black) minute_border_col: 0,0,0 (black) second_border_col: 0,0,0 (black)
type
The type of the needle. 0=No needle, 1=Triangle, 2=Rectangle, 3=Romb. Default hour_type: 3 minute_type: 3 second_type: 3
width
The width of the needle.
Default hour_width: 7 minute_width: 5 second_width: 3
len
The length of the needle in % of the clock.
Default hour_len: 70 minute_len: 75 second_len: 90
These applets have been written by Nizze


Table Name: tabEmployee Loan Application
| Sr | Fieldname | Type | Label | Options |
|---|---|---|---|---|
| 1 | posting_date |
Date | Posting Date | |
| 2 | employee |
Link | Employee | Employee |
| 3 | employee_name |
Read Only | Employee Name |
employee.employee_name |
| 4 | column_break_2 |
Column Break | ||
| 5 | status |
Select | Status |
Open Approved Rejected |
| 6 | company |
Link | Company | Company |
| 7 | section_break_4 |
Section Break | Loan Info | |
| 8 | loan_type |
Link | Loan Type | Loan Type |
| 9 | loan_amount |
Currency | Loan Amount |
Company:company:default_currency |
| 10 | required_by_date |
Date | Required by Date | |
| 11 | column_break_7 |
Column Break | ||
| 12 | description |
Small Text | Reason | |
| 13 | repayment_info |
Section Break | Repayment Info | |
| 14 | repayment_method |
Select | Repayment Method |
Repay Fixed Amount per Period Repay Over Number of Periods |
| 15 | rate_of_interest |
Percent | Rate of Interest |
loan_type.rate_of_interest |
| 16 | total_payable_interest |
Currency | Total Payable Interest |
Company:company:default_currency |
| 17 | column_break_11 |
Column Break | ||
| 18 | repayment_amount |
Currency | Monthly Repayment Amount |
Company:company:default_currency |
| 19 | repayment_periods |
Int | Repayment Period in Months | |
| 20 | total_payable_amount |
Currency | Total Payable Amount |
Company:company:default_currency |
| 21 | amended_from |
Link | Amended From | Employee Loan Application |
Inherits from frappe.model.document.Document
Public API
/api/method/erpnext.hr.doctype.employee_loan_application.employee_loan_application.make_employee_loan
erpnext.hr.doctype.employee_loan_application.employee_loan_application.make_employee_loan (source_name, target_doc=None)
No docs


Descendants of Thomas Williams
[ Click on the red arrow for a shortcut to the list of family
trees
s Click on the
blue question mark for assistance in navigating among family trees
Thomas
WILLIAMS was
born about 1780. It is believed that
Thomas Williams came from Maryland to Greene County, PA, at an unknown date,
then in 1838 arrived in Tyler County, WV.
There is a Thomas Williams in Greene County, PA in the 1820 census.
Thomas was not located in the 1830 census in either Pennsylvania or (West)
Virginia. He does appear in the 1840
census living near Jacob and a Joseph Williams, who was possibly another
son.
The "History of the First
Baptist Church of Sistersville" notes in June 1838, Thomas Williams and
Serena, his wife, were presented as members in good standing at the Long Reach
Baptist Church. A history of Jacob Williams'
family in the Tyler County, WV history refers to Serena as a stepmother.
No death record for Thomas or
Serena has been located. They have not
been found in the 1850 census.
Another possible child: There
is also an Elizabeth Williams Scarbrough who is living next to Susanna and Levi
in the 1870 census of Monroe County. Was she connected to this Williams
family? Her birth year of 1835 would
not seem to fit this family unless Thomas married a second time.
Thomas WILLIAMS was married to
Serena (possibly Roberts). She may have been
a second wife. Thomas had the following
children:
I. Levi WILLIAMS was born on March 7, 1811. He died on February 12, 1879. Levi Williams died 12 Feb 1879 aged 67, born
Greene County PA. His will named widow
Lucinda, sons Jacob and Martin L., daughters Melissa Knowlton, Cyrene Devore,
Mary Devore, Serepta Williams and Emily Williams.
Levi appears
in Monroe County in 1860 and 1870. He
married in Tyler County, WV in 1841 to Lucinda Cooper. Jacob Williams married Susan Cooper in Tyler
County in 1840. I feel fairly certain
these were brothers of Susanna Williams.
In 1840 Tyler County census, Jacob Williams is living next to Joseph and
Thomas Williams. Thomas is the oldest
of the three and has a son in the household who would be the right age to be
Levi. There was also a Thomas Williams
in 1820 in Greene County PA who had children who would have fit the ages of
Susanna and Levi.
Levi WILLIAMS was married to Lucinda Cooper on September
1, 1841 in Tyler County, West Virginia.
Lucinda Cooper was born on December 29, 1823. She died on March 17, 1893 in Tyler County,
West Virginia. She was buried in Conner
Ridge Methodist Cemetery, Wayne Township, Monroe County, Ohio. Levi WILLIAMS and Lucinda Cooper had the
following children:
A. Charlotte
WILLIAMS was born in 1843 in Virginia.
B. Melissa
WILLIAMS was born on July 24, 1844.
She died on January 15, 1921 in Monroe County, Ohio. She was buried in Hartshorn Ridge Cemetery,
Graysville, Ohio.
Melissa
WILLIAMS was married to William Knowlton.
William Knowlton was born on July 24, 1835. He died on August 28, 1898 in Monroe County,
OH. He was buried in Hartshorn Ridge
Cemetery, Graysville, Ohio. Melissa
WILLIAMS and William Knowlton had the following children:
1. Levi P. Knowlton was born on January 13, 1861
in Monroe County, OH. He died on August
5, 1933 in Delaware, Ohio.
Levi
P. Knowlton was married to Sarah Hannah Hickinbotham on November 10, 1883 in
Monroe County OH. Sarah Hannah Hickinbotham
was born on February 21, 1864 in Monroe County, OH. She died on June 28, 1959 in Knox County, Ohio.
2. Sarah
N. Knowlton was born about 1862.
3. Nancy
J. Knowlton was born about 1865.
4. Mary
E. Knowlton was born in 1867. She died
in 1942. She was buried in Conner Ridge
Methodist Cemetery, Wayne Township, Monroe County, Ohio.
5. James
P. Knowlton was born about 1870.
6. H.
S. J. T. Knowlton was born about 1877.
7. Pomeroy
Knowlton was born about 1879. He
died in 1960. He was buried in Conner
Ridge Methodist Cemetery, Wayne Township, Monroe County, Ohio.
C. William
Thomas WILLIAMS was born on January 25, 1845. He died on January 20, 1847.
He was buried in Conner Ridge Methodist Cemetery, Wayne Township, Monroe
County, Ohio.
D. Jacob
WILLIAMS was born in 1848 in Ohio.
Jacob
WILLIAMS was married to Elizabeth Smith on August 23, 1868 in Monroe County OH
. Jacob WILLIAMS and Elizabeth Smith
had the following children:
1. John
R. WILLIAMS was born in 1872.
2. Pluma
L. WILLIAMS was born in 1878.
3. Levadia
WILLIAMS was born in 1878 in Monroe County OH, .
Levadia
WILLIAMS was married to George O. Ayers on January 18, 1901 in Monroe County
OH, . George O. Ayers was born
in 1879.
4. Albert
WILLIAMS was born in 1880.
Albert
WILLIAMS was married to Cora May Hogue on March 31, 1901 in Monroe County OH, .
5. Lucinda
WILLIAMS was born in 1882 in Monroe County OH, .
Lucinda
WILLIAMS was married to James Scales on December 31, 1899. James Scales was born in 1871 in Belmont
County OH, . Lucinda WILLIAMS and James
Scales had the following children:
a.
Lela Scales was born on June 8, 1901.
She died on December 23, 1901.
E. Sarena
(Cyrene) WILLIAMS was born in 1853 in Ohio. She died in 1930.
Sarena (Cyrene) WILLIAMS was married to Isaac W. Devore on September 29, 1874
in Monroe County OH. Isaac W. Devore
was born in 1853. He died in 1935. Sarena (Cyrene) WILLIAMS and Isaac W. Devore
had the following children:
1. Mary
E. Devore was born in 1876.
2. Sarepta E. Devore was born in 1878.
3. Parry
Devore was born in 1879. He died in
1959. He was buried in Conner Ridge
Methodist Cemetery, Wayne Township, Monroe County, Ohio.
Parry
Devore was married to Mollie Smith on September 15, 1900 in Monroe County OH. Mollie Smith was born in 1881 in Monroe
County, OH. She died in 1940.
4. Martin
L. Devore was born in 1882 in Monroe County OH.
Martin
L. Devore was married to Bessie P. Harmon on September 10, 1904 in Monroe
County OH. Bessie P. Harmon was
born in 1886 in Monroe County OH.
F. Martin L. WILLIAMS was born in 1855. He died in 1928. He was buried in Conner Ridge Methodist Cemetery, Wayne Township,
Monroe County, Ohio.
Martin L.
WILLIAMS was married to Catharine F.
Devore on January 9, 1876 in Monroe County OH. Martin L. WILLIAMS and Catharine F. Devore
had the following children:
1. Herbert L. WILLIAMS was born in 1877.
Herbert
L. WILLIAMS was married to Mary Bell Christy
on May 9, 1903 in Monroe County OH.
Mary B. Christy was born in 1878 in Monroe County OH. Herbert L. WILLIAMS and Mary B. Christy had
the following children:
a.
Georgia E. WILLIAMS was born on February 13, 1906. She died on July 24, 1906.
2. Levi
T. WILLIAMS was born on August 12, 1878 in Monroe County OH. He died on May 30, 1957. He was buried in Conner Ridge Methodist Cemetery,
Wayne Township, Monroe County, Ohio.
Levi
T. WILLIAMS was married to Lauretta P. Edington on December 24, 1900 in Monroe
County OH. Lauretta P. Edington
was born on September 28, 1881 in Monroe County OH. She died on February 16, 1951.
Levi T. WILLIAMS and Lauretta P. Edington had the following children:
a.
Luther WILLIAMS was born on April 22, 1910. He died on July 29, 1911.
3. Mollie
L. WILLIAMS was born in 1881 in Monroe County OH.
Mollie
L. WILLIAMS was married to F. E. Edington on October 6, 1904 in Monroe County
OH. F. E. Edington was born in
1884 in Monroe County OH.
4. Minnie W. WILLIAMS was born in 1883 in
Monroe County OH. 1904
Minnie
W. WILLIAMS was married to Harper Steed on December 15, 1904 in Monroe County
OH. Harper Steed was born in
1881 in Monroe County OH.
5. Sarepta WILLIAMS was born in 1886. She died in 1957. She was buried in Conner Ridge Methodist Cemetery, Wayne
Township, Monroe County, Ohio.
Sarepta
WILLIAMS was married to Scott N. Christy on March 5, 1908 in Monroe County OH. Scott N. Christy was born in 1875 in
Monroe County OH. He died in 1956. He was buried in Conner Ridge Methodist
Cemetery, Wayne Township, Monroe County, Ohio.
Sarepta WILLIAMS and Scott N. Christy had the following children:
a.
H. Audra Christy was born on May 13,
1915. She died on September 9, 1916.
6. David
S. WILLIAMS was born in 1888 in Monroe County OH. He died in 1971. He was
buried in Conner Ridge Methodist Cemetery, Wayne Township, Monroe County, Ohio.
David
S. WILLIAMS was married to Georgia Highman on May 15, 1915 in Monroe County,
OH. Georgia Highman was born in
1897.
7. Hazel WILLIAMS was born in 1891 in Monroe County
OH.
Arrena Hazel WILLIAMS was married to Leo Sebastian Burkhart on December 16,
1912 in Monroe County OH. Leo
Burkhart was born in 1889.
G. Mary
E. WILLIAMS was born in 1856. She
died in 1951.
Mary E. WILLIAMS was married to Alex B. Devore on December 22, 1874 in
Monroe County OH. Alex B. Devore
was born in 1854. He died in 1948. Mary E. WILLIAMS and Alex B. Devore had the
following children:
1. Cyrene
M. Devore was born in 1877.
Cyrene
M. Devore was married to W. F. Gatchell on May 8, 1895 in Monroe County OH.
2. Bertha A. Devore was born in 1888 in
Monroe County OH.
Bertha
A. Devore was married to Clarence E. Brown on October 29, 1907 in Monroe County
OH. Clarence E. Brown was born
in 1885 in Wood County, WV. He died in
1971. Buried at Conner Ridge
Cemetery. Next to him is Bertha A.
Dixon 1885-1971. This is probably
Bertha Devore Brown.
3. Edna
M. Devore was born in 1896 in Monroe County OH.
Edna
M. Devore was married to Addison R. Bates on April 29, 1914 in Monroe County
OH. Addison R. Bates was born in
1893 in Monroe County OH.
H. Sarepta
WILLIAMS was born on June 3, 1860.
She died on February 2, 1933.
She was buried in Conner Ridge Methodist Cemetery, Wayne Township,
Monroe County, Ohio.
Sarepta WILLIAMS was married to James Highman on
September 20, 1884 in Monroe County OH.
James Highman was born on September 10,
1861. He died on March 26, 1917. He was buried in Conner Ridge Methodist
Cemetery, Wayne Township, Monroe County, Ohio.
Sarepta WILLIAMS and James Highman had the following children:
1. Delbert Highman was born in 1884 in
Monroe County OH.
Delbert
Highman was married to Alta A. Edington on September 15, 1906 in Monroe County
OH. Alta A. Edington was born in
1889 in Monroe County, OH.
2. Harry
F. Highman was born in 1884 in Monroe County OH.
Harry
F. Highman was married to Stella F. Cronin on July 22, 1906 in Monroe County
OH. Stella F. Cronin was born in
1885 in Monroe County OH.
3. Altie
Highman was born in 1889 in Monroe County OH.
Altie
Highman was married to I. W. Green on June 20, 1908 in Monroe County OH. I. W. Green was born in 1886 in Athens,
Ohio.
I. Emily
WILLIAMS was born in 1862.
II. Jacob
WILLIAMS was born on October 9, 1812 in Greene County PA. He died on August 8, 1896 in Tyler County
West Virginia. He was buried in Lazear
Cemetery, Tyler County, WV. TYLER COUNTY,
WV HISTORY TO 1984: Van Camp -Williams
family by Shirley Walther Shore: Sarah
Elizabeth Williams (1850-1928) was d/o Jacob Williams and Sarah Jane
Cooper. Jacob was born in Greene County
PA in 1812 s/o Thomas Williams (1780).
In 1838 they came to Tyler County where Jacob married Sarah Jane. They had the following children: Levi M.
1841, Missouri Belle 1842, John 1846, Julia Anne 1848, Joseph 1853, Mary Louisa
1854, Jacob J. Jr. 1857, Martha J. 1859, Rosalie J. 1862, Lucretia C. 1864,
Oliver C. 1866. Jacob and Sarah are
buried at Kidwell.
Jacob WILLIAMS
was married to Sarah Jane Cooper on April 9, 1840 in Tyler County West
Virginia. Sarah Jane Cooper was born on June 7, 1823. She died on February 22, 1897. Jacob WILLIAMS and Sarah Jane Cooper had the
following children:
A. Levi
Marion WILLIAMS was born on January 14, 1841. He died on February 13, 1921.
Levi
Marion WILLIAMS was married to Eliza Jane McKaughan on January 6, 1867 in
Douglas, Kansas. Eliza Jane
McKaughan was born in 1847 in Pulaski County, KY.
B. Missouri
Belle WILLIAMS was born on October 26, 1842.
C. John
WILLIAMS was born on February 19, 1846.
D. Julia
Ann WILLIAMS was born on May 7, 1848.
E. Mary
Louisa WILLIAMS was born on November 4, 1854.
F. Jacob
J. WILLIAMS was born on October 25, 1857.
He died on December 28, 1902.
G. Martha
J. WILLIAMS was born on October 25, 1859.
She died in 1953.
H. Rosalia
J. WILLIAMS was born on January 7, 1862.
I. Lucretia
WILLIAMS was born on August 16, 1864.
J. Oliver
Cromwell WILLIAMS was born on October 26, 1866. He died in 1951.
III. Susanna WILLIAMS was born in 1815 in
Pennsylvania. She died possibly 24 Aug 1891. On 7 Apr 1868, Joseph Ellis
married Mrs. Susan Hayes in Monroe County, OH. Joseph Ellis died in July 1868.
In the 1870 census, Susanna Ellis is in Wayne Township., age 54, born
PA. In her household is Florence Booth,
age 4. She is living next to the Levi
Williams family.
Susanna
WILLIAMS was married to James N. HAYES
(son of Isaac HAYES and Mary
Mitchell) about 1835.
James N. HAYES was born in 1800 in VA. He died possibly 1867. (See Hayes line for additional
information.)
Susanna
WILLIAMS and James N. HAYES had the following children:
A. Samuel
Hayes was born in 1836. He died before March 1897 in possibly Monroe
County, Ohio.
Susan
Billiter (daughter of John BILLITER
and Lucy Ann CROW) was born about 1838 in
Marshall County, West Virginia. She
died in 1899 in Monroe County, OH.
Samuel Hayes and Susan Billiter had the following children:
1. Amanda
Isabella HAYES was born on December 21, 1859 in Tyler County WV. She died in 1946 in Monroe County, OH. She was buried in West Union, Perry
Township, Monroe County, Ohio.
Amanda
Isabella HAYES was married to Joe Franklin STINE on January 25, 1880 in Monroe
County, OH. Joe Franklin STINE
was born on January 6, 1861 in Monroe County, Ohio. He died on April 14, 1931 in Monroe County, Ohio. He was buried in West Union, Perry Township,
Monroe County, Ohio. Amanda Isabella
HAYES and Joe Franklin STINE had the following children:
a.
Laura STINE was born in 1881 in Monroe County, Ohio. She died in 1965.
b.
Ethel E. STINE was born in 1884.
She died in 1956.
c.
Elizabeth STINE was born on January 8, 1888 in Sardis, Monroe County,
Ohio. She died on November 16, 1985.
d.
Albert Virgil STINE was born on August 22, 1889 in Antioch, Monroe
County, OH. He died on January 1, 1948.
e.
Clarence STINE was born on April 3, 1891 in Monroe County, Ohio. He died in May 1969 in Sistersville, Tyler
County WV.
f.
Roy E. STINE was born on August 10, 1898 in Monroe County, Ohio. He died in August 1973 in Sardis, Monroe
County, Ohio.
g.
Lula STINE was born on March 16, 1901 in Monroe County, Ohio. She died on March 11, 1999 in Wheeling, Ohio
County WV.
2. Noah
HAYES was born on August 21, 1861 in Point Pleasant, Tyler County WV. Lived Cantwell, Ritchie County WV, in
1897. (Samuel's estate settlement)
Noah
HAYES was married to Rebecca KELICH on April 30, 1887 in Tyler County WV. Noah HAYES and Rebecca KELICH had the
following children:
a.
Hannah HAYES was born in May 1888.
b.
Ida M. HAYES was born in July 1892.
c.
Loyd HAYES was born in 1905.
3. John
Jefferson HAYES was born in September 1863 in Monroe County, OH. He was born in September 1863 in Monroe
County, OH. He died in 1945 in Bedford,
Taylor County, IA. He was buried in
Fairview Cemetery, Bedford, IA.
John
Jefferson HAYES was married to Anna S. Turner on September 9, 1888 in Bedford,
Taylor County, IA. Anna S. Turner
was born in February 1869 in Bedford, Taylor County, IA. She died in 1946. John Jefferson HAYES and Anna S. Turner had the following
children:
a.
Jesse HAYES was born in November 1889 in WV.
b.
Glenn HAYES was born in January 1891 in Bedford, Taylor County, IA. He was born in January 1891 in Iowa.
c.
Chloe HAYES was born in February 1894 in Iowa. She was born in February 1894 in IA. Census
d.
Ervin Paul HAYES was born on November 13, 1900 in Platville, Taylor
County, IA.
e.
Irvin Paul HAYES was born on November 13, 1900 in Platville, Taylor
County IA.
f.
Edna HAYES was born on May 13, 1903 in Benton Township., Taylor County,
IA. She was born on May 13, 1903 in
Benton Township., Taylor County IA.
Birth Record of Taylor County IA
g.
Cecil HAYES was born on February 18, 1906 in Bedford, Taylor County,
IA. He was born on February 18, 1906 in
Bedford, Taylor County, IA. He died on
March 26, 1977 in Jonesboro, AR. He
died on March 26, 1977 in Jonesboro, Arkansas. Birth Record of Taylor County IA
Death
Record of Jonesboro, AR
h.
Gladys HAYES was born in 1912.
She was born in 1912. Census
4. Lucy
HAYES was born in 1866 in Monroe County, OH.
Lucy
HAYES was married to James H. SMITH on July 29, 1886 in Tyler County WV. Lucy HAYES and James H. SMITH had the
following children:
a.
S. SMITH was born in May 1887 in West Virginia.
b.
Louise? SMITH was born in January 1889 in West Virginia.
c.
Unknown SMITH was born in November 1891 in West Virginia.
5. William
Thomas HAYES was born on August 27, 1867 in Monroe County, OH. He died on July 24, 1950 in Monroe County,
OH. He was buried in Mt. Olive, Lee
Township, Monroe County, Ohio.
William Thomas HAYES was married to
Sarah Melina "Mel" SCHOONOVER (daughter of Daniel
S. SCHOONOVER and Elizabeth STEWART)
on February 18, 1894 in Monroe County, OH
Sarah Melina "Mel" SCHOONOVER
was born on November 24, 1874 in Monroe County, OH. She died on July 22, 1947 in Monroe County, OH. She was buried in Mt. Olive Cemetery, Lee
Township, Monroe County, Ohio. William Thomas
HAYES and Sarah Melina "Mel" SCHOONOVER had the following children:
a.
Harry Edward HAYES was born on December 13, 1894 in Lee Township, Monroe
County, Ohio. He died on June 1, 1984
in Marietta, Washington County OH. He
was buried on June 3, 1984 in Mt. Olive, Lee Township, Monroe County, Ohio.
b.
Eva May "Kate" HAYES was born
on June 27, 1896 in Lee Township, Monroe County, Ohio. She died on March 28, 1963 in Jackson
Township, Monroe County, Ohio. She was
buried in Mt. Olive Cemetery, Lee Township, Monroe County, OH. She married Fred W. Jones.
c.
Anna Pearl HAYES was born on September 13, 1898 in Lee Township, Monroe
County, Ohio. She died on February 15,
1989 in New Martinsville, Wetzel County WV.
She was buried on February 17, 1989 in Mt. Olive, Lee Township, Monroe
County, Ohio.
6. Lafayette
HAYES was born on February 9, 1869 in Jackson Township, Monroe County,
Ohio.
Lafayette
HAYES was married to Melissa NEWHOUSE on April 12, 1900 in Monroe County, OH.
7. Mary
Ann HAYES was born on January 25, 1873 in Perry Township, Monroe County,
Ohio.
Mary
Ann HAYES was married to John C. STINE on March 22, 1896 in Monroe County, OH. John C. STINE was born in September 1873
in Monroe County, OH. Mary Ann HAYES
and John C. STINE had the following children:
a.
George R. STINE was born in February 1898 in Monroe County, OH.
b.
Clem J. STINE was born in August 1899 in Monroe County, OH.
8. Cleonie
HAYES was born on April 28, 1876 in Perry Township, Monroe County,
Ohio. She died in February 1975 in
Pittsburgh, Allegheny County PA.
Cleonie
HAYES was married to Samuel HALL on July 5, 1894 in Monroe County, OH. Samuel HALL was born in December 1875 in
Ohio. He died in March 1948 in
Pittsburgh, Allegheny County PA.
Cleonie HAYES and Samuel HALL had the following children:
a.
Wilma Vivian HALL was born on July 6, 1895 in Sardis, Monroe County,
Ohio. She died in March 1983 in
Pittsburgh, Allegheny County PA.
b.
Louis Cecil HALL was born on July 22, 1897 in Ohio. He died in 1984 in Pittsburgh, Allegheny
County PA.
c.
Sarah HALL was born on June 2, 1900 in Pittsburgh, Allegheny County
PA. She died on April 26, 1996 in
Pittsburgh, Allegheny County PA.
d.
Stella HALL was born in 1902 in Pittsburgh, Allegheny County PA. She died in 1949 in Pittsburgh, Allegheny
County PA.
9. Arkansas
HAYES was born on January 14, 1879 in Perry Township, Monroe County,
Ohio. He died on February 25, 1917 in
Malaga Township, Monroe County, Ohio.
Arkansas
HAYES was married to Frances CLAYTON on April 20, 1901 in Monroe County, OH.
Arkansas
HAYES was married to Nellie Gatchell on March 18, 1909 in Monroe County, Ohio.
B. Isaac
HAYES was born in 1838. He resided
in 1860 in Wayne Township. Monroe County OH.
He resided in 1870 in Bethel Township. Monroe County OH.
Elizabeth
was born in 1839 in Ohio. Isaac HAYES
and Elizabeth had the following children:
1. Mary
M. HAYES was born on October 31, 1860 in Ohio. She died on December 12, 1860.
She was buried in Conner Ridge Methodist Cemetery, Wayne Township,
Monroe County, Ohio.
2. Sarah
E. HAYES was born in 1862 in Monroe County, Ohio.
3. Mary
A. HAYES was born on July 16, 1867 in Wayne Township. Monroe County, Ohio.
4. William
A. HAYES was born in 1868 in Franklin Township. Monroe County, Ohio.
C. Sarah
HAYES was born on February 25, 1842 in Ohio. She died on April 5, 1924 in Washington Township, Monroe County,
Ohio.
Sarah
HAYES was married to Cyrus Salsbury or Salsberry (son of Jacob Salsbury and Rachal
Lisk?) on January 20, 1858. Cyrus
Salsbury or Salsberry was born on February 18, 1832 in Ohio. He died on April 21, 1917 in Washington
County OH. Sarah HAYES and Cyrus
Salsbury or Salsberry had the following children:
1. James
W. Salisbury was born in October 1858 in Ohio.
James
W. Salisbury was married to Nancy Rachel Lugan on September 12, 1884 in
Washington County, OH.
2. Sarah
Ellen Salisbury was born in December 1860 in Ohio.
Sarah
Ellen Salisbury was married to Abel Williams on August 15, 1883 in Washington
County OH. Sarah Ellen Salisbury and
Abel Williams had the following children:
a.
Ruchie Williams was born in February 1894.
3. Malinda
Salisbury was born in 1865 in Ohio.
4. George
Salisbury was born in October 1868 in Ohio.
5. Jason
L. E. Salisbury was born in 1869 in Ohio.
6. Nathaniel
E. Salisbury was born in 1870 in Ohio.
7. Eva
May Salsbury died on April 1, 1872.
She was buried in Brownsville Methodist, Benton Township, Monroe County,
Ohio.
8. Rueben
Salsbury was born on June 26, 1872.
He died on September 24, 1876.
He was buried in Brownsville Methodist, Benton Township, Monroe County,
Ohio.
9. Henry
Salisbury was born in May 1873 in Ohio.
10. Jacob
F. Salisbury was born in 1875 in Ohio.
Jacob
F. Salisbury was married to Eulala B. English on April 19, 1908 in Monroe
County, OH. Eulala B. English
was born about 1888 in Monroe County, OH.
11. Mary
E. Salisbury was born in 1878 in Ohio.
12. Jacon
Salsbury was born in December 1878 in OH.
13. Cyrus
J. Salisbury was born in 1880 in Ohio.
14. Charles
Salsbury was born in May 1882 in Ohio.
D. Phebe
HAYES was born on October 13, 1845.
She resided in 1860 in Grandview Township. Washington County OH. She died on January 2, 1865. She was buried in Conner Ridge Methodist
Cemetery, Wayne Township, Monroe County, Ohio.
Phebe
HAYES was married to Elias Kindell (son of Reason Kindell and Lucy Scarbrough)
on March 2, 1864 in Washington County OH.
Phebe HAYES and Elias Kindell had the following children:
1. Infant
son Kindell was born on December 2, 1864.
He died on December 2, 1864.
E. William
Thomas HAYES was born in January 1848 in Monroe County, Ohio.
William
Thomas HAYES was married to Mary Elizabeth KELLEY on August 18, 1867 in Monroe
County, Ohio. Mary Elizabeth KELLEY
was born in 1848. She died in 1915 in
Pleasants County WV. William Thomas
HAYES and Mary Elizabeth KELLEY had the following children:
1. Clara
E. HAYES was born in June 1869 in Ohio.
2. Jane
A. HAYES was born in March 1871 in Ohio.
3. Sarah
B. HAYES was born in July 1872.
4. Lillie
M. HAYES was born in November 1876.
5. Delilah
F. HAYES was born in February 1879 in Monroe County, Ohio.
6. Allen
G. HAYES was born in May 1881 in Monroe County, Ohio.
7. Cleveland
HAYES was born in February 1883.
8. Phoebe
HAYES was born in February 1886 in WV.
F. Francis
M. HAYES was born in June 1850 in Ohio.
He resided in 1860 in Grandview Township, Washington County OH. He resided in 1880 in Tyler County WV.
Francis
M. HAYES was married to Sarah KELLEY on April 22, 1869 in Monroe County, OH. Sarah KELLEY was born in 1851 in
Ohio. Francis M. HAYES and Sarah KELLEY
had the following children:
1. Infant
son HAYES was born on May 4, 1870.
He died on May 4, 1870. He was
buried in Conner Ridge Methodist Cemetery, Wayne Township, Monroe County, Ohio.
2. John
A. HAYES was born in 1871 in Ohio.
3. Clarissa
J. HAYES was born in 1873 in Ohio.
4. Margaret
E. HAYES was born in 1876 in OH.
5. Missouri
B. HAYES was born in 1878 in WV.
6. Clarence
C. HAYES was born in 1879 in WV.
Susanna
WILLIAMS was married to Joseph Ellis on April 7, 1868 in Jackson Township,
Monroe County OH. Joseph Ellis
was born in 1784. He died in July 1868
in Wayne Township, Monroe County, OH.
Susanna WILLIAMS was
married to Reason Kindell on October 25, 1870 in Monroe County, Ohio. Reason Kindell was born in 1818 in
OH. He died in 1898 in County
Infirmary, Woodsfield, OH.
Provided by Karen Romick
Click here for the Short-Cut Table of Contents


my todo application
Add
add your tasks here!
things to do
Done
0
Completed
Delete
Done
0
Completed
Delete


Born in Nazareth, Israel and raised in Nashville. The majority of my life has been spent using, playing with, and problem solving on computers as a hobby.
I derive a great amount of satisfaction from solving issues and being creative with coding. My professional background is in the culinary arts, serving as a Sushi-chef for nearly 7 years. This background of teamwork, problem-solving, self-dicipline, time management, creativity, and communication skills has lead me to the world of fullstack web development. Web devolopment is a place where I can combine all of my skills to do what I love and make it into something greater. Currently an Apprentice Web Devoloper @ Nashville Software School.