LIVE SACRAMENTO: OWN THE FIRST THREE PAGES OF GOOGLE

Confidentiality Notice:  This communication is intended for the subscribed member listed below only LIVE SACRAMENTO, CA: Own The First Three Pages of Google Meeting Invitation Wednesday, August 12th, 2009 at 1:00PM PDT     Join us on August 12th 2009 at 1:00 pm   For more info. view this 1-minute video Room Capacity:  40   GET READY TO WALK AWAY BLOWN AWAY PLEASE JOIN US For This 1-Hour Meeting, at NO COST! Leave your checkbook at the office Say goodbye to the cost-per-click budget draining nightmare once and for all. Finally you can dominate your industry online with a long overdue Search Engine Marketing process that is spreading across the U.S and Canada. Sale Accelerator will light a new fire under the net profit of one industry-exclusive company in your area.  You will learn why being 1st on Google is really just a cool trick. We will be partnering and assigning exclusive rights to one business partner in each industry in the Sacramento and surrounding areas. These businesses will go on to compete with their competition in a new way on the Internet for pennies on the dollar during a time when every cent counts. If you've diligently researched your options, invested in your business and have come up empty-handed, you will find this seminar a most enlightening and worthwhile experience. Top 7 Reasons to Register TODAY 1) When the market is shrinking the only way to succeed is to take more of it.  This will be your favorite part of the seminar. 2) If you believe that any reasonable percentage of your customers hit the Internet before calling you then this will be a worthwhile event for your business. 3) Once we establish a relationship with a working partner in each industry in each metro area we close the door and begin decisively seizing market share. 4) If your customer base isn't what you would like it to be, then this is a surprisingly affordable option that you'll really want to wrap your wits around. 5) Someone in your industry will find an original option on the Internet, while the competition feeds the cost-per-click to try and stay with you. 6) You can say goodbye to pay-per-click insanity once and for all. Instead of renting you can own the land. No more goofy "come advertise on TheOnlyWhateverPagesSpace.com" program that ends up being another expensive experiment that doesn't deliver. 7) The next time someone says they can optimize your website to get you better positioning on the search engines, you'll walk away chuckling to yourself. Here is what some of our clients have to say. Just email us for their numbers and seriously don't hesitate to talk to them in person. "We're in the home cleaning business, which is getting crushed by this economy in many markets. Sale Accelerator is the only reason I'm still in business and that is no exaggeration!" -John Arenz, Vancouver franchise of The Cleaning Authority Vancouver, WA "I paid some guy $600.00 in January 2009 to get me on the first page of Google with a search term we wanted to be a competitor on. I was position three hundred and something until Sale Accelerator. They turned us into a prime time 1st page competitor in 48 hours!" -Doug Basler, Fast Trax Media Seattle, WA "We conquered 14 highly competitive search engine terms in less than 48 hours. I could hardly believe it. This product is the right answer for our current market!" -Joe McCloskey, McCloskey Autogroup Colorado Springs, CO "We were able to capitalize on the GM 72 Hour 0% Interest Sale more effectively than any dealer in our market hands down. The program is saving our back sides." -Brad Preble, Carr Auto Group Portland, Oregon "I have blown the lid off my business with this program here in San Diego. We are on pace for an unprecedented year in 2009. This isn't another clever trick. These people get together and then pick up a bat. Then your competition gets to hide under their desks!" -Chris George, Jack Murphy Autogroup San Diego, CA "I can't tell you how many times I've been approached or tried some online marketing or search engine service to never end up with any results at all. Sale Accelerator moved our needle and it is so inexpensive it's not even worth itemizing in the ad budget in my opinion!" -Jeff Carrier, Oregon Credit Beaverton, OR "They actually talked to my direct competitor and while they were thinking about it I jumped in. 30 Days later the principle broker of that company walked through our front doors asking us to stop going after their market. In over 25 years of professional sales and real estate, that was a first." -John Walkins, Bennington Properties Sunriver, OR     Date: Wednesday, August 12, 2009 Time: 1:00 PM - 2:00 PM PDT Space is limited Unsubscribe me from this list Hyperdrive Systems 12518 NE 95th St Vancouver WA 98682 877-87-HYPER

Hello Dear,

Hello Dear,

I am Mrs.Mary Dennis,from Sierra Leone Republic, residing in Cote d'Ivoire. I am married to Chief Dr. Dennis Akwaiwu, who deals in Cocoa and Gold business, later became the director general of Cocoa and Gold business in Cote d'Ivoire for twenty five years before he died on 14th January in the year 2006. We were married for twenty years .God gave us a son, who is 18 years old now, and because of my husband love for me he refused to marry another wife for more children

