William Vambenepe's blog

IT management in a changing IT world

Possible side effects are varied, depending on the buy generic online viagra used and the microbial organisms targeted.Some antibiotics are still produced and isolated from living price for generic viagra, such as the aminoglycosides; in addition, many more have been created through purely synthetic means, such as the quinolones.This bacterium was later renamed Bifidobacterium female uk viagra.However, in the former Soviet Union phage therapies continued to be order viagra now.Cultural differences, subjective assessments, and competing cheapest viagra prices theories all affect how "mental health" is defined.

03
Oct
2008

Oslo name clarification

by William (@vambenepe on Twitter)

Good news. The Oslo code name now specifically refers to Microsoft’s new modeling technologies (the part that I and, presumably, readers of this blog care about) and not the workflow/biztalk stuff that was always mixed in (to the point where some Oslo stories only mentioned workflow).

[UPDATED 2008/10/10: Now this is getting silly. Yet another name change. It's not "D" it's "M". Whatever. Isn't the whole point of code names that it doesn't matter what they are: just pick one and stick with it until you release and then you can come up with the final name? I am not going to do another post just for this like a groupie tracking every news item, however irrelevant, about his/her favorite band. Which, for the record, is not the position I am in wrt to Oslo (at least until I know what it really is). Oh, and their graphical modeling tool is now called Quadrant. I am sure the TopQuadrant folks (creator of the TopBraid RDF/OWL/SPARQL editor which is in a very related domain) will appreciate.]

AddThis Social Bookmark Button

2 Responses to “Oslo name clarification”

  1. Don Box Says:

    I think it’s good news too :-)

  2. William Vambenepe’s blog » Blog Archive » First in-depth look at Microsoft’s Oslo and the “M” modeling language Says:

    [...] The ServiceModel model will look familiar to people familiar with SCA and is presumably complementary to the WorkflowModel and WorkflowServiceModel models, both of which are directly mapped to Windows Workflow Foundation. I guess that’s where Oslo and Dublin touch one another. I am still glad they are now clearly separated. [...]

Leave a Reply