Rddl

From zedwiki

The current rddl documents seem to describe the following types of information:

The specification with which the profile complies: http://www.rddl.org/purposes.htm#normative-reference

Normative schema http://www.rddl.org/purposes#schema-validation

Prior version http://www.rddl.org/purposes#prior-version

Non-normative software module (schema) http://www.rddl.org/purposes#software-module

CSS http://www.isi.edu/in-notes/iana/assignments/media-types/text/css

Informative reference http://www.rddl.org/purposes.htm#non-normative-reference

Transformations To ZedAi? From ZedAi? http://www.w3.org/1999/XSL/Transform

OASIS catalog urn:oasis:names:tc:entity:xmlns:xml:catalog

Zip archive of the spec, available for download: http://www.rddl.org/purposes#software-package

A list of what we would need (not looking at RDDL) [MG]

• Expressions of compliance
  • references to external normative specifications (such as main zedpsec)
  • internal normative prose (a compliant processing agent must...)

• Formal name

• Current version (of the profile/feature, not the document)

• Link to previous version

• Link to next version (in case we decide to interalize that information), another option is:
• statement whether this is the latest version (of the profile/feature) or not.

• internal informative prose

• normative schema (can be of types rng, xsd, sch, nvdl)
• normative schema module (same type constraint)

• informative schema(can be of types rng, xsd, sch, nvdl)
• informative schema module (same type constraint)

• Which is the default vocab

• documentation (which may be inlined in the resource directory, or just linked from there)

• (XSLT) transformation of instances of this profile to format X
• (XSLT) transformation from format X to instances of this profile

(RDDL doesnt handle the transformation direction distinction IIRC)

• (CSS) styling of instances of this profile

• Other normative references?

• Other informative references; software, related specifications...