Primer on Notation3 (N3)


Understanding namespaces

Less confusing explanation of XML Namespaces compared to what’s on W3C –

… One XML document may use part elements to describe parts of books, another may use part elements to describe parts of cars. An XML application has no way of knowing how to process a part element unless it has some additional information external to the document.

The XML Namespaces Recommendation tries to improve this situation by extending the data model to allow element type names and attribute names to be qualified with a URI. Thus a document that describes parts of cars can use part qualified by one URI; and a document that describes parts of books can use part qualified by another URI. I’ll call the combination of a local name and a qualifying URI a universal name. The role of the URI in a universal name is purely to allow applications to recognize the name. There are no guarantees about the resource identified by the URI. The XML Namespaces Recommendation does not require element type names and attribute names to be universal names; they are also allowed to be local names.

The source of all Semantic Web information

As soon as i read up on everything here and memorize – – I will be a semantic web guru…


Ontologies/Schema for the Semantic Web – brief explanation

This is a very nice explanation from

there’s no way for a computer or human to figure out what a specific term means, or how it should be used. The use of all these URIs is useless if we never describe what they mean. This is where schemas and ontologies come in. A schema and an ontology are ways to describe the meaning and realtionships of terms. This description (in RDF, of course) helps computer systems use terms more easily, and decide how to convert between them.

Project Portfolio Management

Just some important information to keep in mind about porfolio management (source – The PDMA ToolBook for New Product Development)

There are four goals in Portfolio Management

  1. Value Maximization: Allocate resources so as to maximize the value of the portfolio.
  2. Balance of projects: say high-risk & low-risk, or long-term & short-term, etc.
  3. Strategic direction: Portfolio should truly reflect business strategy
  4. Right number of projects: Keep in mind resource available.

All four goals have the potential to compete with each other.

More sematic web reading stuff

So i found an article (third one listed below) and it pointed me to another as pre-read (the second one below) which in turn points me to a high level (first one below). So i’m going to read in this sequence and get sematic-fied.. (Free dictionary meaning of semantic)

  1. High level
  2. Semantic Web in breadth
  3. Semantic Web – An Intro

And then there’s one for developers

Resource Description Framework (RDF)

More semantic web jargon to be familiar with. Again explained much better on Wikipedia. Here’s my understanding.

RDF is a way to model metadata and i think it offers a way to explain relationship between web resources. The example in Wikipedia is “sky has the color blue”. They say it gives information in ‘triples‘ (RDF terminology) or as subject-predicate-object. i.e. sky is the subject, has the color is the predicate and object is blue.

I’m going to try an example of my own here – IT helps to serve banking. So i guess if a machine was to get a user request for IT information, it will understand the relationship based on users interest in banking (possibly through some kind of profile information) to offer results specific to IT as it relates to banking. No guarantees that this is right. I’m just guessing. I’ll probably get it in like 50 years.

Lots more to read up on this. Also need to read up about RDF Schema (RDFS) and Web Ontology Language (OWL). Familiarize with other Ontology Languages. Good heavens – Turtle, N-Triples!!! When am i ever going to know everything there is to know about the Semantic web…. 😦

More later