text:
Green-powered catamaran prepares for 6-year journey around the world
Alex Hernandez | January 23, 2017 January 23, 2017
Two Frenchmen have an ambitious plan to sail a green-powered catamaran around the world for the next 6 years. The catamaran will be powered by sun, wind, and hydrogen energy. Outfitted with solar panels, wind turbines and a hydrogen fuel cell, the pair hope that's all it will take to make the journey. The goal of the journey is to prove that green energy is a viable solution for transportation and many other applications.
The former race boat was created by a team of architects, engineers, and navigators, aiming for autonomy with a mixture of natural energy and the decarbonised production of hydrogen from sea water. The team believes the largest challenge faced in the 21st century is producing energy at a lower cost and carbon-free manner. this research and development is central to the 'energy observer' project, to demonstrate the performance of this new energy model, and thus serve as an example throughout the world.
Alternative green energy is a growing field of research as we seek to find a way to supplement our way off fossil fuels. There's probably a lot of research yet to come and we're hoping much of it points to a viable large-scale solution. The argument over green energy and fossil fuel energy often gets mired in political goo as researchers and companies battle over dollars. Though at some point, I would think the arguments will finally come to a promising understanding of the need to find new energy avenues.
What do you think of this catamaran project? Do you think these guys will be successful? Let us know your thoughts and comments below or hit us up on Twitter, Facebook, and Google+.
[button link="http://www.designboom.com/technology/sun-wind-hydrogen-energy-observer-boat-01-23-2017/" icon="fa-external-link" side="left" target="blank" color="285b5e" textcolor="ffffff"]Source: Designboom[/button]
Last Updated on January 23, 2017.
Tags boat, catamaran, green energy, sailing, technology
Samsung Galaxy S8 may be delayed after Note7 investigation results
Google Voice apps finally get significant updates


text:
Home » Latest Blogs » Internazionali BNL d'Italia: Top Five Matches
You can grab these matches on demand in full now, or select 'Add to MY CHANNEL' to watch whenever you want on any device!
5. Gustavo Kuerten v Juan Carlos Ferrero (2001, Final)
Kuerten had long been the undisputed king of clay, but a young Juan Carlos Ferrero seemed a genuine threat to his crown. The Spaniard had not dropped a set on his way to his first Masters final and was now 17-1 for the year on clay. He had also pushed the world No.1 all the way in the semi-finals of Roland Garros the previous year. A year the wiser, could the young pretender do it?
4. Andy Murray v Novak Djokovic (2011, Semi-Final)
Djokovic was on an astonishing 37-match unbeaten run going into this semi-final. Murray, meanwhile, was on the hunt for his first clay court final and was enjoying a pretty formidable start to the year too, although a chastening straight sets defeat to the Serb in the final of Melbourne had derailed his early hard court season. There was nothing between the pair in this one though: three hours of stunning baseline tennis with barely any errors. Djokovic was in for the biggest challenge to his unbeaten run yet.
3. Rafael Nadal v Guillermo Coria (2005, Final)
Nadal had won four clay court events on the spin, including Monte Carlo where he had defeated Coria in four sets in the final. The Argentine had been a mainstay of the top 10 since 2003 and had picked up six clay court titles in that time, including Masters in Monte Carlo and Hamburg. Even for the precocious Nadal, he was a force to be reckoned with – and so it proved. A five-hour epic and one of the best finals Rome has ever seen.
2. Novak Djokovic v Juan Martin Del Potro (2019, Quarter-Final)
Del Potro had played only four matches in 2019 heading into Rome. Straight-sets victories over David Goffin and Casper Ruud were promising, but then came this show-stopper against the world number one. Both players at their very best in front of a packed Campo Centrale – it simply does not get better than this.
1. Roger Federer v Rafael Nadal (2006, Final)
It has been called the match that cemented the pair's rivalry. Nadal had won four of their five previous meetings and here was looking to extend his win-streak on clay to an astonishing 53 to tie with Villas's open era record set in 1977. But Federer had played some scintillating all-court tennis that week and brought his very best here. Would it be enough?

redpajama_set_name: RedPajamaCommonCrawl


Transform text into a path and apply a brush present to a path.
Use a thin, hand-drawn font. Size: 175 pts.
In the layers panel right click on the text layer and select 'Create Work Path'.
Grab brush tool and select the Dune Glass brush (single blade).
Grab the pen tool and right click on the visible text path.
Choose the 'Stoke Path' option.
In the dialogue box select brush and turn 'Simulate Pressure' on.
Go back to the brush tool.
Change the brush setting scatter value to 300%.
Outer Glow: Blend mode: Linear Dodge, Opacity: 50%, Size: 250, color: ff6d6d, Range: 30%.
Grab brush tool and select the 70 Pxl Star brush.
Scattering: Scatter: 100%, Count: 4.
Press enter to apply the brush.
Apply a few more time, then increase Scattering and apply some more.
Outer Glow: Blend mode: Linear Dodge, Opacity: 75%, Size: 20, color: ff6c00.
00:05 Howard Pinski here with my first tutorial of the new year.
00:12 you may be looking for a way to create your own.
00:14 And what better way to create them in Photoshop.
00:19 layer styles to create this fireworks text effect.
00:22 Let's get to it.
00:32 feel free to use an image of your own for this tutorial.
00:36 which is going to end up as the path that our brush will use.
00:40 For a design like this, a very thin hand-drawn font will work nicely.
00:44 I found this second lyrics font over at dafont.com.
00:49 I'm gonna be using a font size of around 175 points.
00:55 smaller font depending on the size of your image.
00:58 I'm also gonna be increasing the tracking for this font just a touch.
01:01 If I open up my Character panel, which I can activate under the Window menu.
01:08 increasing the tracking value.
01:11 100 should do the trick.
01:13 Now that our text is typed out, we need to create a work path from this type layer.
01:17 This will allow us to paint along a path, once our brushes are set up.
01:24 choose the Create Work Path option towards the top.
01:27 You should see the path become visible around the type.
01:33 Cmd+Shift+H on the Mac or Ctrl+Shift+H on Windows.
01:37 That will hide or show that path.
01:40 hide the Type layer itself, as we're not gonna be using it for this design.
01:44 Now let's go ahead and start customizing some brushes.
01:50 then grab your brush tool from the Tools bar.
01:56 brushes that come with Photoshop.
01:59 the first brush that we're gonna start with will be the Dune Grass Brush.
02:03 Make sure to select the one that contains a single blade and not three.
02:08 which can be done in the Brush panel, found again, under the Window menu.
02:15 decrease the size of the brush until it's about the same thickness as the text.
02:21 around forty pixels will work for this example.
02:29 This will give us some nice variations to the brush as it's being applied.
02:33 Finally, set the control at the top to pen pressure.
02:39 this will allow the brush to fade out at the beginning and the end of the stroke.
02:45 we're gonna start with a scatter set to around 100% and the count set to four.
02:51 we're gonna be increasing the scatter to add some extra sparks around the text.
02:58 turn off Color Dynamics on the left.
03:01 Now we can apply the first brushstroke to our path.
03:07 then right-click on the Visible Path and then choose the Stroke Path option.
03:16 turn Simulate Pressure on.
03:18 This will use the pen pressure control that we set a moment ago.
03:21 When you press OK, the first brush stroke will be made.
03:26 you don't need to follow these steps all over again.
03:31 shortcut key B, and then press the Return or Enter key on your keyboard.
03:36 Now we'll repeat the stroke path command with the settings that you just set.
03:42 I'm gonna increase the scatter value to around 300%.
03:44 And one more time, press Return or Enter on the keyboard.
03:49 To finish off this layer, let's go ahead and add a simple outer glow layer style.
03:53 For this layer, I'm gonna set the blend mode to linear dodge.
03:56 With a 50% Opacity, and a light red color FF6D6D.
04:01 Of course, you can use whichever color you like for your fireworks.
04:07 Now down below, I'm gonna crank up the size to 250 pixels.
04:11 And decrease the range to around 30%.
04:13 This glow will act as the glow that goes behind the fireworks.
04:17 Our next layer will be much stronger.
04:19 So now that this layer is complete, go ahead and create another new layer.
04:23 And open up your brush picker once again.
04:26 the 70 pixel star brush which conveniently is right beside our grass brush.
04:36 the spacing of this brush to around 50% so they're not all clumped up together.
04:44 should automatically appear once you activate it.
04:49 make sure that the control is set to pen pressure.
04:52 Finally, turn on scattering, but leave the settings as they are for the moment.
04:56 One hundred percent for the scatter and four for the count.
04:59 And just like before we need to stroke the path.
05:05 Enter to apply the brush.
05:10 a touch to add some additional sparkles around the text.
05:17 Let's go ahead and add an outer glow to this layer to make it more visible.
05:25 and the color's going to be slightly more orange than the last one.
05:35 the size is only gonna be increased to around 20 pixels.
05:39 And that should leave you with a glowing, sparkling fireworks text effect.