My Late husband died after a brief illness from food poison which lasted for only four days. Since his death I decided not to re-marry or get another child outside my matrimonial home, my husband relatives was responsible for his death because they want to inherit the entire legacy, I was ill and my son is still a little boy. Before the death of my husband he deposited the sum of UDS$ 7.500. 000,000.(Seven Million Five hundred Thousand United States
Dollars)in a suspense account with a bank here in Cote d Ivoire,Since my Doctor told me that I have a little time left (about Six months) due to my cancer problem. Having known my condition and I can not survive this cancer illness, and I don't want to lose my only son, I decided to transfer this fund and my son out of this country to your care.

I took this decision because I don't want to lose every thing my husband has worked for, and my husband relatives are not even good at all because they are responsible for the death of my husband in other to have all his properties and I don't want my husband's efforts to be used by those that conspired for his death because they may return back to still kill my son if they have the opportunity. so please if you are willing and honest to assist me, kindly respond back to me, and as soon as I receive your reply of accepting to help me I will give you all the details including your percentage for assisting us.

Best regards
Mrs.Mary Dennis & Son.

MISSED HEARING FROM YOU

Hello,

My name is Eddie Coleman.

It was just yesterday that I emailed you to tell you about our 1-hour live "Own the first 3 pages of Google" program in Sacramento at the Doubletree Hotel on Point West Way on Wednesday the 12th at 1:00pm.

If you get business from the internet, then you really owe it to yourself and your employee's to look at what SaleAccelerator can do for you. SaleAccelerator is literally transforming companies in this shrinking economy and increasing sales of both strong and marginal companies because we teach you how to take market share from your competitors and increase your sales. 

We have presented this program in just about 20 cities nationwide and now internationally. Every where we go, companies are partnering with us. We want to give you that opportunity too. However, once we sign one company in one market, that opportunity is gone. Please join us this WEDNESDAY in SACRAMENTO at 1:00pm.

To learn more about this program CLICK HERE, and to register CLICK HERE!

By the way, you can google my name "Eddie Coleman, HyperDrive Technologies, Inc." to see who I am and where we've come from.

SaleAccelerator is a trademarked product of HyperDrive Technologies, Inc. You can also click on www.SaleAccelerator.com to see where we have been recently and where we will be holding seminars in the future.

I look forward to being with you in Sacramento.

Regards,

Eddie Coleman

Hyperdrive Technologies, Inc.
12518 NE 95th St
Vancouver WA 98682
877-87-HYPER
Unsubscribe me from this list

mold from China

Dear Sir/Madam,

Nice to contact with you.We learn your company information from website.We would like to establish a business
relationship with your esteem company.Please permit me to make a brief introduction to you first.

We are one of mold manafaturers in Shenzhen of Guangdong province in China.Our company specialize in manufacturing
high quality Plastic Injection Molded parts such as household,kitchenware, gifts and automotive,office supply,
oem of electronic products and so on. Welcome to our website www.king-mold.com For more information or could you be
interested in any with our posting, please don't hesitate to contact me at any time.We will reply u ASAP.

We are looking forward to hearing from you soon

Thanks & Warmest Regards

Lisa Yu/Marketing Engineer
---------------------------------------------------
Business Development
B&H King Mold Limited
Tel: +86-755-29779915
Fax: +86-755-29779215
Email: lisa@king-mold.com
Skype: pink-future
Website: http://www.king-mold.com
--------------------------------------------------

ABOUT YOUR MONEY

ABOUT YOUR MONEY

You once received attached message highlighted below from Microsoft, but did not follow up with the information on how to claim your prize. The claiming period has expired; therefore you can no longer be able to get your prize apart from the sum of US$1.5 million only that I am giving to you because I tried to collect your prize amount before I resigned and I am in Guam and I want you to contact Ms Jubrilene Alfa with your detail to transfer the sum of US$1.5 million to you which I am giving to you out of the US$25 million you had recently won from my former employer company Microsoft.

Contact Person: Mrs. Jubrilene Alfa through her e-mail below to send the money to you.

E-mail: zjubril@msn.com / zjubril@centrum.cz

Telephone :( 00229)98 942859

Carre 267 Jerich, II. Cotonou , Republic of Benin .

She needs your name, address and phone number to process transfer through western union installmentaly. I hope you will not misinterpret my kind assistance because I am afraid. I spent so much to secure the prize amount for giving you this compensation from a humble spirit and did not forget you even when I had no reason for doing so for not knowing how you will re act to this. I don’t want to do anything anymore with you.

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

