Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
Wilmington, North Carolina once had a thriving Black middle class and an elected interracial government. In 1898 white supremacists used violence to overthrow that government, kill Black residents and drive many others from the city.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
Naked objects is an architectural pattern used in software engineering. It is defined by three principles:
The naked object pattern's innovative feature arises by combining the 1st and 2nd principles into a 3rd principle:
The naked objects pattern was first described formally in Richard Pawson's PhD thesis[1] which includes investigation of antecedents and inspirations for the pattern including, for example, the Morphic user interface.
The first complete open source framework to have implemented the pattern was named Naked Objects.[2] In 2021, Pawson announced that he had subsequently applied the same pattern to the Functional Programming programming paradigm, as an alternative to the object-oriented programming paradigm, creating a variant of the Naked Objects framework called Naked Functions.[3]
Pawson's thesis[1] claims four benefits for the pattern:
The Department of Social Protection (DSP) (formerly known as the Department for Social and Family Affairs) in Ireland has built a suite of enterprise applications using the naked objects pattern. As part of its Service Delivery Modernisation (SDM) programme, the DSP designed a new enterprise architecture both to meet its planned new business requirements and to provide greater agility over the longer term. The naked objects pattern forms a key element of the SDM architecture.[4] In November 2002, the DSP went live with a new application to replace its existing system for the administration of child benefit. This is believed to be the first operational application of the naked objects pattern, anywhere. The DSP's experience in building this first application, including the reactions of users to the radical user interface is documented extensively in Pawson's thesis,[1] and more recently in a presentation at QCon London 2011.[5]
One of the more striking aspects of the DSP experience was the way that the Naked Objects technique permitted re-use very actively. Once a domain object, such as a Customer, had been defined for one 'application' it could be (has been) readily adapted with the minimum of tweaking and addition for use elsewhere. This suggests that the approach could become a favourite in government circles, where re-use is seen as a powerful technique for breaking down siloed systems. The UK 'Transformational Government' policy is particularly keen to see re-use become a standard requirement of new government systems, both consuming other governmental system components and making new ones available for others to use. This re-use is often seen in terms of services, but objects could be an equally powerful approach.
The DSP's initial 'Naked Object Architecture' was developed by an external contractor,[6] but the architecture was subsequently redeveloped around the Naked Objects Framework which now forms the basis for future application development, as confirmed in the request for tenders for a four-year programme of further applications to be built using naked objects.[7]
The naked objects pattern has relevance to several other disciplines and/or trends, including:
Object–relational mapping, object databases, and object persistence are all concerned with eliminating the need to write a conventional Data access layer underneath the domain objects. These patterns are complementary and potentially synergistic with the naked objects pattern, which is concerned with eliminating the need to write layers above the domain objects.
Naked objects is compatible with the trend towards agile development methodologies in many different ways, but especially to fine-grained iterative development. The DSP experience (described above) was probably also the largest application of agile software development techniques within a public-sector organization, worldwide.[8]
Domain-driven design is the idea that an evolving domain (object) model should be used as a mechanism to help explore requirements rather than vice versa. The fact that a naked object system forces direct correspondence between the user interface and the domain model makes it easier to attempt domain-driven design, and makes the benefits more visible.[9]
Although naked objects does not conform to the strict definition of MDA, it shares many of the same goals. Dan Haywood has argued that naked objects is a more effective approach to achieving those goals.[10]
A standard for creating a RESTful interface from a domain object model. Though the Restful Objects specification does not state that the interface must be generated reflective from the domain model, that possibility exists.
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Naked objects is an architectural pattern used in software engineering. It is defined by three principles: The naked object pattern's innovative feature arises by combining the 1st and 2nd principles into a 3rd principle: The naked objects pattern was first described formally in Richard Pawson's PhD thesis which includes investigation of antecedents and inspirations for the pattern including, for example, the Morphic user interface. The first complete open source framework to have implemented the pattern was named Naked Objects. In 2021, Pawson announced that he had subsequently applied the same pattern to the Functional Programming programming paradigm, as an alternative to the object-oriented programming paradigm, creating a variant of the Naked Objects framework called Naked Functions.
Naked Objects for .NET or Naked Objects MVC is a software framework that builds upon the ASP.NET MVC framework. As the name suggests, the framework synthesizes two architectural patterns: naked objects and model–view–controller (MVC). These two patterns have been considered as antithetical. However, Trygve Reenskaug (the inventor of the MVC pattern) has made it clear that he does not see it that way, in his foreword to Richard Pawson's PhD thesis on the Naked Objects pattern. The Naked Objects MVC framework will take a domain model (written as Plain Old CLR Objects) and render it as a complete HTML application without the need for writing any user interface code - by means of a small set of generic View and Controller classes. The framework uses reflection rather than code generation. The developer may then choose to create customised Views and/or Controllers, using standard ASP.NET MVC patterns, for use where the generic user interface is not suitable.
In general relativity, a naked singularity is a hypothetical gravitational singularity without an event horizon. When there exists at least one causal geodesic that, in the future, extends either to an observer at infinity or to an observer comoving with the collapsing cloud, and in the past terminates at the gravitational singularity, then that singularity is referred to as a naked singularity. In a black hole, the singularity is completely enclosed by a boundary known as the event horizon, inside which the curvature of spacetime caused by the singularity is so strong that light cannot escape. Hence, objects inside the event horizon—including the singularity itself—cannot be observed directly. In contrast, a naked singularity would be observable. The theoretical existence of naked singularities is important because their existence would mean that it would be possible to observe the collapse of an object to infinite density. It would also cause foundational problems for general relativity, because general relativity cannot make predictions about the evolution of spacetime near a singularity. In generic black holes, this is not a problem, as an outside viewer cannot observe the spacetime within the event horizon. Naked singularities have not been observed in nature. Astronomical observations of black holes indicate that their rate of rotation falls below the threshold to produce a naked singularity (spin parameter 1). GRS 1915+105 comes closest to the limit, with a spin parameter of 0.82-1.00. It is hinted that GRO J1655−40 could be a naked singularity. According to the cosmic censorship hypothesis, gravitational singularities may not be observable. If loop quantum gravity is correct, naked singularities may be possible in nature.
Naked eye, also called bare eye or unaided eye, is the practice of engaging in visual perception unaided by a magnifying, light-collecting optical instrument, such as a telescope or microscope, or eye protection. In astronomy, the naked eye may be used to observe celestial events and objects visible without equipment, such as conjunctions, passing comets, meteor showers, and the brightest asteroids, including 4 Vesta. Sky lore and various tests demonstrate an impressive variety of phenomena visible to the unaided eye.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Mae Jemison, aboard Space Shuttle Endeavour in 1992.