This is the first in a series of blogs in which we will try to introduce you to the concepts behind the TOPSAN Protein Syntax and the TOPSAN semantic notation system. The first article will be the basics of engaging the notation environment and some simple examples of how to use the notation system. Next we will describe how to use obtain and use the semantic information that has been embedded in TOPSAN, compose queries and analyze the available information. Finally we will describe the more advanced concepts involved with the controlled ontology of predicates that the TOPSAN Protein Syntax describes.
What is the semantic web:
How the data is being stored:
All calls embedded in the text of TOPSAN documents begin and end with the double brackets
{{
and
}}
. You then make a call to ‘note.link’. There are two ways to call the function, via sequential argument or by named arguments. For sequential arguments, wrap the arguments with ‘(‘ and ‘)’, and type in the values. This is usually only used for the two argument call, when passing the predicate and the object values. Alternatively, if you want to manipulate additional arguments the named argument format is preferred. In this method, the arguments are wrapped with ‘{‘ and ‘}’, and the name of each of argument is given followed by a ‘:’ and then the value. When using the named argument format you don’t have to remember a specific order of arguments.
Relationships can go in both directions. By default the subject is the current page and the passed value is the object. To reverse this relationship, so that the relationship statement is about the external database pointing to the current page, set ‘rev:true’.
Embed a link to PFAM:
{{ note.link( ‘memberOf’, ‘PFAM:PF07980′ ) }}
{{ note.link( ‘citation’, ‘PMID:19191477′ ) }}
Reverse a relationship:
{{ note.link{ rel:’similar’, value:’UNIPROT:Q8A1G2′, rev:true } }}
{{ note.link{ about:’TOPSAN:2aam’, rel:’similar’, value:’UNIPROT:Q8A1G2′ } }}



| Predicate | Definition |
| similar | Represents a connection between two proteins that are homologous or structurally similar |
| classifiedWith | Connects a protein to an assigned function type |
| memberOf | Connects a single element to group to which it is a part of |
| citation | A connection to a literature citation |
When describing a link to another database, you can use prefix codes that will recognized by TOPSAN and translated accordingly. We have a set of 10 linked databases currently, but this will grow as needed. To use the prefix code, simply name the database by code, followed by a colon and the database identified from the database, ie “PFAM:PF0798″, “UNIPROT:Q8A1G2″, or “PDB:1AAC”.
| Prefix | Database |
| GO | The Gene Ontology database |
| PFAM | The Pfam protein family database |
| UNIPROT | The Uniprot protein database |
| EC | The Enzyme Catalogue |
| TOPSAN | The TOPSAN protein annotation system |
| TAXON | The NCBI taxonomic codes |
| PDB | The Protein Data Base |
| PMID | Pubmed |
| SCOP | Scop domain IDs, ie d1wy7a1 |
| SUNID | Scop ID: ie, 51349 -> Alpha and beta proteins (a/b) |
No references found.