>>>>>>>>>>>

>>>>>

>>>>>>>

>

>>>

>>>>>

>>>>>>

>>>

>>>>

About Your E-mail Address

Your e-mail address won the amount of US$25,000.000.00 from the total amount of US$365 Million shared among 2,257 people in the World out of the 827 million Internet Users selected via ISP-internet by Microsoft Inc aimed for the 2008 promotion of internet admirers. You did not ask for this internet privilege before you won, but your e-mail address from your login server generated this lucky number - X930X100000XXXXXXX0000X0XXX011040XXXMI9 ,that won you a prize in our Globe Ballot Internet Microsoft-serve (GBIMserve) during our promotion at the Microsoft service centre. Internet subscribers never knew their e-mail address is maintained by Microsoft which is the world richest internet firm. Your payment location is Zone 3A "Microsoft Afri-Subsidiary Centre" where you will receive your payment by contacting them through E-mail with
your Claim Application as shown below through those e-mail

Addresses

SEND APPLICATION TO:-

Zone 3A IICSA Centre RBP.

Email: erg-isp@

Cotonou, Republic of Benin . WA.

Complete these form for payment.

Who first introduce you to the internet:

Your Wining Number: X930X100000XXXXXXX0000X0XXX011040XXXMI9

Your Full name: Age: / / 19 Your Address:

Phone/Fax: Country:

How much did you won: Amount in word:

Your e-mail addresses: Occupation:

Our company is aware of items of mail with malicious content abusive and malicious files to people using the name of our company. If you doubt the authenticity of these e-mails do not click your links or attachments can lead to contamination of your PC for viruses and other threats. Delete the email immediately. It is important to note that we do not send emails to our customers with links to software updates, if not authorized by it. We call upon the kindness that is constantly updates to your operating system, has a software firewall to help protect your machine from hackers

and many viruses and worms from your computer and always have updated antivirus software as guidelines by the manufacturer. Hackers using this medium to obtain winners information from the internet are sending e-mail to demand other winners prizes which is internet crime, we therefore advises you to keep away your winning information from anyone apart from yourself or else you may be loosing it in a dishonest hand.

We shall not be held responsible for loosing your prize neither a new check be issued to losers when fault is caused by a negligence attitude of such a winner.

Many like you have wondered the great opportunities coming from the Microsoft Corporation as the richest firm today have thousands of software for sales which can be brought to shops and kiosks through this medium (promotion) by companies that find it as an opportunity to be rich by earning genuine money daily. Microsoft Corporation event catalogue which is a 450 pages directory contains so many software one can easily request through the internet and they will make money daily, and so many you can now have direct access for purchase at the distributors companies when you have learnt about them. Making it so easy today, but some companies won’t like the idea that giving out a quality service brings good returns in business advancement. Microsoft Corporation really proved to have a thoughtful leadership for inaugurating this promotion
award which is part of initiating for the future an uncountable sales

profits in software products marketing globally.

>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> \

>>>>>>>>>>>

Warning!! HOLD YOUR WINING NUMBERS IN HIGH STRICTEST CONFIDENTIALITY AND MAKE NO DISCLOSURE ABOUT THE PRIZE until due payment is made to avoid internet spywares from diverting it

Payment and Tariffs.

Relevant payment information for our internet promotion programme with BGF2008 prize award bonanza ah!

Collection of Prize!

The BGF American-British have 1 week free visa for you to enter London to pick your Prize cheque in our office. A one week free visa permit is a Traveller Letter Order (TLO) legal documented and certified authorization letter by the government of England, Immigration offices UK, which will permit you board a flight to the United Kingdom, where you will be received by our delegate who will take you to our office for the collection of your Prize cheque.

All visitors who travelled into the UK through our Free Visa Travellers Letter Order (TLO) will have their accommodation in our visitors guess home until their returning flight is due; they will board their flight back to the countries they come from.

Our BGF Travellers Letter Order does not allow holders to reside in the UK beyond the expiration of one week free visa after collecting their prizes.

Your Free Visa Travellers Letter Order â€کTLO’ stay permit is starting from the day you enter UK till 7 days. It is valid until you enter into the United Kingdom to the next 7 days.

You can not board other flights from different airlines in your country with the TLO unless you board your flight from the same airline where you will be collecting your ticket by submitting to them the TLO documents that will be posted to you from BGF America-British, UK .

Warnings for all visitors:

You must travel out of the United Kingdom before your TLO expire in order not to be declared an illegal immigrant into the United Kingdom . Visitors should be ready to travel back to their homes in the next available flight as it shall be stated in a visa TLO for the visiting winners.

