COMS E 6125 Web-en. Hanced Information Management (WHIM) Prof. Gail Kaiser Spring 2012 21 February 2012 Kaiser: COMS E 6125 1
Today’s Topic: • Introduction to the Semantic Web • RDF • Ontologies 21 February 2012 Kaiser: COMS E 6125 2
Simplicity is Good • The World Wide Web contains huge amounts of information created by many different organizations, communities and individuals for many different reasons • Web users can easily access this information by specifying a known URL or using a search engine, and following links to find other related resources • This simplicity is a key aspect that made the Web so popular 21 February 2012 Kaiser: COMS E 6125 3
Simplicity is Bad • The simplicity of the current Web has a price • It is very easy to get lost, or discover irrelevant or unrelated information • For instance, if we search for courses taught by a person named “Gail Kaiser”, we might find all kinds of other information • https: //www. google. com/search? q=courses+taught +by+gail+kaiser&ie=utf-8&oe=utf 8&aq=t&rls=org. mozilla: en. US: official&client=firefox-a • The problem is that the search engine does know what “courses” or “taught” means 21 February 2012 Kaiser: COMS E 6125 4
Machine accessible meaning (What it’s like to be a machine) name education CV work private 21 February 2012 Kaiser: COMS E 6125 5
So what does this mean? • What’s a “CV”? • What’s a “name”? • Etc. Ø Need semantics 21 February 2012 Kaiser: COMS E 6125 6
What to do? • Develop enabling standards and technologies – to help machines understand more information on the Web – so that they can support richer discovery, data integration, navigation and automation of tasks 21 February 2012 Kaiser: COMS E 6125 7
Add Metadata • Associate semantically rich, descriptive information with any resource • For instance, add metadata about teaching, so we can search for documents that have metadata specifying “Gail Kaiser” as a “teacher” (or “instructor”) 21 February 2012 Kaiser: COMS E 6125 8
The Semantic Web • Provides a common framework that allows data to be shared and reused across application, enterprise and community boundaries • Not only provides URLs for documents, but to people, concepts and relationships • By giving unique identifiers to the person, the role “teacher” and the concept of “course”, we make very clear who the person is and the corresponding relation between this person and a particular document 21 February 2012 Kaiser: COMS E 6125 9
What’s the difference? • Most Web content today is designed for humans to read, not for computer programs to manipulate meaningfully • Computers can adeptly parse Web pages for layout and routine processing—here a header, there a link to another page—but in general, computers have no reliable way to process the semantics • The Semantic Web brings structure to the meaningful content of Web pages, creating an environment where software agents roaming from page to page can carry out sophisticated tasks for users 21 February 2012 Kaiser: COMS E 6125 10
What’s the difference? The Semantic Web is not a separate web but an extension of the current web, in which information is given well-defined meaning, better enabling computers and people to work in co-operation. [Berners-Lee et al. , 2001] 21 February 2012 Kaiser: COMS E 6125 11
Wasn’t that what XML was supposed to do? • Yes and no • For the Semantic Web to function, computers must have access to structured collections of information and to sets of inference rules that they can use to conduct automated reasoning 21 February 2012 Kaiser: COMS E 6125 12
Isn’t that just Knowledge Representation? • Traditional knowledge representation systems typically have been centralized, requiring everyone to share exactly the same definition of common concepts such as “parent” or “vehicle” • But central control is stifling, and doesn’t scale • Which is why centralized hypertext link servers were abandoned for WWW 21 February 2012 Kaiser: COMS E 6125 13
What about Web Services? • Web services are computational programs accessed using Web technologies • They may or may not operate on Web pages as data • But when they do, the semantics are implied by WSDL descriptions but basically hidden inside the code • There is no way for an arbitrary Web service or other program to “understand” the semantics of Web pages 21 February 2012 Kaiser: COMS E 6125 14
Semantic Web Layers (T. Berners-Lee) 21 February 2012 Kaiser: COMS E 6125 15
Start with XML, not HTML: <H 1>WHIM</H 1> <UL> <LI>Instructor: Gail Kaiser <LI>Students: Donald Duck </UL> XML: <course date=“Spring 2012”> <title>WHIM</title> <instructor>Gail Kaiser</instructor> <students>Donald Duck</students> </course> 21 February 2012 Kaiser: COMS E 6125 16
XML document = labeled tree • node = label + attr/values + contents <course date=“. . . ”> <title>. . . </title> <instructor>. . . </instructor> <name>. . . </name> <http>. . . </http> <students>. . . </students> </course> = course title instructor students name http • XML Schema: grammars for describing legal trees and datatypes 21 February 2012 Kaiser: COMS E 6125 17
Why not use XML Tags to represent Semantics? • Syntax: the structure of your data • Semantics: the meaning of your data • Two conditions necessary for interoperability: – Adopt a common syntax: enables applications to parse the data – Adopt a means for understanding the semantics: enables applications to use the data 21 February 2012 Kaiser: COMS E 6125 18
XML and Semantics? <title> … <title> • But what does “title” mean? • If we ask google, we get (on the 1 st page) – – – – Sports equipment and competitions Prefix or suffix added to person’s name Laws regarding rights to a piece of property HTML tag Women’s underwear Library search for books A research paper on “ENVIRONMENTAL AND ECONOMIC COSTS ASSOCIATED WITH NONINDIGENOUS SPECIES IN THE UNITED STATES” 21 February 2012 Kaiser: COMS E 6125 19
XML Limitations for Semantic Markup • XML makes no commitment on: Domain-specific vocabulary Modeling primitives • Requires pre-arranged agreement on & • Only feasible for closed collaboration – agents in a small & stable community – pages on a small & stable intranet • Not suited for sharing Web resources 21 February 2012 Kaiser: COMS E 6125 20
XML machine accessible meaning name < name > <education> < CV > CV <work> <private> < private > 21 February 2012 Kaiser: COMS E 6125 21
Beyond XML • XML lets everyone create their own tags • Scripts, or programs, can make use of these tags in sophisticated ways - but the programmer has to know what the page writer uses each tag for • XML allows users to add structure to their documents but says nothing about what the structures mean 21 February 2012 Kaiser: COMS E 6125 22
Semantic Web Layers 21 February 2012 Kaiser: COMS E 6125 23
Add RDF = Resource Description Framework • Encodes meaning in sets of triples - subject, predicate and object - analogous to the subject, verb and object of an elementary sentence • Makes assertions that particular things (people, Web pages or whatever) have properties (such as “is a sister of”, “is the author of”) with certain values (another person, another Web page) • This structure can describe much of the data processed by machines 21 February 2012 Kaiser: COMS E 6125 24
Example • Imagine that we want to state the fact that someone named Gail Kaiser wrote a particular Web page • A straightforward way to state this in English would be in the form of a simple statement such as: http: //www. cs. columbia. edu/~kaiser/index. ht ml has an author whose value is Gail Kaiser 21 February 2012 Kaiser: COMS E 6125 25
Making Statements about Resources • We need a way to identify the thing we want to describe (the Web page) • We need a way to identify a specific property (author) of the thing that we want to describe • We need a way to identify the thing we want to assign as the value of this property (who the author is), for the thing we want to describe 21 February 2012 Kaiser: COMS E 6125 26
Making Statements about Resources • In the example, we used the Web page's URL (Uniform Resource Locator) to identify it - subject • We used the word “author” to identify the property we want to talk about - predicate • And the phrase “Gail Kaiser” to identify the thing (a person) we want to say is the value of this property - object 21 February 2012 Kaiser: COMS E 6125 27
Many Statements can be made • We could state other properties of this Web page by writing additional English statements of the same general form http: //www. cs. columbia. edu/~kaiser/index. ht ml has a modification-date whose value is February 01, 2012 http: //www. cs. columbia. edu/~kaiser/index. ht ml has a size whose value is 20, 860 bytes 21 February 2012 Kaiser: COMS E 6125 28
But what do these Statements actually mean? • Subject and object can each be identified by a URL, just as used in a link on a Web page • The verbs – predicates – can also be identified by URLs, which enables anyone to define a new concept, a new predicate, just by defining a URL for it somewhere on the Web (a “Web resource”) • The URLs ensure that concepts are not just words in a document, but are tied to a unique definition that everyone can find on the Web 21 February 2012 Kaiser: COMS E 6125 29
Web Resources • RDF is a language for representing information about resources on the World Wide Web • It is particularly intended for representing metadata about Web resources, such as the title, author, modification date and size of a Web page 21 February 2012 Kaiser: COMS E 6125 30
Generalized Resources • By generalizing the concept of a “Web resource”, RDF can be used to represent information about things that can be identified on the Web, even when they can't be directly retrieved on the Web • Examples include the author of the web page 21 February 2012 Kaiser: COMS E 6125 31
Reconsider Example http: //www. cs. columbia. edu/~kaiser/in dex. html has an author whose value is Gail Kaiser Neither the notion of a “author” nor Gail Kaiser can be retrieved from the Web Thus we need URIs in addition to URLs 21 February 2012 Kaiser: COMS E 6125 32
Concept Graphs • RDF is based on the idea of identifying things using URIs • And describing resources (subjects) in terms of simple properties (verbs or predicates) and property values (objects) • This enables RDF to represent related concepts as a graph of nodes and arcs representing the resources, their properties and values 21 February 2012 Kaiser: COMS E 6125 33
Concept Graph Example • XML syntax • Chained triples form a graph http: //www. psl. cs. columbia. edu/courses/whim/ site-owner W 3 C Kaiser site-owner kaiser+6125 @. . . describes http: //www. w 3. org/RDF 21 February 2012 email <rdf: Description rdf: about=“#Kaiser”> <email>kaiser+6125@. . . </email> </rdf: Description> Kaiser: COMS E 6125 34
Information Exchange • RDF provides a common framework for expressing this information so it can be exchanged between applications without loss of meaning • The ability to exchange information between different applications means that the information may be made available to applications other than those for which it was originally created • Application designers can leverage the availability of common RDF parsers and processing tools • RDF is written in XML format further leveraging XML tools and experience 21 February 2012 Kaiser: COMS E 6125 35
What is RDF (again) ? • RDF is a data model – the model is domain-neutral and applicationneutral – the model can be viewed as directed, labeled graphs or as an object-oriented model (object/attribute/value) • RDF data model is an abstract, conceptual layer independent of XML • consequently, XML is a transfer syntax for RDF, not a component of RDF • RDF data might never occur in XML form 21 February 2012 Kaiser: COMS E 6125 36
RDF Model • RDF “statements” consist of resources (= nodes) = subject which have properties = predicate which have values = object (= nodes, strings) 21 February 2012 Kaiser: COMS E 6125 37
RDF Model resource property value “http: //www. w 3. org/TR/REC-rdf-syntax/ has the editor Dave Beckett” http: //www. w 3. org/TR/REC-rdf-syntax/ editor “Dave Beckett” 21 February 2012 Kaiser: COMS E 6125 38
RDF Model Example “W 3 C” dc: Publisher http: //www. w 3. org/TR/REC-rdf-syntax/ dc: Creator dc: Date “Dave Beckett” “ 2004 -02 -10” 21 February 2012 Kaiser: COMS E 6125 39
Complex Values • So far, values of properties have been strings • A graph node (corresponding to a resource) also can be the value of a property – arbitrarily complex tree and graph structures are possible – syntactically, values can be embedded (i. e. , lexically in-line) or referenced (linked) 21 February 2012 Kaiser: COMS E 6125 40
Complex Values http: //www. w 3. org/TR/REC-rdf-syntax/ dc: Creator p: Name “Dave Beckett” p: EMail “mailto: dave@dajobe. org” 21 February 2012 Kaiser: COMS E 6125 41
Complex Values • Corresponding triples { “http: //www. w 3. org/TR/REC-rdf-syntax/”, dc: Creator, x } { x, p: Name, “Dave Beckett” } { x, p: EMail, “dave@dajobe. org” } http: //www. w 3. org/TR/REC-rdf-syntax/ dc: Creator p: Name “Dave Beckett” p: EMail “mailto: dave@dajobe. org” 21 February 2012 Kaiser: COMS E 6125 42
Containers • Containers are collections - allow grouping of resources (or literal values) • It is possible to make statements about the container (as a whole) or about its members individually Different types of containers – bag - unordered collection – seq - ordered collection (= “sequence”) – alt - represents alternatives • It is possible to create collections based on URI patterns – e. g. , all files in a particular web site • Duplicate values are permitted - no mechanism to enforce unique value constraints 21 February 2012 Kaiser: COMS E 6125 43
Containers http: //www. w 3. org/TR/REC-rdf-syntax dc: Creator rdf: Type rdf: _1 rdf: Seq rdf: _2 “Dave Beckett” “Brian Mc. Bride” 21 February 2012 Kaiser: COMS E 6125 44
Higher-order Statements • One can make RDF statements about other RDF statements • Example: “The Library of Congress affiliates Dave Beckett as the author of the RDF Syntax spec” • Allow us to express beliefs (and other modalities) • Important for trust models, digital signatures, etc. • Constitute metadata about metadata • Represented by modeling RDF in RDF itself 21 February 2012 Kaiser: COMS E 6125 45
Reification http: //www. w 3. org/TR/REC-rdf-syntax dc: Creator “Dave Beckett” dc: Creator “Library of Congress” • The dotted box corresponds to the following statements • • { x, rdf: predicate, “dc: creator” } { x, rdf: subject, “http: //www. w 3. org/TR/REC-rdf-syntax } { x, rdf: object, “Dave Beckett” } { x, rdf: type, “rdf: statement” } 21 February 2012 Kaiser: COMS E 6125 46
Reification • Reification allows a computer to process an abstraction as if it were any other datum • RDF is not really second-order • But it does provide a built-in predicate vocabulary for reification 21 February 2012 Kaiser: COMS E 6125 47
Reification n. Any statement can be an object (graphs can be nested) NYT claims 21 February 2012 pers 05 Author-of ISBN. . . <rdf: Description rdf: about=“#NYT”> <claims> <rdf: Description rdf: about=“#pers 05”> <author. Of>ISBN. . . </author. Of> </rdf: Description> </claims> </rdf: Description> Kaiser: COMS E 6125 48
RDF Schema • Defines small vocabulary for RDF: • Class, sub. Class. Of, type • Property, sub. Property. Of • domain, range • Organizes this vocabulary in a typed hierarchy • Vocabulary can be used to define other vocabularies for your application domain Person sub. Class. Of Student domain has. Super. Visor sub. Class. Of range Researcher type Swap type has. Super. Visor Gail 49
RDF Schema syntax in XML <rdf: Description ID="Motor. Vehicle"> <rdf: type resource="http: //www. w 3. org/. . . #Class"/> <rdf: sub. Class. Of rdf: resource="http: //www. w 3. org/. . . #Resource"/> </rdf: Description> <rdf: Description ID="Truck"> <rdf: type resource="http: //www. w 3. org/. . . #Class"/> <rdf: sub. Class. Of rdf: resource="#Motor. Vehicle"/> </rdf: Description> <rdf: Description ID="registered. To"> <rdf: type resource="http: //www. w 3. org/. . . #Property"/> <rdf: domain rdf: resource="#Motor. Vehicle"/> <rdf: range rdf: resource="#Person"/> </rdf: Description> <rdf: Description ID=”owned. By"> <rdf: type resource="http: //www. w 3. org/. . . #Property"/> <rdf: sub. Property. Of rdf: resource="#registered. To"/> 21 February 2012 Kaiser: COMS E 6125 </rdf: Description> 50
Conclusions about RDF • Next step up from plain XML – modeling primitives – possible to define vocabulary • However: – no precisely described meaning – no inference model • Problematic examples: • “Columbus believed that the world is flat” • “Gloria believes that the Web should be delivered on CD-ROM” 21 February 2012 Kaiser: COMS E 6125 51
Where do we get the precisely defined meaning? • Two databases may use different identifiers for the same concept, such as zip code vs. postal code • A program that wants to compare or combine information across the two databases has to know that these two terms mean the same thing • The program must have a way to discover such common meanings for whatever databases it encounters • A solution to this problem is provided by collections of information called ontologies 21 February 2012 Kaiser: COMS E 6125 52
Semantic Web Layers 21 February 2012 Kaiser: COMS E 6125 53
What is an Ontology? • In philosophy, an ontology is a theory about the nature of existence, of what types of things exist; ontology as a discipline studies such theories • Semantic Web researchers (and various other communities) have co-opted the term for their own jargon • For Semantic Web researchers, an ontology is a document or file that formally defines the relationships among terms • The most typical kind of ontology for the Web has a taxonomy and a set of inference rules 21 February 2012 Kaiser: COMS E 6125 54
Menu What is a Taxonomy? Object Person Student Researcher Topic Document Semantics Doctoral Student Ph. D Student F-Logic Ontology Taxonomy = segmentation, classification and ordering of elements into a classification system according to the relationships between each other 21 February 2012 Kaiser: COMS E 6125 55
Taxonomies • A taxonomy defines classes of objects and relations among them • For example, an address may be defined as a type of location, and city codes may be defined to apply only to locations • If city codes must be of type city and cities generally have Web sites, we can discuss the Web site associated with a city code even if no database links a city code directly to a Web site 21 February 2012 Kaiser: COMS E 6125 56
An Ontology also provides a form of Thesaurus Menu Object Person Topic Document Student Researcher Semantics Doctoral Student Ph. D Student synonym F-Logic Ontology similar • Terminology for specific domain • Graph with primitives, fixed relationships (similar, synonym) 21 February 2012 Kaiser: COMS E 6125 57
An Ontology also provides a Topic Map Menu Object Person knows Topic described_in Document writes Student Researcher Semantics Doctoral Student Ph. D Student synonym Tel Affiliation F-Logic Ontology similar • Topics (nodes), relationships and occurrences (to documents) • Useful for navigation and visualization 21 February 2012 Kaiser: COMS E 6125 58
The Taxonomy is Augmented by Inference Rules Object is_a knows Person described_in Topic Document writes is_a Student Researcher Semantics is_a Doctoral Student Ph. D Student F-Logic instance_of Tel Ontology similar Affiliation Swapneel Sheth Rules T P writes described_in D is_about D T T is_about P knows D T
Inference Rules • An ontology may express the rule “If a city code is associated with a state code, and an address uses that city code, then that address has the associated state code” • A program could then deduce, for instance, that a Columbia University address, being in New York City, must be in New York State, which is in the U. S. , and therefore should be formatted to U. S. standards • The computer doesn't truly “understand” any of this information • But it can now manipulate the terms much more effectively in ways that are useful and meaningful to the human user 21 February 2012 Kaiser: COMS E 6125 60
Solution to Terminology Problems • The meaning of terms or XML tags used on a Web page can be defined by pointers from the page to an ontology • The same problems as before now arise if I point to an ontology that defines addresses as containing a zip code and you point to one that uses postal code • This can be resolved if ontologies (or other Web services) provide equivalence relations: one or both of our ontologies may contain the information that my zip code is equivalent to your postal code 21 February 2012 Kaiser: COMS E 6125 61
Using Ontologies • Ontologies can be used in a simple fashion to improve the accuracy of Web searches • The search program can look for only those pages that refer to a precise concept instead of all the ones using ambiguous keywords • More advanced applications could use ontologies to relate the information on a page to the associated knowledge structures and inference rules 21 February 2012 Kaiser: COMS E 6125 62
Example • Suppose you wish to find the Ms. Cook you met at a trade conference last year • You don't remember her first name, but you remember that she worked for one of your clients and that her brother was a student at your alma mater 21 February 2012 Kaiser: COMS E 6125 63
Example • An intelligent search program can sift through all the pages of people whose name is “Cook” • Sidestep all the pages relating to cooks, cooking, the Cook Islands and so forth • Find the person named Cook who works for a company that's on your client list • And follow links to Web pages of their relatives to track down if any are in school at the right place 21 February 2012 Kaiser: COMS E 6125 64
Agents • The real power of the Semantic Web will be realized when people create (many) programs that collect Web content from diverse sources, process the information and exchange the results with other programs • The effectiveness of such software agents will increase exponentially as more machine-readable Web content and automated services (including other agents) become available 21 February 2012 Kaiser: COMS E 6125 65
Proofs • The Semantic Web promotes this synergy: even agents that were not expressly designed to work together can transfer data among themselves when the data comes with semantics • An important facet of agents' functioning will be the exchange of “proofs” 21 February 2012 Kaiser: COMS E 6125 66
Example • Suppose Ms. Cook's contact information has been located by an online service, and places her in Baghdad • You want to check this, so your computer asks the service for a proof of its answer • An inference engine on your computer verifies this proof, i. e. , that this Ms. Cook indeed matches the one you were seeking, and it can show you the relevant Web pages if you still have doubts 21 February 2012 Kaiser: COMS E 6125 67
Service Discovery • Many automated Web-based services already exist without semantics • But current service discovery initiatives attack the problem at a structural or syntactic level, and rely heavily on standardization of a predetermined set of functionality descriptions 21 February 2012 Kaiser: COMS E 6125 68
Service Discovery • Other programs such as agents have no way to locate a service that will perform a specific function • This process can happen only when there is a common language to describe a service in a way that lets other agents “understand” both the function offered and how to take advantage of it • The consumer and producer agents can reach a shared understanding by exchanging ontologies, which provide the vocabulary needed for discussion • Semantics also makes it easier to take advantage of a service that only partially matches a request 21 February 2012 Kaiser: COMS E 6125 69
Non-Web Applications • The Semantic Web can extend into our physical world • URIs can point to anything, including physical entities, which means we can use RDF to describe devices such as cell phones and TVs • Such devices can advertise their functionality — what they can do and how they are controlled — much like software agents • Semantic descriptions of device capabilities and functionality will let us achieve “home automation” with minimal human intervention 21 February 2012 Kaiser: COMS E 6125 70
Examples • When you answer your phone, other sound is automatically turned down – Instead of having to program each specific appliance, you could program such a function once and for all to cover every local device that advertises having a volume control — the TV, the DVD player, the media players on the laptop, … • Your Web-enabled microwave oven consults the frozen-food manufacturer's Web site for optimal cooking parameters 21 February 2012 Kaiser: COMS E 6125 71
OWL Delivers Ontologies that Work on the Web • What's needed next is a way to develop domain specific vocabularies • An ontology defines the terms used to describe and represent an area of knowledge • Ontologies include computer-usable definitions of basic concepts in the domain and the relationships among them, making that knowledge reusable 21 February 2012 Kaiser: COMS E 6125 72
OWL = Web Ontology Language • For defining structured, Web-based ontologies enabling richer integration and interoperability of data among descriptive communities • Uses URIs for naming • Uses RDF and RDF Schema for description • Adds vocabulary for describing relations between classes (e. g. disjointness), cardinality (e. g. "exactly one"), characteristics of properties (e. g. symmetry) 21 February 2012 Kaiser: COMS E 6125 73
Semantic Web Layers 21 February 2012 Kaiser: COMS E 6125 74
Semantic Web Layers • The Unicode and URI layers make sure that we use international character sets and provide means for identifying the objects in the Semantic Web • The XML layer with namespaces and schema definitions make sure we can integrate the Semantic Web definitions with other XML-based standards 21 February 2012 Kaiser: COMS E 6125 75
Semantic Web Layers • RDF and RDFSchema make it possible to make statements about objects with URIs and define vocabularies that can be referred to by URIs • RDFSchema defines the XML vocabulary for defining classes, subclasses, properties and subproperties • The Ontology layer (OWL) supports the evolution of vocabularies as it can define relations between the different concepts 21 February 2012 Kaiser: COMS E 6125 76
Semantic Web Layers • The top layers, Logic, Proof and Trust, are “under development” • The Logic layer will enable the writing of rules • The Proof layer will execute the rules • The Trust layer together with the Digital Signature layer will provide mechanisms for applications to determine whether to trust the given proof or not 21 February 2012 Kaiser: COMS E 6125 77
Semantic Web Layers Work in Progress Standard RFC 21 February 2012 Kaiser: COMS E 6125 78
Next Assignment: Midterm Paper • Each paper must have a title, an author (with contact information), a brief abstract (about 100 words), an introductory section, some number of body sections (3 -5 is typical), a concluding section, and a bibliographic list of references – most of which are cited somewhere in the paper • Do not simply survey some topic: Instead compare this to that, argue a position in favor or against something, evaluate something according to some meaningful criteria, etc. • Pretend your reader will be another member of the class, who has heard all the same lectures you have/will, but may not know anything at all about the specifics of your particular topic 21 February 2012 Kaiser: COMS E 6125 79
Midterm Paper: Academic Honesty • All copied material must be short and must be explicitly “quoted” and [cited] • Non-copied material based conceptually on references must also be [cited] – do not paraphrase, write in your own words • Example: – “If you don’t like the Android phones on the market, just wait a minute. ” [1] – [1] David Pogue, Android Phones Take a Power Trip, The New York Times, online edition, February 8, 2012, http: //www. nytimes. com/2012/02/09/technology/personaltech/an droid-phones-go-on-a-power-trip-state-of-the-art. html 21 February 2012 Kaiser: COMS E 6125 80
Midterm Paper: Logistics • Due Tuesday February 28 th by 10 am • Approximately 15 pages (not including figures and reference list) • Submit by posting in Full Papers folder on Course. Works • Must be in a format I can read, and the filename must adhere to the required naming convention (e. g. , Full_Paper_Jane_Doe. pdf). 21 February 2012 Kaiser: COMS E 6125 81
Upcoming Assignments • Full paper due Tuesday February 28 th • Project proposal due Tuesday March 6 th • Presentation proposal also due Tuesday March 6 th 21 February 2012 Kaiser: COMS E 6125 82
COMS E 6125 Web-en. Hanced Information Management (WHIM) Prof. Gail Kaiser Spring 2012 21 February 2012 Kaiser: COMS E 6125 83
Скачать презентацию COMS E 6125 Web-en Hanced Information Management WHIM
0f7b7f36f860da931009d28fa4be835c.ppt