This chapter lists all the items (JS configuration, elements, attributes, classes) that can form the ReSpec language.
Content that gets inserted at the end of the SotD; used in case the patent situation of your specification requires some specific mentions (e.g. for an ongoing PAG).
For regular documents, this is used to specify that additional parties hold a copyright jointly with W3C on this document. This is typically used when publishing documents that were developed in cooperation with other friendly SDOs such as the IETF. The option is simply some text giving the addition copyright holders. For unofficial documents, this string is used to replace the default CC licence. Example for regular documents and example for unofficial documents.
An array of objects, each of which has two required fields: uri
, for the link to
the alternate document, and label
, for a human readable string that matches it.
This is used to link to alternate formats for the same content (e.g. PDF, ePub, PS).
An array of objects describing the authors of the document. See editors for details on the objects.
For IG-NOTEs, this must be specified. It is the URL of IP disclosure as per the IG's charter.
ReSpec knows to include a copyright year that matches the publishDate in the copyright notice. However, for documents developed over a period of several years it is preferable to indicate the first year during which the copyright started by setting this option. Note that this can always be safely specified since if copyrightStart is the same as the publishDate's year it is ignored. See an example.
A YYYY-MM-DD
date. Documents that are in Candidate Recommendation
(specStatus is "CR") are required to indicate a date before which the group guarantees
that it will not move to the next step on the track (PR or REC) so that implementers know how
long they have. Use this to provide that date.
If you want to produce a diffmarked version of your specification, you can use this setting to
point to a specific diff tool. It should expect to receive parameters called
oldfile
, newcontent
, and base
. By default it is set to
http://www.aptest.com/standards/htmldiff/htmldiff.pl
.
A setting indicating what version of RDFa to use when annotating the specification with semantic information that is compatible with RDFa Processors as used in the major search engines. Legal values are "1.0" to generate RDFa 1.0-compatible semantic markup, "1.1" to generate RDFa 1.1-compatible semantic markup, and false to indicate that no RDFa information should be included at all. Defaults to "1.1".
The values "1.0" and "1.1" must be included in quotation marks. Also, the value "1.0" should not be used in new specifications - it is only supported for legacy reasons.
The URI of the Editor's Draft, used in the header. This is required for specStatus = "ED". Any good old URL will do the trick.
An array of objects describing the editors of the document (in order). Each object must follow the structure below:
An URL providing a link to a document capturing errata for the specification.
Deprecated. An array of links to additional style sheets to include. This is one of the very few configuration options that is not backwards-compatible with v1 as support for it was completely removed (because almost everyone used it wrong, and it was not very useful).
The URL of the implementation report (documenting how your test suite fares with implementations), gets included in the specification's headers.
An option that tells the system to add a 'permalink' to each non-introductory section of your document assuming the section or heading element has an explicit ID. The permalink will show as an indicator on the same line as the section heading, by default immediately after the heading text. Options include:
Finally, if you do not want a section to have a permlink indicator, a class of "nolink" on that heading will exclude it.
A YYYY-MM-DD
date. Documents that are in Last Call (specStatus is "LC") are
required to indicate an end date for the review period. Use this to provide it.
If you need to include a one-off reference that isn't in the SpecRef database or if you need to override an existing reference with specific content, then you can use this configuration option.
Its value is an object that has the reference names as its keys and specific objects describing the
references as its values. Keys include authors
(an array of names), href
(a link to the reference), title
(the reference's name), status
(its maturity as a standard), and publisher
(the organisation publishing it).
Only title
is required.
localBiblio: { "WEREWOLF": { title: "Tremble Puny Villagers" , href: "http://w3.org/werewolf" , authors: [ "Dominique Hazael-Massieux" , "Doug the Simple Villager" ] , status: "RSCND" , publisher: "W3C" } }
logos
gives you the ability to override the standard W3C logo
with one or more other logos.
The logos
property takes an array that contains a set of objects.
Each of these objects contains at least a `src
` or an `alt
`
property, along with optional `height
`, `width
`,
`id
`, and `url
` properties that can be used to
further customize the included logo.
The above makes more sense when seen in an example:
logos: [ { src: 'https://example.com/logo.gif', href: "https://example.com", alt: "example.com", width: 100, height: 42, id: 'something' } ]
This causes the standard logo to replaced with

A number indicating the maximum depth of the table of contents, in case you wish to limit it so as to keep it more readable. Defaults to 0 which includes all levels.
A boolean indicating that automatically generated legacy DOM-style sections (Attributes and
Methods) following the WebIDL blocks are removed. Setting this boolean true brings the document
style closer to that of used by Anolis. If you are migrating a document that uses the legacy
DOM-style, you need to manually move the prose from Attributes and Methods sections and put it
below the IDL markup definition into its own paragraph(s). Additionally, you need to link the
IDL members back to the prose; ReSpec automatically generates fragment identifiers that start
with #widl-
, and you must manually add corresponding id
s to
appropriate parts in your prose.
A boolean indicating that a document is not intended to become a Recommendation. Used for Notes while in unfinished maturity states.
When set to true, no table of contents is generated.
otherLinks
gives you the ability to add additional links to the header
of the document.
The otherLinks
property takes an array that contains a set of objects.
Each of these objects contains a `key
` and a `data
`
property. The `key`
is the text that will contain the links to
the relevant resources. The `data
` is another array of objects
that contain the data describing the resource (with the properties `value
`
which is a string, and `href
` which is the URL you want to link
to).
The above makes more sense when seen in an example:
otherLinks: [{ key: "Version history:", data: [{ value: "Commit History.", href: "https://github.com/ResponsiveImagesCG/ri-usecases/commits/gh-pages" }, { value: "Github commits on Twitter.", href: "https://twitter.com/respimg_commits" }]
Becomes:
Sometimes it happens that a document is moved in the version control system, passed from one group to another, or split into several smaller documents. In such cases since the version control information is harder to find, this option can be used to point to a previous Editor's Draft. Rarely used.
If you are working on a new version of an existing Recommendation, use this to indicate what its shortName was.
If you are working on a new version of an existing Recommendation, use this to indicate what its URL was.
If a prevRecURI is not specified but prevRecShortname is, the latter will be used to generate the former by prefixing "http://www.w3.org/TR/" to it. Note however that while in the overwhelming majority of cases this works, it is not recommended to use this approach since if the Recommendation is later Rescinded, the link will be stale. Instead, use the dated link to the Recommendation.
When producing a diffmarked version, ReSpec uses the previousURI as the old version by default. Use this configuration option if you wish to override this to a specific URL.
A YYYY-MM-DD
date. When a previousPublishDate is specified, this is
typically required as well in order to generate the "Previous Version" link since it includes an
indication of the previous document's maturity level, which cannot be guessed. The values are
the same as for specStatus. Please note that some values of this option make no sense
depending on the current document specStatus but that the rules for validating
consistency are convoluted enough that ReSpec does not try to check them. If you pick the wrong
value (typically by forgetting to change it), the Link Checker will most likely catch the error
before publication (the same goes for previousPublishDate).
A YYYY-MM-DD
date. When there is a previous release of a given specification, this
is used to generate the "Previous Version" link. It is required for Recommendation Track
documents.
Not normally required, as this is typically defaulted properly for you. However, if the previous version of a document happened not to live on the W3C site (or not at a regular location) then you can set this.
ReSpec knows to include an indication of the W3C process under which the document was developed. This indication appears at the end of the Status of This Document section. By default it indicates the new "2014" process. You can override this by setting the processVersion configuration option to anything other than "2014". The previous process document, for example, was "2005".
A YYYY-MM-DD
date. The publication date of the present document. For documents that
are in flux, such as Editor's Drafts or unofficial documents, this is best left unspecified as
ReSpec will use the document's last modification date (as provided by the browser) in order to
set this. For documents intended for official publication, this is normally required.
Note that the last modified date provided by the browser can at times be wrong. This often happens when the server is itself providing a broken value, or at times when differences in timezones (that are not always well accounted-for by servers or browsers) cause the day to shift by one.
The text of a note to include at the beginning of the References section.
The specification's "short name", which is the name used in W3C URLs such as "http://www.w3.org/TR/short-name" (and several other generated URLs).
The specification's type, which can be a maturity level (e.g. Working Draft) if it is on a publication track but can also take other values for other types of documents (e.g. "unofficial" for, well, unofficial documents).
| value | meaning |
|---|---|
| base | Just the basic template, not a specification. Use this for public documentation produced by a group that has no current clear plan to be officially published. Example |
| MO | Member-Only Document. Similar to base, but for documents that need to be clearly flagged as being restricted in access to W3C Members. This is rarely, if ever, useful. Example |
| unofficial | An unofficial draft. Use this if you're producing a document outside of W3C but want to use styles that match those of W3C specifications, for instance to propose a new document while hosting it on your own server. Note that this automatically licences the content under CC-BY v3.0. If you want a different copyright, you will need to set the various copyright configuration options. Example |
| ED | Editor's Draft. Use this for documents that are maintained in the group's own repository. Requires edDraftURI to be specified. This is the default value. Example |
| FPWD | First Public Working Draft. Example |
| WD | Working Draft. Requires previousPublishDate and previousMaturity. Example |
| LC | Last Call Working Draft. Requires previousPublishDate, previousMaturity, and lcEnd. Example |
| CR | Candidate Recommendation. Requires previousPublishDate, previousMaturity, and crEnd. Example |
| PR | Proposed Recommendation. Requires previousPublishDate and previousMaturity. Example |
| PER | Proposed Edited Recommendation. Requires previousPublishDate and previousMaturity. Example |
| REC | Recommendation. Requires previousPublishDate and previousMaturity. Example |
| RSCND | Rescinded Recommendation. Requires previousPublishDate and previousMaturity. I wish there were more of those. The style is so edgy. Example |
| NOTE | Deprecated. A note. It is unclear to me how this differs from the more specific WG-NOTE and friends. Do not use this. Example |
| FPWD-NOTE | First Public Working Draft of a Note (of any kind, it would seem). Example |
| WG-NOTE | Working Group Note. Example |
| BG-DRAFT, BG-FINAL | Business Group Draft or Final Report. Example Draft Report |
| CG-DRAFT, CG-FINAL | Community Group Draft or Final Report. Example Draft Report |
| IG-NOTE |
Interest Group Note. For this, charterDisclosureURI is required.
Example |
| Member-SUBM | Member Submission. Note that ReSpec uses the default W3C copyright for this, but that you are entitled to retain your own copyright instead of transferring it to W3C. Use the copyright options for this. Example |
| Team-SUBM | Team Submission. Example |
| XGR | Deprecated. Incubator Group Report. Requires xgrGroupShortName and xgrDocShortName. Example |
| draft-finding | Draft TAG Finding. If you are one of the Nine and working on a Finding, this is for you. Note that for findings, ReSpec currently does not support very robust SotD generation (there don't seem to be solid rules for what constitutes a valid Finding SotD) so you'll have to specify your own. If there are rules that could be used, please report a bug. ReSpec further assumes some conventions for finding URLs that are not consistent throughout all of the TAG's repository, specifically that all findings live in "http://www.w3.org/2001/tag/doc/", that the latest version is at "http://www.w3.org/2001/tag/doc/shortName", and that the dated versions are at "shortName-YYYYMMDD". Example |
| finding | TAG Finding. Same as above, but final. Example |
If you wish feedback to your mailing list about this specific document to have a specific prefix subject in its subject line, then specify this (including the [ and ] if you want them). The various of the heading matter that refer to the mailing list will use this information.
A simple string that will be used as a subtitle for the specification, right under the title.
The URL of your test suite, gets included in the specification's headers.
A boolean which when set to true will cause the introductory sections to also show up in the table of contents. This is rarely needed, but some groups prefer to have it that way.
The full public name of the group, including "Working/Interest/Incubator/etc. Group" as applicable. E.g. "Device APIs Working Group".
The URL of the public list of patent disclosures for the group, e.g. "http://www.w3.org/2004/01/pp-impl/43696/status".
PLEASE NOTE: it is extremely easy to cut and paste this value from somewhere else and to fail to notice that you are using the wrong value. Given the legal patent implications in pointing to the wrong resource, please triple-check that you are using the link relevant to your group. In order to find your group's link, go to http://www.w3.org/2004/01/pp-impl/, locate your group, and click on its "(Status)" link.
The short name of the mailing list on which the group conducts its public discussion. E.g. "public-device-apis".
The URI to the public page of the group. E.g. "http://w3.org/2009/dap/".
Deprecated. The short name of the group report, e.g. "mbui". Since XGs typically produce a single report, it is typical to use the same short name for the report as is used for the group, therefore this option defaults to xgrGroupShortName.
Deprecated. The short name of the group, as included in its URI, e.g. "model-based-ui". This is required for XGs.
Specification figures are indicated using the figure
element, with a nested
figcaption
. They can occur anywhere.
A Table of Figures is generated and inserted in the document if you include an element with
ID tof
.
Figures can be automatically linked to using a link pointing to their ID with no content
(e.g.
).
Specification sections are indicated using the section
element. They can be
nested arbitrarily in order to indicate sub-sections.
The first h*
child element is taken to be the section's title. You do not need to
worry about nesting depth: ReSpec will take any element in the h1
-h6
range and renumber it to match the section's nesting depth correctly. It is a common convention
(though by no means a requirement) to use h2
for all sections.
If you nest deeper than the h6
level, apart from having a hard-to-navigate document
you will keep getting h6
elements.
Section can be automatically linked to using a link pointing to their ID with no content
(e.g.
).
Some sections with specific IDs have special meanings.
The title
element is left untouched, but its content is used to also set the
h1
title for the specification.
Data is normally included as HTML (injected into the DOM as such) but there are time when you
want to include content as text. If so, set this attribute to text
. That is the
only supported value (you can also use html
, but that's the default behaviour).
By default inclusion happens by placing the content inside the including element. At time, you will actually want the element to be replaced by the inclusion. If so, simply set this attribute to any truthy value.
Inclusion is normally asynchronous, which means that the content may or may not get further processed by ReSpec depending on the point at which it gets inserted (which isn't deterministic). If you need to ensure that content gets injected before the rest of the pipeline runs, set this to any truthy value.
Be warned that there is a steep performance penalty in doing so, since all ReSpec processing will effectively pause until the content has been fully fetched and inserted.
A URL pointing to a resource, relative to the including document. The content will get included
as a child of the element on which the inclusion is performed (unless
data-include-replace
is used, in which case it replaces the element),
replacing its existing content.
The include filter runs recursively so that included content that contains
data-include
attributes will work (just be sure not to build a circular loop
in there, ReSpec won't detect it if only because it doesn't mind if you're shooting yourself in
the foot).
By default the inclusion is asynchronous, which means that the included content may or may not
be further processed by ReSpec after it gets added to the DOM (the result won't be deterministic
and so is only useful if the content is not meant to be further processed). If you wish
to ensure that ReSpec processing is applied to the content, use
data-include-sync
In the processing pipeline, inclusion happens right after everything to do with the document's headers, style, and transformations have happened, which means that all the processing to do with structure, inlines, WebIDL, and everything else is applied to the included content as if it had always been part of the source.
This is a list of white space separated WebIDL identifiers that you wish to have merged into the current WebIDL section, so as to have them all described together rather than as separate sections. This is typically used to bring the definition for one or more dictionaries into the same section as an interface.
Can be used in conjunction with the configuration option issueBase
and with
a paragraph with class value issue
. The issue number is added to
the header of the paragraph, and linked to the issue by concatenating the values
of issueBase
and data-number
. This is particularly
useful when using GitHub to link into the discussion thread of a particular issue.
A typical example for a file in the github repository https:/github.com/w3c/dpub-pwd
would include, for example:

Change the terminology to "Portable Web Publication"<\p>
If the configuration of the file includes issueBase:"https:/github.com/w3c/dpub-pwd/issues"
,
then the paragraph will be automatically entitled "ISSUE 1", with a link to the
corresponding Github issue.
Behaves in the same way as data-transform
, applied to the included content.
The functions receive a third parameter giving the URL of the loaded content.
This is a list of white space separated JavaScript function names that will be called in turn in order to transform the content inside the given element. The functions need to be globally available.
Each function gets called with the ReSpec utils
object and a string of the content
to transform.
Each function must return the transformed content.
ReSpec defaults the dir
attribute on your root element to ltr
. If you
are writing in a language that requires a different directionality, simply set this attribute to
another value.
ReSpec defaults the lang
attribute on your root element to en
. If you
are writing in another language, simply set this attribute to another value.
Marks a section as being an appendix (which will be numbered with letters). Note that this does not make it informative as some appendices can contain normative material.
It is important to know that every section following an appendix will also be made to be an appendix.
Marks the contents of an element as a "Editor's Note". If the element
is a 'block' element (e.g., div
or
p
) then the Editor's Note will be emitted in a
block that includes an Editor's Note "header" and the contents of the
element as the text of the note.
If the element also has a
title
attribute, the content of the title will
be appended to the header (e.g., "Editor's Note: This is my note").
A block example:

 We are aware that the formatting of this section isn't great. We will fix it in the next revision!

Would be emitted as:

Editor's Note: This section will be reformatted

We are aware that the formatting of this section isn't great. We will fix it in the next revision!

If the element is an 'inline' element (e.g., span) then the
element is left as is and any title
attribute
does not effect the appearance of the note.
An inline example:

Sometimes, when you are looking at an URL I pronounce this as 'earl', so 'An Earl' feels right. But if I said the letters it is 'you are ell', so 'A You Are Ell' would be better. Help? note that the 'scheme' helps understand the rest of the syntax.

Would be emitted as:

Sometimes, when you are looking at an URL I pronounce this as 'earl', so 'An Earl' feels right. But if I said the letters it is 'you are ell', so 'A You Are Ell' would be better. Help? note that the 'scheme' helps understand the rest of the syntax.

In other words, the title
attribute is ignored when the containing
element is "inline".
Marks a pre
or aside
as being an example. This provides it with a
specific styling and header.
Indicates that an example or a code fragment should be syntax highlighted. The syntax highlighter will do its best to guess how to perform highlighting without knowing the language.
If needed you can tweak the syntax highlighting styles in order to obtain better results.
Used for regular sections or appendices that are not meant to contain normative material. It will automatically preface its content with the well-know “This section is non-normative” paragraph.
When set on a section indicates that it is meant as introductory material that need not be linked to from the table of contents. The abstract, SotD, and ToC sections automatically fall into this category (but you need not worry about flagging them as such).
If you do wish all the introductory sections to be present in the ToC, see tocIntroductory.
Marks the contents of an element as a "Note". If the element
is a 'block' element (e.g., div
or
p
) then the Note will be emitted in a
block that includes a Note "header" and the contents of the
element as the text of the note.
If the element also has a
title
attribute, the content of the title will
be appended to the header (e.g., "Note: This is my note").
A block example:

 Remember - if you are using the role attribute to say that a paragraph is a button, you are probably doing it wrong!

Would be emitted as:

Note: Always rely upon native semantics

Remember - if you are using the role attribute to say that a paragraph is a button, you are probably doing it wrong!

An inline example:

This is really important: Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light Don't cross the streams!

Would be emitted as:

This is really important: Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light Don't cross the streams!

In other words, the title
attribute is ignored when the containing
element is "inline".
A div
containing a best practice description.
A paragraph containing the description of a best practice, inside a practice description.
A span
containing the title of a best practice, inside a practice
description.
If you want to include content that is used during the generation of the specification but must
be removed from the output, then add the remove
class to it. That is used for
instance for all the script
elements that pull in ReSpec and define its
configuration.
ReSpec has a general event publish / subscribe system. Developers extending the system can do so by subscribing to events they care about and performing actions when those events are fired. The interfaces and events are documented in this section.
A method to publish event. The event will be delivered to each subscriber.
respecEvents.pub(eventName, message)
A method to subscribe to an event.
respecEvents.sub(eventName, handler)
The following events are currently available from ReSpec.


Chapter 5 Website and Lab Manual
5.1 Website
5.1.1 Details
URL: pielab-science.com
Username and password: email Sara or David for this information.
5.1.2 Purpose
PR for the PIE lab - Who’s part of the PIE lab - What are we currently doing? - (If actively recruiting) landing page for new recuirts - (If ongoing study) landing page for study participants
5.1.3 Current sections
- What we study
- About
- Current lab members (with a page for each)
- Friends of the lab
- Cooling on the rack (news)
5.1.4 How to update
- Go to pielab-science.com/admin and log in (see above for username/password details)
- See sections below for updating specific aspects
<IP_ADDRESS> Your profile
- Go to the Media section (on the left-hand menu) and click Add New
- Drop file into box, or select using menus
- Go to Pages (left-hand menu) and hover over your page – select Edit with Elementor
- Use the interface to change text, upload a new picture, include links to other pages, whatever you want!
- Be sure to click Update before leaving the page.
<IP_ADDRESS> Your CV
- Go to the Media section (on the left-hand menu) and click Add New
- Drop file into box, or select using menus
- Go to Pages (left-hand menu) and hover over your page – select Edit with Elementor
- Hover over the box that contains the text. A pencil will show up in the corner; click on it.
- On the left-hand side, an Edit Text Editor menu will show up. Find the link to your CV. If you click on it, the link to the PDF will appear. You can either
- Edit the link to match the new upload (involves changing the year and month of upload and the name of the file as it was uploaded to Wordpress), or
- Delete the current link to the CV and add a new one with the Add Media button.
- Be sure to click Update before leaving the page.
<IP_ADDRESS> Troubleshooting
If the page doesn’t update
- Wait 15 minutes and reload the webpage.
- Clear the wordpress Cache
- On the wordpress dashboard, click on Mangaged Wordpress (top) and select Flush Cache. This will take a minute or so.
- Clear your browser Cache
- This will be under your browser’s settings.
- Try opening the webpage in an incognito window as well, to see if this is a problem.
5.2 Lab Manual
5.2.1 Clone lab manual to your computer
Notes:
- this is only available to current graduate students and PIs in the lab.
- the steps listed here only need to be followed on the first use.
Necessary materials:
- Git
- GitHub account with access to PIElab organization
- Rstudio that is connected to GitHub through your personal account.
- Go to manual repository.
- Click on the green Clone or download button.
- Copy the link that appears.
- Open RStudio. Create a New Project.
- Select Version Control and then Git. Name the project ``manual’’ (so it matches the Rproj file that already exists in the repository. Save this project somewhere you will remember.
5.2.2 Updating the manual [using the RStudio GUI]
Before you make ANY changes:
- Open the manual RStudio project.
- Pull the most recent version of the manual using the blue down arrow.
Make any changes to the manual as you think are necessary.
- In the Build tab in Rstudio, click on Build Book.
- In the Git tab, click Commit. In the commit message section, briefly (4-5 words max) describe the changes you made. Example: wrote updating manual section. In the window on the left, the easiest thing to do is select everything and click Stage. Ensure all the boxes are checked. This will be slower than only selecting the parts of the book that have changed. However, the nature of an RMarkdown book is many changes affect most parts of the book (because it changes you navigate to them). If you miss a change you have made, the book may not render properly online. Click the Commit Button.
- Click on the green up arrow to push the book to GitHub, which will update the book online.
5.2.3 Updating the manual [using the terminal in Rstudio]
Before you make ANY changes:
- Open the manual RStudio project.
- In the terminal window of RStudio, pull the most recent version using this code:
git pull
Make any changes to the manual as you think are necessary.
- In the Build tab in Rstudio, click on Build Book.
- In the Terminal, commit your changes. The easiest way to do this is to type:
git add .
where the period indicate to include anything. Alternatively, you can add only specific files, if you don’t want to commit everything. For example:
git add file.R
or:
git add path/file.R
To commit your changes, type:
git commit -m "message here"
Be sure to include a message describing the changes. Keep the message short.
Finally upload your changes with:
git push
You’re done!
5.2.4 Requesting updates
You may be unable to make changes to the lab manual because you are not authorized to make changes or don’t know the answer to the question. In either of those cases, you make create an issue on the GitHub page to alert the lab to the need for additional material. To do so:
- Go to the Issues tab on the GitHub page for the lab manual.
- Click on New Issue and complete the form. Be sure to include as much detail as you can about the issue you have. The more detailed your request, the better the information in the manual will be.
Note: create one issue request for each question you have. Don’t put lots of requests into a single issue.
Other lab members can take responsibility for this issue by self-assigning the issue. Once material has been added to the manual, the member responsible for resolving the issue should reply to the original poster, including a link to the relevant section. If this meets the need of the original poster, they should reply so and the issue can be marked as closed.


--- date: 2010-03-02T00:00:00Z published: true title: Campaign Monitor for your mobile url: /2010/03/02/campaign-monitor-for-your-mobile/ ---
Today we're super excited to announce a new mobile optimized version of Campaign Monitor that gives you and your clients quick access to great looking reports on any campaigns you've sent. It's fast, looks great and is available now. Just head to your account on any popular mobile device like an iPhone or Android and the mobile version will be shown by default. You don't need to install anything, because it is a web application, not a native phone application.
I love these guys - they're great.


Playing The Stretchers In Co-Op Is Stumbly, Fumbly Fun
by Paul TamayoI played the surprise co-op game for Switch, The Stretchers, earlier with Stephen. Check out the video above and follow us on Twitch for more streams!
I played the surprise co-op game for Switch, The Stretchers, earlier with Stephen. Check out the video above and follow us on Twitch for more streams!


Part of a volcanic archipelago that encompasses over 6,800 islands, Japan remains one of Asia's most fascinating tourist destinations, where a blend of modernity and tradition creates a look and feel completely different from any other place in the world.  Many tourists on vacation in Japan devote lots of time to the country's unique cuisine, prepared with painstaking attention to detail and a genius for simple yet effective presentation
Places to vist in egypt & main attractions to vist
- Hiroshima
- kamakura
- Itsukushima
- The Ishigaki
Here the
Japan package includes all modes of transport i.e.,
- Air :
The basic price for air ways which includes first class and economic class 4000$ usd.
- Train :
The price for train is 2500$ usd.
- Bus :
The price for bus ways is 2000$ usd.


Reveal.js
The HTML Presentation Framework
Created by
Hakim El Hattab
and
contributors
THE END
-
Try the online editor
-
Source code & documentation


--- layout: page title: Call Me permalink: /call.html #tags: ---
If this device supports phone calls, a call will be placed automatically within 5 seconds to +917719058077. If a call is not placed in 5 seconds, click here to manually place the call.


James Tauber wrote a kind of narrative construction of a template language using simple string substitution. It's an interesting way of building up a template language, but I think unnecessarily complex because of some minor details.
The basic structure he uses is this:
class Template: _template = 'some string with %(sub)s' def __init__(self, dict): self.dict = dict def __str__(self): return self._template % self def __getitem__(self, key): # or some fancier processing... return self.dict[key].upper()
I think it's easier to not think so much in terms of templates as classes, and to put all the logic in __getitem__ mostly disassociated from templates.
The basic pattern is that of a wrapper:
class Wrapper(object): def __init__(self, dict): self.dict = dict def __getitem__(self, item): raise NotImplementedError
Used like this:
rendered = 'some string' % SomeWrapper(data_source)
For instance, his piping technique:
class Piper(Wrapper): def __getitem__(self, item): parts = item.split("|") value = self.dict[parts[0]] for func in parts[1:]: value = self.dict[func](value) return value
Then if you use a key of name|upper you will really mean dict['upper'](dict['name']).  rendered = tmpl % Piper({'name': 'the keymaster', 'upper': lambda x: x.upper()})
Because of the way string.Template is defined you can't use it with complex key names, but this fixes it (from paste.script.copydir):
class LaxTemplate(string.Template): # This change of pattern allows for anything in braces, but # only identifiers outside of braces: pattern = re.compile(r""" \$(?: (?P<escaped>\$) | # Escape sequence of two delimiters (?P<named>[_a-z][_a-z0-9]*) | # delimiter and a Python identifier {(?P<braced>.*?)} | # delimiter and a braced identifier (?P<invalid>) # Other ill-formed delimiter exprs ) """, re.VERBOSE | re.IGNORECASE)
Then you can do:
tmpl = LaxTemplate('Are you ${name|upper}?!?').substitute( Piper({'name': 'the keymaster', 'upper': lambda x: x.upper()}))
So, what if you want to HTML quote everything by default?
class HTMLQuote(Wrapper): def __getitem__(self, item): value = self.dict[item] return cgi.escape(str(value), 1)
What if you want to allow arbitrary expressions for keys?
class Eval(Wrapper): def __getitem__(self, item): return eval(item, self.dict)
Now you can use a template like Name: %(user.name)s.
What if you want catch exceptions ZPT-style, where you use | to indicate alternatives?
class ZPTCatcher(Wrapper): def __getitem__(self, item): alternatives = item.split("|") for i in alternatives[:-1]: try: return self.dict[i] except (KeyError, AttributeError): pass return self.dict[alternatives[-1]]
What if, again ZPT-like, you want to allow different kinds of wrappers based on a prefix? E.g., python:expr for Python syntax, django:value|filter for Django syntax, string:a${b} for a literals with string.Template style substitution.
class Dispatcher(Wrapper): def __init__(self, dict, **prefix_wrappers): self.dict = dict self.prefix_wrappers = prefix_wrappers def __getitem__(self, item): if ':' not in item: wrapper = self.prefix_wrappers['default'] expr = item else: prefix, expr = item.split(':', 1) wrapper = self.prefix_wrappers[prefix] return wrapper(self.dict)[expr] class StringTemplate(Wrapper): def __getitem__(self, item): tmpl = string.Template(item) return tmpl.substitute(self.dict) fancy_dict = Dispatcher(some_dict, python=Eval, string=StringTemplate, django=Piper)
Note that these dictionaries can be used with % or string.Template or anything that uses __getitem__ (and only __getitem__).
This is one reason why any string substitution should allow passing in a dictionary-like object, not just use **kw for passing in dictionaries. This seems to still be a flaw of PEP 3101, which is a expanded string formatting proposal for Python 3. The reason **kw can't work is that these are only very lightly dictionary-like; there is no keys() method. Eval(locals()).keys() would have to enumerate all possible expressions; clearly not feasible. And **kw has to unpack the dictionary (enumerating it) before it can pass it into the function.
you may want to take a look at Templite: http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/496702
it just lets you embed python code directly into your template.
- for example, this code:
tmpl = "Are you %(name|upper)s?!?"
rendered = tmpl % Piper({'name': 'the keymaster', 'upper': lambda x: x.upper()})
- becomes:
tmpl = Templite("Are you ${emit(name.upper())}$?!?"
rendered = tmpl(name ="the keymaster")
-tomer
I had basically the same idea a few months ago and wrote up a generic object wrapper to help with template substitution. You've inspired me to add it to the Cookbook: http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/496730


[§457B-1] Short title. This chapter may be cited as the "Nursing Home Administrators Act". [L 1970, c 63, pt of §1]


class HistoricalCallsManagerCom
extends java.lang.Object
| Modifier and Type | Field and Description |
|---|---|
private MTClientBaseCom |
dcb |
private LogCom |
log |
private java.util.concurrent.LinkedBlockingQueue<HistoricalDataSeriesCom> |
tickerFIFO |
| Constructor and Description |
|---|
HistoricalCallsManagerCom(MTClientBaseCom dcb)
Constructor
|
| Modifier and Type | Method and Description |
|---|---|
private void |
begin(java.util.HashMap<java.lang.String,java.lang.String> data)
This method get called whenever is received a BEGIN message.
|
private void |
candle(java.util.HashMap<java.lang.String,java.lang.String> data)
This method get called whenever is received a CANDLE message.
|
private void |
end(java.util.HashMap<java.lang.String,java.lang.String> data)
This method get called whenever is received an END message.
|
(package private) CandleSeriesCom |
queueCandle(java.lang.String tickerCode)
Add a Candle request for the ticker specified by the tickerCode to the list
|
(package private) TBTSeriesCom |
queueTBT(java.lang.String tickerCode)
Add a TBT request for the ticker specified by the tickerCode to the list
|
(package private) void |
receiveMessage(MessageCom message)
This method get called by a dispatcher whenever it receive data related to
historical calls
|
private void |
tbt(java.util.HashMap<java.lang.String,java.lang.String> data)
This method get called whenever is received a TBT message.
|
private LogCom log
private java.util.concurrent.LinkedBlockingQueue<HistoricalDataSeriesCom> tickerFIFO
private final MTClientBaseCom dcb
HistoricalCallsManagerCom(MTClientBaseCom dcb)
dcb
- - MTClientBaseCom
served by this classTBTSeriesCom queueTBT(java.lang.String tickerCode)
tickerCode
- - the code that specify the TickerCom
tickerTBTSeriesCom
that will be populated when data
become availableCandleSeriesCom queueCandle(java.lang.String tickerCode)
tickerCode
- - the code that specify the TickerCom
tickerCandleSeriesCom
that will be populated when data
become availablevoid receiveMessage(MessageCom message)
message
- - MessageCom
message containing informations received
from Darwinprivate void begin(java.util.HashMap<java.lang.String,java.lang.String> data)
data
- - a key-value collection representing received dataprivate void end(java.util.HashMap<java.lang.String,java.lang.String> data)
HistoricalDataSeriesCom
is readydata
- - a key-value collection representing received dataprivate void candle(java.util.HashMap<java.lang.String,java.lang.String> data)
CandleSeriesCom
data
- - a key-value collection representing received dataprivate void tbt(java.util.HashMap<java.lang.String,java.lang.String> data)
TBTSeriesCom
data
- - a key-value collection representing received data


--- layout: post title: "@Disclosedtech: Edsurge and Springboard" date: 2017-01-06 11:35:00 +0000 tags: image: https://s3.amazonaws.com/hackedu/2017-01-06-pigeon.jpg imagecredits: https://www.flickr.com/photos/eastbeach/6427112717 ---
"New Coding Bootcamp Guarantees Jobs for Gradates," Edsurge wrote on January 5, 2017. Spelling mistake in the headline aside, the problem here is the lack of disclosure.
Springboard, the company in question, shares an investor with Edsurge: John Katzman.
For more information about this disclosure alert, read this blog post.


Unauthorised
You have entered an incorrect user name or password. Try Again?
If you have forgotten your username, see this list.
Forgotten Password
If you have forgotten your password, anyone else who has a conductor password or who is logged in as a conductor can reset it for you.
SSH
If no one is able to reset your password, you can use an ssh connection to reset passwords.
- On another computer, make an ssh connection to ssh<EMAIL_ADDRESS>- If your computer can't find immrama.local:
- Make sure your computer is connected to the immrama WiFi network and Try again.
- If that doesn't help, try<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and pi@immrama
- If you cannot remember the ssh password, consult the written documentation to find the default password.
- Type: sudo cp /boot/htpasswd/lighttpd-htdigest.default /boot/htpasswd/lighttpd-htdigest.user
- Type: sudo service lighttpd restart
- Type: exit
- Your ssh connection should now be over.
- You can now connect with username: conductor password: defaultpass
- Please change your password.
SD Card
You can also change your password via an SD card reader. This method requires crashing the computer by pulling the plug witout first doing a proper shutdown. Ocassionally, doing this may corrupt the SD card and so it should be avoided as muh as possible.
- If the computer is on, pull the plug
- Take out the SD card
- Using another computer with an SD card reader, go to the /boot partition.
- There will be a folder in there called 'htpasswd'
- In the htpasswd folder, throw away the file '/boot/htpasswd/lighttpd-htdigest.user'
- Make a new copy of '/boot/htpasswd/lighttpd-htdigest.default' called /boot/htpasswd/lighttpd-htdigest.user
- Properly unmount the SC card.
- Return the SD card to the Raspberry Pi computer
- Plug in the computer to boot it.
- You can now connect with username: conductor password: defaultpass
- Please change your password.


ACL2 Releases
The current ACL2 release on the ACL2 home page
is Version 8.5 (July, 2022).
Note: Some older versions of the manuals have
been made unreadable to avoid potential security issues.
- Version 8.4 (August, 2021)
- Version 8.3 (April, 2020)
- Version 8.2 (May, 2019)
- Version 8.1 (September, 2018)
- Version 8.0 (December, 2017)
- Version 7.4 (March, 2017)
- Version 7.3 (December, 2016)
- Version 7.2 (January, 2016)
- Version 7.1 (May, 2015)
- Version 7.0 (January, 2015)
- Version 6.5 (August, 2014)
- Version 6.4 (January, 2014)
- Version 6.3 (October, 2013)
- Version 6.2 (June, 2013)
- Version 6.1 (February, 2013)
- Version 6.0 (December, 2012)
- Version 5.0 (August, 2012)
- Version 4.3 (July, 2011)
- Version 4.2 (January, 2011)
- Version 4.1 (September, 2010)
- Version 4.0 (July, 2010)
- Version 3.6.1 (September, 2009)
- Version 3.6 (August, 2009)
- Version 3.5 (May, 2009)
- Version 3.4 (August, 2008)
- Version 3.3 (November, 2007)
- Version 3.2.1 (June, 2007)
- Version 3.2 (April, 2007)
- Version 3.1 (December, 2006)
- Version 3.0.1 (August, 2006)
- Version 3.0 (June, 2006)
- Version 2.9.4 (January, 2006)
- Version 2.9.3 (August, 2005)
- Version 2.9.2 (April, 2005)
- Version 2.9.1 (December, 2004)
- Version 2.9 (October, 2004)
- Version 2.8 (March, 2004)
- Version 2.7 (November, 2002)
- Version 2.6 (November, 2001)
- Version 2.5 (June, 2000)
- Version 2.4 (August, 1999)
- Version 2.3 (October, 1998)
- Version 2.2 (August, 1998)
- Version 2.1 (December, 1997)
- Version 2.0 (July, 1997)
- Version 1.9 (Fall, 1996)
Note: The ACL2 Home Pages for versions between 5.0 and 7.0,
listed above, did not directly include the Community Books, which were
distributed separately. You may find the books for those versions
at http://acl2.org/books-pre-7.0/.


PORT-OF-SPAIN, Trinidad (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...
Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's "State of the Union."


Setting up your very own secure voting system has never been easier.
STEP 1:
GET THE APP
You'll need your own address to continue. The app will generate it and allow you to participate. You'll set up your own or join an existing organisation and suggest motions to vote on.
The installation shouldn't take you more than 30 minutes. Please find detailed instructions on GitHub. If someone already set up the network for you, call them. They'll tell you what to do.


| Interface | Description |
|---|---|
| ImpendingOWLOntologyChangeBroadcastStrategy |
Author: Matthew Horridge
The University of Manchester Bio-Health Informatics Group Date: 04-Jul-2010 |
| ImpendingOWLOntologyChangeListener |
Author: Matthew Horridge
The University of Manchester Bio-Health Informatics Group Date: 04-Jul-2010 |
| MissingImportListener |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 11-Apr-2008 |
| OWLAnnotation |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 18-Dec-2006 Annotations are used in the various types of annotation axioms, which bind annotations to their subjects (i.e. |
| OWLAnnotationAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Nov-2006 Represents AnnotationAssertion axioms in the OWL 2 specification. |
| OWLAnnotationAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 A super interface for annotation axioms. |
| OWLAnnotationAxiomVisitor | |
| OWLAnnotationAxiomVisitorEx<O> | |
| OWLAnnotationObject |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 A marker interface for the values (objects) of annotations. |
| OWLAnnotationObjectVisitor | |
| OWLAnnotationObjectVisitorEx<O> | |
| OWLAnnotationProperty |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 |
| OWLAnnotationPropertyDomainAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 |
| OWLAnnotationPropertyRangeAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 |
| OWLAnnotationSubject |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 A marker interface for annotation subjects, which can either be IRIs or anonymous individuals, with visitor methods. |
| OWLAnnotationSubjectVisitor |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 17-Jan-2010 |
| OWLAnnotationSubjectVisitorEx<E> |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 17-Jan-2010 |
| OWLAnnotationValue |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 A marker interface for annotation values, which can either be an IRI (URI), Literal or Anonymous Individual, with visitor methods. |
| OWLAnnotationValueVisitor | |
| OWLAnnotationValueVisitorEx<O> | |
| OWLAnonymousClassExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 The super interface for all class expressions which are not named class expressions (i.e. |
| OWLAnonymousIndividual |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLAsymmetricObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents AsymmetricObjectProperty axioms in the OWL 2 specification. |
| OWLAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLAxiomVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 26-Oct-2006 |
| OWLAxiomVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLBooleanClassExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLCardinalityRestriction<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>,F extends OWLPropertyRange> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLClass |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a Class in the OWL 2 specification. |
| OWLClassAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents ClassAssertion axioms in the OWL 2 Specification. |
| OWLClassAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLClassExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents Class Expressions in the OWL 2 specification. |
| OWLClassExpressionVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Nov-2006 |
| OWLClassExpressionVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLDataAllValuesFrom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataCardinalityRestriction |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataComplementOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataExactCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataFactory |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 An interface for creating entities, class expressions and axioms. |
| OWLDataHasValue |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataIntersectionOf |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 |
| OWLDataMaxCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataMinCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataOneOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataProperty |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDataPropertyAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DataPropertyAssertion in the OWL 2 Specification. |
| OWLDataPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 26-Oct-2006 A high level interface which marks data property axioms (e.g. |
| OWLDataPropertyCharacteristicAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 26-Oct-2006 |
| OWLDataPropertyDomainAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DataPropertyDomain axiom in the OWL 2 Specification. |
| OWLDataPropertyExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 A high level interface to describe different types of data properties. |
| OWLDataPropertyRangeAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DataPropertyRange axiom in the OWL 2 Specification. |
| OWLDataRange |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DataRange in the OWL 2 Specification. |
| OWLDataRangeVisitor | |
| OWLDataRangeVisitorEx<O> | |
| OWLDataSomeValuesFrom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DataSomeValuesFrom restriction in the OWL 2 Specification. |
| OWLDatatype |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a Datatype (named data range) in the OWL 2 Specification. |
| OWLDatatypeDefinitionAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 24-Mar-2009 Represents a DatatypeDefinition axiom in the OWL 2 Specification. |
| OWLDatatypeRestriction |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DatatypeRestriction data range in the OWL 2 Specification. |
| OWLDataUnionOf |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 Represents a DataUnionOf data range in the OWL 2 Specification. |
| OWLDataVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Nov-2006 A visitor which can visit various data ranges and constants. |
| OWLDataVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLDeclarationAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a Declaration in the OWL 2 Specification. |
| OWLDifferentIndividualsAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DifferentIndividuals axiom in the OWL 2 Specification. |
| OWLDisjointClassesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DisjointClasses axiom in the OWL 2 Specification. |
| OWLDisjointDataPropertiesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DisjointDataProperties axiom in the OWL 2 Specification. |
| OWLDisjointObjectPropertiesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLDisjointUnionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a DisjointUnion axiom in the OWL 2 Specification. |
| OWLEntity |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLEntityVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Nov-2006 |
| OWLEntityVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLEquivalentClassesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an EquivalentClasses axiom in the OWL 2 Specification. |
| OWLEquivalentDataPropertiesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an EquivalentDataProperties axiom in the OWL 2 Specification. |
| OWLEquivalentObjectPropertiesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLFacetRestriction |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 11-Jan-2007 A facet restriction is used to restrict a particular datatype. |
| OWLFunctionalDataPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a FunctionalDataProperty axiom in the OWL 2 Specification. |
| OWLFunctionalObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLHasKeyAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 Represents a HasKey axiom in the OWL 2 Specification. |
| OWLHasValueRestriction<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>,V extends OWLObject> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLImportsDeclaration |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 Represents an import statement in an ontology. |
| OWLIndividual |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 Represents a named or anonymous individual. |
| OWLIndividualAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLIndividualVisitor |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 20-Mar-2009 |
| OWLIndividualVisitorEx<O> |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 20-Mar-2009 |
| OWLInverseFunctionalObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLInverseObjectPropertiesAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 29-Nov-2006 Represents an InverseObjectProperties axiom in the OWL 2 Specification. |
| OWLIrreflexiveObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLLiteral |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a Literal in the OWL 2 Specification. |
| OWLLogicalAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 05-Dec-2006 A base interface of all axioms that affect the logical meaning of an ontology. |
| OWLLogicalAxiomVisitor |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 17-Jan-2009 |
| OWLLogicalAxiomVisitorEx<O> |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 17-Jan-2009 |
| OWLLogicalEntity |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 25-Nov-2009 An OWLLogicalEntity is an OWLEntity that is not an OWLAnnotationProperty . |
| OWLMutableOntology |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| OWLNamedIndividual |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 Represents a Named Individual in the OWL 2 Specification. |
| OWLNamedObject |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a named object for example, class, property, ontology etc. |
| OWLNamedObjectVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Nov-2006 |
| OWLNamedObjectVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLNaryAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 05-Jan-2010 |
| OWLNaryBooleanClassExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLNaryClassAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLNaryDataRange |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 |
| OWLNaryIndividualAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLNaryPropertyAxiom<P extends OWLPropertyExpression<?,?>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLNegativeDataPropertyAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a NegativeDataPropertyAssertion axiom in the OWL 2 Specification. |
| OWLNegativeObjectPropertyAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a NegativeObjectPropertyAssertion axiom in the OWL 2 Specification. |
| OWLObject |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLObjectAllValuesFrom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectAllValuesFrom restriction in the OWL 2 Specification. |
| OWLObjectCardinalityRestriction |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| OWLObjectComplementOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectComplementOf class expression in the OWL 2 Specification. |
| OWLObjectExactCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectExactCardinality restriction in the OWL 2 Specification. |
| OWLObjectHasSelf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectHasSelf class expression in the OWL 2 Specification. |
| OWLObjectHasValue |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectHasValue class expression in the OWL 2 Specification. |
| OWLObjectIntersectionOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 Represents an ObjectIntersectionOf class expression in the OWL 2 Specification. |
| OWLObjectInverseOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a ObjectInverseOf property expression in the OWL 2 Specification. |
| OWLObjectMaxCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectMaxCardinality restriction in the OWL 2 Specification. |
| OWLObjectMinCardinality |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a ObjectMinCardinality restriction in the OWL 2 Specification. |
| OWLObjectOneOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectOneOf class expression in the OWL 2 Specification. |
| OWLObjectProperty |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an Object Property in the OWL 2 Specification. |
| OWLObjectPropertyAssertionAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectPropertyAssertion axiom in the OWL 2 Specification. |
| OWLObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLObjectPropertyCharacteristicAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 26-Oct-2006 |
| OWLObjectPropertyDomainAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLObjectPropertyExpression |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLObjectPropertyRangeAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLObjectSomeValuesFrom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectSomeValuesFrom class expression in the OWL 2 Specification. |
| OWLObjectUnionOf |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an ObjectUnionOf class expression in the OWL 2 Specification. |
| OWLObjectVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 15-Nov-2006 |
| OWLObjectVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLOntology |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLOntologyChangeBroadcastStrategy |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 20-Nov-2006 |
| OWLOntologyChangeListener |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 20-Nov-2006 |
| OWLOntologyChangeProgressListener |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 12-Mar-2009 |
| OWLOntologyChangesVetoedListener |
Author: Matthew Horridge
The University of Manchester Bio-Health Informatics Group Date: 04-Jul-2010 |
| OWLOntologyChangeVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 12-Dec-2006 |
| OWLOntologyChangeVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 12-Dec-2006 |
| OWLOntologyFactory |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 An ontology factory is responsible from creating new ontologies and creating ontologies from ontology document IRIs. |
| OWLOntologyFactory.OWLOntologyCreationHandler |
An
OWLOntologyCreationHandler gets notified when the factory has created an empty
ontology (during the loading process). |
| OWLOntologyIRIMapper |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 The interface to an object that is capable of mapping ontology IRIs to document IRIs. |
| OWLOntologyLoaderListener |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 14-Apr-2008 |
| OWLOntologyManager |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLOntologyManagerFactory |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Mar-2007 |
| OWLOntologySetProvider |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 18-Apr-2007 Inputs to algorithms etc. |
| OWLOntologyStorer |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 02-Jan-2007 An ontology storer stores an ontology in a particular format at a location specified by a particular URI. |
| OWLProperty<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 23-Jan-2007 A marker interface for properties that aren't expression i.e. |
| OWLPropertyAssertionAxiom<P extends OWLPropertyExpression<?,?>,O extends OWLPropertyAssertionObject> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an Assertion in the OWL 2 specification. |
| OWLPropertyAssertionObject |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Mar-2009 |
| OWLPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 The base interface for property axioms. |
| OWLPropertyDomainAxiom<P extends OWLPropertyExpression<?,?>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents ObjectPropertyDomain axioms in the OWL 2 specification. |
| OWLPropertyExpression<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a property or possibly the inverse of a property. |
| OWLPropertyExpressionVisitor |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Nov-2006 |
| OWLPropertyExpressionVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| OWLPropertyRange |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 A marker interface, for objects that can be the ranges of properties |
| OWLPropertyRangeAxiom<P extends OWLPropertyExpression<?,?>,R extends OWLPropertyRange> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents ObjectPropertyRange axioms in the OWL 2 specification. |
| OWLQuantifiedDataRestriction |
A quantified data restriction
|
| OWLQuantifiedObjectRestriction |
A quantified object restriction
|
| OWLQuantifiedRestriction<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>,F extends OWLPropertyRange> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| OWLReflexiveObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents ReflexiveObjectProperty axioms in the OWL 2 specification. |
| OWLRestriction<R extends OWLPropertyRange,P extends OWLPropertyExpression<R,P>,F> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a restriction (Object Property Restriction or Data Property Restriction) in the OWL 2 specification. |
| OWLSameIndividualAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an SameIndividual axiom in the OWL 2 Specification. |
| OWLSubAnnotationPropertyOfAxiom |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 13-Jan-2009 Represents an SubAnnotationPropertyOf axiom in the OWL 2 Specification. |
| OWLSubClassOfAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an SubClassOf axiom in the OWL 2 Specification. |
| OWLSubClassOfAxiomSetShortCut |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 12-Jan-2010 |
| OWLSubClassOfAxiomShortCut |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 12-Jan-2010 |
| OWLSubDataPropertyOfAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents an SubDataPropertyOf axiom in the OWL 2 Specification. |
| OWLSubObjectPropertyOfAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLSubPropertyAxiom<P extends OWLPropertyExpression<?,?>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLSubPropertyChainOfAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 22-Nov-2006 Represents a SubObjectPropertyOf axiom in the OWL 2 Specification where the subproperty is a chain of properties. |
| OWLSymmetricObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 |
| OWLTransitiveObjectPropertyAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 Represents a TransitiveObjectProperty axiom in the OWL 2 Specification. |
| OWLUnaryPropertyAxiom<P extends OWLPropertyExpression<?,?>> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| PrefixManager |
Author: Matthew Horridge
The University Of Manchester Information Management Group Date: 10-Sep-2008 A prefix manager than can provide prefixes for prefix names. |
| SWRLArgument |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents an object in an atom (either a data object or and individual object) |
| SWRLAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents an atom in a rule. |
| SWRLBinaryAtom<A extends SWRLArgument,B extends SWRLArgument> |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents an atom with two ordered arguments |
| SWRLBuiltInAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLClassAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLDArgument |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents arguments in SWRLAtom s that are either
OWLLiteral s or variables for
individuals SWRLLiteralArgument |
| SWRLDataFactory |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm An interface to a factory that can create SWRL objects |
| SWRLDataPropertyAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLDataRangeAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLDifferentIndividualsAtom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 18-Feb-2007 |
| SWRLIArgument |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents arguments in SWRLAtom s that are either
OWLIndividual s or variables for
individuals SWRLIndividualArgument |
| SWRLIndividualArgument |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLLiteralArgument |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLObject |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLObjectPropertyAtom |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLObjectVisitor |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLObjectVisitorEx<O> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 16-Apr-2008 |
| SWRLPredicate |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 04-Jul-2009 |
| SWRLRule |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represent a rule. |
| SWRLSameIndividualAtom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 18-Feb-2007 |
| SWRLUnaryAtom<A extends SWRLArgument> |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm |
| SWRLVariable |
Author: Matthew Horridge
The University Of Manchester Medical Informatics Group Date: Jan 15, 2007<EMAIL_ADDRESS>www.cs.man.ac.uk/~horridgm Represents a variable that can appear in an atom. |
| Class | Description |
|---|---|
| AddAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| AddImport |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Mar-2009 |
| AddOntologyAnnotation |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 24-Mar-2009 |
| AnnotationChange |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Mar-2009 |
| AxiomType<C extends OWLAxiom> |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 27-Jul-2007 |
| DefaultChangeBroadcastStrategy |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 20-Nov-2006 |
| DefaultImpendingChangeBroadcastStrategy |
Author: Matthew Horridge
The University of Manchester Bio-Health Informatics Group Date: 04-Jul-2010 |
| EDTChangeBroadcastStrategy |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 14-Mar-2009 A change broadcast strategy which broadcasts all ontology changes in the Swing Even Dispatch Thread (EDT). |
| EntityType<E extends OWLEntity> |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 11-Oct-2009 |
| ImportChange |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Mar-2009 |
| IRI |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 14-Jan-2009 Represents International Resource Identifiers |
| MissingImportEvent |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 11-Apr-2008 |
| NodeID |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 15-Jan-2009 Represents the Node ID for anonymous individuals |
| OWLAxiomChange |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 12-Dec-2006 |
| OWLOntologyChange |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 |
| OWLOntologyFormat |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 02-Jan-2007 Represents the concrete representation format of an ontology. |
| OWLOntologyID |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Jan-2009 An object that identifies an ontology. |
| OWLOntologyLoaderConfiguration |
Author: Matthew Horridge
The University of Manchester Bio-Health Informatics Group Date: 15/12/2010 |
| OWLOntologyLoaderListener.LoadingEvent | |
| OWLOntologyLoaderListener.LoadingFinishedEvent |
Describes the situation when the loading process for an ontology has
finished.
|
| OWLOntologyLoaderListener.LoadingStartedEvent | |
| OWLOntologyManagerProperties |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 10-Apr-2008 |
| RemoveAxiom |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 25-Oct-2006 Represents an ontology change were an axiom will be removed from an ontology if the change is applied to an ontology. |
| RemoveImport |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Mar-2009 |
| RemoveOntologyAnnotation |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 24-Mar-2009 Represents an ontology change where an annotation is removed from an ontology. |
| SetOntologyID |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 01-Apr-2009 |
| SpecificOntologyChangeBroadcastStrategy |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 20-Nov-2006 A change broadcast strategy that broadcasts changes that have been applied to a specific ontology. |
| Enum | Description |
|---|---|
| ClassExpressionType |
Author: Matthew Horridge
The University Of Manchester Information Management Group Date: 08-Sep-2008 |
| DataRangeType |
Author: Matthew Horridge
The University of Manchester Information Management Group Represents the different types of OWL 2 data ranges. |
| MissingImportHandlingStrategy |
Author: Matthew Horridge
Stanford University Bio-Medical Informatics Research Group Date: 04/01/2012 Specifies how missing imports should be treated during loading. |
| OWLOntologyLoaderConfiguration.MissingOntologyHeaderStrategy |
strategies to cope with missing headers
|
| Exception | Description |
|---|---|
| ImmutableOWLOntologyChangeException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 An exception to describe a situation where there was an attempt to apply a change to an immutable ontology. |
| OWLException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 24-Oct-2006 The root of checked exceptions in the OWL API. |
| OWLOntologyAlreadyExistsException |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 18-Jan-2009 Indicates that an ontology with the given ontology IRI (and possible version IRI) exists. |
| OWLOntologyChangeException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 A high level exception interface that describes errors that occurred when applying changes to ontologies. |
| OWLOntologyChangeVetoException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 Describes a situation where a change was vetoed for some reason. |
| OWLOntologyCreationException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 An exception which describes an error during the creation of an ontology. |
| OWLOntologyDocumentAlreadyExistsException |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 22-Dec-2009 |
| OWLOntologyFactoryNotFoundException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 |
| OWLOntologyIRIMappingNotFoundException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 An exception which describes the situation where no ontology document IRI mapping could be found. |
| OWLOntologyRenameException |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 22-Dec-2009 |
| OWLOntologyResourceAccessException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 An exception to describe a problem in accessing an ontology. |
| OWLOntologyStorageException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 |
| OWLOntologyStorerNotFoundException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 |
| OWLRuntimeException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 The root of runtime exceptions in the OWL API. |
| UnknownOWLOntologyException |
Author: Matthew Horridge
The University Of Manchester Bio-Health Informatics Group Date: 13-Apr-2007 |
| UnloadableImportException |
Author: Matthew Horridge
The University of Manchester Information Management Group Date: 07-Dec-2009 |


Interactive Graphics - Homework 2
Stefano Esposito
Academic Year 2019/2020
Course held by Professor Marco Schaerf
For the development of the application I used as reference the code presented during the lessons of the course and also the code of the examples provided by the textbook.


Plumbing == Time Travel. It's just that instead of taking you back in time, it fast-forwards you to the end of whatever day you start it in.
1/9/2010, 5:04:08 PM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Plumbing == Time Travel. It's just that instead of taking you back in time, it fast-forwards you to the end of whatever day you start it in.
1/9/2010, 5:04:08 PM
Favs: 0
Retweets: 0
link


Privacy Policy of Do Clean
Do Clean is deeply committed to protecting the privacy of all our users. Therefore, we released this Privacy Policy and mean to clearly explain how we collect, use and manage the non-personal information and personal information collected by our services.
By using or interacting with our product, you are agreeing to the terms of this Policy.
Collection Personal Information
We do not collect Personal Information when you use Do Clean. Personal Information is information that identifies you or another person, such as your first name and last name, physical addresses, email addresses, telephone, fax, SSN, information stored within your device.
But you may be asked to provide your personal information anytime you are in contact with Do Clean. You are not required to provide the personal information that we have requested, but, if you chose not to do so, in many cases we will not be able to provide you with our products or services or respond to any queries you may have.
Collection Non-Personal Information
We also collect data in a form that does not, on its own, permit direct association with any specific individual. We may collect, use, transfer, and disclose non-personal information for any purpose.  For example, as many websites, we may use cookies to obtain the above information when you use our application.
Use of information
We may use your information to:
(1)Respond to your requests, inquiries, comments or concerns
(2)Provide technical, product and other support and help keep the Service working, safe and secure
(3)Offer you customized content and individualized personalization of the Service to make it more relevant to your interests and needs;
(4)Enhance, evaluate and improve the Service, its advertisements and promotional campaigns and our products and services and to develop new products and services;
(5)Identify and analyze usage trends, including for the purposes of research, audits, reporting and paying royalties and license fees to third-party content providers;
(6)Notify you about changes or updates to the Service and our products and services
(7)provide you special offers, promotions, surveys and other information about the Service as well as products, events and services of ours, our affiliates and non-affiliated third parties such as societies and sponsors.
Protection of Information
The security and confidentiality of your Information is very important to us, so we take security measures (including physical, electronic and procedural measures) to help safeguard your information from unauthorized access and disclosure. Please know that, despite our efforts, no security measures are perfect or impenetrable.
Changes to Our Privacy Policy
This privacy policy may change over time or be updated for what we recommend and we encourage you to continually review this page to ensure that you agree to such changes.
Contact
If you have any questions, comments or requests regarding this privacy policy or our processing of your information, please contact<EMAIL_ADDRESS>]


 Björn programmed and made levels, while I worked
on creating the graphics, music, and levels.
The game was released as licenceware by F1 in the U.K. but only eleven
people discovered the game. That's not a developers dream -eleven
users :-). We talked about putting it on the Aminet, but none of us had
any internet experience nor connections, so we never did.
However, the game never really left my thoughts so when I registered
as a Be developer I needed an easy project to start with; this game was
the obvious choice.
THANKS
Britta Larsson, Be inc, Jon watte(SoundPlayer),
Arvid Norberg, Daniel Lundin, Lars Vikberg(porting).
LEGAL
DynaMate is licensed under the MIT License.
UPDATES
Currently, the project is being maintained on
Github
by the Haiku community.


Before Change
alpha_ij_out = 1 - (k_out - 1) * integrate.quad(lambda x: (1 - x) ** (k_out - 2), 0, p_ij_out)[0]
N.add_edge(u, v, weight=w, alpha_out=float("%.4f" % alpha_ij_out))
elif k_out == 1 and G.in_degree(G.successors(u)[0]) == 1:
// we need to keep the connection as it is the only way to maintain the connectivity of the network
v = G.successors(u)[0]
w = G[u][v][weight]
After Change
alpha_ij_out = 1 - (k_out - 1) * integrate.quad(lambda x: (1 - x) ** (k_out - 2), 0, p_ij_out)[0]
N.add_edge(u, v, weight=w, alpha_out=float("%.4f" % alpha_ij_out))
elif k_out == 1 and G.in_degree(list(G.successors(u))[0]) == 1:
// we need to keep the connection as it is the only way to maintain the connectivity of the network
v = list(G.successors(u))[0]
w = G[u][v][weight]


Seamus Murphy
104 Captain Morgans Blvd ·<PHONE_NUMBER> ·<EMAIL_ADDRESS>I am a second year ITAS (Information Technology and Applied Systems) at VIU (Vancouver Island University).


Lewis Capaldi poses as High Street Musical star Troy Bolton thanks to NRJ Awards jacket
The Scots singer joked on Instagram about his new look while wearing a snazzy varsity jacket.
by Stephen Stewart, https://www.dailyrecord.co.uk/authors/stephen-stewart/Lewis Capaldi joked he was Troy Bolton from High School Musical as he posed in a snappy red and white varsity jacket given to him by the NRJ Awards.
The Scots singer took to Instagram to reveal he is in Cannes for the posh ceremony on Saturday night. After arriving at his hotel he was given a number of gifts by the French radio station.
His fave present was a bright red and white jacket – which Capaldi said made him look like high school basketball player Troy – played by Zac Efron.
Capaldi said: “See that? Is that the captain of the basketball team?”
“Is that the jock going out with the head cheerleader? He’s the coolest guy in school.
“Thank you NRJ Awards for this lovely jacket. It makes me feel like I’m Troy Bolton.
“I’m Troy Bolton – I’m the prom king, captain of the school basketball team, star quarterback.”
Lewis said he had been wanting to “spice up” his look for a while – making the memorable varsity jacket a perfect gift for him.
The Whitburn singer also revealed that the jacket had his name on the back. He joked: “It says my f***ing name on the back of it. You misspelled s**gger.”


‘Silent genocide happening in Zimbabwe’ says Chamisa
by Staff ReporterMDC leader Nelson Chamisa has accused President Emmerson Mnangagwa’s administration of committing a silent genocide through its failure to address the challenges facing the health sector.
Said Chamisa, “It surprises me that the Mnangagwa regime would fire medical doctors instead of simply paying them a living wage. These are fruits of illegitimacy. There is a silent genocide taking place in Zimbabwe as our hospitals have been shut down for 2 months now. Pay doctors a living wage!”
On Tuesday Health Services Board fired 77 doctors out of 80 who were arraigned before a disciplinary hearing.
Doctors have organised a solidarity protest meeting to be held at Parirenyatwa hospital on Wednesday.
Some social media users have accused Chamisa of being docile and failing to provide leadership.
 People are looking up to you for leadership. You need to realise that you are a leader and an influential one for that matter. Your tweets are now becoming annoying.”
Source – Byo24


---
layout: single
title: "[CFP] ICDF2C 2013 Note of Change of Date"
date: '2013-03-27T09:31:00.002+09:00'
author: Joshua James
tags:
- CFP 2013
- Conferences 2013
modified_time: '2013-03-27T09:31:39.696+09:00'
blogger_id: tag:blogger.com,1999:blog-2701259639305045003.single-3026053237524846746
blogger_orig_url: http://www.cybercrimetech.com/2013/03/cfp-icdf2c-2013-note-of-change-of-date.html
---
Please note, the dates for the ICDF2C 2013 have slightly changed.
Fifth International Conference on Digital Forensics and Cyber Crime - ICDF2C 2013
25-27 September 2013
Moscow, Russia
http://www.d-forensics.org/2013
Submission deadline: 17 May 2013
Notification of Acceptance: 17 June 2013
Camera Ready: 1st September 2013
Conference Date: 25th and 27th September 2013


Done for William Bevington’s Typography and Visual Design, this project is made up of 196 assets, each including a glass icon, a drink name, and various other data. The assets are combined to make three separate posters showing beers, wines, and cocktails, a 24-page monograph making use of Pete Brown’s Man Walks Into A Pub, and a fully interactive mobile site, ondrinking.com.


SetData(PCM, byte[], int, int)
Method
Namespace: Vox
Declared in: Vox.SoundBuffer
Sets the audio buffer PCM data.
Syntax
public void SetData(
PCM format,
byte[] data,
int size,
int frequency
)
Parameters
format
Audio format of the input data
data
Byte array with sound data
size
Size of data in bytes
frequency
Sound frequency
Remarks
8-bit PCM data is expressed as an unsigned value over the range 0 to 255, 128 being an
audio output level of zero. 16-bit PCM data is expressed as a signed value over the
range -32768 to 32767, 0 being an audio output level of zero. Stereo data is expressed
in interleaved format, left channel first. Buffers containing more than one channel of data
will be played without 3D spatialization.
Back to index


--- layout: resources title: Getting Started short: overview permalink: /resources/overview/ ---
This part of the website is still in progress. That being said, you can still use the sectional parts of the docs style guide, on the sidebar to your left.


The simplest API call is to ask the API what version it is running. With curl, this is done as:
curl https://mycoralapiserver.hostname/v0/version
And the server should reply with something like:
{ "versionNumber": "0.2.1" }
With javascript, this is:
There are a few ways to authenticate to coral api server. The simplest is a basic http auth with
coral credentials.
Here's the curl example:
curl -u username:password https://mycoralapiserver.hostname/v0/authenticate
And the server should reply with something like:
{"username":"auth-token","password":"ogps07otsl015pigm63d3snbsk"}
You may use auth-token that is return as way to authenticate on future requests so you don't have to continue sending your username and password.
The token will expire.
You may also configure the coral-api.yml file with a set of tokens that are persistent.
With javascript, this is:
You may change your password by using the resetPassword resource
Here's the curl example:
curl -X POST -H "Content-Type: application/json" -d '{"name":"coral", "password":"newPassword"}' -k -u coral:existingPassword https://mycoralapiserver.hostname/v0/resetPassword
With javascript, this is:
You may get a list of machines by using the machine resource
Here's the curl example:
curl -u username:password https://mycoralapiserver.hostname/v0/machine
With javascript, this is:
You may enable a machine by using the enable resource
Here's the curl example:
curl -X POST -H "Content-Type: application/json" -d '{"member":"coral", "project":"Bootstrap project", "item": "some instrument"}' -u coral:password https://mycoralapiserver.hostname/v0/enable
With javascript, this is:
You may disable a machine by using the disable resource
Here's the curl example:
curl -X POST -H "Content-Type: application/json" -d '{"item": "some instrument"}' -u coral:password https://mycoralapiserver.hostname/v0/disable
With javascript, this is:
You may reserve a machine by using the reservation resource
Here's the curl example:
curl -X POST -H "Content-Type: application/json" -d '{"member":"coral", "project":"Bootstrap project", "item": "some instrument", "bdate": "2015-01-29 15:00:00", "lengthInMinutes": 30}' -u coral:password https://mycoralapiserver.hostname/v0/reservation
With javascript, this is:
You may get a list of reservations for a machine by using the reservation resource
Here's the curl example:
curl -u coral:password https://mycoralapiserver.hostname/v0/reservation?machine=Test%20Machine
With javascript, this is:


If no colors are specified for both the data point and its associated series, the Chart control assigns colors to a data point. The control uses colors from the associated series' palette (set by the Series.Palette property) if one is specified, otherwise it uses the first available color from the control's palette (set by the Chart.Palette property). By default, the control retrieves colors sequentially from a palette.
A custom palette enables you to define your own set of colors to be used when drawing series or data points. If you define color values for the Chart.PaletteCustomColors property and set the Chart.Palette property to ChartColorPalette.None, the Chart uses the values in Chart.PaletteCustomColors to color series or data points.
Most pre-defined palettes in the Chart control contain more than 16 colors. When defining a custom palette, you should consider how many series or data points your chart will display and add the appropriate number of colors. If there are more series or data points than custom palette colors in your chart, the control displays some colors in the palette more than once.