Researching into technology

One thing I did yesturday was look into a main point of interest to navigate around the Archive platform that I am trying to create.

An idea was to geographically interpret data to where it was filmed. The idea is that the places could be related to the individual who uses the site, as a way into to engage with them on a somewhat personal level.

A way of doing this is to use Google Earth as an existing platform to geographically place markers that relate directly to the gallery. This way of contextualising the data would make it immediately obvious what was filmed near an individuals address. This in turn could create a manual exploration of the UK or even the world.

The main purpose: To engage with a user contextualising the area in which they live in with BBC related television.

I began to research online to find out the technologies used to plug-in Google Earth with any website.

I came across Google earth API which is:

The Google Earth Plug-in and its JavaScript API let you embed Google Earth, a true 3D digital globe, into your web pages. Using the API you can draw markers and lines, drape images over the terrain, add 3D  models, or load KML files, allowing you to build sophisticated 3D map applications. If you have an existing Maps API site, you can 3D-enable your page with as little as one line of code.


Ok, so if Google Earth can be plug-in really simply to any site this is a good start to use as a canvas for this way of displaying data.


KML is a file format used to display geographic data in an Earth browser such as Google Earth, Google Maps, and Google Maps for mobile.

It is common for XML to be used in interchanging data over the Internet. RFC 3023 gives rules for the construction of Internet Media Types for use when sending XML. It also defines the types “application/xml” and “text/xml”, which say only that the data is in XML, and nothing about its semantics. The use of “text/xml” has been criticized as a potential source of encoding problems and is now in the process of being deprecated.[16] RFC 3023 also recommends that XML-based languages be given media types beginning in “application/” and ending in “+xml”; for example “application/svg+xml” for SVG.

Further guidelines for the use of XML in a networked context may be found in RFC 3470, also known as IETF BCP 70; this document is very wide-ranging and covers many aspects of designing and deploying an XML-based language.


Extensible Markup Language (XML) is a set of rules for encoding documents in machine-readable form. It is defined in the XML 1.0 Specification[4] produced by theW3C, and several other related specifications, all gratis open standards.

Links in with JavaScript and HTML.

XML Separates Data from HTML

If you need to display dynamic data in your HTML document, it will take a lot of work to edit the HTML each time the data changes.

With XML, data can be stored in separate XML files. This way you can concentrate on using HTML for layout and display, and be sure that changes in the underlying data will not require any changes to the HTML.

With a few lines of JavaScript code, you can read an external XML file and update the data content of your web page.

XML Does Not DO Anything

Maybe it is a little hard to understand, but XML does not DO anything. XML was created to structure, store, and transport information.

XML is Used to Create New Internet Languages

A lot of new Internet languages are created with XML.

Here are some examples:

  • WSDL for describing available web services
  • WAP and WML as markup languages for handheld devices
  • RSS languages for news feeds
  • RDF and OWL for describing resources and ontology
  • SMIL for describing multimedia for the web

What is CSS?

  • CSS stands for Cascading Style Sheets
  • Styles define how to display HTML elements
  • Styles were added to HTML 4.0 to solve a problem
  • External Style Sheets can save a lot of work
  • External Style Sheets are stored in CSS files


Scaling is one thing I need to look into, as I have been told, scaling up from a small image is easier than scaling down. If it works small, then it’ll work big (to some extent.)

Usability Metrics

These are the parameters and considerations that have to be realised. These are the considerations that exist in many of our lives. These are the things that needed to be taken into account so no problems will be produced from the product. With digital interactive technologies many things such as navigation, intuitive interaction, resolution, sound etc.


I have started to loose my rag with this project today, which is not a good thing. I am getting really bogged down with the technical side of things. I just don’t have enough experience yet to really understand whats going on exactly. I feel my creative side of design wants to take over (which isn’t a bad thing) but I really wanted to use this project as a way of exploring technology.


I attended the D&AD Sharpener event this evening for some guidance and advice. The event was set up for past judges to come and display their insight into what is expected at through the D&AD judging process. Multiple examples of the past years projects and some of their own were shown. At the end of the event I had a massive brainstorm due to seeing the winning entry to the BBC brief last year. It gave me a new way of thinking. I feel I don’t need to know how to build this site fully at this point in the year but understand about the technologies that surround it, at the end of the day its about the quality of the idea that will be the most valuable asset to myself.

This entry was posted in PG02 - Negotiated. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s