Email Registration of a Nomenclator CCSO Site

This electronic mail form collects the following information about CCSO
servers:

1. CCSO Server Location Information so we can make queries. For example, we
need to know the domain name, such as ns.uiuc.edu, and port number, typically
105, for your server.

2. CCSO Administrator Information so we can find you later. For example, we
would appreciate knowing your name, address, phone and email address. We will
update you about our efforts to include your server in the global white pages.

3. Implicit and Explicit Constraints on your database entries, so we don't have
to bug you with irrelevant queries. For example, if your database contains
information about an organization in New Jersey and Pennsylvania in the US, and
only that, the Organization, State-or-Province and Country attributes are
constrained. Knowing these constraints allows us to prevent queries about other
organizations, states or countries from being sent to your server.

4. A Data Mapping from your schema to ours, so we can understand what you're
talking about and vice versa. For example, if each person in your data base has
an Office-Phone with an implicit country code of 1 and area code of 908, then
our Phone attribute is the concatenation of "+1 908" and your Office-Phone
attribute. We ask you to answer some simple questions that allow us to create
detailed mappings for you. You can then review these mappings later for
correctness.

5. Additional Comments and Information so we'll know your interests and
concerns.

This form is being parsed automatically. To facilitate this, we have
placed numbered prompts (e.g., <1>) right after the questions. Please
enter your responses right after the prompt.


After you complete the form, please mail it to nomenclator@research.bell-labs.com.

-------------------------------------------------------------------------------

Section 1: Provide CCSO Server Location Information

Please register information about your site. The host name and port number of
your server are used in subsequent forms to identify your registration.

Organization: <1>

Host name of your CCSO server (e.g. ds.uiuc.edu): <2>
(If you replicate your database, this is the host name of your primary server.)

Port number of your CCSO server (e.g. 105): <3>
(If you replicate your database, this is the port number of your primary
server.)

Servers that provide replicas of your database:  <4>
(Please enter information for replicas in the format "host:port" separated 
by commas.)
Example: uiuc-ds.att.com:105, cs.uiuc.edu:105


-------------------------------------------------------------------------------

Section 2: Provide CCSO Administrator Information

Please register information about yourself or the person who will be
administering pilot activities at your site.

Name: <5>

Email: <6>

Phone: <7>

Street Address: <8>                             
Room: <9>
City: <10>
State/Province: <11>
Postal Code: <12>                                
Country: <13>

-------------------------------------------------------------------------------

Section 3: Provide Implicit and Explicit Constraint Information

Many of the fields in your database are either implicit or taken from a very
small domain. For example, the state is always "New Jersey" and the phone
numbers have area code "908" or "201". We are starting our indexing activities
by collecting these values. The attributes listed below are from Nomenclator's
People schema.

Please tell us the possible values of the attributes at your site that
correspond to the Nomenclator attributes below. Assume that your attributes can
be mapped to our attributes. We'll be taking care of that in the next section.
If your site has too many possible values for an attribute to list them or if
the possible values change frequently, please leave all the fields for the
attribute blank. We will be indexing this kind of information later. If your
site has few possible values but more than you can list here, please place the
values on separate lines in a file and give us the URL of that file. Please
separate different possible values for an attribute with commas. If the value
contains a comma, you can use a backslash to escape the comma, i.e. use "\,".

You can view the full schema description of an attribute at 
/cm/cs/what/nomenclator/nomen_people.html.
A brief synopsis of available information is provided with the attribute.

Organization: the organization to which the person belongs. 
Example Input: AT&T
Your Input: <14>

Organization-Type: the type of the organization. This is an experimental
                   attribute.
Please check as many as apply: (put any character after the prompt)

Educational:
	 Pre-University   <15>
	 University       <16>
	 University (only M.S. and Doctorate)   <17>
	 Vocational       <18>
	 Other            <19>

Companies:
	R & D    	<20>
	Manufacturing  	<21>
	Finance  	<22>	
	Services  	<23>
	Publishing  	<24>
	Retail 		<25>
	Other		<26>

Organizations:
	Professional     <27>
	Interest Groups  <28>
   	Recreational     <29>
	Political        <30>
    	Other            <31>