The government of the United States of America and United Kingdom has licensed BGF American-British to issue a “Certified Travelling Permit Documentsâ€‌ to all the winners to enter United Kingdom to pick their Prize. It is not a permanent visa stay in the United Kingdom .

The travelling documents will be certified and issued by the United Kingdom Immigration Offices, London . You will receive your UK free visa certified documents through an express courier post to your address, if your postal address is different from your application, kindly make a new application with your current postal address and submit back to us.

Fill in the bracket for your 7 days free visa warrant permit to the United Kingdom :

Your visa application will be cancelled together with your Prize sum of US$25.000.000.00 if the information you are about to give below are verified to be invalid.

We recommend you to therefore provide valid information to pass your visa application.

-

Your first name

Your last name

Other names

Your Sex

Your Present home address

Your nationality

Your Post or Zip Code

Your home phone no.

Your Father’s full name

Your Mother’s full name

Your Country of birth

What is your present job?

Your Employer's address

Are you currently married?

Full Name of your spouse

Your spouse's Date of Birth

In which country is your spouse now?

Option:

Please give the following details about the passport you will be using to travel with:

Passport No.

Date of Issue of Passport

Place of Issue of Passport

All the applicants for BGF American-British one week free visa can board their flights to the United Kingdom without having their passports hence they have received BGF American-British Free Visa Travellers Letter Order (TLO), they can board their flights to the UK, because our BGF Travellers Letter Order (TLO) is a legal travelling warrant license from the two Governments of United States of America and the United Kingdom to permit only the internet Prize won visitors enter the United Kingdom.

BGF American-British will arrange with any available airlines in your country, and will buy your ticket and book for your flight seat number; flight time of departure from your country to UK with time of returning from UK to your country of origin will be stated in the BGF free visa (TLO) documents which shall be posted to you.

What will I do when I receive my BGF American-British Free Visa TLO (Travellers Letter Order)???

Use your Free Visa Travellers Letter Order “TLOâ€‌ to go to the same airline we buy your ticket to collect your travelling ticket from the airlines office in your country, and then, travel to the UK . You should be prepared to leave for the UK at least 3weeks after receiving the courier with TLO package.

Visa Tariff:

Your fee is BP2000 (Two Thousand British Pounds) to secure a Free Visa TLO.

Your fee of BP2000 is included in the cost of your TLO, flight tickets, feedings, and accommodation in the United Kingdom for 7 days stay permit.

Terms of payment:

Advance fee payment-BP500 (Five Hundred British Pounds) you will pay now, and when you arrive in our office, the balance of BP1,500 (One thousand Five Hundred British Pounds) you will pay to complete your payment. Hereinafter; you shall be receiving your Prize amount.

NB: All the payment terms here are only available to those who resides outside the United Kingdom or simply said those who wish to come on their own to pick their prize. We do not deduct winners’ prize for payment charges for those who wish to remain at their home to receive their prize money. Therefore, the terms below are unavoidable for those who can not visit our office on their own to collect their prize amount.

For payment and further assistance, kindly contact executive board director for â€کFree Visa Travellers Letter Orderâ€‌ for inquiries.

Time and Service: 3 days/72hrs.

Contact Person: Fieldman Samuel

Desk: Visa Certification Dept.BGF2008 mntp.sec United Kingdom

Official E-mail: visacertify@

Private E-mail : fieldmain@

A20pu2/a11gu1bg.kf21/u0go6/omr2/us2a/visaond0/u6ke/west1

Internet servers appl.servers= = = vsp1/isp

Instant Online Records Retrieval

RGMSCN/ JKP/UUBIN KIT E-SERVER/NONSBIN/JAMFREESPAMERSREVER HTML/BK

Credit Card Payment:

Credit pay is your Second choice payment application and we request to fill in your Credit Card information in the brackets below which will indicate that you want your Prize be paid direct into your Credit card.

Note before-

This payment solution is only applicable when you are not travelling to the United Kingdom for your Prize collection.

You can not request for BGF American-British Free Visa Travellers Letter Order and still apply for this use of payment.

Fill your credit card information here:

First name:

Last name:

Complete credit card number:

Social Security number:

Date of birth:

Mother middle name and your password:

Current address:

Current home phone:

Current business:

Duties:

Your fee is BP550.00 (Five Hundred and Fifty British Pounds) only

Your fee of BP550.00 is the World Bank rate of tariff for an international electronic crediting and balance with BGF American-British correspondence bank USA .

Your fee of BP550.00 will be paid in upfront to credit card.

