Knowledge Architect/Reference/Glossary/R

Resource Description Framework, a W3C semantic web standard.

Important logic principle for processing nested structures. Resources and processes are natural nested recursive structures and each process orchestrates its sub-processes through its multi-level schedule relation resource.

One of the main resource  access types, determining resource recycling capabilities that include retiring, as well as purge and archiving (e.g. purge) behaviors.

Background color used for modeling  schedule  resources. Red is the hottest primary color, and time-based resources (schedules) are the highest business priority resource archetype.

One of the main resource  access types, determining resource referencing capabilities that include overview listing and reading (e.g. list, TOC, summary) behaviors.

The reference monitor is a DNAOS run-time service set responsible for ensuring that all references and accesses conform to corresponding defined entitlement and for logging and tracking  Resources access.

Direct References are universal unique identifiers for the respective referenced Resources, while other references are Indirect (e.g. query).

Addition of details. Qualification.

A process to register users, visitors, administrators, partners, suppliers. etc. to membership, activities, and resources.

resource type used to define and qualify an association from subject resources to object resources; relations are qualified, identified, and classified. As well, they provide references to both source (e.g. Subject, From) and destination (e.g. Object, To) resources. Some basic relation types include, for example, access, event, schedule, event, process, and case relations.

REMMS (Resource  Entitlement  Modeling, Management, and Sharing) standards proposal, also referred to as universal REMMS, are a DNAOS inspired set of standard specifications proposed to support information and knowledge sharing securely, universally. As entitlement is a type of relation between resources, REMMS specify compatibility for modeling, managing, and sharing information as resources linked by relations.

Laid-out and formatted XPath  application resources reports, generated by a report services engine, from advanced XQuery, SQL  queries, as well as layout information.

Identifiable quality set. Resource qualities can also define resource behavior. Resources are also defined as any piece of identified and classified information. Anything or any information that anyone defines, including application resources, virtual resources, profiles, datasets, and data-structures; resources, content, and profiles, analyzed, processed, transformed and persisted by applications; distributed  application resources (e.g. systems, humans, content, relations, business, schedules, processes). Resources are commonly split between entities and relations.

One of the 10 main resource  access types, determining resource retiring capabilities that include modification, as well as deletion (e.g. delete) behaviors.

Rights are granted with role assignments (access  resources). See also Privileges.

Risk is a function of the likelihood or probability of threat-sources exercising potential resource vulnerabilities, as well as the related potential impacts on associated resources (e.g. systems, organizations). Risk should be managed.

Risk assessment is a risk management operation that typically includes: resource characterization, threat and vulnerability identification, likelihood or probability determination, control and impact analysis, risk  estimation, as well as recommendations and documentation.

Risk management assesses and mitigates  risk, as well as evaluate and optimize risk assessment and mitigation.

Risk mitigation is a risk management operation that typically uses planning, research, and acknowledgment to optimize risk assumption, avoidance, limitation, and transference (e.g. accept, avoid, limit, and transfer).

Relation  quality defining the access  rights and responsibilities (interaction) between resources (e.g. self or others). A basic knowledge archetype, typically modeled with a yellow background.

A basic modeling layout operation, available to DNAOS rich graphical SOA client  applications and users, to selectively move and turn forward or backward around an axis, application resources, virtual  profiles, and business processes. see also Auto-Layout and Zoom.

A logical grouping structure resource typically used in forms, as well as layout and formatting applications. Rows are often mapped to corresponding form, table, or panel rows. Rows typically contain cell resources.

A common news feed and blog protocol, which is progressively being replaced by the Atom protocol, which is the DNAOS built-in news feed and blog protocol. DNAOS can import and export RSS feeds.

Primary quality components, rules are typically used to express context-based policies. They are theoretically executable statements or instructions defining typically context-related conditions, rights, privileges, and responsibilities. Rules are also used in schema to define resource  metadata. Because rules apply to resources that form context for the rules, they are also often referred to as context rules. Rules are used for many different purposes including access control, Dynamic Key Indicators (DKIs), page layout, report queries. DNAOS rules are executable context aware instructions, typically based on XPath standards. Many sophisticated queries can define rules often using XQuery and SQL languages. RuleML and SBVR are also rule languages.

Previous Top Next