Consensuality - Trusting Online Environments
Consensuality is the active collaboration and cooperation for the
self-benefit, join aim, profit, pleasure and well-being of all
concerned. In the case of social and business netwoks, this consent
often includes that of people not directly involved - primary partners,
voluntaries and other parties are affected by agreements, sometimes not
written, not signed, ad-hoc established and based on common sense.
Defining consent can sometimes be tricky. If someone consents under
pressure, we don't think that meets the "active collaboration"
criterion. And you can't consent to something you don't know about:
"Well you didn't say I couldn't send you an email when you agreed to
participate" .
Studies examine chemistry instruction from a perspective based
primarily on John Ziman's communal knowledge model for science. Several
lessons by three different teachers at three different schools were
observed and audiotaped. Data were examined to demonstrate the
occurrence of certain specific pedagogic tactics embodied in some
metacommunicative teacher utterances within the chemistry classroom
teaching/learning discourse. These tactics reflect teachers' concerns
for: (1) consensuality of their discourse; (2) consensibility of their
teaching utterances; (3) commonality of the frame of reference with
their students; and (4) the commensurability of the subject of their
teaching discourse with course requirements, curricular structure, and
nature of the discipline.
In addition, the study relates these four tactics to four analogous
pedagogic concerns on the part of a teacher. In turn, these are
developed as four constructs for use by researchers or practitioners in
recasting the original "pedagogic problematic," namely, the difficulty
many students experience in learning chemistry. The problem is
reinterpreted from the point of view of pedagogic consensuality,
consensibility, commonality of frame of reference, and
commensurability. The nature of these findings is discussed, and their
implications for practice and as a new focus for teacher education are
outlined.
Consensuality is the active collaboration for the mutual benefir and
well-being of all concerned. In the case of social networks, this
consent often includes that of people far away are affected by
non-written and non-signed contracts and based on mutual coomitments
for a join aim.
European Technological Platform in Trust. TRUST ONLINE. Trust for consensuality is in reference to Web and Network based.
Building Trust: Trust is an essential basis for a productive,
satisfying and fun business information and communication environment.
Suspicion corrodes working relationships and undermines people’s
confidence in themselves and their colleagues. Leaders need to offer
trust, since the only way to prove whether others are trustworthy or
not is by experience. Organizational leaders have nearly all the power,
so it’s usually up to them to set the ball rolling. Trust is always a
gift. As a leader, you need to be the one who begins the giving process.
What does it take to initiate a process of trust?
Courage, certainly, and the willingness to take a risk. Employees who
have been denied trust, maybe for years, don’t find it easy to accept
responsibility in an instant. You’ll need to help them rebuild their
confidence in themselves. You’ll probably have to deal with more than
few cynics as well: people who claim to approve the idea of trust, yet
constantly find reasons why it shouldn’t be this person, in this
circumstance, at this time..
CONSENSUALITY
Consent: Compliance with or in approval of what is done or proposed by another.
We talk about consent a lot. There is a very good reason for that. The
line between D/s and abuse is consent. Non-consensual control,
manipulation, application of pain or direction is abuse or assault.
However, as in most things the meaning of consent is far from simple.
When a submissive is new in their exploration of the D/s and BDSM
worlds they are simply virgins. They have no personal experience of
many or most of the things which now confront them. What they do have
is ideas, thoughts, hopes, dreams, feelings, beliefs and desires. These
may or may not apply in reality. A person can 'think' they will enjoy
something only to find that in reality they do not. So we are
immediately faced with a dilemma.
As the community becomes more open and readily accessible the numbers
of new Dominant's and submissives is rapidly increasing. With this
increase comes an increasing number of problems.
It is impossible to truthfully consent to something you have never
experienced. You can consent to trying something, but cannot accurately
state that you will enjoy or like it until after it occurs. This means
that in some ways the consent offered is not a blanket approval of
action. In many cases it really means that the submissive will
'consider' trying something to see if they enjoy it. From the
Dominant's standpoint this is treading on shaky ground.
Many new Dominant's and submissives spend a great deal of time looking
for and searching out someone (frequently on the Internet community).
Often they find potential partners who live at some distance from them
physically. This can lead to protracted long distance cyber and phone
relationships. These types of communication can foster the building up
of scenario's, ideas and expectations.
When the two manage to arrange a meeting they bring with them all of
the baggage which has accumulated from their interaction. Many vacate
simple safety issues in lieu of their 'feeling' of everything being
perfect. They are SO eager to jump in that they want to play within
hours of a first meeting. Sometimes they go so far as to pre-scene this
meeting based on the 'ideas' that they have allowed to become 'limits'.
It is not terribly uncommon for a new submissive to agree to a first
meeting which places her in a foreign state, in a motel room, naked,
kneeling and waiting for 'her Master' to show up.
In addition the new Dominant comes prepared with the 'expectations' of
the submissive to perform this 'scene'. In many cases this may be the
very first scene the Dominant has ever tried and s/he may have or feel
extreme pressure to 'meet the submissives need'. This can be a setup
for true disaster.
This week the news was filled with an ongoing court case in NY wherein
a woman is suing a man whom she claims raped her. She made contact with
him on the Internet and engaged in extensive correspondence (some of
which is court record), and phone conversations. After 5-6 months they
arranged such a meeting. They engaged 'in-scene' for nearly 20 hours.
Afterwards she accused him of rape, rough sex, forcible sodomy,
assault, battery, various kinds of bondage and torture and a few other
things. She agreed that she talked to him about her interest in BDSM
but she claims that she was 'interested in him' and 'played along'
because she liked him. She acknowledges voluntarily meeting him.
This is important. Early, heavy scening with an unknown person forces
assumptions of consent on both people. A submissive can and may feel
pressured to go quite far in order not to displease their new Dominant.
They may agree to things under duress or contact pressure. A Dominant
can and may feel pressured to perform to the 'ideas' they have fostered
through prior communication. They can be a total novice doing things
they are not really prepared for. It is simply impossible to 'know' a
person you have just met. You cannot know their body language, the
suggestions and subtle signals necessary to truly read someone's
responses. This type of pre-scene creation can and does kill people. It
can create situations much like I just described which are becoming
much more common.
Many people believe that 'consent' is a license. That it gives them a
blanket permission to 'do' what they want to do. This is simply not
true. Consent at the beginning of a relationship is more the 'option'
to explore further. It offers no guarantee to the Dominant or
submissive that they will be held blameless for what occurs. Those that
engage in sudden intense sceneing willfully place their reputations,
careers, family, and life on the line. When you are dealing with a
stranger you cannot guess how they will react 3 days after a scene when
they bottom out and you are not there. Remorse, pain, regret,
embarrassment, shame, anger, feelings of diminished self respect and
outright rage can and will drive people to take actions against this
person they have 'consented' to scene with.
Those actions can reveal the other persons kink to their entire
community. The person may lose a spouse, children, job, respectability
or more or less everything including the risk of imprisonment all to
meet the needs of instant gratification. It simply is not worth it.
Initial limits are just that...initial. They should be expected to
change, evolve and alter over years and experiences. They are merely a
way of offering an 'idea' of the range of interest that the individual
believes they are interested in pursuing. Consent can best be
considered to be fluid. In addition to the above, it should be noted
that everyone is not the same every day. There are days when consent to
the range of play will be much wider than on other days. These
variables can be effected by mood, health, stress and many other
things. Assumptions that consent is constant can and will lead to
problems.
The pollution of information (INFOLLUTION) is the excess of information
and messaging that reduce the quality of the initial information or the
communicatio
All start with an unique user semantic-profile, maybe associated to an
unique IP Identificator (linked to Ipv6 IPs). To have a unique [ULICA]
user micro-profile accessible, feasible, always up-to-date which allow
the preservation of the user privacy and control of personal data and
provate information, the identification, authentication, authorisation,
localisation and characterisation (accessibility/usability defined by
context and user) for trusting digital relationships and enhancing the
network Consensuality for enabling collaboration and improve the
results of social, industrial and business distributed and diverse
virtual networks.
Federation key to NETWORK SECURITY SERVICES
function MM_jumpMenu(targ,selObj,restore){ //v3.0 var test = "/adtran/solutionDetails.jsp?subject=" eval(targ+".location='"+test+"'+'"+selObj.options[selObj.selectedIndex].value+"'") if (restore) selObj.selectedIndex=0; }Heterogeneity rules in network security environments. In the stubbornly multiorganizational, multidomain and multivendor world of Web services, the political concept of "federation" takes on new meaning. Federation describes scenarios in which no one group or organization manages all users and resources in a distributed application environment. Instead, administrators in diverse domains must manage local security policies that support mutually beneficial transactions among their respective spheres of operation.
The term federation derives from the Latin word for trust. In the world of distributed network services, the term refers to the need for trust agreements among decentralized security and policy domains. Federation lets access-management functions span diverse organizations, business units, sites, platforms, products and applications. Federation requires that an organization trust each trading partner to authenticate its own users' identities. In a federated environment, a user can log on to his home domain and access resources transparently in external domains, such as those managed by customers or suppliers, subject to various policies defined by home and external administrators.
You increasingly will see the term federation used with a new security standard, the XML-based Security Assertions Markup Language (SAML) 1.0, which is nearing ratification by the Organization for the Advancement of Structured Information Standards (OASIS). Web access-management vendors such as IBM/Tivoli, RSA Security/Securant, Netegrity, Oblix, Entegrity, Entrust Technologies and Sun/iPlanet have rallied around SAML 1.0 as a means for establishing standards-based interoperability among their products. As these vendors sell their wares into corporations large and small, SAML-based federation will be critical to knitting organizations' diverse access-management environments into unified business-to-business supply chains.
So what precisely is SAML 1.0? At its heart, the standard defines XML/Simple Object Access Protocol-based protocol interactions that support real-time authentication and authorization across federated Web services environments. The standard defines request and response messages that security domains use to exchange authentication, attribute and authorization information in the form of trust-assertion messages about named users and resources. Users log on to their home domains through authentication techniques such as ID/password or Kerberos, and this authentication is communicated to a federated destination site through a SAML authentication assertion.
In coming months, SAML-based products will be promoted so aggressively that we'll have to remind ourselves of the standard's immaturity, limited commercial availability and functional constraints. For starters, SAML 1.0 is not yet a ratified OASIS standard and won't likely attain that status until mid- to late summer. In addition, there are few SAML-enabled Web access-management products on the market, though standards-compliant products will become increasingly available over the coming year.
But an even more pressing concern is the need for SAML deployment guidelines. Web access-management vendors will need to help users implement SAML federation profiles without getting lost in the sundry technical options that the standard allows - or doesn't address at all.
During the next several months, Web access-management vendors will address interoperability issues among their SAML 1.0 implementations. If all goes well with initial interoperability testing, expect to see some commercial SAML 1.0-enabled products this year. But it may take several years before SAML-based products mature to the point where users can implement federated single sign-on and authorization scenarios without having to write excessive amounts of custom code to bridge divergent vendor implementations of the core standard.
In any event, we can't afford to ignore SAML. Federation is no fad, and SAML will become a key standard for bridging security domains across Web services environments.

:: 



WEKOMS 