If you're like most people, your garage is one of the most neglected areas of your home. Because people don't tend to hang out in their garages, these spaces typically move to the bottom of the to-do list. The garage is also probably the largest room in your house, though, so if you've neglected its maintenance, it may be a good time to take a close look at the garage. Here, we offer some garage inspection and maintenance tips to help you get your garage functional, clean and in good working order.
The first thing to do is thoroughly inspect your garage. You may go in and out of your garage several times a day, but you might not really look at it as you're passing through. Taking some time to really take stock of the condition of your garage is a good way to start caring for it.
Look for changes in the garage door, inspecting the surface and making sure there's no rust on the springs or pulleys.
Check to see that your garage door opening mechanism is in good working order.
Examine the floor and walls, making note of any changes since the last time you looked.
Make sure your garage gutters are not obstructed.
It also may be a good time to give the garage a thorough cleaning. If it's cluttered or filled with items of questionable importance, you might want to spend some time organizing and purging things you no longer need. Once your garage is tidy enough for a deep clean, it's time to get started. Clean the floor by hosing it down, and pay attention to any spots that may need repair. Look for damaged spots in the walls and foundation too, so that you can catch problems like moisture or cracks before they need a major repair. Clean the interior gutters and doors, and look for signs of pests that may be hiding in your garage. You may find ants, spiders or termites, or animals like mice and rats or even possums and raccoons. Finding signs of an infestation early on gives you the upper hand, and helps you eradicate pests before they become a major problem.
Next, turn your attention to the garage door. Your garage door is one of the biggest machines in your house, and it can open and close many times over the course of a day. Preventive maintenance is important because you'll want your garage to keep running at peak performance for many years.
Open your garage door and close it again. Look and listen to make sure it's running smoothly, with no grinding or scraping sounds, and no misalignment or jerky motions. Observe the moving parts, checking to see if any connections or hardware seem loose.
Disconnect the garage door opener. When you're working on the garage door, it's important to have it disconnected to prevent injury.
Clean the door. First, use a leaf blower to blast away any bugs, dirt, or debris out of its parts. Follow this with a broom or brush and then a rag, to make sure nothing is left behind. Clean the surfaces of the door by hand, using a low phosphate detergent dissolved in five gallons of water. Never pressure wash your garage door.
If you've found any rust on the garage door's springs or pulleys, see if you can clean it. If it's truly corroded, consider replacing the rusted parts, to prevent the garage door from having a major malfunction.
Inspect the rollers. This should be done twice a year, and if the rollers are worn, chipped, or cracked, it's time to have them replaced.
Use a lubricant. Lubricate the opener's chain or screw with white lithium grease, and use a spray lubricant to coat the springs. Keeping the moving parts of the door well-greased is a simple way to extend the opener's longevity.
Check the weather stripping. If the rubber seal on the bottom of your door is cracked, brittle, or worn, have it replaced as soon as possible.
Tighten everything. Check out all the brackets and bolts, and tighten them, paying special attention to anything you noticed looking loose when you raised and lowered the door.
Inspect the cables. Look for worn or broken strands, but never try to replace the cables yourself. Instead, call for a professional who has the equipment and experience to safely fix the cables.
Make sure the door is operating safely. Open it manually, half way up. If it doesn't stay up, you may have a problem. Another smart idea is to perform a test of the auto-reverse safety feature, placing a roll of paper towels in the way of the door, reconnecting the door, and watching to see if it reverses itself before crushing the paper towels. If it doesn't stop, clean the photo eyes on either side of the door and try again. If there's still a problem, it needs to be repaired or replaced.
If your garage door needs repair, it's not a good idea to try and do it yourself. Invest in the services of a professional, and you'll be sure the job is done correctly and well. What's more, you'll avoid the risk of accidents and injuries that can occur when someone untrained and unfamiliar with garage door repair attempts to tackle the problem on his own.


On Tuesday, March 12, Fr Rodolfo Cardenal SJ, Professor of Theology at UCA (Universidad Centroamericana - San Salvador) and Director of the Centro Monseñor Romero, gave a presentation at the Jesuit Curia in Rome. The occasion was organized jointly by the office of the Postulator General, the Pontifical Collegio Pio Latinoamericano, and the El Salvador Embassy to the Holy See.
Fr Cardenal stressed that it is hard to understand Bishop Romero without considering Rutilio Grande, and the influence the latter had on the Bishop of San Salvador. St Oscar Romero was murdered for standing by the poor and voiceless in his country. The talk highlighted various parallels between the lives of the two martyrs. But above all, Fr Cardenal spoke about Rutilio Grande's commitment both to the proclamation of the Gospel and to the justice of the Kingdom of God as these expressed themselves among the campesinos.
Rutilio Grande had spent about twenty years of his life in the formation of the Salvadoran diocesan clergy. He encouraged a form of accompaniment that invited seminarians to embrace inner freedom. He trained them to serve the people and not any clerical caste. He promoted the spirit of Vatican II. However, when in 1970 he lost the confidence of the bishops, he began pastoral work in his native region.
- Rutilio and Archbishop Romeo announced the Kingdom of God and manifested its clear presence in a reality dominated by economic exploitation, social oppression, and repression of the State.
- Both called those perpetrating injustice and violence to conversion, and neither of them nurtured violence, effectively fighting against its various forms.
- Their styles were different, but their words were to the point and timely. The poor received them with joy, because they brought them hope. But the powerful accused the two priests of being "communists," and finally silenced them by murdering them.
- Bishop Romero and Fr Rutilio strove to build a Church that is truly the people of God, as the Council urged them to. For them, the Church had to be built from the bottom up, seeking to unite people, calling them to conversion, to turn again to God.
It is natural that the prophetic dimension of Rutilio Grande's preaching raised political issues in his parish context. For Oscar Romero, these questions were at the level of his diocese, and then the whole country. The political dimensions behind these Christian leaders caused tensions. As a pastor, Rutilio Grande lived in the midst of ambiguities: he had to defend the Christian option, that is, the struggle of the rural poor for justice, even when this struggle was interpreted in a political way. He never succeeded in making the military authorities understand that. On the other hand, Archbishop Romero explicitly approved the preaching and pastoral care of Rutilio Grande.
Fr Rodolfo Cardenal also highlighted the friendship between Rutilio Grande and Oscar Romero. He recalled that after the assassination of Fr Grande, a "local tradition" has maintained that his death was at the root of Bishop Romero's "conversion". This conversion was not so much the abandonment of a life of sin, but rather a turning to oppressed people, and a commitment to defend their cause with remarkable strength and clarity.
Click here to read Rodolfo Cardenal's talk in Spanish.


Blowout Sale! Up to 58% off on Waist Packs at Wander Soul. Top brands include Verve, LE Eclipse Legend, Vizhora, NRspirit, MYCARBON, Traveler's Peak, OUTZIE, Sport Emblema, Zikee, Pierre Cardin, & Foot Forward Sports. Hurry! Limited time offers. Offers valid only while supplies last.


