DITA XML.org is the official community gathering place and information resource for the DITA OASIS Standard, an XML architecture for designing, writing, managing, and publishing information. We encourage you to contribute content to this site.

Test: OASIS Security Services Technical Committee

Announcements:

29-Sep-2005: The individual SAML V2.0 schema files are now available from persistent URLs of the form " http://docs.oasis-open.org/security/saml/v2.0/...". They are all linked from the SAML V2.0 and Post-V2.0 Information section below.

16-Aug-2005: The Liberty Alliance ran a SAML V2.0 interoperability testing session, which was successfully completed by eight companies.

Overview:

SAML, developed by the Security Services Technical Committee of OASIS, is an XML-based framework for communicating user authentication, entitlement, and attribute information. As its name suggests, SAML allows business entities to make assertions regarding the identity, attributes, and entitlements of a subject (an entity that is often a human user) to other entities, such as a partner company or another enterprise application.

For more information, see the TC Charter and FAQ

Subcommittees:
The SSTC has a SAML Adoption Subcommittee. Technical Work Produced by the Committee:
External Resources:

Although not produced by the SSTC, the following information offers useful insights into its work:

Namespaces when Specializing

To make it easier for information architects who are creating specializations, it helps to have guidelines for specializers.

This guideline speaks in favor of creating a distinctive namespace for the new identifiers in a specialized module. It explains how to do so, and some of the consequences.

The content is based on an e-mail message from Eliot Kimber on February 8, 2006 to the mailing list of the OASIS DITA Technical Committee. Note: this was written quickly, for a language design discussion. Suggestion: edit for a less conversational style.

Read more

Guidelines for Specializers

These guidelines are primarily for information architects who are considering adding to the pool of DITA Specializations. Please add your own suggestions, marking with "Suggestion:" any contributions that you believe the community might need to come to consensus on.

Several categories of information are relevant:

  • What a specializer needs to know about modules in DITA
  • Where existing modules are catalogued

Some special topics are also provided:

 

dsflkjs

ksjfd

Read more

Blast Radius

"While DITA was conceived for tech pubs, its benefits make it well-suited for other types of content, particularly the kinds of granular, customer-facing content that we typically see on the web.   For example, product or services descriptions, reviews, and FAQs are inherently topic-oriented, but today are implemented in ad hoc or proprietary formats. Companies can benefit using DITA specializations for these types of content through streamlined flow of content within and across enterprises and between systems, and the lower costs of localization.  And because of these benefits, we expect to see DITA applied to a number of scenarios, such as e-Learning, CRM, and e-Service.  We may even see industry-specific DITA specializations for enabling unstructured content interchange between trading partners, such as the syndication of product descriptions between manufacturers and retailers."

-- Paul Wlodarczyk, Director, ECM Strategy, Blast Radius Inc.

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I