3. Variables and Assignment. So far, whenever we have puts ed a string or a number, the thing we puts ed is gone. What I mean is, if we wanted to print something out twice, we would have to type it in twice: puts ' ...you can say that again... ' puts ' ...you can say that again.. ...you can say that again... ...you can say that again... It would be nice if we could just type it in once and then hang on to it... store it somewhere. To store the string in your computer's memory, we need to give the string a name. Assignment , and they call the names variables . MyString = ' ...you can say that again... ' puts myString puts myString Whenever you tried to do something to myString , the program did it to ' ...you can say that again... ' instead.
Name = ' Patricia Rosanna Jessica Mildred Oppenheimer ' puts ' My name is ' + name + ' . ' puts ' Wow! My name is Patricia Rosanna Jessica Mildred Oppenheimer. Also, just as we can an object to a variable, we can a different object to that variable. Just another string 15 8 8 eight 8.
Zope. Annotea Protocols. This version: Latest version: Previous version: Authors: Ralph Swick <swick> Eric Prud'hommeaux <eric> Marja-Riitta Koivunen <marja> Jose Kahan <jose> Copyright © 2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. Abstract Annotea is a system for creating and publishing shareable annotations of Web documents. Status of this document This section describes the status of this document at the time of its publication. This document is a public DRAFT for discussion. The aim of this DRAFT document is to describe the general Annotea protocol as the authors currently see it. Our future plans include a revision of the protocol to add some extra information (attributions) about the origin of the data. We expect to have more discussions in the www-annotation@w3.org mailing list about attributions and other protocol issues that may arise.
Table of contents. Mozilla Firefox. Algae: Table of Contents. Algae: Examples. Following are several examples designed to show off Algae's capabilities as well as to give you a feel for how it is used. The `examples' directory in the source distribution of Algae contains some additional code for perusal. 3.1 Temperature Conversion This Algae program prints a table of Fahrenheit temperatures and their Celsius equivalents: Its output looks like this: This program does quite a bit in only four lines. In the second line we define the Fahrenheit temperatures for our table. The third line computes the Celsius equivalents using the familiar conversion formula. Even though all of the terms so far have been integers, celsius is a real-valued vector. The last line prints the temperatures out as a matrix, with the Fahrenheit temperatures in the first column and their Celsius equivalents in the second column. 3.2 Reading and Summing Numbers This Algae program reads a bunch of numbers, adds them up, and prints the result: 3.3 Integer Powers.
Algae RDF Query Language. Abstract The document describes Algae, an RDF query language used in the W3C Annotea Server. Algae has also served as a research platform for studies in interfacing with relational databases and system information. Status of this Document This document is a work in progress by the author and does not represent any endorsement from the W3C. Table of contents Introduction The Algae query language evolved to serve the needs of W3C's Annotea protocol. Informal Description Algae can be used to query a graph, insert data into a graph, or write rules to automatically insert data when a query is matches. Query Description This section describes how an Algae query selects nodes and statements from an RDF graph.
Example 1: find nodes of a given type (RDQL Example 1) ask (? The query pattern (inside 'ask()') is a series (in this case, a single one) of query terms. The query terms may be simplified (or at least shortened) by declaring namespace prefixes. Example 2: query with multiple terms (RDQL Example 2) Annotea: Metadata based annotation infrastructure - Slide list. Dublin Core Element Set, Version 1.1 - Reference Description.
Introduction The document summarizes the updated definitions for the Dublin Core metadata elements as originally defined in [RFC2413]. These new definitions will be officially known as Version 1.1. The definitions utilise a formal standard for the description of metadata elements. This formalisation helps to improve consistency with other metadata communities and enhances the clarity, scope, and internal consistency of the Dublin Core metadata element definitions. Each Dublin Core element is defined using a set of ten attributes from the ISO/IEC 11179 [ISO11179] standard for the description of data elements. These include: Fortunately, six of the above ten attributes are common to all the Dublin Core elements.
Version: 1.1 Registration Authority: Dublin Core Metadata Initiative Language: en Obligation: Optional Datatype: Character String Maximum Occurrence: Unlimited The definitions provided here include both the conceptual and representational form of the Dublin Core elements. References. Annotea: A Generic Annotation Environment Using RDF/XML - Slide list. Annotea related documents. Annotea Quick Tutorial. This tutorial contains the basic steps needed for creating and deleting annotations on documents or on the content of the annotations themselves or replies. It also describes how to create a reply to an annotation. You can also refer to a more thorough manual of the Amaya user interface to annotations. Note: The replies and annotations on annotations or replies will be available starting from Amaya version 5.3 and will need an Annotea server that understands replies. Step 0: Configuring servers This step needs to be done only once unless you want to change the server settings.
Select the "Configure... " menu command and a dialog box will appear to help you to configure annotation servers. Write the name of the annotation post server in the "Annotation post server" field and click the "Apply" button. Add the post server to the list of annotation servers. Note: It is a good practice to always post the replies to the same server as where the head annotation of the thread is.