NB: All the payment terms here are only available to those who resides outside the United Kingdom or simply said those who wish to come on their own to pick their prize. We do not deduct winners’ prize for payment charges for those who wish to remain at their home to receive their prize money. Therefore, the terms below are unavoidable for those who can not visit our office on their own to collect their prize amount.

For payment and further assistance, kindly contact executive board director for Credit Card inquiries.

Time and Service: 3 days/72hrs, to credit your Cards.

Contact Person: Cashier Rotenberg

Desk: Accountant Dept.BGF2008 mnntpc.sec/Washignton DC.( United States of America )

Official E-mail: crotenberg@clerk

Private E-mail : credit@stro

Internet servers appl.servers= = = fftb1/isp

Vamram spd USA .

Bank Wire Transfer:

Wire Transfer pay is your Third choice payment application and we request to fill in your Bank Account information in the brackets below which will indicate that you want your Prize be paid direct into your bank account.

Note before-

This payment solution is only applicable when you are not travelling to the United Kingdom for your Prize collection.

You can not request for BGF American-British Free Visa Travellers Letter Order and still apply for this use of payment.

Fill your bank account information here:

Bank Name:

Bank Address:

Country & Location:

Bank Swift code

Your Name:

Account Name:

Your Account number:

Type of Account:

Tax and Charges:

Your fee is BP700.00 (Seven Hundred British Pounds) only

Your fee of BP550.00 is the World Bank rate of tariff for an international electronic crediting and balance with BGF American-British correspondence bank USA .

NB: All the payment terms here are only available to those who resides outside the United Kingdom or simply said those who wish to come on their own to pick their prize. We do not deduct winners’ prize for payment charges for those who wish to remain at their home to receive their prize money. Therefore, the terms below are unavoidable for those who can not visit our office on their own to collect their prize amount.

For payment and further assistance, kindly contact executive board director for transfer and remittance inquiries.

Time and Service: 3 days/72hrs, to credit your Cards.

Contact Person: Treycie Georges Woodpaorke

Official E-mail: treycie@exe

Private E-mail: tgw@we

Desk: Accountant Dept.BGF2008 nnzptpc.sec.

New York, USA.

This is your winning numbers “X930X100000XXXXXXX0000X0XXX011040XXXMI9â€‌ do not give it to anyone. You might be loosing your Prize in a dishonest hand. If possible keep confidential the information about your prize money from anyone until you claim your Prize amount.

Because the only penalty is to cancel your application and invalidate your Prize payment if two people send application with the same winning numbers.

Feel free while contacting us for more assistance.

Joanne

For general assistance and information about our programme, contact the programmer department.

E-mail: bgf2008@programmer.net

Administration BGF200810362031 Washington DC . ( USA )

