Reports
INFO

The purpose of this database is to implement a common ontology development architecture for use by the IEEE Standard Upper Ontology (SUO) Working Group, and thereby facilitate the development of the IEEE Standard Upper Ontology.

Coda provides a collaborative framework that people can use to document and define ontologies. Coda addresses the following requirements:

- open to input from multiple contributors
- a contributors input is easily published on the web, directly by the contributor
- readers can view any contributor's work
- contributors can only edit their own contributions
- teams of people can collaborate to develop consensus definitions, or agree to disagree
- multiple ontology efforts / directions can be pursued in parallel
- support for namespaces within each ontology effort
- openness to different notations, and different levels of formalization, to facilitate flexibility in exploring new ideas, as well as rigorous formalization of ideas.

Coda is essentially a "glorified dictionary". Contributors to Coda use it to define elements of an ontology.

Each entry in Coda may be specified as belonging to an "ontology workspace". An ontology workspace is a name for an overall ontology effort, within which terms are being defined. For example, "Merged Ontology" could be an ontology workspace.

Each entry in Coda may also be specified as belonging to an "ontology namespace". Within an ontology workspace, multiple namespaces may be defined and interrelated, using the SUO "Ontology Modules" database.

Users may create namespaces as they wish, or not use the namespace feature if they prefer. Users may use "dot notation" (or any other notation they invent) to indicate that a namespace occurs within a hierarchy of namespaces, e.g. "FooOntology.Generic.Physics".

Coda follows an "open-source", "Build It And They Will Come" approach: Users can put their own contributions directly into the database. They can correspond directly with each other to resolve differences of opinion and agree upon a single definition, or they can agree to disagree and submit different definitions for the same terms.

Readers can choose to see all the contributions or just those from a particular author or for a particular ontology namespace or workspace.

HOW TO GET EDIT ACCESS TO CODA
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Begin by clicking on the "SIGN IN" link at the upper right corner of the SUO Coda web page:

 https://www.quickbase.com/db/6urbwpxk 

This will open a "sign-in" web page in your browser. Click "Register". Register (for free), using the same email address that you used for subscribing to the SUO mailing list (see "Email Reflectors" at http://suo.ieee.org).

At the end of the registration process you will be sent an email message. When you receive it, click on the link in it. You should be taken to a webpage that says "Welcome to Quickbase -- congratulations, you are now a registered user". Click Next. You'll be taken to the SUO Coda web page. You can view the database, but not yet edit it.

Next, send email to phil.jackson@computer.org, requesting access to Coda and giving the email address you used for registering with Quickbase. Within a few days, edit access should be granted.

To verify that you have edit access, go back to the SUO Coda web page periodically, and perform the following steps:

Click "Sign in" at the upper right area of the page. Enter your email address or the screen name you chose during registration, and the password you chose. Your "My Quickbase" page will be displayed. Click "My Favorites", and your list of quickbases will be displayed. One of them should be Coda. Click on Coda, and you should see the Coda webpage. You should now also see "Add Record" at the upper left area of the page. If you click "Add Record" you can add entries to Coda, and you should only be able to edit entries that you have added.

COPYRIGHT INFORMATION
~~~~~~~~~~~~~~~~~~~~~
With each contribution to the Coda database, please include a copyright statement, e.g. of the form:

"Copyright 2001 by <author's name>. Permission is granted to IEEE to reproduce and distribute without restriction, and without charge to IEEE."

Contributors should only submit material to which they have copyright, or which they have permission to submit granted by the copyright owner.

In submitting information, contributors represent that permission will be granted to IEEE to reproduce and distribute the submitted material without restriction, and without charge to IEEE.

Contributors retain their rights to copyright, and to separately modify and distribute the original material they submit.

Use or non-use by IEEE of any material submitted will be at the discretion of IEEE and the Standard Upper Ontology Working Group.

HISTORY OF CODA
~~~~~~~~~~~~~~~~
This database was originally created by Philip Jackson, with advice from Robert E. Kent and James Schoening. The first formal content in this database was provided by Robert E. Kent.

Manager: ieee_suo
Account: ieee_suo
Last modified: June 26, 2017 1:53 AM (PDT)
application stats

Report Name *
Description
Reports and Charts Panel
Each table has a panel listing its reports and charts, organized in groups.
Please wait while your new report is saved...
Field label
Column heading override
Justification
What does auto mean?
Fields in:

Fields to Extract:

Name for the new table:
Items in the new table are called:

When you bring additional fields into a conversion, Quickbase often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quickbase finds three different locations for Acme. A single value in the column you're converting can only match one value in any additional field. Quickbase needs you to clean up the extra cities before it can create your new table. To do so, you have one of two choices:

  • If you want to create three separate Acme records (Acme-New York, Acme-Dallas and Acme-Portland) click the Conform link at the top of the column.
  • If the dissimilar entries are mistakes (say Acme only has one office in New York and the other locations are data-entry errors) go back into your table and correct the inconsistencies—in this case, changing all locations to New York. Then try the conversion again.

Read more about converting a column into a table.

Show fields from Show fields from Show fields from a related table

We're glad you're interested in doing more with Quickbase!

Now we need to make you official before you share apps or manage your account.

Verifying your email lets you share Quickbase with others in your company.

Your work email
Your company