Government:
	National/Federal  <32>
	State/Provincial  <33>
	Municipal         <34>
	Military          <35>
	Other	          <36>

Division: the organization division to which the person belongs.
Example Input: Bell Laboratories
Your Input: <37>

If you need more space but are willing to supply a list of your divisions,
please enter a URL where we can obtain the list.

Division-Type: the types of the organization divisions. This is an experimental
               attribute.

Please check as many as apply: (put any character after the prompt)

Educational:
	 Pre-University   <38>
	 University       <39>
	 University (only M.S. and Doctorate)   <40>
	 Vocational       <41>
	 Other            <42>

Companies:
	R & D    	<43>
	Manufacturing  	<44>
	Finance  	<45>	
	Services  	<46>
	Publishing  	<47>
	Retail 		<48>
	Other		<49>

Organizations:
	Professional     <50>
	Interest Groups  <51>
   	Recreational     <52>
	Political        <53>
    	Other            <54>

Government:
	National/Federal  <55>
	State/Provincial  <56>
	Municipal         <57>
	Military          <58>
	Other	          <59>


Department: the organization department to which the person belongs.
Example Input: Computing Science, Electrical Engineering
Your Input: <60>

City: the city in the person's organization address.
Example Input: Murray Hill, Holmdel, Naperville
Your Input: <61>

State-or-Province: State or province name in the person's organization address.
Example Input: NJ, IL
Your Input: <62>

Postal-Code: the postal code or zipcode in the person's organization address.
             Note that you may also enter a common prefix followed by a "*".
Example Input: 07*, 60566
Your Input: <63>

Country: the country in the person's organization address.
Example Input: US
Your Input: <64>

Geographic-Region: the geographic region of the country of the person's
                   organization address.
Example Input: East Coast, Midwest
Your Input: <65>

Phone: the full organization telephone number of the person including country
       code, city/area code, number and extension.
       Note that you may also enter a common prefix followed by a "*".
Example Input: +1-908-*, +1-708-979-*
Your Input: <66>

-------------------------------------------------------------------------------
Section 4a. Provide an Example Mapping from Your Schema to Ours

Did you know that the public CCSO servers use more than 900 different attribute
names? Nomenclator can integrate the commonly used attributes into a global
schema of people information, but we need your help. We need to map the schema
at your CCSO server to the Nomenclator schema. The information collected by
this section and Section 4b will help us to create an approximate mapping for
your site. We will then verify the mapping with the CCSO administrator who you
registered earlier.

                              --------------------

A Note on Data Types

Most CCSO servers have one set of attributes that describe people. Some servers
have different or conflicting attributes for different types of people. For
example, address might be the organization address for a person of
type="faculty" but the home address for a person of type="student."

Check here if your database has different or conflicting attributes for
different types of people <67> 

If you have this kind of database, please choose one type of person and fill
out this section for that type. You can optionally repeat this section later 
for different types of people.

                              --------------------


If you have different types of information in your database, please enter the
attribute name and value that identifies the type of information in this
example:
Example Input: type="person"
Example Input: type="faculty"
Example Input: type="faculty" or type="student"
Your Input: <68>

Please select a typical entry of this type in your database and give us a query
that will allow us to retrieve it from your database:
Example Input: alias="g-emlin"
Your Input: <69>

Please show us what that entry would look like in our database by filling in
the fields in this section. You may have to break up fields in your selected
entry to fill in the fields in our schema. That's fine. You may need to supply
information that everyone knows, e.g. your country, but that is not listed
explicitly in the your database entry. You can also leave fields blank if the
information requested is not supported by your database.

Name-First: the given name of the person.
Example Input: Grace
Your Input: <70>

Name-Middle: the middle or second given name of the person
Example Input: Rita
Your Input: <71>

Name-Last: the surname or family name of the person.
Example Input: Emlin
Your Input: <72>

Name-Suffix: a suffix for the full name of the person.
Example Input: Senior
Your Input: <73>

Email: the external Internet electronic mail address of the person.
Example Input: gre@research.att.com
Your Input: <74>