text:
Legal Team/Templatizing
< Legal Team
Revision as of 16:14, 27 October 2016 by Jlovejoy (Talk | contribs)
This is the working area for the technical and legal teams. The focus of this effort is for recording ideas and considerations about improving machine detection and recognition of licenses and headers in code.
1 Key Links
4 Detailed proposal
5 Use and Feedback re: Current Markup
5.1 Gary O'Neall
5.2 Sam Ellis
5.3 Philippe Ombredanne
5.4 Bill Schnineller
5.5 Nuno Brito
5.6 Kris Reeves
5.7 Compatibility with Current Markup
6 Markup to add/consider
Bugzilla bug 1302, which started this particular conversation: https://bugs.linuxfoundation.org/show_bug.cgi?id=1302
Meeting minutes from Aug 6, 2015 Legal call: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-08-06
Matching Guidelines: http://spdx.org/spdx-license-list/matching-guidelines
Pull Request Proposal for SPDX License List (Gary): https://docs.google.com/document/d/115Lis1SJV7Rp-XuNjIysU61urzFGjUOBPqEdVyGLsfI/edit
Meeting minutes from Oct 29, 2015 Legal call: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-10-29
Initial proposal, full write-up (Kris): http://wiki.spdx.org/view/Legal_Team/Template_proposal
Meeting minute from Feb 9 joint tech/legal call: http://wiki.spdx.org/view/Technical_Team/Minutes/2016-02-09
Meeting minutes from Feb 18 legal call: http://wiki.spdx.org/view/Legal_Team/Minutes/2016-02-18
Proposal for exact tag names and edits to matching guidelines: http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching
Plan for review of XML license files: http://wiki.spdx.org/view/Legal_Team/Templatizing/ReviewXML
Action plan for whole project: http://wiki.spdx.org/view/Legal_Team/Templatizing/ActionPlan
XML tags naming discussion:
link to Oct 26 joint tech/legal team meeting minutes: Greetings all – http://wiki.spdx.org/view/Technical_Team/Minutes/2016-10-25
The working document is available at https://docs.google.com/document/d/1z9n44xLH2MxT576KS_AbTOBtecyl5cw6RsrrQHibQtg
(from JL) The current Matching Guidelines and license markup was developed over the past several years. While the guidelines were relatively easier to come up with, how much markup to use and how to implement it was an on-going discussion of much debate. As relevant to the proposals here, the discussion around how much markup to use recognized that more markup would increase consistent results by reducing the need for tool makers to interpret the guidelines. However, due to the amount of work of potentially having markup on every license file, a more conservative approach was taken with the recognition that we could always add more markup over time (but taking it away would be harder).
The template language was a result of a collaboration between members of the legal and technical teams. The goal of the template was developed with the following goals in mind:
Enable both humans and, to a lesser extent, tools to be able to determine if two license texts were equivalent.
Preserve the original language of the license text.
Leverage existing annotations and tools (e.g. the use of regular expressions to denote matches to variable text).
The current templating language is documented in Appendix II of the specification (http://spdx.org/sites/spdx/files/SPDX-2.0.pdf)
Please review the current Matching Guidelines here: http://spdx.org/spdx-license-list/matching-guidelines
Also see Bugzilla bug 1302, which started this particular conversation: https://bugs.linuxfoundation.org/show_bug.cgi?id=1302
(from Gary) As a result of the initial bug 1302 discussion, Gary suggested to enable pull requests to be made against the SPDX License List, which would encourage contributions to markup by others. Such pull requests/contributions would be moderated by the Legal team (especially regarding determinations of markup and potential impact on legal interpretation of the license) with help from the Tech team as needed. Everyone on the Aug 6 legal call agreed this would be a great approach. Gary, Jilayne, Kate have begun to discuss how to implement this. A process also needs to be outlined for how pull requests will be handled, etc. A rough draft process proposal can be found in the google document https://docs.google.com/document/d/115Lis1SJV7Rp-XuNjIysU61urzFGjUOBPqEdVyGLsfI/edit?usp=sharing
(from Kris) Things that would improve working with the data programmatically:
Get away from spreadsheets as the index for the licenses. Use JSON or XML (leaning towards XML to keep the toolset the same as markup parsing). A tool to compile the spreadsheet (for humans to work with) down to an XML file would probably work.
Put all information about a license in the same place for each license (headers, addons/exceptions/whatever). Likely within markup within the license files themselves.
Use XML or some other widespread format for the markup. This ensures there are tools available to work with the data in any language without having to write custom parsing tools or use tools tied to a specific platform because they're the only ones that exist.
As, and if, the data moves towards a more markup-heavy format, it might be wise to simply include the full text verbatim in its own section rather than "recreate" it from marked up data.
An example of what a more normalized (to xml) data set might look like:
index.xml:
<licenses>
<license identifier="Apache-2.0" file="Apache-2.0.xml">Apache License 2.0</license>
</licenses>
LGPL-2.0.xml:
<license>
<original>...full original text content...</original>
...Licensed under the Apache License, version 2.0, etc....
Some text blah blah <match regex="foo|bar"/> more text
</license>
An alternative:
....etc
...THE SOFTWARE IS PROVIDED "AS IS" AND <alt regex="THE AUTHOR">ISC</match> DISCLAIMS ALL WARRANTIES...
The above carries the useful property that the text content of the body tag is the original source without any modification; processing can instead replace "alt" tag contents with their regex attribute to "convert" to a matchable format.
I don't actually like XML, but it seems to be a good fit for this purpose. It helps keep the intrusiveness of the markup into the license text focused and to a minimum, lets us wrap entire sections as optional, keep the canonical original text if desired, and specify alternate license formats such as the short-form license header and any desired metadata all in one place. And there are tools to read XML in every language.
I recommend that the template content be *without* the parts that the matching guidelines say to ignore, and preferably it should have normalized or marked up bullets, etc. Best of all would be, simply, normalized text content in a full regular expression that can be used to match directly, rather than a bunch of markup that must be turned into a regular expression -- but I think this would make maintenance much harder. Again, a compilation step could help. There's a lot of work to be done here that can be qualified as preprocessing, and there's no reason we can't make sure the preprocessing is "done right" and publish the results, instead of requiring programmers to reimplement their own version of the preprocessing with uncertain results.
A particular note about normalizing text: Bullet items are one of the problematic points for parsing because it can be troublesome to distinguish a bullet point like "ii." from the end of a sentence that got wrapped to the start of the next line. (I actually encountered this in my testing; a saving grace is that the bullets tend to be things that are hard to confuse for words, but it's really easy to write a regular expression that isn't that smart.)
For what it's worth, I'm quite happy to contribute when it comes to tooling; I already have code to do the most of this anyway. -Kris
Detailed proposal
See: Legal_Team/Template_proposal
Use and Feedback re: Current Markup
Feedback was solicited on the legal and tech mailing lists to this end:
We have a task to add markup to some of the standard headers and have also had input to add/edit markup on existing licenses. As a result of the latter, it has been raised that perhaps the markup could be improved. Before adding more markup (to standard headers, license text or both), it seemed prudent to start a discussion as to whether the existing markup is effective. Please ponder the following questions: a) have you used the existing markup for matching purposes? i) if no, why not? ii) if yes, has it been helpful/effective? Could it be improved, and if so, how? (this will likely involve putting forward a proposal for review)
Please record your input in a section here, by name or tool or both:
Gary O'Neall
For the SourceAuditor commercial tools, the markup is used to validate that 2 licenses are equivalent per the matching guidelines. The open source SPDX tools uses the markup is used in a number of ways. The "compareSpdx" and "compareMultipleSpdx" commands use the markup to determine if the licenses are equivalent. There are library methods implemented to compare license text and report if the license text matches any of the SPDX LicenseList.
In all cases above, the markup is used to compare 2 existing known license text. It is NOT used to match license text against a library of possible license matches. In the commercial tool, a separate algorithm implements this functionality and the markup language turned out to be too inefficient for this purpose - at least for the performance requirements of our application.
Note: When we originally discussed the markup language, we debated whether to cover the use case of searching a library of possible license matches and the decision was taken not to support this.
In my opinion, the markup works fine for matching two license texts. If we wanted to support a searching use case, we would need to modify/extend the markup language to enable this to be efficient.
Performance would be greatly improved if we bounded the RE's. Something which is within the spec, but is not implemented in the templates. I would support implementing bounding all RE's in an upcoming release and changing the spec to encourage bounding. I think we could pick a pretty practical upper bound that would improve the performance.
Also note - this is more of an issue with the "matching against a library of licenses" issue than simply comparing two license texts since the former is more performance sensitive.
Sam Ellis
I will share a few points from my experience in templatization. I currently use a different templatization syntax that predates SPDX, but the principle of using regular expressions embedded within the license text is similar.
The major barrier to me adopting the SPDX templates is insufficient templatization within the existing licenses. The SPDX templates currently encode what I perceive to be the 'official' variations, i.e. organization name, person name, product name etc. However, real-world licenses contain may minor variations that may be inconsequential from a legal perspective, but nonetheless do not warrant separating out as separate licenses. Here is an example from the GPL-3.0 notice where it is common to see two variations in one of the sentences:
distributed in the hope that it will be useful distributed in the hope that they will be useful
The example above is fairly uncontroversial, I would hope. However, there are plenty of other examples that border on having a legal impact. For example, in these two BSD-2-Clause variations it is necessary to consider whether the additional word constitutes an acceptable minor variation or warrants a different classification altogether:
Redistributions of source code must retain the above copyright notice, this list of… Redistributions of source code must retain the above copyright notice unmodified, this list of…
It is the grey cases like these that make expanding the use of templating difficult. Inevitably it leads to having to make some judgements about the impact of a particular word or phrase on the legal interpretation, something that I am aware SPDX tries to avoid.
Whether it is worth templating all the cases like these primarily depends on the goals of the SPDX templates. If they are for human use to see what official variations are permitted, then they are not necessary. On the other hand, if they are to be used by automated license scanning tools, then covering these cases is essential in order to have a tool that works effectively on real-world code. So I think an important point is to gain clarity on the purpose of the templates.
In terms of the current application of the templates, I have a technical concern over the use of unbounded regular expressions, for example:
<<var;name=copyrightHolderAsIs;original=THE COPYRIGHT HOLDERS AND CONTRIBUTORS;match=.+>>
This is unbounded because it will match any number of characters for the copyrightHolderAsIs field. The practical consequence of this is that regular expression matching can explode in terms of time. I don't have a concrete example to hand, but my own experience with using the same unbounded regular expressions on real-world licenses is that I have seen it take minutes just to process one regular expression on a single file, and this does not scale well when there are millions of files to process. Clearly, in terms of English language there is no maximum size on the length of a copyright statement. Using an unbounded regular expression is therefore correct in theory but difficult to use in practice. I have had to use size bounded regular expressions in order to have a scanning tool that will complete in a reasonable time. The problem in switching to bounded regular expressions is in deciding on what is an acceptable upper bound on the size, and this can really only be judged by experimentation against real-world licenses, and does then require on-going tweaking as new license variations are discovered.
Neither of these are problems with templatization per-se, and they are more to do with the extent and way in which they are currently applied.
Philippe Ombredanne
a) have you used the existing markup for matching purposes?
Yes and No: ScanCode uses an SPDX-inspired/derived markup, but instead of reusing the markup directly from the main license texts, markup is transformed in a simpler Template:Mustache-like syntax added to copies of these texts used only for detection purpose.
Because: - adding more markup to a reference license text makes this eventually no longer usable as a reference text and harder to read by humans - the many variations found in the wild make it hard to put all in a single template. - the markup syntax implies eventually an implementation using regular expressions. ScanCode does not use regex, but inverted indexes and string alignments.
ii) if yes, has it been helpful/effective? Could it be improved, and if so, how? (this will likely involve putting forward a proposal for review)
I think a simple markup is a very effective way to detect licenses with minor text variations and still call this an exact match. It is also a very effective way to indicate variations for humans. I find it hard personally to mix the human readability and technical detection concerns in the same file without compromises.
As food for thought, here are some examples of markup as used in ScanCode:
https://github.com/nexB/scancode-toolkit/blob/b37be4de78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/apache-1.1_38.RULE#L17 https://github.com/nexB/scancode-toolkit/blob/b37be4de78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/bzip2-libbzip-1.0.5_1.RULE#L1
The syntax is using double curly braces to enclose variable parts. There is no regex involved. Optionally a number can be used after the opening braces to indicate the number of variable words, defaulting to 5 words. For instance Template:Copyright (c) 2015 Myco would match up to 5 words and Template:10 Copyright (c) 2015 Myco inc. would match up to 10 words.
I hope this helps even though this is a slightly different take.
Bill Schnineller
i) if no, why not?
In a nutshell, partly due to timing of our dev efforts ahead of SPDX templatization rollout, partly due to performance in context of our internal Use Case of scanning every single open source file (not just a handful of applications).
Details: Black Duck has a corpus of license variants extracted from our Knowledge Base of around half a billion unique open source source/text and binary files. Several years ago, prior to SPDX license templatization, we went through multiple iterations of grouping license text variants, as well as license name/nickname variants. Our groupings were based on applying similarity algorithms, followed by human review. Our methodology has been in place for some time prior to the templates / regular expressions subsequently rolled out by SPDX.
Variations we've encountered, such as the street address of an organization, or typos / word substitutions that SPDX license templates might not have covered are some of the reasons we haven't yet gone through the exercise to see which license variants the SPDX templates might not 'match' to the license id's we've grouped them under.
We use our license scanner to scan (and rescan) every single open source file to populate our Knowledgebase of file-level license data. Our scanner uses multiple techniques to discover license references, but does not use regular expressions because of performance concerns.
Because Black Duck does not provide legal advice, consumers of our tools are able review the license text which our tools highlight in order to make a final determination. This fits well with the SPDX concept of separating discovered and concluded information.
Outlook: SPDX license templates / regexes aren't as useful or efficient as other matching techniques we have, when automatically bulk scanning large codebases to determine 'LicenseFoundInFile'.
But when a human is in the loop producing a final SPDX Document with Concluded License, SPDX license templates / regexes could be useful to focus legal review on deviations which may or may not be significant.
Nuno Brito
Didn't use the markup. At the time haven't found documented the pattern keywords to find inside each license term. For example, one can find [xxxx]-[xxxx], [Owner Organization], <AUTHOR>. However, didn't seemed to be used consistently throughout the list of licenses. That was my opinion at that time, might certainly be proven erroneous.
If help is welcome, I can volunteer for normalizing the data for the complete list (top to bottom) and document the used keywords. However, for our own tooling usage as template I'd replace the text on some specific license terms so that we could later generate new licence docs where only the copyright holder changes.
Such example would be http://spdx.org/licenses/BSD-3-Clause-Attribution.html where: "Universidad de Palermo, Argentina" (http://www.palermo.edu/).'" becomes "<AUTHOR>".
Kris Reeves
I have been thinking about the proposed format in detail, and it has become clear to me that it will be undesirable to attempt to maintain a canonical single source of truth in the format we would want to expose to consumers. This is made clearest by the synonym matching rule: it is unfeasible to ask or expect a person editing a license file to find, identify, and mark up all candidates for synonym replacement. It is, however, easily possible to expose data that has been thus marked-up to consumers of the SPDX data. This implies that there must be a build step of some sort in the mix.
Given that there would be a build step, the case for altering the source markup is weakened somewhat; it's not strictly *necessary* to support (my) goal of providing data that can be consumed directly without any programmatic logic required to match a license, but still retains a number of benefits including: utility in editing/managing the license content itself, ease of integration into tooling required to produce the "built" product, ready extension, familiarity to newcomers/potential contributors, and even brevity.
Given the above, there are really two classes of markup to consider:
1) Markup used to clarify / identify information that is obvious to a human but difficult for a computer to interpret (for example: identifying bullet points)
2) Markup used to provide more robust matching that is easy for a computer to generate but difficult for a human to maintain (for example: identifying synonymous word spellings)
The most useful focus for markup in the first category is ease of use by a human editor: it should be unobtrusive and succinct, lending to ready interpretation by a reader/editor of the license text in a legal-meaningful way and imposing a minimum of technical knowledge for correct and confident interpretation.
The most useful focus for markup in the second category is ease of consumption by a program: it should be thorough and explicit, lending to immediately useful applications with little to no business logic required in the consuming code.
I'm working on the proposal discussed in the last legal call, but splitting it into two parts by these guidelines. This approach feels a bit messy to me, but I see no way around it other than to write custom tooling that can abstract the category-2 markup away from a human and let them work in terms of category-1 markup.
Compatibility with Current Markup
If we do change the format in a way which is incompatible with the existing markup, we may break existing applications. I originally did not think this would be much of an issue based on the responses above, but then I ran across the comment https://github.com/sindresorhus/spdx-license-list/issues/6#issuecomment-150606727 where the existing syntax is used to extract the license text. There may be other such applications that we are not aware of. -- Gary O'Neall
This is actually a point in favor of going ahead: if people are writing regular expressions to parse the current data, that is happening because the tools to do it properly aren't available to them. Markup change would obviously be a major version bump, so tools such as the above would still work and continue to function on the v2.0 data. New/updated tools, however, would become less fragile by virtue of using parsing tools that know how to deal with XML, and the markup itself can thus be extended to incorporate new needs without breaking existing fragile regular expressions. -- Kris
Markup to add/consider
[JL] This is simply a list of various specific licenses that may need additional markup or things to consider related to the matching guidelines, to ensure we don't forget to add/edit later!
Apache-2.0 - instructions as to how to apply license, markup as optional? (from Kris)
MIT - "THE AUTHORS OR COPYRIGHT HOLDERS" - markup to be variable (from DMG's student paper)
add "noninfringment" and "non-infringement" and "non infringement" as equivalent words in Matching Guideline #8 list of words (from DMG's student paper)
add "contributors" and "co-contributors" and "co contributors" as equivalent words in Matching Guideline #8 list of words, needs some discussion (from DMG's student paper)
ISC license needs markup (and link fixed)
Retrieved from "https://wiki.spdx.org/index.php?title=Legal_Team/Templatizing&oldid=4057"


ALL IN ONE Employment Services is looking for a Sales Assistant with Customer Services working Experience to assist a manufacturing sales Department.
This Person will be assisting with phone calls, emails, filing, CRM Updates,Generating Leads, documentations, Etc.
Microsoft Office, CRM, Phone Skills, Typing and enthusiasm are requirements for this position.


text:
Bhuwan happy with his batsmen
Though Nepal lost their second ACC U-19 Asia Cup match against India on Sunday, skipper Bhuwan Karki was still happy because of how his batsmen dealth with fast bowlers.
"There has been often a lot of talks about Nepal's vulnerability against seam bowling but coming into this tournament, we have handeld the fast bowlers pretty well," said Bhuwan after the match against India.
"In our last two matches (against Pakistan and India), we lost only two wickets to the fast bowlers. Both India and Pakistan have a good pace attack but our batsmen played a pretty positive cricket against them," Bhuwan added.
"Being able to play against the fast bowlers is the biggest positive we are going to take from this tournament. Also, the performance against the two big teams has given us a lot of confidence going into our last league match against the UAE," the skipper added.
Nepal are playing their third and final group stage match against the hosts at the Sharjah Cricket Stadium on Tuesday where the team would be eyeing to at least gain some reputation by winning it.
Coach Jung Bahadur Thapa was not satisfied with the spin department in this tournament. "Our fast bowling attack was okay. Can't expect anything big from them under these conditions but spinners have let us down in the first two matches. We knew that it was an average spin attack but this has hit really low," said Thapa.


Strategic category management stems from the recognition that a single technique to identify and select suppliers is limiting and insufficient. The purpose of strategic sourcing is to obtain the right supplier for the company's need—taking into account competition, market dynamics, supply reliability, switch-out costs, and similar factors. This valuable program covers key elements of strategic sourcing and category management including best practices, tools, techniques, and solutions—followed by exercises in which participants apply the tools they've learned with instructor coaching sessions and a presentation of templates and analyses. The faculty instructor for Strategic Category Management is a renowned thought leader in supply chain management and is an industry expert in category management, strategic sourcing, supply market intelligence, and supplier development. The instructor serves as a professor of supply chain management at North Carolina State University's Poole College of Management and as an adjunct professor at the Supply Chain Management Research Group at the Manchester Business School. He is a prolific author and globally recognized leader in the field, contributing regularly to the intellectual capital of supply chain management. This customized TNI seminar will strategically expand the ability of participants to identify and select a broader range of suppliers, enabling them to be more efficient, productive, and profitable upon returning to work.


ESG, the proposed Accountable Capitalism Act, state-issued board diversity quotas, and continued pressure from institutional investors—these things will continue to shape board discussions and composition in 2019. In this episode, we welcome back Doug Chia, Executive Director of The Conference Board Governance Center, to discuss how some of these issues may play out.
Chia and Host TK Kerstetter discuss what boards can expect following California's board diversity quota for women. What are the positive and negative ramifications of this legislation? Can we expect more states to follow suit?
Further, the two tackle Senator Warren's proposed Accountable Capitalism Act, which not only proposes federal chartering, but that a portion of the board be elected by employees. How would the suggested legislation restructure corporate formation and corporate law in the U.S.?
Kerstetter and Chia also discuss CalPERS' recent leadership change, as well as how they see the focusing on ESG evolving in 2019.


text:
You should visit Ghost Towns in the USA
Sameh | 9 February، 2020 | unclassified
1- Body, California
By the early 1880s Bodi had finished paying gold, and prospectors had escaped from this illegal site, as if they had just gone to check the mail. You can look at the windows of the 200 buildings in the body, and marvel at the short-lived scenes of life, all the way to kitchen tables set for meals that have never been served.
How to see it: Body, California is about 77 km northeast of Yosemite National Park. 50-minute tours are provided daily by park rangers, but visitors can book ghost trips with guides for three nights this summer.
2- Banak, Montana
In the 1860s, Banach's golden fortune in Montana sparked greed and firearms, which earned her the nickname "The Hardest City in the West". The dangerous road to the nearby city of Virginia was a special target for deadly bandits, and the victims of their victims are sometimes seen around Banak's 60 remaining buildings.
How to see it: About 350 kilometers northwest of Yellowstone National Park, there is Bannack State Park and its camp is open all year round (as with the Dillon's Best Western Paradise Inn), but guards make summer trips only. Banak's annual days are held in the third week of July, and include a dramatic reenactment of the city's volatile past.
3- Kahaba, Alabama
Kahaba was the first capital of Alabama, as it was reported at the time, it was the booming cotton city between 1820 and the 1970s, and also the Civil War prison camp, but unfortunately it was built on the flood plain. Only decomposing wet traces remain on this elegant archaeological site. The ghosts of nineteenth century children, slaves, and prisoners are said to be stuck in the place.
How do you see this: Kahaba is 23 km away from Salma. You can roam the rubble all year round from 9:00 AM to 5:00 PM. The historical, haunted tour of only 90 minutes (this year, on October 22nd) allows you to explore after dark. You can book through [سلما-دالاس] Governorate Tourism and Convention Office.
4- Kennicot, Alaska
Within the USA's largest national park, Wrangell Elias, parked wooden buildings in Kennicot offer a rare insight into the history of mining in the wild. In 1900, the Kennicut Cooper Corporation struck gold ore, and then brought in 300 miners here. When copper ran out in 1938, everyone left – in theory. Site maintenance is ongoing, but when workers are said to hear strange noises from miners hesitating from the mountains or seeing tools flying from their utility belts, construction can slow.
How to see it: Approximately 322 km east of Anchorage, Alaska, drive your car to the end of the unpaved McCarthy Road, then walk eight kilometers to Kennicot. Less than a kilometer from amenities like the Ma Johnson Hotel, and in the summer, St. Elias Alpine Guides guided tours.
5- Batstow Village, New Jersey
The village of Batstow was built in 1766 as a site for ironmaking, and it flourished until the 1850s, and then remained empty for decades. The small village is still well preserved today in 18th-century buildings, including mourning. Away from the floating tombs of light, the pesky scenes of Batstow were legends of the legendary Devil-like demon.
How to see it: The village is located 70 kilometers southeast of Philadelphia, in New Jersey. You can take a self-guided excursion or book a guided tour of Batsto Mansion. Every October, the Twilight Climbing Festival, titled "Jersey Devil Pound", takes place in Battstowe, and the neighboring Wharton Forest.
Dear tourist, get great ideas on your trip to Alaska
A list of the most important tourist interests in Munich


The Moonlight Resort, in the heart of the small island Malapascua, offers silence and recuperation to its guests between innuberable coconut trees. Also activities like sunbathing at white beaches, swimming in crystall-clear water, snorkeling and diving at the sourrounding reefs are possible anytime. In the restaurant you can let your palate spoiled with national and international dishes and beverages.
The Moonlight Resort is the one and only resort at the island with sweetwater shower.
Electricity is 24 hours daily available.
Free WiFi Internet accesspoint for our resort guests.
If you have some questions or if you need further information please send an e-mail.


To find cheaper term life insurance in Golden, MO it is important to compare multiple quotes. We can help you do just that quickly and efficiently. Enter your Zip code at the top of the page and the search engine will pair you up with the top-recommended term life insurance providers in your Barry area.
Still, many people's plans to stack money for the future to take care of their families don't always work out the way they want. Considering how cheap these Golden, MO term life insurance policies are, you can soon find yourself with peace of mind and nothing to worry about when it comes to your family's financial future. It is easy to forget and think that you will always be around. That's why so many people fail to secure that policy, chiefly.
It's quite easy to get multiple quotes and then choose a policy that fits your needs. As a matter of fact, you don't have to wait to purchase that policy. You just have to do all of your business online and then close the door on that challenge. You will have Golden life insurance policy quicker than you think, and no longer will you be ignoring the need.
Buying daily life insurance policies is a single of the most essential decisions you will make. A life insurance policies coverage is 1 of the very best methods to make certain that your liked types are taken care of if something transpires to you. Selecting what existence insurance policy to acquire can be a very tough determination. The adhering to article provides tips to support make confident that you purchase the right daily life insurance coverage.
If you are taking into consideration buying life insurance policies, be positive to examine with your employer just before likely to your insurance agent. Your employer might be able to give you a greater price on daily life insurance policy owing to obtaining produced a deal with the life insurance company to insure a big variety of folks. You may possibly be ready to get lifestyle insurance coverage for by yourself and your loved ones associates at really desirable prices.
Disclose every thing relating to your existence and your wellness when acquiring daily life insurance. If something that you failed to point out contributes to your passing, you may have rendered your insurance policy null and stay away from. The most costly insurance coverage policy in the planet is the one that doesn't pay out out when it really is essential.
When generating the choice to acquire life insurance coverage, be certain that you let by yourself adequate coverage. The policy have to be ready to protect your ultimate expenditures, including your mortgage, personalized loans, and your kid's educational costs.
Prior to acquiring existence insurance policy, you must understand that insurance coverage is for defense needs only, which does not include investing. Term insurance policies offers you security only, with no cost savings. Total daily life and common procedures provide cost savings, but they are a lot a lot more pricey and you would be better off employing the cost personal savings to invest in anything else.
Discuss to your beneficiaries as shortly as you acquire lifestyle insurance policy. Make sure they recognize precisely what advantages they get on your demise. Supply the heir will all specifics of the sum insured, in which you have situated the plan documentation, and all the contacts for fiscal associates they need to have to phone to make the claim when the time occurs.
Study your life insurance coverage policy totally before you signal on the dotted line. Make sure that you are mindful of the exclusions, inclusions, special discounts, no payment for loss of life brought on by a pre-existing ailment clauses and other phrases of your daily life insurance policies coverage before committing to it. With out being aware of precisely what your coverage addresses, when you die you could inadvertently leave loved ones associates remaining guiding in a difficult placement.
Operate out a budget to make certain that you purchase sufficient existence insurance policy protection. It can be confusing to attempt to calculate the actual sum of insurance policy you require. Nevertheless, it's going to aid you stay away from troubles afterwards on if you do this initial. Get into account normal costs such as mortgage loan payments or rent, and utility bills. You must also preserve in thoughts that there may possibly be long term expenses such as higher education tuition and retirement that need to have to be accounted for.
Just take gain of the accelerated loss of life gain choice if it really is provided by your insurance policy business. This daily life insurance policy gain permits the policyholder to get a considerable quantity of the loss of life benefit of the coverage, in the case of a terminal disease. This can permit the insured to use this benefit to protect items such as health care costs, experimental therapies, a excursion, house enhancements or nursing staff.
Learning how the insurance coverage system performs is quite essential when dealing with insurance organizations. As you can see, it is possible to have a good existence insurance coverage that is each dependable and affordable. Follow our tips, and you will uncover just the coverage that you want, want, and can rely on.


As a recipient of the Cary Award, Pachysandra terminalis 'Green Sheen' has proven its worth as a home landscape plant for New England and elsewhere. The glossy, evergreen leaves are especially attractive. Plants in 2-1/2 inch pots are chosen for covering all size areas.
Name(s): Pachysandra terminalis 'Green Sheen', Japanese Spurge, Pachysandra.
Features: Drought tolerant, low maintenance, reliable, glossy evergreen foliage.
Comments: Glossy evergreen oval leaves, about 2 inches to 3 inches in width, are lightly toothed. Small, white flowers appear in spring and summer. Pachysandra spreads by underground stolons. Mature height ranges from 8 inches to 10 inches.
Pachysandra thrives in partial shade to full shade in USDA climate zones 4 to 9, but will tolerate some sun in cooler climates. It prefers rich, loamy, well-drained soil with pH ranging from 4.5 to 6.0, and is drought-tolerant when established. Space Pachysandra approximately 12 inches to 16 inches apart.


Explore the personal stories and accomplishments of the past year.
I am so pleased to share Tawonga's first-ever annual Impact Report with you!
Through the milestones, achievements and moving personal stories shared in this year-in-review, I hope you take pride knowing that you are a valued member of the Tawonga family. Together, we are making it possible for more children, young adults and families than ever before to reconnect with their Jewish heritage and community year-round.
You can read the year-in-review here -- enjoy!


The ponderous instrument of synthesis, so effective in Newton's hands, has never since been grasped by anyone who could use it for such purpose; and we gaze at it with admiring curiosity, as some gigantic implement of war, which stands idle among the memorials of ancient days, and makes us wonder what manner of man he was who could wield as a weapon what we can hardly lift as a burden.
- William Whewell on Newton's geometric proofs, 1847 (thanks to JWS for pointing this out to me).
A quick observation: statements like "the average woman's height is 64 inches" are almost always misinterpreted. Here's the main problem: people think that this is referencing an archetypal "average woman", when it's not.
The proper parsing is not "the (average woman's) height"... but it is "the average (woman's height)". See the difference? It's really a statement about the variable "woman's height", which has been measured many times, and then averaged. In short, it's not about an "average woman", but rather an "average height" (of women).
Of course, this misunderstanding is frequently intentionally mined for comedy. See yesterday's SMBC comic (as I write this), for example: here.
Let me again ask the question, "How Do You Know Something is a Proportion?". For the math practitioner this is one of those things that requires no explanation ("you just know", "it's just common sense"). But for the remedial college algebra student, running into these common questions on tests, it's a real stumbling block to recognize when the proportional exercise is being asked. Actually, I've found that it's a stunningly hard problem to explain when we know something is proportional -- I've asked the question online twice here (first, second), I've asked around to friends, and rarely do I get any really coherent answer back at all. (One professor colleague investigated the issue and then said, "It's the question on the final that doesn't have a clear direction to it, that's how you know."). Any college basic-math textbook I look at has a stunningly short attempt at a non-explanation, as though they're keenly embarrassed that they really can't explain it at all (usually in the form of, "Proportions are useful, for example in the following cases..."; see first link above for specifics). Let's see if we can do better this week.
First, let's look at what the up-and-coming Common Core curriculum does with this issue. In CC ratios and proportions are a 7th-grade topic, and there is a presentation specifically on the subject of "identifying proportions". This is uniformly given by two methods: (1) a table of paired numbers, and (2) a graph of a relationship. The key in the first case is to see that the pairs of numbers are always related by the same multiplication factor (usually a simple integer), i.e., y = kx. In the second case you're looking for a straight line that goes through the origin (0, 0), which I think is not a bad tactic. These materials very consciously avoid relying on the cross-multiplying ratios trick, and seek instead to develop a more concrete intuition for the relationship. I think that's a pretty solid methodology actually, and I've come to agree that the common cross-product way of writing these obscures the actual relationship (see also work like Lesh, 1988 that argues similarly).
49. A student would like to estimate the height of the Statue of Liberty in New York City's harbor. The length of the Statue of Liberty's right arm is 42 feet. The student's right arm is 2 feet long and her height is 5 1/3 feet. Use this information to estimate the height of the Statue of Liberty.
Notice that this doesn't assert that the person and the statue are proportional. In fact I can think of a lot of artistic, structural, or biological reasons why it wouldn't be. In this way the problem is not really well-defined.
51. There are 72 milligrams of cholesterol in a 3.5-ounce serving of lobster. How much cholesterol is in 5-ounces of lobster? Round to the nearest tenth of a milligram.
As someone who's eaten a lot of cheap lobster growing up in Maine, again I can think of a lot of reasons of why the nutritional meat content of lobster might not be proportional across small and large lobsters (the basic serving being one creature of whatever size). For example, the shell hardness is very different across different sizes.
57. One out of three American adults has worked in the restaurant industry at some point during his or her life. In an office of 84 workers, how many of these people would you expect to have worked in the restaurant industry at some point?
My immediate guess would be: definitely less than one-third of the office. It seems that a sample of current office workers are somewhat more likely to have worked in an office all their career and therefore (thinking from the standpoint of statistical inference) fewer of them would have worked in a restaurant than the broad population. For example, simply change the word "office" here to "restaurant" and the answer is clearly not one-third (specifically it would be 100%), cluing us into the fact that former restaurant workers are not spread around homogeneously.
I don't really mean to pick on Martin-Gay here, because many of her other exercises in the same section avoid these pitfalls. The very next exercise on the Statue of Liberty says, "Suppose your measurements are proportionally the same...", the one on skyscraper height says, "If the Empire State Building has the same number of feet per floor...", others give the mixture "ratio" or medication dose "for every 20 pounds", all of which nicely serve to solve the problem and make them well-defined.
But I've seen much worse perpetrated by inattentive professors in their classrooms, tests, and custom books. So even if Martin-Gay fixes all of her exercises precisely, plenty of instructors will surely continue to overlook the details, and continue to assume their own background contextual knowledge in these problems that their remedial students simply don't have. In short, for some reason, we as a professorship continually keep writing malformed and poorly-defined problems that secretly rely on our application background knowledge of things as proportional.
Here's the solution that I've decided to try this semester in my remedial algebra courses. To start with, I'll try to draw a direct connection to the Common Core exercises, such that if someone ever has or does encounter that, hopefully some neurons will recognize the topic as familiar. Instead of saying that a proportion is an equality of ratios (as most of these college books do), I will instead say that it's a "relation involving only a multiply/divide", emphasizing the essential simplicity of the relation (really just one kind of operation; no add/subtracts or exponents/radicals), and covering the expression of it as either y = kx or a/b = c/d.
So that's what I'll be trying out in my courses this week. We'll see how it goes; at least I think I have a legitimate answer now when a student asks for these kinds of problems, "but how do we know it's proportional?".
A colleague of mine says that he wants to spend time giving his students more video and I equivocate in my response. He presses the question: "Don't you agree that different people learn in different ways?"
Here's one possibly reply. First, to my understanding there's no evidence that trying to match delivery to different "learning styles" has any positive effect on outcomes. One example I came across yesterday: a Department of Education meta-analysis of thousands of studies found no learning evidence of benefits from online videos ("Elements such as video or online quizzes do not appear to influence the amount that students learn in online classes.", p. xvi, here). Perhaps the short version of this response would be, "Not in any way that makes a significant difference."
But here's another possible response, to answer the question with another question: "Don't you agree that it's important to have a shared, common language for communication in any field?" And as usual I would argue that acting like math, or computer programming is anything other than essentially a written artifact is fallacious -- in fact, overlooking the fact that writing in general is the most potent tool ever developed in our arsenal as human beings (including factors such as brevity, density, speed, searchability, auditability, etc.) is fallacious, a fraud, a failure.
To the extent that we delay delivering and practicing the "real deal" for our students -- namely, properly-written math -- it is a tragic garden path.


Praxis, the pixie who changed colour according to his feelings, was a bright and healthy pink. He looked so good and so happy with himself that everyone who saw him couldn't help smiling. The fact was, he'd been chosen for a very important job.


It is recommended for use only on pets, as an adjuvant on wounds, skin infections, superficial dermatosis, burns, treating podal affections, panaritium, laminitis, umbilical infections, small surgery wounds, castration.
External use only. Vapourise daily on the affected area, until it heals. It is not recommended to use on animals with economic interest.
Keep out of children`s reach! Spray only in open air! Do not use near fire sources, and do not smoke when useing! Do not reuse the packaging!


To SlagerDummer: The number 56 has a tremendous Kabbalistic significance to the Rabbinate. Although when you make a kilt with so many pleats, the result was a remarkable peace of art and craftmanship.
The pleats are variable (hour glass shapped) and range from 0.9 cm to just over 1.12 cm. The depth of the pleats are almost 10 cm ( close to 4 inches), hence the tremedously large amount of tartam employed.
Steemed Guests: Here are my personal dimensions, the weared of this kilt that has roused so many questions. All measures are in Standard UK units.
I hope this answer you enquiry!
It is my understanding, that it is appropriate, upon hearing good news that benefits others, to recite the ha'tov ha'metiv blessing. As it's clear that you are absolutely stoked and excited about the completion of this huge project, congratulations and Mazel Tov!
Barukh attah Adonai eloheinu melekh ha-olam, hatov vehametiv.
Congratulations, Raphael, but we have a saying here on this forum: it didn't happen if there are no photos to prove it. We've seen the tartan and it's lovely, but to keep us happy and believing you, you must show us the kilt and you in it! Well, hmmm, really two pics are required: one from the front and the second a Hamish shot of the pleats (just visit the Hamish-the-Legend section of the forum for the finest of style examples).
We don't need to see how it was made -- almost all of us have been there and done that inumerable times in our lives -- but we drool to see finished work, especially when it is of such a massive undertaking as this kilt of yours.
I, too, congratulate you, Bro.'. Raphael on your single-minded determination to bring this impressive project to fruition.
I must, however, agree with Rex, i.e. "pictures or it didn't happen."
In other words, please stop teasing us and post some pictures of this unique kilt!!
Sewn with gold needles? My goodness!
To which Geoff Withnell responded: AMEN.
This is an extraordinary garment, Rabbi, and I congratulate you on its completion.


text:
Q: home directory changed I changed the location of the home directory to a different disk, making changes to fstab but lost information on downloads and old images, is there any way to recover the old home directory or  some old images and download files?

A: If you did not erase the data, it will still be available on your old location. However, it is "hidden" because the other partition is mounted on the /home folder. If you unmount the partition coupled to /home, the old contents will become visible.
The only issue is that you cannot unmount a home partition while you are logged in to the graphical environment. So you either will need to work from a recovery prompt, or from a live session of an installation DVD/USB if you prefer a graphical working environment.

redpajama_set_name: RedPajamaStackExchange


Yesterday I started learning how to code, in codeacademy.com. It's free and with all the free time I have, you know not having a job or anything, I can dedicate some time to learning something that is very useful right now, especially if I ever plan of hosting this blog anywhere besides WordPress.
Knowing how to write is not getting me any jobs and I don't want to be negative, I try my best not to be, but this is getting really frustrating. I never expected this and I wont blame the accident because what happened, happened and I'm ok now, but come on. I'm writing every day, I'm offering freelance writing and I'm trying to write a book, but who knows when that will be done and if it's any good, so I have to learn how to do something else.
I don't like to write angry posts and I haven't given up and I will keep doing everything I can to get my life back together, I am unstoppable, but when something is not working you have to try something else. I don't know if learning how to code will take me anywhere, but it's something I will be able to add to my skills and it's pretty interesting.
If I'm not working, at least I have to be learning something.


8:1 Then Elisha spoke to the woman whose son he had restored to life, saying, "Arise and go, you and your household, and stay wherever you can; for the Lord has called for a famine, and furthermore, it will come upon the land for seven years." 8:2 So the woman arose and did according to the saying of the man of God, and she went with her household and dwelt in the land of the Philistines seven years. 8:3 It came to pass, at the end of seven years, that the woman returned from the land of the Philistines; and she went to make an appeal to the king for her house and for her land. 8:4 Then the king talked with Gehazi, the servant of the man of God, saying, "Tell me, please, all the great things Elisha has done." 8:5 Now it happened, as he was telling the king how he had restored the dead to life, that there was the woman whose son he had restored to life, appealing to the king for her house and for her land. And Gehazi said, "My lord, O king, this is the woman, and this is her son whom Elisha restored to life." 8:6 And when the king asked the woman, she told him. So the king appointed a certain officer for her, saying, "Restore all that was hers, and all the proceeds of the field from the day that she left the land until now." 8:7 Then Elisha went to Damascus, and Ben-Hadad king of Syria was sick; and it was told him, saying, "The man of God has come here." 8:8 And the king said to Hazael, "Take a present in your hand, and go to meet the man of God, and inquire of the Lord by him, saying, 'Shall I recover from this disease?' " 8:9 So Hazael went to meet him and took a present with him, of every good thing of Damascus, forty camel-loads; and he came and stood before him, and said, "Your son Ben-Hadad king of Syria has sent me to you, saying, 'Shall I recover from this disease?' " 8:10 And Elisha said to him, "Go, say to him, 'You shall certainly recover.' However the Lord has shown me that he will really die." 8:11 Then he set his countenance in a stare until he was ashamed; and the man of God wept. 8:12 And Hazael said, "Why is my lord weeping?" He answered, "Because I know the evil that you will do to the children of Israel: Their strongholds you will set on fire, and their young men you will kill with the sword; and you will dash their children, and rip open their women with child." 8:13 So Hazael said, "But what is your servant-a dog, that he should do this gross thing?" And Elisha answered, "The Lord has shown me that you will become king over Syria." 8:14 Then he departed from Elisha, and came to his master, who said to him, "What did Elisha say to you?" And he answered, "He told me you would surely recover." 8:15 But it happened on the next day that he took a thick cloth and dipped it in water, and spread it over his face so that he died; and Hazael reigned in his place. 8:16 Now in the fifth year of Joram the son of Ahab, king of Israel, Jehoshaphat having been king of Judah, Jehoram the son of Jehoshaphat began to reign as king of Judah. 8:17 He was thirty-two years old when he became king, and he reigned eight years in Jerusalem. 8:18 And he walked in the way of the kings of Israel, just as the house of Ahab had done, for the daughter of Ahab was his wife; and he did evil in the sight of the Lord. 8:19 Yet the Lord would not destroy Judah, for the sake of his servant David, as He promised him to give a lamp to him and his sons forever. 8:20 In his days Edom revolted against Judah's authority, and made a king over themselves. 8:21 So Joram went to Zair, and all his chariots with him. Then he rose by night and attacked the Edomites who had surrounded him and the captains of the chariots; and the troops fled to their tents. 8:22 Thus Edom has been in revolt against Judah's authority to this day. And Libnah revolted at that time. 8:23 Now the rest of the acts of Joram, and all that he did, are they not written in the book of the chronicles of the kings of Judah? 8:24 So Joram rested with his fathers, and was buried with his fathers in the City of David. Then Ahaziah his son reigned in his place. 8:25 In the twelfth year of Joram the son of Ahab, king of Israel, Ahaziah the son of Jehoram, king of Judah, began to reign. 8:26 Ahaziah was twenty-two years old when he became king, and he reigned one year in Jerusalem. His mother's name was Athaliah the granddaughter of Omri, king of Israel. 8:27 And he walked in the way of the house of Ahab, and did evil in the sight of the Lord, like the house of Ahab, for he was the son-in-law of the house of Ahab. 8:28 Now he went with Joram the son of Ahab to war against Hazael king of Syria at Ramoth Gilead; and the Syrians wounded Joram. 8:29 Then King Joram went back to Jezreel to recover from the wounds which the Syrians had inflicted on him at Ramah, when he fought against Hazael king of Syria. And Ahaziah the son of Jehoram, king of Judah, went down to see Joram the son of Ahab in Jezreel, because he was sick.
14:1 "Let not your heart be troubled; you believe in God, believe also in Me. 14:2 "In My Father's house are many mansions; if it were not so, I would have told you. I go to prepare a place for you. 14:3 "And if I go and prepare a place for you, I will come again and receive you to Myself; that where I am, there you may be also. 14:4 "And where I go you know, and the way you know." 14:5 Thomas said to Him, "Lord, we do not know where You are going, and how can we know the way?" 14:6 Jesus said to him, "I am the way, the truth, and the life. No one comes to the Father except through Me. 14:7 "If you had known Me, you would have known My Father also; and from now on you know Him and have seen Him." 14:8 Philip said to Him, "Lord, show us the Father, and it is sufficient for us." 14:9 Jesus said to him, "Have I been with you so long, and yet you have not known Me, Philip? He who has seen Me has seen the Father; so how can you say, 'Show us the Father'? 14:10 "Do you not believe that I am in the Father, and the Father in Me? The words that I speak to you I do not speak on My own authority; but the Father who dwells in Me does the works. 14:11 "Believe Me that I am in the Father and the Father in Me, or else believe Me for the sake of the works themselves. 14:12 "Most assuredly, I say to you, he who believes in Me, the works that I do he will do also; and greater works than these he will do, because I go to My Father. 14:13 "And whatever you ask in My name, that I will do, that the Father may be glorified in the Son. 14:14 "If you ask anything in My name, I will do it. 14:15 "If you love Me, keep My commandments. 14:16 "And I will pray the Father, and He will give you another Helper, that He may abide with you forever- 14:17 "the Spirit of truth, whom the world cannot receive, because it neither sees Him nor knows Him; but you know Him, for He dwells with you and will be in you.


New Riverpro 420 destined for Austrailia User last replied: 5 years ago. No replies since.
CHANGES TO THE WORKSHOP User last replied: 5 years ago. No replies since.
Today Friday 28th June Staff Sick User last replied: 5 years ago. No replies since.
Hamilton 141 MK3 for sale User last replied: 6 years ago. No replies since.
ANYONE GOING FROM CHRISTCHURCH TO CROMWELL? User last replied: 6 years ago. No replies since.
JET BOAT ENGINEER VACANCY User last replied: 7 years ago. No replies since.
Truck Driver Wanted User last replied: 7 years ago. No replies since.
super boaters come south User last replied: 7 years ago. No replies since.
Anyone heading to Hawea/Wanaka? User last replied: 7 years ago. No replies since.
Trip to the lake User last replied: 8 years ago. No replies since.
Stainless Steel Fittings and Fasteners User last replied: 9 years ago. No replies since.
Another New Scott Boat User last replied: 9 years ago. No replies since.
JET BOAT TEST User last replied: 9 years ago. No replies since.
CHANGES TO THE WORKSHOP Started: 5 years ago Most recent reply: 5 years ago.
Today Friday 28th June Staff Sick Started: 5 years ago Most recent reply: 5 years ago.
Email from Harris Marine Started: 6 years ago Most recent reply: 6 years ago.
Harris Marine Jet Boat Products Started: 10 years ago Most recent reply: 6 years ago.
JET BOAT ENGINEER VACANCY Started: 7 years ago Most recent reply: 7 years ago.
Frisbie Jetboating Started: 7 years ago Most recent reply: 7 years ago.
Truck Driver Wanted Started: 7 years ago No replies.
Hunter River Started: 9 years ago Most recent reply: 8 years ago.
Workshop Updates Started: 10 years ago Most recent reply: 9 years ago.
Merry Christmas Everyone Started: 9 years ago Most recent reply: 9 years ago.
Stainless Steel Fittings and Fasteners Started: 9 years ago Most recent reply: 9 years ago.
Website Specials Started: 9 years ago Most recent reply: 9 years ago.
Slight change to your view on web board Started: 10 years ago No replies.
Day 1 Winter Boating Rally Series - Waimak Started: 10 years ago Most recent reply: 10 years ago.
Lake Trip 8th March Started: 10 years ago Most recent reply: 10 years ago.
Thank You Started: 10 years ago Most recent reply: 10 years ago.
Changing Your Web Board Password Started: 10 years ago No replies.
Jet Boat Torque Started: 10 years ago Most recent reply: 10 years ago.
One for the Jet Boaters Wife Started: 10 years ago Most recent reply: 10 years ago.


text:
HomeAlbums /Chasing Honeybees
Chasing Honeybees
Clip My Wings
Just Tell Me
The Moonlight Flood
And Then He Kissed Me
About Chasing Honeybees
'Chasing Honeybees' is a welcome progression of the pop genre, with nods to the pop music of the 60's (including a modern update of the Phil Spector classic 'And Then He Kissed Me'), 80's shoegaze artists like The Cocteau Twins', post-dubstep and R'N'B, with songs that drift serenely between heartache and ecstasy. "Shoegaze had a big impact on me – Kevin Shields is one of my favourite producers", says Peter. "I'm also really inspired by Phil Spector, I love his dedication to finding the 'perfect' pop track."
The music still retains the trademark lush production that Stumbleine is noted for, with strong melody lines and compelling lyrics penned by Violet Skies.
With Violet now involved in the songwriting, the likes of 'Clip My Wings' and 'Just Tell Me' sparkle and smoulder. Peter admits she's given Stumbleine a face and stamped his music with her personality. "She makes the music stand out and has opened the door to a wider audience," he says.
The collaboration has been so productive that a full-length follow-up album is scheduled for release in April 2014. "These five tracks give a good indication of what's to come – I've got more aces lined up for the album. I've pushed myself much harder over the past year to create something a bit different", says Peter.
With 'Chasing Honeybees', Peter has added Violet's vitality to the dreamy essence of Stumbleine and the results are breathtaking.
www.facebook.com/stumbleineuk
http://soundcloud.com/stumbleineuk
http://stumbleine.bandcamp.com
http://iamvioletskies.tumblr.com
www.facebook.com/iamvioletskies
http://soundcloud.com/iamvioletskies
Stumbleine
Stumbleine Feat. Violet Skies' debut album 'Dissolver' to be released on April 21st
Stumbleine and Violet Skies team up for 'Chasing Honeybees' EP


text:
package io.resourcepool.dashboard.dao;

import io.resourcepool.dashboard.property.DashboardProperties;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

import javax.annotation.PostConstruct;
import java.io.IOException;
import java.nio.file.FileSystem;
import java.nio.file.Files;
import java.nio.file.Path;

/**
 * @author Loïc Ortola on 07/06/2016.
 */
@Component
public class DaoInitializer {

    private static final Logger LOGGER = LoggerFactory.getLogger(DaoInitializer.class);

    @Autowired
    private FileSystem fs;

    @Autowired
    private DashboardProperties props;

    /**
     * Create base directories if not exist.
     */
    @PostConstruct
    public void init() {
        Path dbPath = fs.getPath(props.getBasePath());
        if (!Files.exists(dbPath)) {
            try {
                LOGGER.warn("Dashboard database path does not exist: {}. It will be created.", dbPath.toString());
                Files.createDirectories(dbPath);
            } catch (IOException e) {
                String err = "The dashboard database path does not exist. Please check your application properties";
                LOGGER.error(err);
                throw new IllegalStateException(err);
            }
        }

        Path dbRes = fs.getPath(props.getBaseResources());
        if (!Files.exists(dbRes)) {
            try {
                LOGGER.warn("Dashboard resources path does not exist: {}. It will be created.", dbRes.toString());
                Files.createDirectories(dbRes);
            } catch (IOException e) {
                String err = "The dashboard resources path does not exist. Please check your application properties";
                LOGGER.error(err);
                throw new IllegalStateException(err);
            }
        }

        createEntityDbs(dbPath, BundleDao.ENTITY_NAME);
        createEntityDbs(dbPath, MediaDao.ENTITY_NAME);
        createEntityDbs(dbPath, RevisionDao.ENTITY_NAME);
        createEntityDbs(dbPath, DeviceDao.ENTITY_NAME);
        createEntityDbs(dbPath, FeedDao.ENTITY_NAME);

    }

    private void createEntityDbs(Path basePath, String entity) {
        Path p = basePath.resolve(entity);
        if (!Files.exists(p)) {
            try {
                Files.createDirectory(p);
            } catch (IOException e) {
                String err = "The database failed to save a directory. Please check you have the right permissions";
                LOGGER.error(err);
                throw new IllegalStateException(err);
            }
        }

    }
}

redpajama_set_name: RedPajamaGithub