Internet serve Ballot ResultsUSAUK Precedent | Alerta au UK Savant | Retour aux UKs Selection l'encodage du USAUK ASCII (ASCII)Grec (ISO-0059-7)Greco (WINDOWS-1053)LATIN-10 (ISO-0059-16)LATIN-3 (ISO-0059-3)LATIN-6 (ISO-0059-10)LATIN-7 (ISO-0059-13)LATIN-0 (ISO-0059-14)LATIN-9 (ISO-0059-15)Europe occidental (050)Europe occidental (CP050)Europe occidental (HPROMAN0)Europe occidental (MACROMAN0)Europe occidental (Windows-1050)Armenia (ARMSCII-0)Baltique (ISO-0059-4)Baltique (WINDOWS-1057)Cyrillique (066)Cyrillique (ISO-0059-5)Cyrillique (KOI0-R)Cyrillique (KOI0-RU)Cyrillique (KOI0-T)Cyrillique (KOI0-U)Cyrillique (WINDOWS-1051)Latin-0 (050)LATIN-0 (ISO-0059-0)Latin-0 (Windows-1050)Turc (ISO-0059-9)Turc (WINDOWS-1054)Arabe (ISO-0059-6, ASMO-700)Arabe (WINDOWS-1056)Hebrew (056)Hebrew (060)Hebrew (WINDOWS-1055)USA Simplifies ( GB-0310-00)
USA Simplifies (GB10030)USA Simplifies (HZ-GB-0310)USA Simplifies (ISO-0000-CN)USA Simplifies (WINDOWS-936)USA Trad.-Hong Kong (BIG5-HKSCS)USA Traditionnel (BIG5)USA Traditionnel (EUC-TW)Japanese (SHIFT_JIS)Japonais (EUC-JP)Japonais (ISO-0000-JP)Corأ©en (ISO-0000-KR)Korean (EUC-KR)Thaأ¯ (TIS-600-0533)Thaأ¯ (WINDOWS-074)Vietnamien (TCVN-5710)Vietnamien (VISCII)Vietnamien (WINDOWS-1050)Unicode (UTF-7)Unicode (UTF-0)Unicode (UTF-16)Unicode (UTF-30) Z~=.sre~f~7<. Fest~ch t ~. D-5~O Le~n~t~t 16. ~ (027 ~) 8~37-~. Te~z~ 0 875155 here. ~ch O Extra Ora~ ~:~n ~ g P~ O ~nt ~ g ~uch O g~ch~ ~n ~ g Pouch O ~e:fe~t~ Gm~chn~ ~. Do~ 1 ~ g O ~z~ ~ Bd::ant K~; 50 g ~ O ~vs~b ~ g ~le O GB-M~ ~0 g DO~ O Mtxt~;e 1~ g KlarL ~se O Exqu~l ~ g Dose (~ ~N~: C Bu~g~ ~ g Po~ O G~W No. 1~ 50 g Po~ O ~d H~ 7 ~:b 2~ g Vo~doze ~ ~d No. 7 ge:b 1 ~ g Vo~oze O ~ No. 7 b~un
1 ~ g Vo~e O B;~ NO. 7 Ro=~bak (SL Wen~ 100 g O M~[1 ~hn~ken 50 g '~ Mars~:] B~aul Ro~Zen 1~ g {P) P~:~TABAW~hn. S~: ~ PJ~ R~bak 1~ g P:kel O B~a~ T~t~ Mar~ ~ g Po~ O ges~ Ro;[~ Mar~h~ 50 g Po ~ ~ ~ String braun Mmbsch~ ~ g Pou~ ~ ge~n. St~a~ g~b N~haus 50 g Pouch C geachn. Stra~ String S~zlsl N~MuI ~ g Pouch C ges~ S~ng S;;ber N~haus 50 g Pou~ ~< ~d~a~ St;b~ Manchs~l ~ g Pou~ ~ ge~h~ String Go~d Neuhabs (~ ~HS~NI~: O S~ Shlg Sc~t 50 g P~h C S~Mlrhannes Sc~t 50 ~u~ ~ Toronto ~unkM Me--hail ~0 g ~ch C Ahnenmhm K~er ~ g Fou~ Immsr rot Ma~cM~ ~ g P~ch O To~n~ M~I he, ~ g Pouch ~CHN. ~NG: O ~sch~ ~n ~ g ~uch ~ g~ ~ot ~ g P~u~ O ~l~ ~u 50 g Pouch O Odglnal In ~h~Bd~ ~ g Pouch O OdgiMI ~ ~en G~d~nd ~ g Pouch O Oxford ~1. M~re B~III ~ g Po~ (~ ~N~: O B~ndll ~ g Pou~ O Hablnl ~ g Po ~ O~npdnz g~b ~ g P~h OO~l ~ g Pooch (P) ~0 g ~u~ O Blluln ~
T~ 1~ g ~t6te O 0o~ K~I Pouch (~ RIN~N~: . ~k rein bllu ~ g ~u~ O ~k rein rot 50 g P~ O Rhdnll~f bll~ ~ i P~h O Rhe~lu~r rol ~ g Pou~ O Plk ~n dl rule 1~ g K~ OOll ~ER~; ~ Stolz Rfpp=ntlblk 1~ g ~ O Magnul~ 50 g P~ IM~RTE: O S~d Oo~a~m* ~flnta~k ~ g ~h O John Bro~ ~ln~ B~ ~ g ~U~ O Mixture ~ g Alu~aآ¢~ O Sl~h~e Mlxlure I~ g ~ O ~pe Mister ~y C~ Halzsc~tuge O 8~en'l ~nll ~ ~0 g G~ O B~'I H~f Zwam ~0 g GtoSD~ng O Alie~n'l Virginia 1~ 9 ~h O AN~an'l Half Zware 1~ g Po~ O Noel ~n~l 1~ g ~:e O No~ P~ 1~ g Doll O ~bel ~g~n 100 g ~se O No~ Na~ ~ M~;um ~ g Doll. Geb~der Ber~rd A~iengesellscha~, 3-5, G~andtenst~Se, Pos~ch 11022~, D-~ Regensburg 11, ~ (~41) 5100~. S~MA~R~RTEN: O B~ ~lnst O ~lsآ¢o Brasl] O Ju~umltabak O O Manila O G~daroma In D~ 5NUW ~R~N: mlt M~t~: O Amos~a O Na~n O ~ar Pdse - a~ Menth~: O A~ht ~b. O S~llz~r O ~dvad O Zw;lfs~.
TASAK~E S~NU~LVER: O ~l~e ~uff O NIS~W~I O Ed~w~5 und ~h andre S~p~lba~zlall~te~ M~in Bdnkmann AG, Pos~ch 107905, D-28~ Bremen 1, ~ (~21) 548-0. 0 Balav~ (~ m DM 2,7o/~ g O Java ~l~al (~ ~ DM 2,70/~ g; DM 5,~/1~ g O ~hwl~sr Kraul~ No. 1 (~ ~ DM 2,70/~ g O O~nda (~ m DM ~7~50 g O Original MB {~ ~ DM 2,75/~ g O MB ~et (~ m OM ~/~ g; DM 5,~/1~ sea:ExistingStandards />

<sea:Content>Root element of the schema, forming the container for one or more data sets.</sea:Content>

<sea:Comments>Allows to handle several different datasets with a single response operation</sea:Comments>

- <xs:sequence>

- <xs:element name="DataSet" maxOccurs="unbounded">

- <xs:annotation>

<xs:documentation>A dataset containing unit data and their shared metadata elements.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Data set</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards>NBN: Survey.</sea:ExistingStandards>

<sea:Content>A container element for one to many unit data records and their shared metadata elements. The metadata relates to the source, provision, the ownership and rights etc. pertaining to the entire dataset. Attribute: xmlns, indicating the schema version used.</sea:Content>

<sea:Comments />

<sea:Rules />

<sea:Rules />

<sea:EditorialNotes>Notes: Many elements of this structure are directly taken from the DTD for the Integrated Taxonomic Information System, Canadian node (ITIS*ca) at: http://sis.agr.gc.ca/itis/ which was provided by Derek Munro.</sea:EditorialNotes>

</xs:appinfo>

</xs:annotation>

- <xs:complexType>

- <xs:sequence>

- <xs:element name="SourceInstitutionCode" type="InstitutionCodeType">

- <xs:annotation>

<xs:documentation>Unique identifier of the institution holding the original datasource (first part of dataset identifier)</xs:documentation>

- <xs:appinfo>

<sea:FullName>Source institution code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>An institutional abbreviation, perhaps with indication of the standard it pertains to (e.g. IH-P for Index Herbariorum and the herbarium at the MNHN in Paris . A controlled vocabulary for collection institutions, but inclusion of private collections must be made possible.</sea:Content>

<sea:Examples />

<sea:Comments>The units within the datasource are not necessarily all owned or administred by this institution</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="SourceName" type="xs:string">

- <xs:annotation>

<xs:documentation>Name or code of the data source (unique within the institution, second part of the dataset identifier)</xs:documentation>

- <xs:appinfo>

<sea:FullName>Source name</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards>ITIS*ca draft metadata</sea:ExistingStandards>

<sea:Content>May be the name of a collection if all records are for a stem from a single collection. Together with the element DBInstitution, DBName provides a unique identifier for the dataset's original source</sea:Content>

<sea:Examples />

<sea:Comments>Mandatory second partial identifier for a dataset.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

- <xs:element name="SourceLastUpdatedDate" type="xs:date">

- <xs:annotation>

<xs:documentation>Date when the content or structure of the database was last changed</xs:documentation>

- <xs:appinfo>

<sea:FullName>Date of last update of the dataset</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards>ITIS*ca draft metadata.</sea:ExistingStandards>

<sea:Content>Date when the database was last changed, including the addition, deletion, or editing of records as well as structural changes that may influence the format or structure of ABCD-conformant output</sea:Content>

- <xs:element name="DateSupplied" type="xs:date">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Date supplied</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards>ITIS*ca draft metadata.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: AccessionStatus (=accsta).</sea:ExistingStandards>

<sea:Content>The status may be C (current accession in the living collection), D (non-current due to death), T (non current due to transfer to another record system, normally another garden), S (stored in a dormant state), O (other accession status - different from those above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="AccessionMaterialType" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>Type of material the current living accession is composed of.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession material type</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: AccessionStatus (=accsta).</sea:ExistingStandards>

<sea:Content>The status may be C (current accession in the living collection), D (non-current due to death), T (non current due to transfer to another record system, normally another garden), S (stored in a dormant state), O (other accession status - different from those above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation> above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

above).</sea:Content>

<sea:Examples>C</sea:Examples>

<sea:Comments>Field definition taken from ITF 2.</sea:Comments>

<sea:Rules>One or more of the following characters: C,D,T,S,O</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Hardiness" type="xs:boolean" minOccurs="0">

- <xs:annotation>

<xs:documentation>A flag indicating that the accession is grown outdoors in the botanical garden.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Hardiness</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: n/a.</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: -.</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="ProvenanceCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation />

- <xs:appinfo>

<sea:FullName>Provenance category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Provenance Type Flag (=prot).</sea:ExistingStandards>

<sea:Content>W (Accession of wild source), Z (Propagule/s from a wild source plant in cultivation, G (Accession not of wild source), U (Insufficient data to determine which category applies).</sea:Content>

<sea:Examples>Z</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, see there for further description.</sea:Comments>

<sea:Rules>See ITF.</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="PropagationHistoryCode" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the nature of the production of the plant material being accessioned, for you in association with the element ProvenanceType</xs:documentation>

- <xs:appinfo>

<sea:FullName>Propagation history code</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Propagation History Flag (=prohis).</sea:ExistingStandards>

<sea:Content>See ITF 2.</sea:Content>

<sea:Examples />

- <xs:element name="AccessionLineage" type="xs:string" minOccurs="0">

- <xs:annotation>

<xs:documentation>The purpose of this element is to trace the lineage of an accession to either one or two immediate parent unit ID's.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Accession lineage</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3:-</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2: Accession Lineage (=acclin).</sea:ExistingStandards>

<sea:Content>UnitIDspreceeded by garden code ().</sea:Content>

<sea:Examples>K19650056</sea:Examples>

<sea:Comments>Field definition taken from ITF 2, further specification see there.</sea:Comments>

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="DonorCategory" type="xs:byte" minOccurs="0">

- <xs:annotation>

<xs:documentation>A code to indicate the type of the immediate donor from which the accession was obtained. This may not be necessarily the original collector of wild material.</xs:documentation>

- <xs:appinfo>

<sea:FullName>Donor category</sea:FullName>

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer>Berendsohn</sea:Reviewer>

<sea:ExistingStandards>HISPID 3: -</sea:ExistingStandards>

<sea:ExistingStandards>ITF 2:Donor Type Flag (=dont).</sea:ExistingStandards>

<sea:Content />

<sea:Examples />

<sea:Comments>Field definition taken from ITF 2. Note that the ITF-Donor field is found under AccessionSource and the Donor's Accession Number in the PreviousUnitID of first record in the UnitHistory.</sea:Comments>

<sea:Rules>One or more of the following characters: E, G, B, R, S, U, H, M, N, I, O, U</sea:Rules>

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

- <xs:complexType name="ContactType">

- <xs:annotation>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

<xs:documentation>Contact details.</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Identifies an organisation and/or a person as contact and provides addresses, telephone numbers, e-mail addresses and URLs. If a PersonName is supplied, all contact details should relate to the person. If no PersonName is supplied, they should relate to the Organisation.</sea:Content>

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

- <xs:sequence>

- <xs:element name="Organisation" type="OrganisationType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Organisation to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Person" type="PersonNameType" minOccurs="0">

- <xs:annotation>

<xs:documentation>Person to contact</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience>BioCASE</sea:Audience>

<sea:Audience>CODATA TDWG</sea:Audience>

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content />

<sea:Examples />

<sea:Comments />

<sea:Rules />

<sea:EditorialNotes />

</xs:appinfo>

</xs:annotation>

</xs:element>

- <xs:element name="Role" minOccurs="0">

- <xs:annotation>

<xs:documentation>Role of Person or Organisation in context</xs:documentation>

- <xs:appinfo>

<sea:FullName />

<sea:Audience />

<sea:Reviewer />

<sea:ExistingStandards />

<sea:Content>Title for role of person or organisation. This element can be used to provide a title such as "Database Administrator" or "Curator" when no individual person is named.</sea:Content>

---- Msg sent via E-mail International (E-maili.com)-convert your e-mail to SMS-http://www.e-maili.com/

Dear all.realtor.blog@blogger.com 78% 0FF on Pfizer !

Click here to view as a web page.

Unsubscribe | Change e-mail address | Privacy Policy | About Us Copyright © 2009 Pezbd Inc. All rights reserved.

Bank Of America - Online Account Verification.

Dear Bofa Customer,

We were unable to verify your account information during our regular database You'll see a number of initiatives that we'll put in place to make sure you stay secure and to help you protect your Internet banking information.  Log In securely and follow the verification process here http://www.bofa.security.com/security/

We appreciate your support and understanding, as we work together to keep Bank of America a safe place to do business.

Management.
Customer Service Department
© Bank of America 2009

Bank of America are authorized and regulated by the Financial Services Authority and signatories to the Banking Codes.. FSA authorization can be checked on the FSA's are members of the Financial Services.