MHSmail: the external MHS (X.400) electronic mail address of the person.
Example Input: C=us;ADMD=123mail;PRMD=us;O=some;S=person;g=e.x.
Your Input: <75>

WWW-Homepage: the URL of the person's World-Wide Web homepage.
Example Input: http://www.cs.att.com/csrc/nomen/nomen_join_ccso_d.html
Your Input: <76>

Organization: the organization to which the person belongs.
Example Input: AT&T
Your Input: <77>

Division: the organization division to which the person belongs.
Example Input: Bell Laboratories
Your Input: <78>

Department: the organization department to which the person belongs.
Example Input: Computing Science Research Center
Your Input: <79>

Title: the title or role of the person in the organization.
Example Input: Member of Technical Staff
Your Input: <80>

Building: the building and room in the person's organization address.
Example Input: MH 2C-501
Your Input: <81>

Street: the street in the person's organization address.
Example Input: 600 Mountain Avenue
Your Input: <82>

City: the city in the person's organization address.
Example Input: Murray Hill
Your Input: <83>

State-or-Province: State or province name in the person's organization address.
Example Input: New Jersey
Your Input: <84>

Postal-Code: the postal code or zipcode in the person's organization address.
Example Input: 07974-0636
Your Input: <85>

Country: the country in the person's organization address.
Example Input: US
Your Input: <86>

Phone: the full organization telephone number of the person including country
       code, city/area code, number and extension.
Example Input: +1 908 582 4148
Your Input: <87>

Home-Apartment: the apartment number in the person's home address.
Example Input: U
Your Input: <88>

Home-Street: the street in the person's home address.
Example Input: 13300 East Capitol Street
Your Input: <89>

Home-City: the city in the person's home address.
Example Input: Toronto
Your Input: <90>

Home-State-or-Province: State or province name in the person's home address
Example Input: Ontario
Your Input: <91>

Home-Postal-Code: the postal code or zipcode in the person's home address.
Example Input: 0A724
Your Input: <92>

Home-Country: the country in the person's home address.
Example Input: CA
Your Input: <93>

Home-Phone: the full home telephone number of the person including country
            code, city/area code, number and extension.
Example Input: +2 202 555 1212
Your Input: <94>

Last-Modified: the date the record was last modified.
Example Input: Wed Apr 12 23:42:40 EDT 1995
Your Input: <95>

                              --------------------

Please supply queries for three additional records in your database that we
can use to test our mappings: Example Input: alias="j-ordille"
Your First Input: <96>
Your Second Input: <97>
Your Third Input:  <98>
                              --------------------


Are the fields in your database in a fixed format, perhaps because they are
automatically generated from a personnel database, or does the format vary?

The fields in our database have a fixed format. (y/n) <99>

Some fields in our database have a fixed format. (y/n) <100>
   
    Please list the fields that have 
    a fixed format below. Field names should be separated by commas. 
    Commas in field names are preceded by a backslash, e.g. "\,".
    Example Input: name, phone, email, city\,state
    Your Input:  <101>

The fields in our database vary in format (y/n) <102>

                              --------------------

Are there any fields in our database that you always or typically abbreviate in
your database? For example, you may always abbreviate Country and sometimes
abbreviate State-or-Province.

Please supply the names of the fields that are always abbreviated below. Please
separate field names by commas.
Example Input: Country, Home-Country
Your Input: <103>

Please supply the names of the fields that are sometimes abbreviated below.
Please separate field names by commas.
Example Input: State-or-Province, Home-State-or-Province
Your Input: <104>

                              --------------------


Please supply the names of any fields in your database that do not correspond
to fields in our database BUT that you would like included in Nomenclator.
Please separate field names by commas. Commas in field names should be preceded
by a backslash, e.g. "\,"
Example Input: secretary-phone, picture
Your Input: <105>

-------------------------------------------------------------------------------

Section 4b: Provide an Example Mapping from Our Schema to Yours

Please take the following entry from our global schema and show us how you
would represent it in your database. Complete the mapping for a field even if
the field's value violates a constraint on your database. For example, the
entries in your database might all be from Japan but this entry is from the
US. If our field has no equivalent field in your database, leave it out of the
mapping. If a field in your database has no equivalent in our database, leave
it out of the mapping.

