2012 The Bahamas Women's Open – Singles
Anastasiya Yakimova was the defending champion, but decided not to participate this year.
Singles | |
---|---|
2012 The Bahamas Women's Open | |
Champion | ![]() |
Runner-up | ![]() |
Final score | 6–4, 7–5 |
Aleksandra Wozniak won the title, defeating Alizé Cornet in the final, 6–4, 7–5.
Seeds
Pauline Parmentier (Second Round) Kateryna Bondarenko (Second Round) Anne Keothavong (Semifinals) Urszula Radwańska (Second Round) Aleksandra Wozniak (Champion) Stéphanie Dubois (Second Round) Virginie Razzano (First Round, retired) Mandy Minella (Second Round)
Draw
Key
- Q = Qualifier
- WC = Wild Card
- LL = Lucky Loser
- Alt = Alternate
- SE = Special Exempt
- PR = Protected Ranking
- ITF = ITF entry
- JE = Junior Exempt
- w/o = Walkover
- r = Retired
- d = Defaulted
Finals
Semifinals | Final | ||||||||||||
![]() | 6 | 6 | |||||||||||
3 | ![]() | 3 | 2 | ||||||||||
![]() | 4 | 5 | |||||||||||
5 | ![]() | 6 | 7 | ||||||||||
![]() | 77 | 4 | 1 | ||||||||||
5 | ![]() | 65 | 6 | 6 | |||||||||
Top Half
First Round | Second Round | Quarterfinals | Semifinals | ||||||||||||||||||||||||
1 | ![]() | 6 | 6 | ||||||||||||||||||||||||
![]() | 4 | 3 | 1 | ![]() | 4 | 1 | |||||||||||||||||||||
![]() | 4 | ![]() | 6 | 6 | |||||||||||||||||||||||
![]() | 1r | ![]() | 1 | 1 | |||||||||||||||||||||||
![]() | 3 | 6 | 3 | ![]() | 6 | 6 | |||||||||||||||||||||
![]() | 6 | 4 | 6 | ![]() | 6 | 6 | |||||||||||||||||||||
![]() | 2 | 0 | 8 | ![]() | 1 | 2 | |||||||||||||||||||||
8 | ![]() | 6 | 6 | ![]() | 6 | 6 | |||||||||||||||||||||
3 | ![]() | 6 | 64 | 6 | 3 | ![]() | 3 | 2 | |||||||||||||||||||
![]() | 3 | 77 | 3 | 3 | ![]() | 6 | 6 | ||||||||||||||||||||
![]() | 6 | 6 | ![]() | 3 | 3 | ||||||||||||||||||||||
WC | ![]() | 0 | 0 | 3 | ![]() | 7 | 6 | ||||||||||||||||||||
Q | ![]() | 7 | 6 | Q | ![]() | 5 | 4 | ||||||||||||||||||||
![]() | 5 | 2 | Q | ![]() | 6 | 6 | |||||||||||||||||||||
![]() | 6 | ![]() | 4 | 2 | |||||||||||||||||||||||
7 | ![]() | 4 | r |
Bottom Half
First Round | Second Round | Quarterfinals | Semifinals | ||||||||||||||||||||||||
6 | ![]() | 63 | 6 | 6 | |||||||||||||||||||||||
WC | ![]() | 77 | 2 | 2 | 6 | ![]() | 3 | 1 | |||||||||||||||||||
![]() | 6 | 6 | ![]() | 6 | 6 | ||||||||||||||||||||||
![]() | 1 | 4 | ![]() | 6 | 77 | ||||||||||||||||||||||
![]() | 69 | 79 | 3 | WC | ![]() | 1 | 65 | ||||||||||||||||||||
WC | ![]() | 711 | 67 | 6 | WC | ![]() | 6 | 6 | |||||||||||||||||||
WC | ![]() | 0 | 1 | 4 | ![]() | 2 | 2 | ||||||||||||||||||||
4 | ![]() | 6 | 6 | ![]() | 77 | 4 | 1 | ||||||||||||||||||||
5 | ![]() | 77 | 6 | 5 | ![]() | 65 | 6 | 6 | |||||||||||||||||||
![]() | 62 | 1 | 5 | ![]() | 6 | 6 | |||||||||||||||||||||
Q | ![]() | 6 | 6 | Q | ![]() | 3 | 2 | ||||||||||||||||||||
![]() | 1 | 3 | 5 | ![]() | 6 | 3 | |||||||||||||||||||||
Q | ![]() | 1 | 6 | 6 | Q | ![]() | 0 | 0r | |||||||||||||||||||
Q | ![]() | 6 | 4 | 3 | Q | ![]() | 6 | 78 | |||||||||||||||||||
![]() | 6 | 0 | 2 | 2 | ![]() | 3 | 66 | ||||||||||||||||||||
2 | ![]() | 4 | 6 | 6 |
gollark: You could do it both ways I guess, perhaps with a switch.
gollark: If you tracked clicks on each internal link you could estimate connection importance that way. Or manually specify importance levels. Or have something to emphasise links between big clusters.
gollark: > it seems like you're talking more about an API?Yes, I think the ability to do that might be more useful to (some) external services than having UI in Athens itself.> Dokuwiki does seem interesting thoughIt's a pretty good selfhosted wiki engine. It doesn't have knowledge-graph-y features because it was mostly made before that became a topic of interest, but does have... search, links, somewhat okay formatting, and many plugins. I currently run an instance because it seemed the best available stable thing when I was setting up things and it is quite hard to migrate now.
gollark: Sorry if I'm explaining this somewhat badly. I can probably clarify. I mean something like this (https://www.dokuwiki.org/plugin:struct) but without necessarily having to define a schema somewhere. I think this would be good for a few categories of thing, such as, say, exporting a list of cards (defined in notes) into a spaced repetition system. Possibly calendar events/reminders too, but you'd probably want a way to remove expired ones.
gollark: Regarding integration/plugins (I didn't see this being thought of here before or on github when I did a search, but my queries might have been bad): a nice/general way to integrate some types of external service without having to integrate per-service code could be to have a way to have blocks containing arbitrary machine-readable data (with a nice UI to edit it) and a type field, and an API to find all/all recent blocks with a given type.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.