Costco Zinfandel—I'd Say Try It!
The last time I was at Costco, I picked up a bottle of Kirkland "Grandmere" Amador County Zinfandel. I thought I'd check it out as an inexpensive wine. I think it was about $10/bottle. My guess was that as a private label, this wine was probably made by Renwood, the only winery I am familiar with that calls some of its zin vines by the name "Grandmere". If it was Renwood, I knew it would likely be good, so I took a chance.
I opened the bottle last night and shared it with some friends. Gotta say, this was a tasty wine, especially, relative to what it cost. It was fruity, lightly tannic and was an overall, well-balanced and pleasant zinfandel. Those who tasted it along with me, including Doug, who doesn't even like red wine that much, enjoyed it. This bottle had the characteristics that make many zins crowd pleasers.
05/18/2012 in Red Red Wine, Wine Reviews.
Old Vine Zinfandel–A Celebratory Drink!
When I was in Asia last month, I saw an interesting documentary on Costco(!), and in it was a segment that focused on the head wine buyer. It was fascinating. Costco is the largest seller of wine by volume in the US, so they have a lot of leverage. They even talked about the private label product and how meticulous they are in selecting the winery who will produce the p.l. product. I'll see if I can track the video down for you. Cheers!
I saw the same segment, but here in Sacto. It was on CNBC; Carl Quintilla was the journalist. (we watch alot of money shows 🙂 Well worth your time!
Hi Susan. I'm taking a Double Chocolate Bundt Cake w/Ganache Glaze to a dinner party this weekend, and wanted to bring a late harvest Zin to go with (instead of going the port or vin santo route). Looked for a late harvest Seghesio Zin but could not find it.
Bogle Old Vine Zinfandel 2012 ($9.99) – may have tasted this once upon a time, but don't recall TJ Grand Reserve Zinfandel 2012 ($12.99) – might be worth a try??
Open to any other suggestions. Just trying to stay local instead of running around too much, but there are a couple other places I could try.
I would give the Easton a try. They do a nice job out if the foothills with many of their wines. His Zins get nice reviews. Let me know what you think!
Thanks, Susan–I'll let you know!


text:
Q: Recursive jQuery submit function doesn't submit the form I need some code to run right after the submit button has been clicked and before the form has actually been submitted.
I've stripped the code and left only the parts needed to show you the problem.
What I need the code to do is go inside the submit function, but instead of submitting the form call the function again.
The form should submit only in that second iteration.
Except it doesn't. The code is fully executed as it should but the form doesn't submit in the end.
I would appreciate it if someone can explain why.
Here's the code (simplr-reg's the form's name):
<script>

var reallySubmit = false;

$('#simplr-reg').submit(function(event)
{
   if (false == reallySubmit)
   {
      reallySubmit = true;
      $('#simplr-reg').submit();
      event.preventDefault();
      return false;
   }
   else
   {
      return true;
   }
});

</script>

A: $("#simplr-reg").submit();

That says "call the submit method on the jQuery selection".  You have a jQuery submit handler bound to the selection.  Since you have triggered the event on the jQuery selection, the jQuery handler is also triggered.
If you trigger the event on the native DOM form object (this within the submit handler), the jQuery handler will not be triggered, so you won't go round in circles.  Call the form.submit method:
this.submit();

A: Change it from a 'submit' event to a 'click' event and attach it to the button itself rather than the form?
ETA: be sure to 'return false' on your non-submit case.
$("#simplr-reg-submit").click(function()
{
      alert("1st iteration");
      $("#simplr-reg").submit();
       return false;
});

redpajama_set_name: RedPajamaStackExchange


text:
Монові () — селище () в США, в окрузі Бойд штату Небраска. Населення — 1 особа (2010).

Особливістю населеного пункту є те що, він не є невключеною територією, а має власну виборну адміністрацію в особі єдиної мешканки Елсі Ейлер. Єдина мешканка поселення Елсі Ейлер є водночас його мером, універсальним муніципальним службовцем, єдиним виборцем, платником податків, власником таверни та бібліотеки.
Через свою особливість поселення є доволі популярним туристичним об'єктом як серед мешканців сусідніх населених пунктів, так і туристів з інших штатів США. Найбільша кількість населення Монові була зафіксована у 1930 році. Тоді в селі проживало 130 осіб.

Географія
Монові розташоване за координатами  (42.830705, -98.329560). За даними Бюро перепису населення США в 2010 році селище мало площу 0,55 км², уся площа — суходіл.

Демографія

Згідно з переписом 2010 року, у селищі мешкала 1 особа в 1 домогосподарстві у складі 0 родин. Густота населення становила 2 особи/км². Було 3 помешкання (5/км²).

Расовий склад населення:

До двох чи більше рас належало 0,0 %. Частка іспаномовних становила 0,0 % від усіх жителів.

За віковим діапазоном населення розподілялося таким чином: 0,0 % — особи молодші 18 років, 0,0 % — особи у віці 18—64 років, 100,0 % — особи у віці 65 років та старші. Медіана віку мешканця становила 76,5 року. На 100 осіб жіночої статі у селищі припадало 0,0 чоловіків; на 100 жінок у віці від 18 років та старших — 0,0 чоловіків також старших 18 років.

Цивільне працевлаштоване населення становило 0 осіб.

Джерела

Посилання
 Найменше у світі місто з населенням 1 людина
 Монові: місто однієї людини
 Welcome to Monowi, Nebraska: population 1
 What It's Like to Be the Only Resident in a Pop. 1 Town
 Monowi, Nebraska

Селища Небраски
Населені пункти округу Бойд (Небраска)

redpajama_set_name: RedPajamaWikipedia


It was quiet for a few moments and then she said, "What about your New Year's resolutions?"
I informed her I was working on a brand-new set of New Year's resolutions for the coming year. I think it's rather important to jot down a few things you would like to do, maybe some improvements you would like to make or maybe something I should like to give up for the New Year.
I had resolved to improve my diet and lose some weight. Fortunately, I did not put down how much weight I proposed to lose. I did lose 1 pound 974 times but it always found its way home. I spent some time in Michigan this past summer and just as I was leaving, I threw a pound out the window and hurried on. By the time I got home to Florida that pound was waiting for me at the front door munching on an Apple fritter. What's a person to do?


InfoQ Homepage Articles Is REST the future for SOA?
It seems like everywhere we turn we keep hearing that SOA's future is REST. There are a lot of publications comparing REST to SOAP and WS*, but such comparison seems to be too simplistic. There are two main approaches that have emerged lately – true REST and REST as a technology approach for services (aka REST Web Services). In this article I will try to discuss whether either of these approaches can improve SOA implementations.
A true REST is effectively an implementation of Resource-Oriented architecture and not a pure technology decision. So the right question to ask when discussing true REST is whether its underpinning – ROA - is a good fit for your SOA implementation.
In order to assess the problem correctly, let's first recall that the SOA architectural style  is based on a functional decomposition of enterprise business architecture and introduces two high-level abstractions: enterprise business services and business processes. Enterprise business services represent existing IT capabilities (aligned with the business functions of the enterprise). Business processes, which orchestrate business services, define the overall functioning of the business.
REST, on another hand, is a set of architectural guidelines  expressed as Resource-Oriented Architecture (ROA). ROA is based upon the concept of resources; each resource is a directly-accessible distributed component that is handled through a standard, common interface. So, the foundation of ROA is a resource-based decomposition.
A service is not a programming construct or a set of APIs, but rather an architectural (unit of design, implementation, and maintenance) and deployment artifact used for implementation of enterprise solutions. The service functionality is defined by a service interface (specific for a given service), which can be supported by multiple implementations. There are two basic ways of defining a service interface – RPC-style and messaging-style. RPC-style implementations use service invocation semantics and are defined through a set of parameters in the service interface. In the case of messaging style, a service interface is effectively fixed – it essentially performs "execute" - with an XML document as input and output (much like the GoF command pattern). A service semantic, in this case, is defined by the semantics of the input and output messages.
Historically, services are often defined as a collection of methods, but as explained in  these methods are independent from each other and such collection serves as a namespace, simplifying the management of the services.
In the simplest case, a resource can be defined as a directly-accessible, independently-developed, deployed, managed and maintained software artifact supporting specific data. A resource is defined by a noun for example, "doctor's appointment" that describes the data provided by the resource. A resource can also relateto other resources and provide a reference (link) to them. In effect, a resource is similar to an object, but with a predefined (CRUDish) interface semantic.
A resource is defined by its URL and definition of inputs/outputs for every operation supported by a resource. Unlike a service, where methods are completely independent and can be deployed as independent endpoints, methods on a resource follow OO semantics, which means that all of them (except createResource) have to exist on the underlying resource (same URL).
Based on the above definitions of resources and services, it seems intuitively obvious that they are very different. Let's delve into these differences first, and then discuss how they can impact resulting architecture.
Here we will use a slightly different analogy, one based on J2EE. We can think of services as stateless session beans and resources as entity beans.
Services – session beans – serve as controllers allowing execution of a required operation, regardless of the underlying resource. For example, a debit account service might take the account ID and the amount and debit required account. A single service can debit any of the existing accounts.
Resources – aka entity beans – serve as a data access mechanism for a given instance of given data type. For example, in order to debit a certain account, it is necessary to find a resource representing this account and then update it to debit the required amount. An additional caveat here is that unlike an entity bean which can implement any required method, a REST resource has only a single modify resource method. This means that the actual business operation, the debit, has to be encoded as part of the request.
Based on the above, it is impossible to build an SOA system using true REST. It is possible to build a system, but it won't be SOA. Both will start with the business-aligned decomposition, but because they are using very different decomposition approaches they will result in completely different architectural styles based on different set of components and connectors.
Just because they are trying to solve the same problem – business/IT alignment and are both based on business driven decomposition does not mean that the result will adhere to the same architectural style.
Another question is whether it is possible to build a complete system using true REST. Based on the above, it is a question of whether it is possible to build a complete system using only a database or entity beans. Certainly you could, but it would require adding procedural code in the form of stored procedures (overwriting the meaning of the methods) or triggers (doing post processing based on the data changes). The same is typically true for a true REST implementation – you have to change the meaning of the modifyResource method (often using command pattern) to do more than data update.
As a result, a REST-based implementation is rarely true REST; it typically includes at least some elements of REST Web Services. So what does it mean to be a REST Web Service?
The REST Web Service approach is an approach for using REST purely as a communication technology to build SOA. In this case, services are defined using SOA style decomposition and REST-based Web Services are leveraged as a transport.
Although these differences are important (I will discuss them in detail later in the article), the main difference between SOAP and REST is the fact that while REST is implemented directly on top of the HTTP protocol, SOAP introduces an abstraction layer (SOAP messaging), that can be implemented on top of any transport. Standardized SOAP bindings currently exist for HTTP, SMTP and JMS, but non-standard bindings have been implemented for other transport solutions. This additional abstraction layer that provides decoupling between existing transports and SOAP-based implementations is the root cause of major differences between SOAP and REST Web Services.
The opinions about this abstraction layer vary significantly depending on whom you talk to. The REST camp considers it to be over-engineering and claims that it does not provide any real value. They claim that HTTP already provides all of the features required for implementation of services interactions. The SOAP camp, on the other hand, will argue that HTTP is not the only transport that is typically required for service interactions (especially inside the enterprise) and having a portable, extensible abstraction layer is necessary for building robust, feature-rich service interactions.
Although both points of view have their merits, in my experience trying to limit SOA implementation to a single transport – HTTP - rarely works in practice. Yes, HTTP is ubiquitous and its usage typically does not require any additional infrastructure investments, but it is not reliable (HTTP-R is not widely adopted), synchronous only (creating temporal coupling), does not have transactional semantics and so on.
Additionally, even if HTTP is the only transport used in implementation, the SOAP envelope can become very handy for a clean separation of business (SOAP Body) and infrastructure or out-of-bound (SOAP Headers) data in SOAP messages. And finally, if your original implementation does not require any infrastructure or out-of-bound data, the overhead of the SOAP envelope is minimal – two tags, but provides a well-defined way for adding such data as the need arises.
So, at the end of the day, data enveloping with separation of business and infrastructure concerns is a very powerful paradigm, which is often used even in the REST Web Services implementations. Whether to use a standardized SOAP or a custom enveloping schema has to be decided by a specific implementation.
Let's take a moment to discuss some of the other differentiators between SOAP and REST Web Services often cited in publications.
Defining an interface in a text document and "manually" coding of data marshalling/unmarshalling based on a common interface definition described in the interface document. Although such an approach is often promoted by REST advocates, it rarely scales beyond 10 - 15 elements, which is not typical for coarse grained REST services. Besides, such an approach is very error prone and as a result, most of the available REST frameworks have abandoned it in favor of the next approach.
Defining an interface on the XSD level and generation of the data marshalling/unmarshalling based on the preferred framework (for example, JAXB or Castor in the case of XML payload or Jackson, in the case of JSON payload). Such an approach is, in effect, a minimalistic version of WSDL and requires about the same amount of effort as SOAP-based implementations. In fact, exactly the same approach is often used in the SOAP-based implementation, leveraging a single interface and a command pattern for service execution. The extension of this approach is usage of WSDL2.0  and/or WADL  for REST.
So, with the exception of the most simplistic examples like "temperature converters", REST is not any more simple than SOAP.
SOAP requires an XML wrapper around every request and response, which increases the size of a message. Although this is true, the important thing to consider here is not how many bytes the wrapper adds, but rather the percentage of overhead it creates. Because the wrapper size is constant, this percentage decreases as the size of the message grows, eventually becoming negligible. Considering that a typical service is fairly coarse-grained, the size of the request and reply is fairly large and consequently the overhead of a SOAP envelope is rarely an issue.
SOAP is XML-based messaging, which uses verbose encoding. REST, on the hand, provides a more lightweight messaging alternative – JSON. Although this is true, usage of the Message Transmission Optimization Mechanism (MTOM) , supported by most SOAP frameworks, allows for splitting of messages into minimal XML-based SOAP Envelope/Header/Body parts and additional parts containing message content that can be encoded as any MIME types, including JSON, binary streams, etc.
Although in theory, REST is lighter-weight compared to SOAP, in practice, with some advanced SOAP design techniques, the difference between size of realistic SOAP and REST messages can be made minimal.
Because REST is based on HTTP, one of the claims of its proponents is that one can use familiar technologies like the Java servlet API and Java HTTP support to write REST services implementations and clients without any specialized toolkits. This is true if one wants to "manually" implement building input/output messages and data marshalling. The same can be done for SOAP Web Services as well. However, people rarely want to write such boilerplate code and as a result use toolkits for both SOAP and REST .
REST can be used as both system design approach leveraging ROA (true REST approach) and SOA design implementation leveraging REST technologies (REST Web Services). Although both approaches have their merits, they do not change the hardest part– defining business services/resources aligned with the enterprise business model. There are cases for both SOA and ROA, but at the end of the day those are two very different styles.
6. Dhananjay Nene. Service oriented REST architecture is an oxymoron.
8. Dhananjay Nene. Musings on REST.
11. Arun Gandhi. SOAP vs. REST – The Best WebService.
12. Please see this link.
15. Stefan Tilkov Interview with Sanjiva Weerawarana: Debunking REST/WS-* Myths.
16. Lori MacVittie. SOAP vs REST: The war between simplicity and standards.
17. Please see this link.
18. Mark Little. A Comparison of JAX-RS Implementations.
 I am using here the term, that technically make no sense, and is not REST, but is widely adopted in industry and is considered to be REST by many people.
 A typical implementation of such service is based on "command pattern". An input document defines both command itself and data used by this command.
 Method independence stems from the fact that although different methods can be executed on the same data – here this is an enterprise data which exists regardless of whether it is exposed by services, not an object instance specific data as it is used in OO.
 Many of the REST proponents claim that the latter is not necessary. We will return to this point later in the article.
 Another misnomer popular in industry – Web Services are SOAP by definition.
 All of the WS* implementation heavily relies on SOAP, more specifically on SOAP headers.
 You can always implement asynchronous messaging on top of HTTP, but you need an additional abstraction layer, for example SOAP with WS-Addressing, on top of it.
 Many REST proponents will argue that HTTP already have a set of standard headers thus SOAP headers are completely unnecessary. The issue here is that a predefined set of HTTP headers  has a very well defined semantics and any application specific data requires a custom HTTP header, which creates the same level of complexity as custom SOAP header.
 An interesting example of this is usage of the client APIs in many JAX-RS implementations, where interface is effectively a java interface – so much for multi language support.
Is REST the future of SOA? Yes!
Really good article, particularly pointing out that REST web services are really just a different protocol used to implement what is architecturally the same thing as what you get with WS-*. That said, having worked with both, I favor using REST as a protocol simply because it better supports my incremental development style that involves manually interacting with the service through a browser. This reflects my history using the ancient, text-based Internet where the analog to the browser was Telnet and I could invoke and 'converse' with services manually e.g. FTP, NNTP, etc. and thereby more quickly debug my programmatic service clients.
This is a great write up to compare both ROA & SOA as well as REST & SOAP. Thanks!
The simplicity of REST when i read about it, it's on the client side, you only need to know the parameters the service need and write a simple request...on the other side, on SOAP WSDL and all that stuff you will need a framework, but when you have 5 or more services on different ws-stack...you start to have troubles, the classloader and the conflicting libraries are the most common problems you will found..on my experience the REST aproach is more simpler to work that the SOAP approach. At least on java applications.
I hope people take more seriously REST Web Services using json.
One of the benefits of a true REST implementation is the navigability. Each resource can provide hypermedia with links to potential "next steps". With WS-* style services the client needs more documentation.
OData is very data focused.
You can expose a set of interrelated data entities as a model (in metadata) and query and update the entities in more or less arbitrary ways.
Nice article though. I still think we need a new term instead of REST to denote non-REST web interactions.
Thank you for writing this article, im glad that I read it.
Think about the differences between Resource and Services, is crucial in this matter.
It is without a doubt the first valuable article on the subject. People tend to misunderstand the REST, REST Webservices, SOAP and SOA. Now you are puting things on their places.
This article is complete crap, and misrepresents REST in too many ways to enumerate. Please ignore it.
Shame on you, InfoQ editorial staff.
REST is actually an architectural style and some REST people will tell you it is not a protocol. That is why it makes no sense to compare REST against SOAP.
Actually, that simplicity you mention, if I understand correctly, is real, but it is not from REST. You see, REST is hard, actually, as all you should need to know is the initial URL. You should not have any prior knowledge about operations or parameters before hand. It is mentioned in this comments, HATEOAS is a requirement not often met. Knowing about the operations and parameters and even the url format (like templating) before consuming the resource is like having the WSDL not in XML but on your mind, or written in out-of-band.
Is there no editorial review at infoq? You dont need to read more than the first two paragraphs to know that the author has no idea what REST actually is.
Very good article. I specially like the idea to clarify that REST and REST-WS are different things.
1. I do not like the REST~Resource CRUD idea. You know, HTTP operations have similarities with CRUD, but are essentially different. The GET is not a read, it is a request for a representation. The PUT (often used as an update in REST community) is really a creation operation within the client's control space (it is the client the one that provides the URL or ID of the new resource). The POST is not an update nor a create (as in the REST Community), but an "Send" operation, where you send or post some data TO a resource. What that posting means and affects is totally depending on the actual resource business semantics. Thus, posting may result in a creation of a sub resource, in an update or even in a simple notification without any resource change. You see, not quite CRUD.
3. REST is more than a set of architectural guidelines, it is actually an architectural style based on the combination of other styles, specially tuned to meet the Web requirements. It is a nice comparison between the resource and a service, but it is also important to compare REST style vs SOA style. REST is for networked applications and SOA for integrated ones, the components and relations are different, etc. And of course, comparing SOAP vr REST makes no sense as they are at different levels.
I think it's very hard to get out of the RPC way of thinking and planning; it's simply faster/easier and more concrete to hack together an RPC style wrapper around some data/function (that's probably RPC like to begin with). Thinking and designing with resources, representations and hypermedia is still hard work and takes time. Most developers and managers can't be bothered because they don't see any immediate value. Sadly this story is not news to anyone.
In my mind, and I write this explicitly - SOA is an architectural style, while Web services is a communication mechanism. Moreover, in my mind, Web Services is an extremely unfortunate name - it has nothing to do with Web, hence there are multiple binding, SOAP over HTTP being just one of them. Now what you are describing is, in my mind is true REST, not REST Web Services.
I fully agree true REST represent ROA architectural style. I am in now position to judge whether SOA is better or worse then SOA, I am only saying they are different and should not be confused.
Paul, You bring up good points on how seemingly hard it is to design RESTful services. SOA as an architectural style isn't constrained; to the contrary, REST as an architectural style is a constrained architecture with very specific constraints; in a sense its opinionated; a term popularized by 37signals/ruby-on-rails.
It is unfortunate that vendors have made developing SOAP based Web Services very easy to develop and put out into the wild, without any service orientation nor architecture; I like to call these services-that-get-the-job-done. IMO RESTful systems are hard because it makes people think about what they are doing.
"Most developers and managers can't be bothered because they don't see any immediate value. Sadly this story is not news to anyone."
Indeed it isn't news and it's a good chunk of the reason why our industry largely under-achieves.
"A "Service" is defined by a verb ( For example, "validate customer's credit score", which describes the business function it implements.)"
That's one means of defining a service (functional) but there's another one (data). If one follows the rule of thumb that says "don't move lots of data across functions" (research.microsoft.com/apps/pubs/default.aspx?i...) then one can see that splitting services on the basis of function is often (but not always) a poor choice. The point then is that service design (like all design) is a matter of taste and judgement, not fixed process and checklists to be followed blindly with no thought.
1. I think that one of the reason why our industry is largely under-achieves is because we are not willing to either read or listen. We tend to form our own opinions even before we read or listen to something.
2. For better or worse SOA is based on the functional decomposition which often makes it difficult to accommodate enterprise data www.infoq.com/articles/SOA-enterprise-data. As for the data service, it is typically a data access service, which does not really solve the problem of moving data.
3. An article is not trying to compare functional and data decomposition. It merely states that they are different. I happen to agree that "service design (like all design) is a matter of taste and judgement, not fixed process and checklists to be followed blindly with no thought." I also happen to think that a good service design is still an art, not a science.
4. There is no place in the article that talks about how design should be done. What do I know, I am just an architect.
Did you really mean to write this?
1) You bring up good points on how seemingly hard it is to design RESTful services.
I may misunderstand what you mean.
I also would like to remind everyone that to the best of my knowledge JAX-RS was designed with Roy Fielding's participating and blessing. Here is the list of "experts"
1. Any real world business service that you can possibly think of can be defined as one of the HTTP methods. In fact, in your example ("VALIDATE customer's credit score") I stil don't know what service does for me. The consumer is not interested in validation part, but in the outcome of the validation of the thing that needs to be validated. So, from business perspective, the better service would be: "give me customer's credit score". The validation part is the implementation. What I'm trying to explain is that from business perspective the consumer always wants to give or get something. The "noun" can be important, but is only part of the giving or getting. That's why probably in your experience too, almost any service starts with get, save or something similar. Other noun's are rare or have stupid names like "process". So, it's all about the payload and not the service.
2. The comparison with DMBS is clever, but completely wrong. Similarity in methods says nothing about granularity. Business service can be "give me monthly report" which can based on many systems and databases.
3. You are actually admitting that you never haven seen REST based system: "Another question is whether it is possible to build a complete system using true REST". So, based on what did you wrote this article. A lot of theory? The arguments from REST community comes from practical experience.
5. Simplicity vs. standards. I don't really get it what you are trying to say. So, if we implement all those WS* standards we will have great systems? Well, I would rather bet on simple systems which are easily changeable. This is a fundamental difference in the way we see system engineering. Agile crowd tend to go for simplicity, which proves in practice as a better approach. Standards are important, but so often not needed and only a bottleneck in delivering business value.
What I mean by this resource oriented design involves re-thinking how one thinks about distributed systems and thats not easy. While the principles of RESTful systems are very simple at a high level, it involves a lot of design thinking. Which is why you see a lot of systems claiming to be RESTFul, that are really RPC systems over the web; where developers try to shoe horn the RPC paradigm onto a web platform.
With tools/frameworks that allow an object oriented system to be exposed as a "web-service" easily and tools that can generate proxies that can be used to talk to these services; it makes it easy to expose a system thats not designed to be distributed, easily exposed for consumption over the wire. I don't mean this in a derogatory way; you can do good SOA with the tools, its the flip side thats unfortunate.
I like the notion of decomposition and the discussion in general. Well said!
I agree with the select few here who say REST is not a protocol, nor does it dictate HTTP as a transport. It's a paradigm.
As for the difference between a service and a resource, I think it's valid to differentiate but at the end of the day does it matter? I call a service and get a resource. In many ways I can think of them as the same. REST to me doesn't dictate that it's an extension of the database and therefore restricted in data manipulation as a service would do. I expect a requestee to do what it needs to do to service my requestor. Some of my services are really physical resources (address), some are logical resources (payment). Maybe I'm violating something, but it's working really well to allow variance in my abstractions.
sorry, I thought I had heard repeatedly the other way around from RESTafarians, that was actually the selling point of REST.
What in specific? Do you mean development and implementation or architecture? RESTful systems, provided you understand the principles and constrain the architecture according to them, is technically very simple to understand.
really? anyways, understanding is a moot points, as architects we all know that LOE, cost, ROI, time-to-market is really what counts. Hard to do vs Easy to do is impacting all of them. I guess that should easily close the debate then.
I disagree! Strategically good architecture is important for LOE, cost and ROI. Time to market is not a one time thing. If you don't have a good architectural foundation you cant sustain all of those metrics. Business agility comes with good architecture and good architecture only comes with understanding; be it SOA or RESTful architecture.
Any real world business service that you can possibly think of can be defined as one of the HTTP methods.
There are two issues here. Services in SOA are not necessarily services delivered to end user. The majority of SOA services are the building blocks of the solutions satisfying user's needs. Second is that they can not really be delivered as an HTTP method. They can be delivered using HTTP as a transport and there is a big difference between these two statement.
from business perspective, the better service would be: "give me customer's credit score"...The "noun" can be important, but is only part of the giving or getting. That's why probably in your experience too, almost any service starts with get, save or something similar.
With all due respect I disagree. In your example, The noun will be "calculate Credit Score" and a customer will be a parameter.
The comparison with DMBS is clever, but completely wrong. Similarity in methods says nothing about granularity. Business service can be "give me monthly report" which can based on many systems and databases.
First its not mine, its belongs to Nene. Second the comparison is on API not a granularity level. The resource can be as complex as it needs to be.
You are actually admitting that you never haven seen REST based system: "Another question is whether it is possible to build a complete system using true REST". So, based on what did you wrote this article. A lot of theory?
Well, I have been an architect for about 15 years, developer before that. I have done quite a few systems implementations. What I am saying is that every REST implementation that I did or have seen always was a mix of True REST with REST Web services, which disqualifies it as a true REST implementation.
In your article, I did not find a single example of a situation and service that cannot be solved with REST.
Yes, but it will not be SOA system anymore. That's my point.
Simplicity vs. standards... So, if we implement all those WS* standards we will have great systems? Well, I would rather bet on simple systems which are easily changeable. This is a fundamental difference in the way we see system engineering.
If you agree service design is a matter of taste why are you prepared to be bound by SOA being defined as a functional decomposition? Presumably some element of the industry has decided this is the rule? There are a number of examples of SOA's that aren't decomposed by pure function and with good reason (see my original reference to Jim Gray's analysis).
More importantly, if one ignores this rule of functional decomposition being the driving design approach for an SOA, services start to look a lot more resource oriented and can thus be made RESTful.
"There is no place in the article that talks about how design should be done."
Except that you insist that SOA is all about functional decomposition, which is an assertion about how design should be done i.e. you cannot focus on a data-based approach.
"As for the data service, it is typically a data access service, which does not really solve the problem of moving data"
Typically is not a rule though, so one can design a data service that isn't about purely data access and thus does address the moving data problem.
That is exactly my point. If you do this, then you do not have SOA. You have REST. SOA is an architectural style, which defines services as a result of functional decomposition.
Yes, but this is yet another architectural style, which I am using a lot lately with my Hadoop - based implementations.
Once again - my point is that there are many architectural styles in a true architect toolbox and he has to pick the one or combination of several to do his job. The is the right thing to do. He also has to know exactly which style and why he is using for solving specific problem.
The SOA group of the enterprise I consult with has developed a data oriented scheme for organizing service interfaces.
All services are organized around major entities (such as Customer, Part, Vehicle, etc). This organization is apparent in the WSDL target namespaces (e.g. urn:customer/...; urn:part/..; etc). All new services are organized this way.
There is a kind of a macro-level OO'ness present here. Service operations are considered as operations around a major entity. An entity can have multiple services allowing us to grow an entity over time.
See the soon to be published "SOA with REST" book for more details.
@Faisal I don't follow how this is different from functional decomposition. What is the significance of "grow[ing] and entity over time"? Does this mean adding new operations?
Yes mostly adding new operations (and/or new services).
The goal is to build and an 'enterprise api' over time. Realize that enterprise data models are very complex (much more so than say facebook or ebay public data models). So the api we are building is virtual as it is composed of different services implemented by different groups, over time.
The key is that we are using major entities (as opposed to functions) as the organizing principle for services. The api is discoverable via the registry (and we have prototyped ways of making it browsable by entity in a nice Silverlight front-end).
Business processes 'stitch' services together. Most of these are implemented as applications but many are implemented with BPMS tools. We heavliy use intermediaries such as xml gateways and have started to use an ESB for async and pub-sub.
I don't want to give the impression that we are already there and successful. This is a journey that we have been on for over a year now. All I can say is that we are progressing well and have not found any major disconnects, yet.
This is very real - not fluffy pontification.
Hi Mark. +1 to your comment.
Besides the mis-information about REST, I think the article mis-represents the very issues of the problem domain. Maybe the problem is more one of the writing than of your knowledge of the problem space? Could it be that the points your are trying to make simply don't come across?
REST is like a method to manipulate data with set-operations (Insert, Delete, Update, Select), WS-* is like a way to manipulate data with stored procedures. sp-s do create an additional abstraction layer for the same reasons and with the same results as WS-* do.
Jan, thank you for the benefit of the doubt.
Of course I am not the best writer, at the end of the day my PhD was in EE not English literature, and besides, English is my second language. But may be, just may be not all the blame should be addressed to me. May be some of the problem is the way people are reading this article. Quite a few comments that I see here puzzle me. The article is NOT about benefits or shortcoming of either REST or SOA (sorry, both of them have shortcoming), its about the fact that they are different styles.
Now, what exactly did I mis-inform and mis-represent? If I am blamed for something I prefer this being more specific.
The data transportation mechanism you use to carry event notifications and parameter values from a client to an application does not change the architecture of that application. The application interface is always (if OO) one or more roles performing operations on business entities. No external thing EVER accesses a business entity directly but goes through a role (to give RBAC). A set of operations supports a business process run by the roles and is called a service. Web or restful services are at a lower layer in the ISO 7 layer model. When such a service is invoked it has to translate to calling an operation on a role. This is exactly the same as you do in a GUI though in a thick client the widgets may invoke a role operation directly. A restful interface can talk about modifying a business entity directly but it never does – it is an abstraction exactly as we have been doing for years in GUI design. The RBAC "layer" has to be there.
Perhaps you are right but I would like to elaborate further.
1.	Engineering: Part has engineering and design aspects (concept; prototyping; testing; final specification; engineering changes over time; etc.). Parts range from simple (nuts and bolts) to complex sub-assemblies.
3.	Manufacturing – parts eventually are included in an end product (such as engine or transmission) and have to be tracked as part the bill-of-material of the final product. Also part of the supply chain.
The above is what we would call functional areas. The entity Part cuts across them all. Each functional area itself is huge in terms of Part data and business processes. The only data element common across all functional areas is the part-number.
While the functional areas appear to be silos they are in fact all linked together with complex interdependencies. For example, warranty repairs may trigger engineering design changes with cascading consequences. There are also interdependencies between different entities such as Part and Vehicle.
Systems in the functional areas were pretty much silos before SOA. With SOA we can link the functional areas better and reduce (but not eliminate) data movement. The approach we have taken gives us a consistent way of building a façade to enterprise data and processing. Operations around Part can be logically grouped together in a coherent view, even when each service/operation is managed by a different functional area.
There is so much metadata that it would be impossible to deal with the data without some kind of metadata description language that is machine readable. Operations are not all CRUD type. There are set operations and other business process specific operations.
Also it is impossible to create a single model for any major entity as that model keeps changing all the time and no one person knows it all. We deal with piecemeal models of each entity in relation to service calls – with contracts and versioning.
The challenges are enormous and I don't want to minimize that. We have our feeble attempt to address these challenges, which seems to be working thus far. Whether we are ultimately successful, we don't know.
[Service | Resource] Oriented Architecture representing the same level of abstraction? And are they mutually exclusive? Or does 'Service' simply represent a business offering or solution, while 'Resource' represents a business concept or entity? And so, can a Service be a Resource, or vice versa?
Of all the terms here, REST seems the most clearly defined based as it is on other, already well defined Internet characteristics through Fielding's thesis. However, it's level of descriptive abstraction seems to me completely orthogonal to the so-called architectural styles being argued above. It seems to me more like a design technique than an architecture, though it is itself is an abstraction of certain Internet architecture properties.
The use of the word 'protocol' also requires better care in usage: It does not always or only refer to networking and communications. A protocol just describes the discrete steps of some process with well defined results. Consequently, we may use the term at practically any level of descriptive abstraction.
I still think the article is quite useful and well written in that it brings up several points well worth further discussion. And it does take care to try and carefully define terms. Readers just need to be a bit less orthodox and parochial in their reading of it.
The abstraction here is an entity with it's operations (somewhat like OO).
I will refrain from using the term Entity Orientation :).
In our model, a service is just a container for operations on an entity. New operations can be added to services at any time because that does not break existing contracts.
Entities are virtual but their operations are concrete and may be spread across multiple services (at different hosts). Registry and metadata bring it all together.
PS. The browser equivalent in WS* world is the tool SoapUI which is useful for manually exploring and interacting with services.
If it helps, here are some ways in which the article seems to misrepresent REST.
1. REST is not built on the HTTP verbs. REST is a style and those verbs are part of the HTTP realisation of that style. Rheims Cathedral is built in a gothic style, but that does not mean you have to look like Rheims to be gothic. You can be RESTful without using the HTTP verbs.
2. The descriptions of PUT and POST are confused. A PUT is idempotent, but creating a new resource is not idempotent.
3. REST is not about entity beans. Just because the HTTP verbs can be interpreted as CRUD (Create, Read, Update and Delete) does not mean that REST is just for CRUD. It is for managing resources. Where a resource is directly mapped to an Entity, it will look like an entity. Where the resource is not directly mapped to an entity it will not. For example, you can use a Transaction resource to manage a transaction using REST.
4. The other defining characteristics of REST are ignored. Namely: multiple representations; every resource is a URL; Hypertext as the engine of application state. These are far more important to understand than the universal interface.
5. The context of REST is ignored. This is explicitly a style for mediating between user agents and resource managers. There is no such context for Web services.
6. The reason why RESTafarians believe that WSDL is not needed for RESTful services is completely misunderstood. It is precisely because it is the User Agent's job to represent a resource, but the person's job to understand it, that WSDL is not needed at run time. REST does not need expensive dynamic binding like SOAP.
For these reasons, and a few more, I concur with Mark Baker's assessment of the article.
1. Technically you can, practically I've never seen it.
2. Sorry, my and inspire.jrc.ec.europa.eu/reports/ImplementingRu... mistake, which does not really change anything in the content.
3 Comparison to Entity beans has nothing to do with CRUD. The difference between Entity beans and Session beans(I know it was long time) is that an instance of Entity bean is associated with the explicit resource (database record), while Session bean is resource independent and resource is passed to it as a parameter.
4. Yes, I did not write about these additional features of REST, because they are not relevant to the topic. I do happen to know about them, but this was REST usage for SOA article, not REST evaluation.
I might be wrong, but it feels like part belongs more to the canonical data model than to service definition.
Also, when you are saying things keep changing, which is normal. The question is whether base entities are changing fast (should not happen) or the processes orchestrating these services are changing (expected).
It is hard to completely model a major entity like Part in a large enterprise. A major entity has its tentacles in many functional areas. It will have to be a coordinated effort of multiple knowledgeable individuals and will require so much time that by the time its done things will have changed.
In the meanwhile we can't stop groups building services to support the process they are implementing.
Changes in business process and new processes often do require new data to be kept and managed which many times is associated major entities.
I think the right 'solution' to the modeling problem is to move to semantic models (owl,rdf)that can be grown organically over time. However that is a major shift from where enterprises are today. Perhaps the adoption of NoSql/graph stores will slowly move us in this direction.
It seems, that your are mixing the semantics of "simple" and "easy". The uniform interface is simplistic, which means it is "artles" or "plain".
You have to know more, than a single bookmark URI. There must be an agreement on media types and relation semantics. Furthermore, no one hinders you to use a schema to describe you representations.
Did you ever try to consume SOAP service with mobile clients? Microsoft did a pretty good job there on their mobile platforms. But all others have really bad support for SOAP. Why is that? I think due to the restricted resources on the phone.
For AJAX clients its very easy to consume REST "Services" due to JSON support.
"REST does not restrict communication to a particular protocol, but it does constrain the interface between components, and hence the scope of interaction and implementation assumptions that might otherwise be made between components. For example, the Web's primary transfer protocol is HTTP, but the architecture also includes seamless access to resources that originate on pre-existing network servers, including FTP , Gopher , and WAIS ."
Resources are not only "things". An activity/task/process can be a resource, too (see pautasso's work). Fielding: "Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on. In other words, any concept that might be the target of an author's hypertext reference must fit within the definition of a resource"
I love some stuff in SOAP world (e.g. proxy generation). But i think, REST has some really "cool stuff": The biggest power of HTTP/REST is the linking of things. Through the simplistic nature of the interface, everything is linkable - even task/activities/processes.
By the way: A REST-based web service is (usually) not a single resource.
The functional complexity is split up on multiple resources. Some of them may be activity resources. I dont see, why a SOA can´t be realized with the REST approach... The functional decomposition is just different in comparision to the SOAP/RPC style. Here, a service is one endpoint with multiple methods.
something like compare white(color) to animal. what's difference between animal and white?
"REST is the brainchild of Roy T. Fielding, cofounder of the Apache HTTP server project and coauthor of the HTTP and URI standards.
In 2000, he wrote a doctoral dissertation for the University of California at Irvine called 'Architectural Styles and the Design of Network-based Software Architectures', wherein he defined REST."
REST has the advantage of easily making use of a well defined set of HTTP status codes.


text:
Hands On Training
H.O.T. Instructors
Leadership/Command Series
HomeLecturers
Travis HowzeKeynote Speaker
Travis Howze is an internationally touring comedian and motivational speaker who spent 14 years in the military and emergency services as a U.S. Marine, Police Officer and Firefighter. Whether performing at corporate events and fundraisers to top comedy clubs, colleges and multiple tours overseas for the troops, Travis has become a comedic demand in multiple arena's who always leaves his audiences craving more!
Known as the military and emergency services voice of comedy, the topics of Travis' humor are limitless: from being raised in South Carolina to married life and fatherhood to his time in uniform and much more. Whether dodging bullets, chasing bad guys, running into burning buildings or just being a dad, Travis is always FUNNY UNDER FIRE! Appearing on Gotham Comedy Live, HULUTV's Coming to the Stage, National Geographic and NBC's Night Shift, Travis was dubbed "Artist To Watch" by Young Hollywood Magazine.
Not only is Travis the Author of the Best Selling book "Create Your Own Light, an autobiography of his life on "Finding Post Traumatic Purpose." His album, "Reporting for Duty," debuted at number 7 of top 100 comedy albums, and is in regular rotation on SiriusXm. IGNITING top level comedy stages for over a decade, he's a comedian with an extremely unique and marketable edge that has never been seen before, thus allowing him to connect and develop a very loyal brotherhood style fan base of military, emergency services personnel and their supporters from all over.
In June of 2007 while working a furniture warehouse fire in Charleston, South Carolina, 9 of his brother firefighters tragically perished in the line of duty while rescuing a trapped civilian. Due to injuries that he sustained in that same fire, Travis was forced to leave the job that he truly loved.
closepopup
Sean DuffyLecture Series
Sean Duffy is a 16-year veteran of the fire service and has worked for both County and City departments. He is currently a Firefighter/Paramedic for the City of Venice in South West Florida. Sean is a Co-Founder of Build Your Culture LLC. and developed the courses entitled "Searchable vs. Survivable- Educational Decision Making on the Fire ground" and "Build Your Culture- Professionalism or Minimalism. He has an Associates in Fire Science and is also a State of Florida Fire Instructor, Fire Officer 1 and Live Fire Training Instructor. Sean is an active member the Marion County Fools Chapter (McFools) and enjoys being a student of the craft as well as passing on knowledge gained from real world experiences.
Pablo GenerLecture Series
Pablo Gener
-13 year veteran of the fire service
-Special ops team experience
-Instructor at Marion County training division
-Peer fitness trainer Marion County health and wellness center.
-Multiple fire conferences and FOOLS event across the nation both attended and instructed.
-FOOLS member since 2008
Anthony GillamLecture Series
Anthony Gillam is the Lieutenant of E24 in Marion County Florida and has been in the fire service since 2005. He is a state of Florida certified instructor and is part of Marion County Fire Rescues instructor cadre for new hires and ongoing education. Anthony has spent the last 5 years as an instructor for the Orlando Fire Conference rescue site and also teaches RIT, firefighter survival and search in other parts of Florida. He is a United States Marine Corps veteran and has been heavily involved with the FOOLS including serving as the Marion County chapter president for the last 8 years. Antony is an avid student of the fire service and is all about honing our craft and helping others do the same. He is deeply involved in positive and proactive leadership, while being well versed in VES, forcible entry and an advocate for an aggressive search culture and Engine work.
Bill GustinLecture Series
Bill Gustin is a 48-year veteran of the Fire Service and is a Captain on the Miami-Dade County Fire-Rescue Dept. He began his career in the Chicago area where he was firefighter for 5 years before taking a position with Miami-Dade. He is a lead instructor in Miami-Dade's officer development program and an author and technical editor of Fire Engineering Magazine. He is an instructor at FDIC and conducts training programs throughout the United States and Canada.
Rob RamirezLecture Series
Capt. Rob Ramirez has been a student of the fire service for over 20 years. He is also a Rescue Team Manager for the Dept. of Homeland Security F.E.M.A. U.S.A.R. Florida Task Force 2 since 2006, and has been on many high profile F.E.M.A. U.S.A.R. deployments including the Haiti earthquake of 2010, and Hurricane Katrina. Rob is a lead Fire, Military, and Special Operations Instructor for National Rescue Consultants, an all hazards national training company based out of West Palm Beach Florida. He is a former Coral Spring (Fl.) Fire Academy Instructor, and a founding member of the Firefighter Advanced Survival Techniques program. Rob is the currently the lead Firefighter Survival program Instructor at the annual Fort Lauderdale Fire Expo, an Engine Company (MEGA) Instructor at the Orlando Fire Conference (OFC), and the Metro Atlanta Firefighter Conference (MAFFC). Throughout his fire service career Rob has held the rank of Firefighter, Paramedic, Lieutenant, Dept. Training Officer, and Captain. Rob is currently assigned to the operations division on a busy urban suppression company in Broward County, Florida.
Jimm WalshLecture Series
Leadership & Command Series
Scott ChappellLeadership/Command Series
Scott Chappell is the US&R and Haz Mat Program Coordinator for the State Fire Marshal at the Florida State Fire College. He entered the fire service in 1993 and has been working at the Florida State Fire College since 2000. Scott now coordinates Florida's eight US&R Task Forces, thirty Regional Hazardous Materials Teams, and fifty Technical Rescue Teams, and seven Mutual Aid Radio Cache (MARC) Units. Scott deployed to the State EOC where he operated as US&R Specialist for Hurricanes Hermine and Matthew and as US&R Coordinator for Hurricanes Irma, Michael, and Dorian. Additionally, Scott deployed to the State (FL) Logistics Response Center warehouse where he served as Florida's Deputy Logistics Section Chief during COVID-19. He is a Captain with Marion County Fire Rescue where he serves as the C-Shift District 5 Command Officer, the C-Shift Special Operations Officer, and a Task Force Leader with Florida US&R Task Force 8. Scott has a Bachelor's Degree from the University of Florida, a Master's Degree in Public Administration from Barry University, and is currently enrolled in the Executive Fire Officer Program at the National Fire Academy.
Robert KrauseLeadership/Command Series
Bob Krause, a Battalion Chief in Toledo, Ohio, has over 37 years of experience working in emergency services. He's an active firefighter, fire officer, paramedic, EMS instructor, firefighting instructor, lecturer, researcher and published author. He has held positions as an Engine Company Officer, Fire Training Officer, Fire & EMS Academy Program Director, Fire & EMS Communications Supervisor, Chief of Emergency Medical Services and Emergency Medical Services Educator. Bob is currently assigned to Battalion One, in Toledo's busiest fire district. Dr. Krause's doctoral research focused on firefighter fatalities, identifying common themes, related causes and the development of potential methods to minimize the risk of a fatal incident for firefighters. As an author, Dr. Krause's work has been published in professional journals, magazines and textbooks.
Walter LewisLeadership/Command Series
Walter Lewis has been involved in the fire service since 1990, the last 25 years with the Orlando Fire Department. He presently serves as District 1, in downtown Orlando. Chief Lewis has been involved with instructing and presenting programs at a variety of fire service venues and institutions since 1999, among which have been FDIC and the Orlando Fire Conference and is a continual student of the fire service.
David McGrailLeadership/Command Series
Dave McGrail is a 39-year veteran of the fire service and an Assistant Chief with the Denver Fire Department (DFD) assigned to the Operations Division, District #3. He instructs internationally on a wide range of fire service topics, specializing in high-rise firefighting command and control, and engine company standpipe operations. He is a member of the FDIC Educational Advisory Board and is editorial advisor and contributing editor for Fire Engineering Magazine. He is the author of the book Firefighting Operations in High-rise and Standpipe Equipped Buildings published by PennWell (Fire Engineering Books and Videos) in 2007. Dave holds two Associate of Applied Science Degrees in Fire Science Technology, one with a focus in Fire Suppression, and the other with a focus in Fire Prevention. Dave also holds two Bachelor of Science Degrees, one in Human Resource Management, and the other in Fire Service Administration. Dave is a second-generation firefighter, who was born and raised in Denver, Colorado.
Gerald "Jerry" TracyLeadership/Command Series
Chief Tracy, retired Battalion Commander, having served 31 years with the FDNY. Acknowledged for developing numerous training programs presented at the FDNY academy for all ranks including Chief Officers. Attributes for the revising of many procedural documents for the FDNY. There are numerous articles authored by Chief Tracy and published in the FDNY's training publication WNYF (With New York Firefighters), Fire Engineering and Fire House magazines. Chief Tracy was the catalyst to bring about the live fire research conducted by NIST and NYU Polytechnic Institute to better understand Fire (behavior) Dynamics in High Rise Buildings with emphasis on Wind Impacted Fires. Further research conducted were methods to achieve Smoke Management and Control enhancing the life safety for building occupants. That included stairwell pressurization with portable fans (PPV). He was a keynote speaker at the FDIC conference in 2007, hosted by Fire Engineering Magazine and recipient of the "Tom Brennan Lifetime Achievement Award" in 2016.
Copyright 2002-2021, Orlando Fire Conference. All Rights Reserved.

redpajama_set_name: RedPajamaCommonCrawl


Microsoft has confirmed that the Xbox 360 holiday bundle for the North American market will feature Halo Reach and Fable III this year for the 250GB system. The $299 bundle will also include a wireless controller, wired headset, and three months of Xbox Live for free. From what we understand, Fable III will be included on disc, while Halo Reach will be included as a download token.
For those that want Kinect, Microsoft will also be offering a Kinect bundle this holiday season. The $399 Kinect bundle will feature a 250GB Xbox 360, a single wireless controller, Kinect, wired headset, Kinect Adventures, Carnival Games: Monkey See Monkey Do; and, of course, three months of Xbox Live.
Microsoft is apparently expecting strong sales of consoles this holiday season, but there has been no price drop as many have expected. Analysts tell us that the console is selling well enough at the current price that there is no real reason to drop the price, but sweetening the deal with some add-ins could help move more consoles this holiday season.


text:
Natasha Oughtred is an English ballerina and retired principal dancer with the Birmingham Royal Ballet.

Biography
Natasha Oughtred was born in North Cave, a village near Kingston upon Hull in the East Riding of Yorkshire. She began to study dance at the age of 3 with the Skelton Hooper School of Dance in Hull, under the guidance of the Principal Vanessa Hooper, a former soloist of The Royal Ballet.  She has achieved examination passes with the Royal Academy of Dance and the International Dance Teachers' Association.  She later received additional coaching in ballet from Niall McMahon, a former dancer with the Scottish Ballet and artistic director of New English Contemporary Ballet.  After reaching the semi finals of the prestigious Prix de Lausanne, she received a scholarship to continue her training at the upper school of the Royal Ballet School and joined The Royal Ballet company in 2000, eventually being promoted to the rank of Soloist.  Oughtred joined the Birmingham Royal Ballet as a Soloist in 2007.  She was promoted to First Soloist rank in 2008 and was promoted to the most senior rank of Principal in 2009.

Created roles
 Being and Having Been - Choreographer: Alastair Marriott
 Castle Nowhere - Choreographer: Matjash Mrozewski
 Children of Adam - Choreographer: Alastair Marriott
 Continued - Choreographer: Alastair Marriott
 Frozen - Choreographer: Vanessa Fenton
 Homage to the Queen - Fire - Choreographer: Christopher Wheeldon
 Knots - Choreographer: Vanessa Fenton
 Le Baiser de la Fée - The Fairy's Kiss - Choreographer: Michael Corder
 On Public Display - Choreographer: Vanessa Fenton
 Siren Song - Choreographer: Poppy Ben-David

Repertoire

Royal Ballet
 A Month in the Country - Vera - Choreographer: Sir Frederick Ashton
 La Bayadère - 3rd Solo Shade - Production: Natalia Makarova
 Cinderella - Spring Fairy - Production: Sir Frederick Ashton
 La Fin du Jour - Cerise Couple - Choreographer: Sir Kenneth MacMillan
 Giselle - Moyna - Production: Sir Peter Wright
 Gloria - The Girl - Choreographer: Sir Kenneth MacMillan
 Mayerling - Princess Stephanie and Princess Louise - Choreographer: Sir Kenneth MacMillan
 The Nutcracker - Clara - Choreographer: Sir Peter Wright
 Les Rendezvous - Pas de Trois - Choreographer: Sir Frederick Ashton
 Scenes de Ballet - Spring Fairy - Choreographer: Sir Frederick Ashton
 Sinfonietta - Choreographer: Jirí Kylián
 The Sleeping Beauty - Various Roles - Production: Dame Monica Mason and Christopher Newton
 The Sleeping Beauty - Various Roles - Production: Natalia Makarova
 Swan Lake - Pas de Trois - Production: Sir Anthony Dowell
 La Sylphide - Pas de Deux - Choreographer: August Bournonville
 The Vertiginous Thrill of Exactitude - Choreographer: William Forsythe

Birmingham Royal Ballet
 Card Game - Two of Diamonds - Choreographer: John Cranko
 Concerto Barocco - Choreographer: George Balanchine
 Coppélia - Prayer - Choreographer: Sir Peter Wright
 Daphnis and Chloë - Chloë - Choreographer: Sir Frederick Ashton
 Giselle - Harvest - Choreography: David Bintley and Galina Samsova
 The Nutcracker - Sugar Plum Fairy & Rose Fairy - Choreographer: Sir Peter Wright
 Paquita - Fourth Solo - Choreographer: Marius Petipa
 The Shakespeare Suite - Juliet - Choreographer: David Bintley
 Swan Lake - Odette/Odile - Choreography: Sir Peter Wright and Galina Samsova
 Take Five - Three to Get Ready - Choreographer: David Bintley

Awards
 2000 - Genée International Ballet Competition - Royal Academy of Dance - Silver Medal

References

Living people
People educated at the Royal Ballet School
English ballerinas
People from Kingston upon Hull
Dancers of The Royal Ballet
Birmingham Royal Ballet principal dancers
Year of birth missing (living people)


text:
Maps About Nothing. A global guide to Seinfeld.
It's a Seinfeld reality tour on steroids.
Maps About Comedians In Cars Getting Coffee
A World Of Nothing
← The Suicide
The Maid →
May 14, 2013 Seinfeld Season 7	Leave a comment
The Hot Tub
by Master Of This Domain
The Hot Tub (season 7, episode 5)
written by Gregg Kavet & Andy Robin, directed by Andy Ackerman
original airdate: October 19, 1995
Elaine hosts Jean-Paul for the NYC marathon. He has a history of oversleeping, so Jerry fixates on ensuring he's up in time for the race. Kramer installs a hot tub in his living room.
The Improv
Jerry's Apartment
Jerry ends up hosting Jean-Paul, after he is booted from Elaine's apartment the night before the marathon. Kramer's hot tub, however, blows power to the building, causing Jean-Paul to once again oversleep.
Monk's Café
Elaine tells the gang that Jean-Paul is staying with her, getting pressure from Jerry to ensure he is woken up with a proper alarm clock. George tells Jerry his trick to always looking busy, and then shares his new Astros vernacular with the gang.
NORWAY (map)
One of the products George reads about in the Peterman catalog is the Norwegian ice-fishing vest.
Pendant Publishing
Elaine mentions she met Jean-Paul while editing a book on running while at Pendant.
TRINIDAD AND TOBAGO (map)
Elaine hosts Jean-Paul, a Trinidadian runner in town for the New York Marathon. According to Elaine, he's "Trinidadian and Toboggan."
Estadi Olímpic de Montjuïc (now Estadi Olímpic Lluís Companys)
Passeig Olímpic 17, Barcelona, SPAIN (map)
Jerry mentions how Jean-Paul famously overslept at the Olympics four years earlier and missed the marathon. Jerry claims if he had been with him in Barcelona, "you'd be polishing that gold medal right now" (there were no actual competitors from Trinidad And Tobago in men's or women's marathon at the 1992 Summer Olympics).
George is penned a rage-a-holic by Mr. Wilhelm, giving him the Houston Astros assignment. George is eventually made to soak in a hot tub with Mr. Steinbrenner to "relieve" his tension.
Kramer's Apartment
Kramer installs a hot tub in his apartment, which knocks out the power throughout the whole building.
Cleveland, OHIO (map)
Jerry remembers once missing a flight to Cleveland because of Elaine's shoddy alarm clock, out of concern for Jean-Paul.
Houston, TEXAS (map)
George hosts team representatives flying in from the Houston Astros organization, to discuss interleague play against the Yankees.
SWEDEN (map)
Kramer remarks how he opens up all the windows in his apartment, so its freezing cold, while the hot tub is boiling hot…"it's like Sweden…Sweeeeden!"
Fitzpatrick's
1641 Second Ave., New York, NEW YORK (map)
nearest subway: 86th Street (4,5,6)
George takes out those "bastards" and "sons of bitches" from the Houston Astros organization out to the bar.
J. Peterman
Elaine has "catalouge writer's block" coming up with copy for the Himalayan walking shoe, in her first appearance working at the Peterman catalogue.
Himalayas Mountains, ASIA (map)
Elaine spends the duration of the episode struggling to write copy for a new Peterman catalogue item, the Himalayan walking shoe. The Himalayan mountain range spreads across five Asian countries (Bhutan, China, India, Nepal and Pakistan).
Timbuktu, MALI (map)
Elaine starts off her Himalayan Walking Shoe copy with "it was a cold winter's night in Timbuktu."
Elaine's Apartment
Marathon runner Jean-Paul stays with Elaine, but ends up with Jerry when he spots a bastard child and inadvertently harasses the mother about it.
Bedford Hotel (NOW CLOSED)
118 E. 40th St., New York, NEW YORK (map)
nearest subway: Grand Central – 42nd Street (4,5,6,7)
Jerry checks Jean-Paul in here to get a good night's sleep (and a guaranteed alarm clock), but takes him back to his apartment when he supposedly upsets the wake-up call guy and fears the wake-up will never come.
Jungfrau Railway
Bernese Oberland, SWITZERLAND (map)
Kramer has a poster over his bed of the Jungfrau Railway in the Bernese Oberland.
CANADA (map)
A large Canadian flag is clearly seen amongst the crowd at the start of the New York Marathon. Kramer is also shown to have a poster in his apartment from the Canadian National Railway, reading "Snow Time is Playtime in Canada."
Verranzo-Narrows Bridge
Staten Island, NEW YORK (map)
Jerry drops off Jean-Paul here at the start of the race, the starting point each year for the New York Marathon. Jean-Paul runs the Marathon, and is en route to victory when Kramer accidentally hands him coffee, which he throws on his face and burns himself.
NEW JERSEY (map)
Mr. Steinbrenner tells George that when he used to get angry, he would tell people he was moving the team to New Jersey "just to upset people."
Put it in the vault! Cancel reply
When you don't care, that indifference makes you attractive.
Send us praise, hate, yada yada...
mapsaboutnothing@gmail.com


Berkeley's new Dharma College will open its doors to students this fall as an educational center dedicated to bringing together seekers and thinkers, scientists, humanists, and spiritual leaders from throughout the Bay Area and around the world to explore the nature of the human mind and its transformative potential. Its classes are open to the general public and are welcoming to adults of all backgrounds and beliefs.
Inaugural six-week courses begin October 3 and run through November 10, 2012. Dharma College courses will encourage individuals to explore and develop their inner resources and to awaken a more positive way to experience the world.
Dharma College and its sister downtown organizations were founded by Tibetan Buddhist Lama Tarthang Tulku Rinpoche, a refugee who fled his homeland in 1959 and settled in Berkeley in 1969.
A fullytrained Master Teacher in the Nyingma lineage of Tibetan Buddhism and author of over two-dozen books, he has devoted his lifelong efforts to preserving Tibetan Buddhist culture and bringing its profound teachings to the West. Since 1978, he has been on permanent retreat at Odiyan, a monastery in Sonoma County.


We're continuously looking for can-do, enthusiastic people with a sense of fun and a clear and confident point of view. We hire the best talent, irrespective of difference; the difference, that in fact enriches C'arch as a practice. Adaptability, curiosity and energy are essential. If you want to be part of something special, we'd love to hear from you.
Are you an architecture student looking for hands on experience in an award-winning architecture and design office? Are you excited about assisting on exciting projects? Are you keen to learn on the job and develop your skills alongside your studies?
This is a great chance to enhance your studies, boost your CV, and work with a fantastic team who are keen to develop your talents. You will receive regular feedback and have access to mentoring, internal and external training and great on-the-job learning opportunities. Please get in touch and tell us what you want to achieve. We'd love to hear from you.


Exact words I said when I saw this... "Woah.." And the I was speechless.
Yeah, saw that one in the store and was about to try it on until I saw that price tag. My next thought? I bet Kayla could make one like it.
I love this! I could totally see you in that too. It's so pretty!


Our graduates give you undoubtable reasons to believe in the benefits of studying Biomedical Engineering at Makerere University. This section is dedicated to some of the most iconic, exemplary, and hardworking students of the association. They empower the continuing Biomedical Engineering students to believe and count on every effort put towards achieving the course objectives. We pride in the support offered by distinguished MUBESA alumni, ranging from financial donations, practical support and career guidance to continuing students.
It is for these reasons that any alumni is always encouraged to share their knowledge and experience with students whenever given the opportunity. MUBESA alumni meet regularly at workshops, conferences or places of work, where they share information from both a student and professionals' point of view. This is a stepping-stone towards achieving sustainable professional networks once students graduate.


text:
Updated on: Wednesday, December 08, 2021, 07:43 PM IST
Hero Electric clocks sales of over 7,000 EV two-wheeler units in November
Given the surge for EVs, the company is working to meet the rising demand and are hopeful to end the year on a high note, he added. / Representative Image | File pic
Hero Electric on Wednesday said it sold over 7,000 electric two-wheelers in the country last month. The company said it had sold 1,169 units in the corresponding period last year.
''At Hero, we have been steering EV (electric vehicle) adoption in India and are witnessing stronger consumer confidence towards electric mobility solutions.
''The government initiatives and customer-friendly policies have continued to drive demand for the category, translating into positive sales momentum,'' Hero Electric CEO Sohinder Gill said in a statement.
Given the surge for EVs, the company is working to meet the rising demand and are hopeful to end the year on a high note, he added.
Published on: Wednesday, December 08, 2021, 07:42 PM IST
EV two-wheeler units in November


The FINANCIAL -- From bio-based shells to wood-fiber jeans, outdoor industry brands continue to prioritize sustainable manufacturing and product design. And it's all on display at this year's Outdoor Retailer Snow Show 2019.
As outdoor recreation becomes increasingly mainstream, so too do sustainability initiatives that aim to preserve our wild spaces. For example, we reported on the outdoor education programs at Utah State University, Western State Colorado University, and the University of Oregon. These degrees require sustainability-specific courses as prerequisites.
And last year, the industry released its first-ever sustainability report. That benchmark, published by the Outdoor Industry Association, is based on a decade of data and will help brands prioritize future eco-related investment.
This week, we'll hear the word "sustainable" a lot and see products that fall somewhere on the eco-friendly spectrum. Here are five new products for 2019 that push forward industry standards and will be at the Outdoor Retailer Snow Show.
Using recycled materials to create technical apparel has its own hurdles. This year, Patagonia will be the first company in the outdoor industry to manufacture all of its shells — 62 jackets total— with 100 percent recycled materials.
Among the line, the Ascensionist Jacket is intended for light, fast movement in the mountains. It's Patagonia's lightest-weight Gore-Tex product to date. The three-layer jacket weighs 13 ounces and uses a 30-denier nylon face fabric that took two years to develop.
Furthermore, the entire lineup of jackets, coined the Responsible Shell Collection, will be sewn in Fair Trade Certified Factories.
"Creating a [new] standard takes time, commitment, and collaboration between brands and factories to accomplish. Since 2014, we have been working towards making each of our finished good factories Fair Trade Certified … The good news is, once a factory is Fair Trade Certified, any company can have their products certified as well by paying a premium to the factory" - said Corey Simpson, Patagonia's PR and communications coordinator.
Shoppers can find the Ascensionist Jacket in August online, at Patagonia retail stores, and wholesale stores nationwide.
"To make the world's most sustainable shoe, SOLE and United By Blue had to collect, engineer and create natural, sustainable materials that simply weren't available on the market," said Zachary Osness, VP of global sales and merchandising for SOLE.
Introducing the Jasper Wool Eco Chukka, a collaborative design that tells a sustainability story in all facets.
SOLE created the chukka's midsole with ReCORK — made entirely from post-consumer recycled wine cork. Meanwhile, the insulation uses BisonShield: a breathable, hypoallergenic material made from the hollow-fiber hair of bison and recycled polyester. That alone took United By Blue five years to create.
Finally, the shoe's upper comprises 80 percent merino wool, the outsole is made out of rice, and the insole comes from BLOOM Foam Algae.
Picture Organic Clothing is an eco-based brand dedicated to producing gear made from a minimum of 50 percent recycled or bio-based materials.
This fall, Picture will debut the Harvest Jacket along with the brand's first partially bio-based membrane: Pebax Renew.
"We know that [bio-based] technology is just as durable and waterproof-breathable as the petroleum-based membranes on the market," explained Jeremy Rochette, Picture's co-founder and head of design.
Pebax Renew originates as oil derived from castor seeds. The new membrane replaces petroleum-made synthetic fibers. In fact, Maro LaBlance of Campfire Collective told us that castor oil predated petroleum for use in textiles, going back to the 1950s.
Picture advertises the Harvest as a lightweight jacket with a solid 20K/20K waterproof-breathable rating for skiers and riders. And the knit-constructed side panels will help dump heat during high activity.
Folks can find the jacket in September 2019.
Jack Wolfskin will expand its Texapore Ecosphere recycled collection — the world's first 100 percent recycled apparel line — at OR. The Big White Jacket features an outer fabric, waterproof membrane, lining, and insulation that are all made from recycled materials.
The Big White Jacket is also 100 percent PFC-free. In fact, the jacket's zippers, pull-tabs, and labels are the only components that are not recycled … yet. Jack Wolfskin said it's already working on recycled alternatives for those as well.
With tops and feet covered, all that remains are the legs. Enter reDEW Frost Jeans: the first jeans to be developed with handmade, renewable fibers. The denim fabric actually comes from sustainably grown wood.
"They look, feel, and wear exactly like your favorite denim jeans, but without the environmental impacts of cotton," the brand told us. In fact, reDEW advertises that each pair saves more than 7,000 liters (1,850 gallons) of water compared to the process of creating a classic pair of jeans.


text:
Walmart Goodies: retail giant goes gourmet
Walmart has launched Goodies, a monthly food service that delivers boxes of gourmet food samples to subscribers for the Walmart-cheap price of $7 per month. Can Goodies help Walmart attract a new customer base?
Wal-Mart/AP
This still frame made from an undated video advertisement provided by Wal-Mart Stores Inc., shows the logo for the company's new mail subscription service, Goodies. The program will officially launch on Wednesday, Nov. 14, 2012. For a monthly fee of $7 that includes tax and shipping, customers get a box of five to eight sample-size food items, ranging from organic to ethnic products that are not currently carried on Walmart shelves.
By Schuyler Velasco Correspondent
"Gourmet" and "artisan" are probably not the first words that come to mind when you see a Walmart logo. But Walmart is trying to change that.
The world's largest retailer is jumping into the gourmet game with "Goodies," a service that delivers monthly subscribers samplings of high-end snacks. November's "Easy Entertainment"-themed offering features white cheddar popcorn, chocolate soufflé mix, and pumpkin pie spice tea, among others. Like any food-of-the-month club, subscribers don't know what they're getting until it shows up at their address. The products are not sold at Walmart stores.
"For only $7 a month, including tax and shipping, subscribers receive a gift box at their doorstep filled with five to eight hand-picked taster samples ranging from healthy and organic to artisan and ethnic," Walmart said in a statement Wednesday. "The new Goodies Co. box underscores Walmart's commitment to e-commerce and its use of social innovations to create new offerings for consumers."
Goodies has been in beta testing for a few months, and now has over 3,000 subscribers, according to the company.
Safe to say, Walmart is the last place most foodies think of to try new, high quality food products. But the retailer's big advantage (typically) is price: "Unlike current offerings, Goodies Co. is the first to offer a large assortment of products for a total price that is almost half of the total value of the items if they were purchased separately," the Walmart release says. "The total price for all of the items in the November box would be approximately $15 compared to the Goodies Co. $7 price."
The products are sample size, but subscribers can purchase full portions of the products they like at the Goodies website, www.goodies.co, and post reviews and redeem loyalty points toward future Goodies purchases.
The service also doubles as a bit of paid market testing for the retailer: Ravi Raj, vice president of products at Walmart Labs, told CNNMoney that the more popular products have a good chance at eventually being offered in Walmart stores.
Walmart's main selling point as a shopping destination has long been price, often at the cost of quality and appearances. Goodies is the company's latest effort to try and change that image and attract a new set of tech savvy, conscientious (and probably younger) customers. The company has been touting efforts to offer more organic, locally grown grocery items for years and has launched a number of efforts to increase its online footprint. Last year's holiday season brought Shopycat, a social media app that uses Facebook to recommend gifts. This year's Black Friday ad includes deals on Apple products including the iPad 2 and iPod Touch.
It's unclear whether or not Walmart can balance attracting those new customers with its prevailing status as the place for the best deals, but as the largest and most profitable retailer in the world (pulling in $447 billion in global revenue last year), it has some room to experiment.
Test your knowledge Are you a smart shopper? Take our quiz.
International Women's Day: Meet the 10 richest women
10 weirdest global fast foods


124 5777 Birney Avenue, Vancouver - 1 bed, 1 bath - For Sale | Regent Park Realty Inc.
Welcome to Pathways by Adera at UBC! Quality concrete built one bedroom + Den unit with a huge East facing private patio adjoining the tranquil and serene garden courtyard. This great quality and excellent designed is more like a Townhouse! Natural setting with fantastic over 300 sqft patio and exterior entry from the private patio. Very functional layout, well-maintained, over height ceilings, caesar stone countertops and high end stainless steal appliances. Plus 1 parking and 1 storage locker. Steps to Save on Foods, cafes, shops and restaurants. Great investment or Move in before the Fall semester starts! Don't miss the opportunity. It won't last!


text:
Five Things I Saw & Heard This Week
Transcripts from the everyday world of music by Martin Colyer
You are here: Home / Weekly Roundup / Five Things, Wednesday 7th August
Five Things, Wednesday 7th August
August 7, 2014 by martin colyer 4 Comments
"She's all I got is gone": David Bromberg & Larry Campbell at Bush Hall
After a vivid ride through London on the back of Kevin's motorbike (a big BMW, as used by the Met, for all you bike fans) we turn up at Bush Hall to see Dylan sidemen from different eras making a joyous noise – two performers who really love playing together, picking songs that they've probably played forever. Yes, there are plenty of phenomenal guitarists out there, but often they're players whose virtuosity is almost a barrier to connection. That's not the case here. This was a conversation between erudite practitioners who transmuted the pleasure they find in playing into the audience's unalloyed enjoyment.
Towering over all the risqué blues songs (Bromberg's speciality) and the transposed Irish and Texan fiddle tunes (Larry's bag) is a performance of "Delia" that is just hypnotic. For ten minutes, Bromberg sings and recounts the origins of the song against honeyed and stately tick-tock fingerpicking, while Campbell embellishes the tune with a swooping, swooning accompaniment on the bottleneck, finding beautiful, piercing melodies for as long as the song takes to wend its way to the last sigh. And every verse ends with the sad and resigned statement above, sing/spoken in the most poignant fashion. I'd a been happy if it had lasted twice as long.
Autopsy: Karen Carpenter, Channel 5
Alternately fascinating and grim (with actors playing Karen, Richard and their parents) as only programmes called Autopsy can be, this peculiarly tragic episode piled up the evidence for a recovery from anorexia, only for her to be failed by a pitifully weakened heart. My friend Andrew and I saw the Carpenters play a midnight show at the London Palladium in 1976 (yes, '76, the year of Punk). It was in aid of Capital Radio's Help a London Child, and you had to queue at Capital's HQ at Euston Tower at seven in the morning. With a soft toy. So we did. The show was great – Richard's dreadful vaudeville numbers, Karen's drum solo and all. Tony Pelusi ripped out the classic guitar solo on "Goodbye to Love", and Karen sang like she always did, trying to keep that melancholy tear at the edge of her voice at bay.
Bolt Dances to The Proclaimers, Hampden Park
And sets off a string of memories: I first saw The Proclaimers, as did most of Britain, when they appeared on The Tube. Our band was on that Friday, too, along with the Psychedelic Furs. We had travelled up to Newcastle, where the studios of Tyne Tees were, on the Quayside, and my day had already been made by the sight of Bobby Charlton being signed in at Reception. I remember two things well from the show. One was talking to Mars Williams, sax player for the Furs, and interesting to me as he had been a member of The Waitresses. They were a band I loved, for its mixture of Patty Donahue's knowing sarcasm and the NY new wave of Chris Butler's songs (songs with titles like "They're All Out Of Liquor, Let's Find Another Party" and "I Could Rule the World If I Could Only Get the Parts"). I tended to buy anything that I could find on their label, Ze Records. Among their bizarre acts (Mutant Disco became the quick catch-all for what their releases sounded like) was an early version of Lana Del Ray who went by the name of Cristina ("Is That All There Is?" is still a masterpiece) and the stunning Material (including Bill Laswell and Fred Maher) whose "Busting Out", with Nona Hendryx singing, you really need to hear. This a nice piece about The Waitresses… I Know what Girls like: The Waitresses and the limits of the "Female-Fronted Band by Lindsay Zoladz on Pitchfork.
The other thing I remember was being intrigued by The Proclaimers' Buddy Holly-like appearance and the closeness of their singing, like one voice with two sides. I told them they were great and would go far, one of the rare occasions that I was right. I loved seeing the Commonwealth Games audience singing "I'm Gonna Be (500 Miles)" as Usain Bolt shook down his arms, then threw out the pointed finger a few times before miming walking as the crowd hit the chorus. Then he conducted the spectators for a bit before going into the "Pulp Fiction Eyes". I'm not sure he would have remained so loose if he'd been about to run his banner event, the 100 metres, but here he allows himself to be enticed by the crowd's reaction…
Dennis Hopper, The Lost Album, Royal Academy
Richard Williams writes so well about this exhibition (and the use of The Band's "The Weight" here) that I'm not sure that I can add anything much. Oh, except that my problem with exhibitions of photography are often about sizing. 400 10×8 prints is a lot to look at, and there's too much here that is run-of-the-mill. The good ones deserve better printing to bring out the shadow detail, and sometimes more scale would be a good thing: Double Standard works well as a huge poster at the entrance, but its charms are lessened as a 10×8, where it looks a poor cousin to a Friedlander, Winogrand or Frank shot (above: the blow up/an introductory caption/watching a loop of Easy Rider from the balcony.) By the cafe is a small temporary screening room where Easy Rider and The Last Movie are shown a couple of times a day. I caught the last thirty minutes of Easy Rider, which looks pretty dated but is carried by its fervour – it feels like something that Fonda and Hopper needed to make, and not a studio product. I remembered that a cover version of "The Weight" was used on the soundtrack album, but had forgotten that "It's Alright, Ma" – a song that eloquently addresses some of the film's concerns – is used at the end. Sadly it's a woefully lackluster version by Roger McGuinn, and just proves that it's one of those Bob songs that should never be covered.
Upon leaving the Royal Academy, this "Jazz" sweater caught my eye in Burlington Arcade. The word we're looking for is "why".
Filed Under: Weekly Roundup Tagged With: Bob Dylan, Dennis Hopper, Karen Carpenter, Lindsay Zoladz, Patty Donahue, Royal Academy, The Lost Album, The Proclaimers, The Waitresses, Usain Bolt
« Five Things, Wednesday 30th July
Five Things, Wednesday 13th August »
John Savage says:
Thanks for the review of Dave Bromberg and Larry Campbell. We were lucky enough to see them last week at the Victory Hall a lovely little village theatre in Thorner Yorkshire. Absolutely terrific show from beginning to end. Their first in the UK as a duo. The version of Delia was a particular highlight, and the story surrounding it. For further reading on this I can recommend the Sean Wilentz book "Bob Dylan in America".
martin colyer says:
Thanks, John, I've never got round to getting that, but will now…
Dave Heasman says:
"Cristina" was Christina Monet, wife of the label's owner Michael Zilka. I have her first LP in the attic I thought I had a Ze compilation with a dynamite Material track and an odd one by Alan Vega, but it seems that was on Celluloid, which was an associated label. Oh well.
Yes, you're right, Dave. The second LP was pretty wild, and includes a cover of Prince's "When You Were Mine". And, according to an interview done in 2004, "I don't think Sleep It Off sounds dated, because it's so out there," Cristina says. "It never fit in any frame, and it still doesn't." Unfortunately, the record was so ahead of its time that it flopped; defeated, the singer retired. "I believed the idea that Michael had bought me a career to such an extent that I felt sheepish and guilty, which I shouldn't have been," she says. "By that point I was a wife and a mother, and then we moved to Texas; I felt like Madame Bovary of the freeway." The following two decades were low-key. Cristina divorced Zilkha in 1990 and returned to New York, where she still lives. A nimble writer, she's contributed learned essays and reviews to publications such as London's Times Literary Supplement. Great line, Madame Bovary of the Freeway…
Leave a Reply to martin colyer Cancel reply
Songs for dark days
Freedom For The Stallion [Live]
13th Century Metal
"They've got men building fences to keep other men out / Ignore him if he whispers and kill him if he shouts."
Two live recordings of songs about freedom and harmony that popped up together on a random playlist yesterday. Toussaint's reading of the exquisite "Freedom for the Stallion" has his superlative piano playing – part gospel, part New Orleans, mixed up with that ethereal Southern Nights ambience, where beautifully stretched melodies play out…
That's followed by Brittany Howard playing the extraordinary "13th Century Metal" live at KCRW in L.A. last month. There's a singularity to Howard – her take on life is so artful and strong. "We are all brothers and sisters, I learned that as a child, it's a simple concept to grasp…" she intones over a smorgasbord of funk laid down by her crackshot band.
Follow FTIS&HTW via Email
Enter your email address and follow FTIS&HTW. You'll receive a weekly notification by email.
About Martin/Five Things Book/Discount Fireworks CD
Buy Five Things – the book!
Order Discount Fireworks here!
Subjects Covered, by Tags
Adele Aimee Mann Allen Toussaint Amanda Petrusich Amy Winehouse Another Self Portrait Aretha Franklin Barbican Barney Hoskyns Bill Colyer Bill Frisell Bob Dylan Bonnie Raitt Brett Mielke Bruce Springsteen Christies David Bowie David Remnick Desert Island Discs Eddie Hinton Every Record Tells a Story Hot House Inside Llewyn Davis Janis Joplin JazzWax Joe Boyd John Cuneo Joni MItchell Jonny Hannah Jonny Trunk Kanye West Ken Colyer Later Laura Barton Leonard Cohen Levon Helm likeahammerinthesink London Jazz Collector Lorde Marc Myers Martin Colyer Mavis Staples Michael Gray Mick Gold Miles Davis Muddy Waters music Music Documentaries Neil Young New Yorker Nina Simone Prince Richard Williams rick danko Robbie Fulks Robbie Robertson rocksbackpages.com Rolling Stone Magazine Ry Cooder Sam Amidon Sam Charters Sammy Rimington Shortlist Steely Dan Stephen Collins Steve Miller Studio 51 St Vincent The Band thebluemoment.com The Guardian The New Yorker Tom Jones US Esquire Van Morrison
Archives Select Month December 2019 November 2019 September 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 September 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 December 2017 November 2017 October 2017 September 2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 February 2017 January 2017 December 2016 November 2016 October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015 November 2015 October 2015 September 2015 August 2015 July 2015 June 2015 May 2015 April 2015 March 2015 February 2015 January 2015 December 2014 November 2014 October 2014 September 2014 August 2014 July 2014 June 2014 May 2014 April 2014 March 2014 February 2014 January 2014 December 2013 November 2013 October 2013 September 2013 August 2013 July 2013 June 2013 May 2013 April 2013 March 2013 February 2013 January 2013 December 2012 November 2012 October 2012 September 2012 August 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012