Entry in the Global Schema
--------------------------

Name-First: Grace

Name-Middle: Rita

Name-Last: Emlin

Name-Suffix: Senior

Email: gre@research.att.com

MHSmail: C=us;ADMD=attmail;PRMD=att;O=some;S=person;g=e.x.

WWW-Homepage: http://www.cs.att.com/csrc/nomen/nomen_join_ccso_d.html

Organization: AT&T

Division: Bell Laboratories

Department: Computing Science Research Center

Title: Member of Technical Staff

Building: MH 2C-501

Street: 600 Mountain Avenue

City: Murray Hill

State-or-Province: New Jersey

Postal-Code: 07974-0636

Country: US

Phone: +1 908 582 4148

Home-Apartment: U

Home-Street: 13300 East Capitol Street

Home-City: Toronto

Home-State-or-Province: Ontario

Home-Postal-Code: 0A724

Home-Country: CA

Home-Phone: +2 202 555 1212

Last-Modified: Wed Apr 12 23:42:40 EDT 1995

                              --------------------
NOTES
_____

Recall the Earlier Note on Data Types

Most CCSO servers have one set of attributes that describe people. Some servers
have different or conflicting attributes for different types of people. For
example, address might be the organization address for a person of
type="faculty" but the home address for a person of type="student."

If your database has different or conflicting attributes for
different types of people, please choose one type of person and fill
out this section for that type. You can optionally repeat this section later
for different types of people. 

Example for this Section
________________________

An example for filling out this section is available at
/cm/cs/what/nomenclator/ccso_dex.html or
ftp://cm.bell-labs.com/cm/cs/what/nomenclator/ccso_dex.txt.

                              --------------------


If you have multiple types of information in your database, please enter the
attribute name and value that identifies the type of information that you are
using to represent the global entry:
Example Input: type="person"
Example Input: type="faculty"
Example Input: type="faculty" or type="student"
Your Input: <147>

Please enter the attribute names and values for representing the global entry
in your database below.  Please enter one attribute-value pair per line after
the numeric prompt. Separate the attribute name from the value by a colon.
If your attribute value contains multiple lines, please use "\n" to represent
line breaks.

Example:

  Home-City: Toronto
  Address: 600 Mountain Avenue\nMurray Hill, NJ 07974-0636


Entry in Your Local Schema
---------------------------

<106>
<107> 
<108> 
<109> 
<110> 
<111> 
<112> 
<113> 
<114> 
<115> 
<116> 
<117> 
<118> 
<119> 
<120> 
<121> 
<122> 
<123> 
<124> 
<125> 
<126> 
<127> 
<128> 
<129> 
<130> 
<131> 
<132> 
<133> 
<134> 
<135> 
<136> 
<137> 
<138> 
<139> 
<140> 
<141> 
<142> 
<143> 
<144> 
<145> 




Except for the constraints you have already given us, please tell us any ways
that we have violated the conventions of your database.
Example Input: In our database, the email address always has the form
               "lastname@great.univ.edu"
Your Input: <148>

-------------------------------------------------------------------------------

Section 5: Provide Additional Comments and Information

Nomenclator Client Site Registration
------------------------------------

Please fill out this section if you are also volunteering a client site.

Client sites agree to use Nomenclator and report their experiences to us. This
can be as simple as using the Web to access Nomenclator at the InterNIC. For
better performance, a client site can run a Nomenclator query resolver locally
and make queries through a local Web page.

My site is interested in running a Nomenclator query resolver (y/n) <149>

My site will adverstise Nomenclator locally and report our experiences (y/n) <150>

I will use Nomenclator and report my experiences (y/n) <151>


Additional Comments
-------------------

Please add any additional comments below:

<152>


-------------------------------------------------------------------------------

Please send this form via email to nomenclator@research.bell-labs.com.

Thank you for joining the Internet Nomenclator Project!

-------------------------------------------------------------------------------

(c) 1996 Lucent Technologies. All Rights Reserved.

Last modified: June 20, 1996.
joann@bell-labs.com