A schema can extend and override elements of another schema. Because of this, schemas form a tree structure (more precisely a forest). @author Jean-Paul Vetterli @version 1.0.0
Schemas are generally specified in an XML file which is then parsed with SchemaParser.
Schemas are used by the GXP compiler to do input vaidation (for example, checking that an attribute really exists) and also for providing other special knowledge about attributes and elements. (eg: which attributes are boolean, and what doctypes are supported)
Most GXP users will probably not need to write schemas. Only one schema is required per output format. If you feel the urge to write a schema, first investigate to see if someone has already written one for the same language.
Specifies a custom KML schema that is used to add custom data to KML Features. The "id" attribute is required and must be unique within the KML file.
<Schema name="string" id="ID"> <SimpleField type="string" name="string"> <displayName>...</displayName> <!-- string --> </SimpleField> </Schema>Extends: @see : This is a root element. Contained By: @see :
A schema may be one of:
This is very much provisional; in the future will be more control for validation (i.e, controlling the number of occurances), and support for analogs of W3C SChema sequence and choice. The excess flexibility here forces some validation into element objects (the objects created from the {@link org.apache.hivemind.schema.Rule}s within the {@link org.apache.hivemind.schema.ElementModel}s). @author Howard Lewis Ship
org.apache.ws.commons.schema.XmlSchema. For applications that use other representations for XML Schema content, it also provides a reference to the org.apache.woden.XMLElement object that wraps the underlying <xs:schema> or <xs:import> element. It also indicates whether the schema is 'referenceable' by the surrounding WSDL document, as defined by the schema referenceability rules in the WSDL 2.0 spec. NOTE: non-XML type systems like DTD are not handled by this interface. They must be handled by WSDL 2.0 extension mechanisms.
TODO Need to determine if this interface is suitable for use with other xml-based schema types like Relax NG or if some type of schema extension mechanism is required.
@author John Kaputin (jkaputin@apache.org)
Interface of a database schema.
@author Jochen WiedmannThese methods are often used for implementation the convience methods such as FeatureType.getAttributeCount(), although they may be used directly with any FeatureType.
These schema methods are based on the *complete* picture indicated by a FeatureType and its ancestors. Many of these methods are focused on the derivation of AttribtueTypes during an override.
@see FeatureTypes @see FeatureType @author Jody Garnett @since 2.1.0 @deprecated This helper class was for the old feature model; please use FeatureTypes @source $URL$This Interface is intended to represent the public portion of an XML Schema. By public portion, I mean the portion of the Schema which can be included in an instance document, or imported into another Schema.
The distinction between the public portion of a XML Schema and the entire XML Schema is or particular important when comparing, or printing two XML Schemas. This interface does is intended to provide enough information to re-create the original Schema (note the lack or annotations as an example). This interface is however intended to provide functional semantic equivalence. By this is mean that two XML Schemas represented using this interface should have the same SET of declarations. There is no guarantee that the Schema represented matches the original document with respect to orderwithin the sets, except where order is explicitly defined (Sequence, Choice).
This method must be inplemented within extensions: public static Schema getInstance();. It will be used by the Schema factory to load the required extensions into memory.
@author dzwiers www.refractions.net @source $URL$A Schema belongs to a {@link Catalog} and contains a number of{@link Cube}s and shared {@link Dimension}s. @author jhyde @version $Id: Schema.java 315 2010-05-29 00:56:11Z jhyde $ @since Oct 13, 2006
The intention of a schema is to provide a resuable set of attribute types. These types are used when building attribute instances.
@author Jody Garnett, Refractions Research, Inc. @author Justin Deoliveira, The Open Planning Project @source $URL$A schema as defined by the Open mHealth specification.
This class is immutable.
@author John JenkinsThe following features are implemented:
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |