SADiC: The Semantic API for the Delivery Context

Strong

If you select this mode the CC/PP processor will treat as semantically equivalent all the attribute properties and component types whose definition takes place simultaneously within multiple and different RDF schemas representing subsequent versions of a whole logical vocabulary.  For example, actually there are three versions of the UAProf specification and each one redefines (either extends) the vocabulary defined by the previous versions within a newer namespace.

Weak

If you select this mode the CC/PP processor will consider multiple versions of a vocabulary as different vocabularies tied to different namespaces. However, since in some cases the same vocabulary can be identified by multiple and different  namespace URIs, the processor will manage these cases of vocabulary equivalence by mapping  all the "alias" namespaces to the same vocabulary. For example, the canonical namespace of the vocabulary tied to the first version of the UAProf specification is:
        http://www.wapforum.org/UAPROF/ccppschema-20000405
but this vocabulary is also referenced through one of  the following namespaces:
        http://www.wapforum.org/UAPROF/ccppschema-19991014
        http://www.wapforum.org/UAPROF/ccppschema-20010330
        http://www.wapforum.org/profiles/UAPROF/ccppschema-20010330

Option:

Description:

Processor Behavior:

Regards the validation of the RDF structure through which the value of an attribute property is instanced within a profile, with respect to the structure indicated for the range values of that property by the vocabulary that defines the attribute (e.g., an RDF container or an RDF Literal).

Regards the validation of the data items that populate the structure of the value of an attribute property indicated within a profile,  with respect to the data type indicated for the data items of the range values of that property by the vocabulary that defines the attribute (e.g., a data type representing an integer number). If the attribute range values are not structured (i.e., the values are not to be expressed through an RDF container) then the value of an instance of that attribute property within a profile must contain only one data item that corresponds to the property value itself.

Regards the validation of the data items whose data type represents text values (e.g. the "Literal" data type defined by UAProf). The usefulness of this option arises from the fact that often the constraints imposed by such data types are not strictly respected. For example, the "Literal" data type defined by UAProf constrains the data items of this type to be alphanumeric strings. However, many profiles (also proposed in the UAProf specification itself) indicate as value items of this type strings containing not allowed characters like white spaces or the '*' character.

Regards the validation of the declaration of the profile components and default blocks against the vocabularies that define their RDF type. Furthermore, this option regards the verification that attributes belonging to a certain profile component respect the component constraints defined by a vocabulary.
(Note: be aware that if the RDF type of a profile component is a sub-type of another component type, then such a component is simultaneously of both the two component types and the attributes applicable to components of the parent-type can be asserted for the component of the child-type too. On the contrary, attributes constrained to be applicable for components of the child-type cannot be asserted for a component of the parent-type unless the type of such a component is the child-type itself or a sub-type of this).

If you select this level all the processing information will be printed.

If you select this level only the information on validation faults (both bypassed or that caused actions)
will be printed.

If you select this level only the information on validation faults that caused the ignoring of components
or attributes (or either the aborting of a profile) will be printed.

If you select this level only the information on validation faults that caused the ignoring of components
or the aborting of a profile will be printed.

Do not active this option if one of the profiles you want to process may change dynamically even if it is stored always at the same URL.
(Note:  the processor retrieves a processed profile from the cache only if its creation pattern, including ontology mode and behavior on validation options, matches the current settings. However, when a profile is retrieved from the local cache, the available processing information  is that created when the profile was cached, and, therefore, the printed messages will depend on the log level that was set at that time).

Active this option if you want to be sure that the processing messages refer effectively to the profiles you want to process (and/or if you want to be sure that the processing information that will be printed respects the log level you have selected).

Option:

Description:

When this option is active the processor does not try to retrieve a referenced profile from its local repository but directly tries to fetch it from the Internet. Active this option if one of the profiles you want to process may change dynamically even if it is to be retrieved always from the same URL.

When this option is active the profiles retrieved from the Internet are saved in a local repository for future use. Do not active this option if you do not want that the SADiC instance on this site maintains hard copies of your profiles.