Attention all business owners! Do you know the answer to this question: Who gets to keep the website after you divorce your webmaster?

Just like in a marriage, it all depends on the pre-nuptial agreement (contract). Do you have one?

My personal disclaimer: Some of this information may be about legal issues; however this article is not intended as a substitute for legal advice. I am not an attorney nor do I play one on webTV therefore you should consult with an attorney familiar with the laws concerning internet and intellectual property.

Ok, now on with the story, the short version. . .

Here's the situation, for whatever reason the client decided not to pay their annual bill for web hosting services. Even though there were several attempts to reach the client the bill went unpaid for more than 90 days. As a result, the hosting was cancelled and the site was removed from the server.

Several months later the client sent this exact message: "you have my website and I need you to let me know how to get it back, like I said before I paid you money to build it so....? that money had nothing to do with hosting or anything".

Just because you paid for the development of your website does not mean you own it. There are Intellectual Property laws designed to protect the creator and to encourage the creator to create. If you hired a company they own the software development and website design produced by its employees. If you hired an independent contractor you must obtain a written "assignment" of the copyright in the commissioned work from them.

Most business owners unknowingly give their webmaster complete control over their business website. Even if you don't have a pre-nuptial agreement (contract) or own your website you can still maintain some control. While you and your webmaster are honeymooning be sure you can document the answer to these questions:

1. What software was used to develop the website?

• Exact name
• Version
• Software website

2. How to access the code?

3. Where is the code located on the server?

4. How to change the content?

• Graphics
• Text

5. How to create a weekly back up?

6. How to grant access to additional users?

7. How to obtain the master copies of your website design?

As a business owner, how many people realize their webmaster is like their spouse? Voluntarily joined for life (or until divorce), not many! Just like in marriage a prenuptial agreement (contract) is a practical solution to dealing with the risks and problematic topic of who gets to keep the website after your divorce.

Introduction

Semantic web as defined by the creator of the web Tim Berners-Lee is "a web of data, in some ways like a global database" (Berners-Lee, 1998). To elaborate further Mr. Berners-Lee explains in an interview held by IDG Now, data is expressed on computers as associated files with applications that deal specifically with information, an example would be, data in calendars, bank systems, spreadsheets, and database application. Looking at a web page, data is not clearly defined and not associated with any of the applications usually on computers. Semantic web will allow data to interact and connect together; it will bring on a common data format for all applications, for databases and web pages alike (Moon, 1999). Semantic web is not to build an artificial intelligence system which allows computers to understand what humans write on web pages; on the contrary, it is an attempt to make web pages more understandable and well-defined to support automatic extraction of data from within web content (Berners-Lee, 1998).

Analysis

The emergence of the web and the way HTML took off was driven by how society's needed to grew, from Internet chat to file transfer to high-end communities through blogs and wiki's. HTML was not limited to web content, knowledge base and help files adapted the language as a format to document software applications and provide training material. The revolution of technologies on the Internet allowed companies like Google to index pages; a thought that was very far away, says Tim Berners-Lee in his lecture at MIT. Web services have evolved to pave the road for distributed information and modular programming allowing interoperability among sites. Through XML, data in one site can be used by another using the common protocols and standards supported by both (Berners-Lee, 1998). XML defines schemas that deal with fields of data, what is required is a system that can tell the computer what sort of information (data) it can derive from within a page (Moon, 1999). With Web 3.0 a site will provide data that can be navigated through and extracted from multiple sites, this is a result of the fact that semantic web data model is closely related to a relational database where records of data share common fields that connect them together (Berners-Lee, 1998).

The solution provided to support semantic web is in the form of metadata that describes the data contained on web pages. Resource Description Framework (RDF) is a base to manage metadata; it is the ground that computers can use to exchange and interact with applications on the Web (W3C RFC, 1999). The applications for RDF include digital libraries, online catalogs, and indexing systems that are usually associated with content and content relationships models deployed in most web pages. With RDF data within business portals will be analyzed and identified as resources, properties, or statements transparent to the domain, further more, the specifications will merge with other documents to comprise a framework of classes. Classes organized as a hierarchy comprises a schema that can be reusable as metadata definitions along side multiple platforms. Resources created in this hierarchy can be identified using a resource identifier (URI), which enables a document given to a machine with this identification to be recognized by the system and triggers it to dig and find similar data (Berners-Lee, 1998).

Implications

Semantic web can be the solution to overpower the limitations of current information management systems in finding and extracting data from unorganized resources. RDF is meant to describe any data regardless of its character, location, source, or type, the concept of URI is richer to uniquely identify any object on the web (Berners-Lee, 1998). The pillars of Semantic web are standards and common protocols that are the bases for knowledge representation; HTML, RDF, the data language resource description web ontology language (OWL) that describes to the machine what is going on, in addition to RDF1 which is a query language to make inquiries among machines much easer, will all emerge and collaborate to bring in more to the web and more intelligent programs that will bring the Internet more closer (Cleave, 2004).

The current research and implementation of Abilene network and the Next Generation Internet (NGI) Internet 2 of high-performance backbone network linking major universities and research labs across the US, is a good foundation for what Semantic web can do, and represent the perfect platform for grid computing, digital libraries, virtual laboratories, and distance learning (Abilene, Internet2). Internet2 or I2 was developed by a group of universities in 1996 providing improved connectivity standards to reach 10gbps (gigabits per second). With more than 227 universities and libraries connected, network based applications and experimental programs can run on this network of high-bandwidth connection feeding on the latest technology of gigabit Ethernet and IP protocol version 6 (Reardon, 2004). Semantic web standards can be the base of material and data distributed on this network, providing the best test platform to explore the full potential and what can be achieved.

Conclusion

Tim Berners-Lee believes that with Web 3.0 we can succeed and fantastic things can happen, but the infrastructure need to be built, laws of privacy and security need to be revised and honored, further more, the web need to remain open for researchers to allow for continuous upgrade and development. Semantic web will kick off when individuals materialize the need to work on data processing, and think about collaborating their data, with company's information and that of the government (Moon, 1999).

References:

1. Berners-Lee, Tim. 1998. Semantic Web Road map.W3C team. (14 October 1998) http://www.w3.org/ DesignIssues/Semantic (accessed 16 Jul 2007)
2. Moon, Peter. 1999. The future of the Web as seen by its creator. IT World IDG Now (7 July 1999) http://www.itworld.com/Tech/4535/070709future/ (accessed 14 Jul 2007)
3. W3C RFC. 1999. Resource Description Framework (RDF) Model and Syntax Specification. W3 Consortium (5 January 1999) http:// www.w3.org/TR/PR-rdf-syntax/ (accessed 20 Jul 2007)
4. Cleave, Kenith Van. 2004. Regis University Database Practicum Experience. Regis University. (14 November 2004) http:// trackit.arn.regis.edu/dba/Thesis%2520Papers/

   kvancleave_2004Bfinalreport_20041118.pdf (accessed 16 Jul 2007)

5. Abilene, Internet2. http://abilene.internet2.edu/about/ (accessed 17 Jul 2007)
6. Reardon, Marguerite. 2004. Internet2: 2004 and beyond. CNET, News (24 August 2004) http:// news.com.com/2100-1034_3-5321053.html (accessed 19 Jul 2007)

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.