You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by an...@apache.org on 2014/06/27 22:57:03 UTC
svn commit: r1606224 -
/jena/site/trunk/content/documentation/tools/schemagen.mdtext
Author: andy
Date: Fri Jun 27 20:57:02 2014
New Revision: 1606224
URL: http://svn.apache.org/r1606224
Log:
More fixing up \> escapes
Modified:
jena/site/trunk/content/documentation/tools/schemagen.mdtext
Modified: jena/site/trunk/content/documentation/tools/schemagen.mdtext
URL: http://svn.apache.org/viewvc/jena/site/trunk/content/documentation/tools/schemagen.mdtext?rev=1606224&r1=1606223&r2=1606224&view=diff
==============================================================================
--- jena/site/trunk/content/documentation/tools/schemagen.mdtext (original)
+++ jena/site/trunk/content/documentation/tools/schemagen.mdtext Fri Jun 27 20:57:02 2014
@@ -40,7 +40,7 @@ Command line option | RDF config file pr
`--footer <string>` | `sgen:footer` | Template for standard text to add to the end of the file.
`--header <string>` | `sgen:header` | Template for the file header, including the class comment.
`-i <filename>` <br />`-i <url>` | `sgen:input` | Specify the input document to load
-`--include <uri\>` | `sgen:include` | Option for including non-local URI's in vocabulary
+`--include <uri>` | `sgen:include` | Option for including non-local URI's in vocabulary
`--individualsSection <string>` | `sgen:individualsSection` | Section declaration comment for individuals section.
`--individualTemplate <string>` | `sgen:individualTemplate` | Template for writing out declarations of individuals.
`--inference` | `sgen:inference` | Causes the model that loads the document prior to being processed to apply inference rules appropriate to the language. E.g. OWL inference rules will be used on a `.owl` file.
@@ -91,23 +91,23 @@ does is to show an example. Consider the
vocabulary:
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- Â Â Â Â Â Â Â Â xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
- Â Â Â Â Â Â Â Â Â Â Â xmlns="http://example.org/eg#"
- Â Â Â Â Â Â Â Â xml:base="http://example.org/eg">
- Â <rdfs:Class rdf:ID="Dog">
- Â Â Â Â Â <rdfs:comment>A class of canine companions</rdfs:comment>
- Â </rdfs:Class>
- Â <rdf:Property rdf:ID="petName">
- Â Â Â Â Â <rdfs:comment>The name that everyone calls a dog</rdfs:comment>
- Â Â Â Â Â <rdfs:domain rdf:resource="http://example.org/eg#Dog" />
- Â </rdf:Property>
- Â <rdf:Property rdf:ID="kennelName">
- Â Â Â Â Â <rdfs:comment>Posh dogs have a formal name on their KC certificate</rdfs:comment>
- Â </rdf:Property>
- Â <Dog rdf:ID="deputy">
- Â Â Â Â Â <rdfs:comment>Deputy is a particular Dog</rdfs:comment>
- Â Â Â Â Â <kennelName>Deputy Dawg of Chilcompton</kennelName>
- Â </Dog>
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
+ xmlns="http://example.org/eg#"
+ xml:base="http://example.org/eg">
+ <rdfs:Class rdf:ID="Dog">
+ <rdfs:comment>A class of canine companions</rdfs:comment>
+ </rdfs:Class>
+ <rdf:Property rdf:ID="petName">
+ <rdfs:comment>The name that everyone calls a dog</rdfs:comment>
+ <rdfs:domain rdf:resource="http://example.org/eg#Dog" />
+ </rdf:Property>
+ <rdf:Property rdf:ID="kennelName">
+ <rdfs:comment>Posh dogs have a formal name on their KC certificate</rdfs:comment>
+ </rdf:Property>
+ <Dog rdf:ID="deputy">
+ <rdfs:comment>Deputy is a particular Dog</rdfs:comment>
+ <kennelName>Deputy Dawg of Chilcompton</kennelName>
+ </Dog>
</rdf:RDF>
We process this document with a command something like:
@@ -123,27 +123,27 @@ to produce the following generated class
* @author Auto-generated by schemagen on 01 May 2003 21:49
*/
public class Deputy {
- Â Â Â /** <p>The RDF model that holds the vocabulary terms</p> */
- Â Â Â private static Model m_model = ModelFactory.createDefaultModel();
- Â Â Â
- Â Â Â /** <p>The namespace of the vocabulary as a string {@value}</p> */
- Â Â Â public static final String NS = "http://example.org/eg#";
- Â Â Â
- Â Â Â /** <p>The namespace of the vocabulary as a resource {@value}</p> */
- Â Â Â public static final Resource NAMESPACE = m_model.createResource( "http://example.org/eg#" );
- Â Â Â
- Â Â Â /** <p>The name that everyone calls a dog</p> */
- Â Â Â public static final Property petName = m_model.createProperty( "http://example.org/eg#petName" );
- Â Â Â
- Â Â Â /** <p>Posh dogs have a formal name on their KC certificate</p> */
- Â Â Â public static final Property kennelName = m_model.createProperty( "http://example.org/eg#kennelName" );
- Â Â Â
- Â Â Â /** <p>A class of canine companions</p> */
- Â Â Â public static final Resource Dog = m_model.createResource( "http://example.org/eg#Dog" );
- Â Â Â
- Â Â Â /** <p>Deputy is a particular Dog</p> */
- Â Â Â public static final Resource deputy = m_model.createResource( "http://example.org/eg#deputy" );
- Â Â Â
+ /** <p>The RDF model that holds the vocabulary terms</p> */
+ private static Model m_model = ModelFactory.createDefaultModel();
+
+ /** <p>The namespace of the vocabulary as a string {@value}</p> */
+ public static final String NS = "http://example.org/eg#";
+
+ /** <p>The namespace of the vocabulary as a resource {@value}</p> */
+ public static final Resource NAMESPACE = m_model.createResource( "http://example.org/eg#" );
+
+ /** <p>The name that everyone calls a dog</p> */
+ public static final Property petName = m_model.createProperty( "http://example.org/eg#petName" );
+
+ /** <p>Posh dogs have a formal name on their KC certificate</p> */
+ public static final Property kennelName = m_model.createProperty( "http://example.org/eg#kennelName" );
+
+ /** <p>A class of canine companions</p> */
+ public static final Resource Dog = m_model.createResource( "http://example.org/eg#Dog" );
+
+ /** <p>Deputy is a particular Dog</p> */
+ public static final Resource deputy = m_model.createResource( "http://example.org/eg#deputy" );
+
}
Some things to note in this example. All of the named classes,
@@ -172,27 +172,27 @@ to get:
* @author Auto-generated by schemagen on 01 May 2003 22:03
*/
public class Deputy {
- Â Â Â /** <p>The ontology model that holds the vocabulary terms</p> */
- Â Â Â private static OntModel m_model = ModelFactory.createOntologyModel( ProfileRegistry.OWL_LANG );
- Â Â Â
- Â Â Â /** <p>The namespace of the vocabulary as a string {@value}</p> */
- Â Â Â public static final String NS = "http://example.org/eg#";
- Â Â Â
- Â Â Â /** <p>The namespace of the vocabulary as a resource {@value}</p> */
- Â Â Â public static final Resource NAMESPACE = m_model.createResource( "http://example.org/eg#" );
- Â Â Â
- Â Â Â /** <p>The name that everyone calls a dog</p> */
- Â Â Â public static final Property petName = m_model.createProperty( "http://example.org/eg#petName" );
- Â Â Â
- Â Â Â /** <p>Posh dogs have a formal name on their KC certificate</p> */
- Â Â Â public static final Property kennelName = m_model.createProperty( "http://example.org/eg#kennelName" );
- Â Â Â
- Â Â Â /** <p>A class of canine companions</p> */
- Â Â Â public static final OntClass Dog = m_model.createClass( "http://example.org/eg#Dog" );
- Â Â Â
- Â Â Â /** <p>Deputy is a particular Dog</p> */
- Â Â Â public static final Individual deputy = m_model.createIndividual( Dog, "http://example.org/eg#deputy" );
- Â Â Â
+ /** <p>The ontology model that holds the vocabulary terms</p> */
+ private static OntModel m_model = ModelFactory.createOntologyModel( ProfileRegistry.OWL_LANG );
+
+ /** <p>The namespace of the vocabulary as a string {@value}</p> */
+ public static final String NS = "http://example.org/eg#";
+
+ /** <p>The namespace of the vocabulary as a resource {@value}</p> */
+ public static final Resource NAMESPACE = m_model.createResource( "http://example.org/eg#" );
+
+ /** <p>The name that everyone calls a dog</p> */
+ public static final Property petName = m_model.createProperty( "http://example.org/eg#petName" );
+
+ /** <p>Posh dogs have a formal name on their KC certificate</p> */
+ public static final Property kennelName = m_model.createProperty( "http://example.org/eg#kennelName" );
+
+ /** <p>A class of canine companions</p> */
+ public static final OntClass Dog = m_model.createClass( "http://example.org/eg#Dog" );
+
+ /** <p>Deputy is a particular Dog</p> */
+ public static final Individual deputy = m_model.createIndividual( Dog, "http://example.org/eg#deputy" );
+
}
## General principles
@@ -306,7 +306,7 @@ itself is desirable.
|
--- | ---
-**Command line** | `-c <*config-file-path*\>`<br />`-c <*config-file-URL*\>`
+**Command line** | `-c <*config-file-path*>`<br />`-c <*config-file-URL*>`
**Config file** | n/a
The default configuration file name is `schemagen.rdf` in the
@@ -329,7 +329,7 @@ By default it assumes RDF/XML.
|
--- | ---
-**Command line** | `-r <*config-root-URI*\>`
+**Command line** | `-r <*config-root-URI*>`
**Config file** | n/a
It is possible to have more than one set of configuration options
@@ -354,8 +354,8 @@ matches:
|
--- | ---
-**Command line** | `-i <*input-file-path*\>`<br />`-i <*input-URL*\>`
-**Config file** | `<sgen:input rdf:resource="*inputURL*" /\>`
+**Command line** | `-i <*input-file-path*>`<br />`-i <*input-URL*>`
+**Config file** | `<sgen:input rdf:resource="*inputURL*" />`
The only mandatory argument to schemagen is the input document to
process. This can be specified in the configuration file, though
@@ -370,8 +370,8 @@ typing. For other means of automating sc
|
--- | ---
-**Command line** | `-o <*input-file-path*\>`<br />`-o <*output-dir*\>`
-**Config file** | `<sgen:output rdf:datatype="&xsd;string"\>*output-path-or-dir*</sgen:output\>`
+**Command line** | `-o <*input-file-path*>`<br />`-o <*output-dir*>`
+**Config file** | `<sgen:output rdf:datatype="&xsd;string">*output-path-or-dir*</sgen:output>`
Schemagen must know where to write the generated Java file. By
default, the output is written to the standard output. Various
@@ -392,15 +392,15 @@ line endings, use `--dos`.
|
--- | ---
**Command line** | `--dos`
-**Config file** | `<sgen:dos rdf:datatype="&xsd;boolean"\>true</sgen:dos\>`
+**Config file** | `<sgen:dos rdf:datatype="&xsd;boolean">true</sgen:dos>`
### Specifying the class name
|
--- | ---
-**Command line** | `-n <*class-name*\>`
-**Config file** | `<sgen:classname rdf:datatype="&xsd;string"\>*classname*</sgen:classname\>`
+**Command line** | `-n <*class-name*>`
+**Config file** | `<sgen:classname rdf:datatype="&xsd;string">*classname*</sgen:classname>`
By default, the name of the class will be based on the name of the
input file. Specifically, the last component of the input
@@ -418,8 +418,8 @@ option:
|
--- | ---
-**Command line** | `--classnamesuffix <*suffix*\>`
-**Config file** | `<sgen:classnamesuffix rdf:datatype="&xsd;string"\>*suffix*</sgen:classnamesuffix\>`
+**Command line** | `--classnamesuffix <*suffix*>`
+**Config file** | `<sgen:classnamesuffix rdf:datatype="&xsd;string">*suffix*</sgen:classnamesuffix>`
See also the [note on legal Java identifiers](#java-ids), which
@@ -431,8 +431,8 @@ applies to generated class names.
|
--- | ---
-**Command line** | `-a <*namespace-URI*\>`
-**Config file** | `<sgen:namespace rdf:datatype="&xsd;string"\>*namespace*</sgen:namespace\>`
+**Command line** | `-a <*namespace-URI*>`
+**Config file** | `<sgen:namespace rdf:datatype="&xsd;string">*namespace*</sgen:namespace>`
Since ontology files are often modularised, it is not the case that
all of the resource names appearing in a given document are being
@@ -455,8 +455,8 @@ generated Java class by the include opti
|
--- | ---
-**Command line** | `--include <*namespace-URI*\>`
-**Config file** | `<sgen:include rdf:datatype="&xsd;string"\>*namespace*</sgen:include\>`
+**Command line** | `--include <*namespace-URI*>`
+**Config file** | `<sgen:include rdf:datatype="&xsd;string">*namespace*</sgen:include>`
The include option may repeated multiple times to include a variety
@@ -475,15 +475,15 @@ vocabulary.
|
--- | ---
**Command line** | `--strictIndividuals`
-**Config file** | `<sgen:strictIndividuals /\>`
+**Config file** | `<sgen:strictIndividuals />`
### Specifying the syntax (encoding) of the input document
|
--- | ---
-**Command line** | `-e <*encoding*\>`
-**Config file** | `<sgen:encoding rdf:datatype="&xsd;string"\>*encoding*</sgen:encoding\>`
+**Command line** | `-e <*encoding*>`
+**Config file** | `<sgen:encoding rdf:datatype="&xsd;string">*encoding*</sgen:encoding>`
Jena can parse a number of different presentation syntaxes for RDF
documents, including RDF/XML, N3 and NTRIPLE. By default, the
@@ -498,7 +498,7 @@ the encoding configuration option.
|
--- | ---
**Command line** | `--ontology`
-**Config file** | `<sgen:ontology rdf:datatype="&xsd;boolean"\>*true or false*</sgen:ontology\>`
+**Config file** | `<sgen:ontology rdf:datatype="&xsd;boolean">*true or false*</sgen:ontology>`
By default, the Java class generated by schemagen will generate
constants that are plain RDF Resource, Property or Literal
@@ -517,18 +517,18 @@ for the constants in the generated Java
|
--- | ---
**Command line** | `--owl`
-**Config file** | `<sgen:owl rdf:datatype="&xsd;boolean"\>true</sgen:owl\>`
+**Config file** | `<sgen:owl rdf:datatype="&xsd;boolean">true</sgen:owl>`
|
--- | ---
**Command line** | `--rdfs`
-**Config file** | `<sgen:rdfs rdf:datatype="&xsd;boolean"\>true</sgen:owl\>`
+**Config file** | `<sgen:rdfs rdf:datatype="&xsd;boolean">true</sgen:owl>`
Prior to Jena 2.2, schemagen used a Jena model to load the input
document that also applied some *rules of inference* to the input
data. So, for example, a resource that is mentioned as the
`owl:range` of a property can be inferred to be
-`rdf:type owl:Class`, and hence listed in the class constants in
+`rdf:type owl:Class`, and hence listed in the class constants in
the generated Java class, even if that fact is not directly
asserted in the input model. From Jena 2.2 onwards, this option is
now **off by default**. If correct handling of an input document by
@@ -538,14 +538,14 @@ specified by the `inference` option.
|
--- | ---
**Command line** | `--inference`
-**Config file** | `<sgen:inference rdf:datatype="&xsd;boolean"\>true</sgen:owl\>`
+**Config file** | `<sgen:inference rdf:datatype="&xsd;boolean">true</sgen:owl>`
### Specifying the Java package
|
--- | ---
-**Command line** | `--package <*package-name*\>`
-**Config file** | `<sgen:package rdf:datatype="&xsd;string"\>*package-name*</sgen:package\>`
+**Command line** | `--package <*package-name*>`
+**Config file** | `<sgen:package rdf:datatype="&xsd;string">*package-name*</sgen:package>`
By default, the Java class generated by schemagen will not be in a
Java package. Set the package configuration option to specify the
@@ -558,22 +558,22 @@ the [output directory](#output) to match
|
--- | ---
-**Command line** | `--classdec <*class-declaration*\>`
-**Config file** | `<sgen:classdec rdf:datatype="&xsd;string"\>*class-declaration*</sgen:classdec\>`
+**Command line** | `--classdec <*class-declaration*>`
+**Config file** | `<sgen:classdec rdf:datatype="&xsd;string">*class-declaration*</sgen:classdec>`
In some applications, it may be convenient to add additional
information to the declaration of the Java class, for example that
the class implements a given interface (such as
`java.lang.Serializable`). Any string given as the value of the
class-declaration option will be written immediately after
-"`public class <i>ClassName</i>`".
+"`public class <i>ClassName</i>`".
### Adding general declarations within the generated class
|
--- | ---
-**Command line** | `--declarations <*declarations*\>`
-**Config file** | `<sgen:declarations rdf:datatype="&xsd;string"\>*declarations*</sgen:declarations\>`
+**Command line** | `--declarations <*declarations*>`
+**Config file** | `<sgen:declarations rdf:datatype="&xsd;string">*declarations*</sgen:declarations>`
Some more complex vocabularies may require access to static
constants, or other Java objects or factories to fully declare the
@@ -591,7 +591,7 @@ configuration options file.
|
--- | ---
**Command line** | `--noclasses`<br />`--nodatatypes`<br />`--noproperties`<br />`--noindividuals`
-**Config file** | `<sgen:noclassses rdf:datatype="&xsd;boolean"\>true</sgen:noclassses\>`<br />`<sgen:nodatatypes rdf:datatype="&xsd;boolean"\>true</sgen:nodatatypes\>`<br />`<sgen:noproperties rdf:datatype="&xsd;boolean"\>true</sgen:noproperties\>`<br />`<sgen:noindividuals rdf:datatype="&xsd;boolean"\>true</sgen:noindividuals\>`
+**Config file** | `<sgen:noclassses rdf:datatype="&xsd;boolean">true</sgen:noclassses>`<br />`<sgen:nodatatypes rdf:datatype="&xsd;boolean">true</sgen:nodatatypes>`<br />`<sgen:noproperties rdf:datatype="&xsd;boolean">true</sgen:noproperties>`<br />`<sgen:noindividuals rdf:datatype="&xsd;boolean">true</sgen:noindividuals>`
By default, the vocabulary class generated from a given ontology
will include constants for each of the included classes, datatypes, properties
@@ -605,8 +605,8 @@ ontology, irrespective of what is in the
|
--- | ---
-**Command line** | `--classSection *<section heading\>*`<br />`--datatypeSection *<section heading\>*`<br />`--propSection *<section heading\>*`<br />`--individualSection *<section heading*\>`<br />`--header *<file header section\>*`<br />`--footer *<file footer section\>*`
-**Config file** | `<sgen:classSection rdf:datatype="&xsd;string"\>*section heading*</sgen:classSection\>`<br />`<sgen:datatypeSection rdf:datatype="&xsd;string"\>*section heading*</sgen:datatypeSection\>`<br />`<sgen:propSection rdf:datatype="&xsd;string"\>*section heading*</sgen:propSection\>`<br />`<sgen:individualSection rdf:datatype="&xsd;string"\>*section heading*</sgen:individualSection\>`<br />`<sgen:header rdf:datatype="&xsd;string"\>*file header*</sgen:header\>`<br />`<sgen:footer rdf:datatype="&xsd;string"\>*file footer*</sgen:footer\>`
+**Command line** | `--classSection *<section heading>*`<br />`--datatypeSection *<section heading>*`<br />`--propSection *<section heading>*`<br />`--individualSection *<section heading*>`<br />`--header *<file header section>*`<br />`--footer *<file footer section>*`
+**Config file** | `<sgen:classSection rdf:datatype="&xsd;string">*section heading*</sgen:classSection>`<br />`<sgen:datatypeSection rdf:datatype="&xsd;string">*section heading*</sgen:datatypeSection>`<br />`<sgen:propSection rdf:datatype="&xsd;string">*section heading*</sgen:propSection>`<br />`<sgen:individualSection rdf:datatype="&xsd;string">*section heading*</sgen:individualSection>`<br />`<sgen:header rdf:datatype="&xsd;string">*file header*</sgen:header>`<br />`<sgen:footer rdf:datatype="&xsd;string">*file footer*</sgen:footer>`
Some coding styles use block comments to delineate different
sections of a class. These options allow the introduction of
@@ -620,7 +620,7 @@ and individual constant declarations.
|
--- | ---
**Command line** | `--includeSource`
-**Config file** | `\<sgen:includeSource rdf:datatype="&xsd;boolean"\>true\</sgen:includeSource\>`
+**Config file** | `\<sgen:includeSource rdf:datatype="&xsd;boolean">true\</sgen:includeSource>`
Schemagen's primary role is to provide Java constants corresponding to the names in
a vocabulary. Sometimes, however, we may need more information from the vocabulary
@@ -755,67 +755,67 @@ blue.
<?xml version='1.0'?>
<!DOCTYPE rdf:RDF [
-    <!ENTITY jena    'http://jena.hpl.hp.com/'>
+ <!ENTITY jena 'http://jena.hpl.hp.com/'>
-    <!ENTITY rdf     'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
-    <!ENTITY rdfs    'http://www.w3.org/2000/01/rdf-schema#'>
-    <!ENTITY owl     'http://www.w3.org/2002/07/owl#'>
-    <!ENTITY xsd     'http://www.w3.org/2001/XMLSchema#'>
-    <!ENTITY base    '&jena;2003/04/schemagen'>
-    <!ENTITY sgen    '&base;#'>
+ <!ENTITY rdf 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
+ <!ENTITY rdfs 'http://www.w3.org/2000/01/rdf-schema#'>
+ <!ENTITY owl 'http://www.w3.org/2002/07/owl#'>
+ <!ENTITY xsd 'http://www.w3.org/2001/XMLSchema#'>
+ <!ENTITY base '&jena;2003/04/schemagen'>
+ <!ENTITY sgen '&base;#'>
]>
<rdf:RDF
-  xmlns:rdf   ="&rdf;"
-  xmlns:rdfs  ="&rdfs;"
-  xmlns:owl   ="&owl;"
- Â xmlns:sgen ="&sgen;"
-  xmlns       ="&sgen;"
-  xml:base    ="&base;"
+ xmlns:rdf ="&rdf;"
+ xmlns:rdfs ="&rdfs;"
+ xmlns:owl ="&owl;"
+ xmlns:sgen ="&sgen;"
+ xmlns ="&sgen;"
+ xml:base ="&base;"
>
<!--
Example schemagen configuration for use with jena.schemagen
- Â Â Â Not all possible options are used in this example, see Javadoc and Howto for full details.
+ Not all possible options are used in this example, see Javadoc and Howto for full details.
Author: Ian Dickinson, mailto:ian.dickinson@hp.com
- CVs: Â Â Â $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $
+ CVs: $Id: schemagen.html,v 1.16 2010-06-11 00:08:23 ian_dickinson Exp $
-->
<sgen:Config>
-    <!-- specifies that the  source document uses OWL -->
- Â Â Â <sgen:owl rdf:datatype="&xsd;boolean">true</sgen:owl>
+ <!-- specifies that the source document uses OWL -->
+ <sgen:owl rdf:datatype="&xsd;boolean">true</sgen:owl>
- Â Â Â <!-- specifies that we want the generated vocab to use OntClass, OntProperty, etc, not Resource and Property -->
- Â Â Â <sgen:ontology rdf:datatype="&xsd;boolean">true</sgen:ontology>
+ <!-- specifies that we want the generated vocab to use OntClass, OntProperty, etc, not Resource and Property -->
+ <sgen:ontology rdf:datatype="&xsd;boolean">true</sgen:ontology>
- Â Â Â <!-- specifies that we want names mapped to uppercase (as standard Java constants) -->
- Â Â Â <sgen:uppercase rdf:datatype="&xsd;boolean">true</sgen:uppercase>
+ <!-- specifies that we want names mapped to uppercase (as standard Java constants) -->
+ <sgen:uppercase rdf:datatype="&xsd;boolean">true</sgen:uppercase>
- Â Â Â <!-- append Vocab to class name, so input beer.owl becomes BeerVocab.java -->
- Â Â Â <sgen:classnamesuffix rdf:datatype="&xsd;string">Vocab</sgen:classnamesuffix>
+ <!-- append Vocab to class name, so input beer.owl becomes BeerVocab.java -->
+ <sgen:classnamesuffix rdf:datatype="&xsd;string">Vocab</sgen:classnamesuffix>
- Â Â Â <!-- the Java package that the vocabulary is in -->
- Â Â Â <sgen:package rdf:datatype="&xsd;string">com.example.vocabulary</sgen:package>
+ <!-- the Java package that the vocabulary is in -->
+ <sgen:package rdf:datatype="&xsd;string">com.example.vocabulary</sgen:package>
- Â Â Â <!-- the directory or file to write the results out to -->
- Â Â Â <sgen:output rdf:datatype="&xsd;string">src/com/example/vocabulary</sgen:output>
+ <!-- the directory or file to write the results out to -->
+ <sgen:output rdf:datatype="&xsd;string">src/com/example/vocabulary</sgen:output>
- Â Â Â <!-- the template for the file header -->
+ <!-- the template for the file header -->
<sgen:header rdf:datatype="&xsd;string">/*****************************************************************************
* Source code information
* -----------------------
- * Original author    Jane Smart, example.com
- * Author email       jane.smart@example.com
- * Package            @package@
- * Web site           @website@
- * Created            %date%
- * Filename           $RCSfile: schemagen.html,v $
- * Revision           $Revision: 1.16 $
- * Release status     @releaseStatus@ $State: Exp $
+ * Original author Jane Smart, example.com
+ * Author email jane.smart@example.com
+ * Package @package@
+ * Web site @website@
+ * Created %date%
+ * Filename $RCSfile: schemagen.html,v $
+ * Revision $Revision: 1.16 $
+ * Release status @releaseStatus@ $State: Exp $
*
- * Last modified on   $Date: 2010-06-11 00:08:23 $
- *               by   $Author: ian_dickinson $
+ * Last modified on $Date: 2010-06-11 00:08:23 $
+ * by $Author: ian_dickinson $
*
* @copyright@
*****************************************************************************/
@@ -846,39 +846,39 @@ blue.
<!-- template for extra declarations at the top of the class file -->
<sgen:declarations rdf:datatype="&xsd;string">
- Â Â Â /** Factory for generating symbols */
- Â Â Â private static KsValueFactory s_vf = new DefaultValueFactory();
+ /** Factory for generating symbols */
+ private static KsValueFactory s_vf = new DefaultValueFactory();
</sgen:declarations>
<!-- template for introducing the properties in the vocabulary -->
<sgen:propSection rdf:datatype="&xsd;string">
- Â Â Â // Vocabulary properties
- Â Â Â ///////////////////////////
+ // Vocabulary properties
+ ///////////////////////////
</sgen:propSection>
<!-- template for introducing the classes in the vocabulary -->
<sgen:classSection rdf:datatype="&xsd;string">
- Â Â Â // Vocabulary classes
- Â Â Â ///////////////////////////
+ // Vocabulary classes
+ ///////////////////////////
</sgen:classSection>
<!-- template for introducing the datatypes in the vocabulary -->
<sgen:datatypeSection rdf:datatype="&xsd;string">
- Â Â Â // Vocabulary datatypes
- Â Â Â ///////////////////////////
+ // Vocabulary datatypes
+ ///////////////////////////
</sgen:datatypeSection>
<!-- template for introducing the individuals in the vocabulary -->
<sgen:individualsSection rdf:datatype="&xsd;string">
- Â Â Â // Vocabulary individuals
- Â Â Â ///////////////////////////
+ // Vocabulary individuals
+ ///////////////////////////
</sgen:individualsSection>
<!-- template for doing fancy declarations of individuals -->
<sgen:individualTemplate rdf:datatype="&xsd;string">public static final KsSymbol %valname% = s_vf.newSymbol( "%valuri%" );
- Â Â Â /** Ontology individual corresponding to {@link #%valname%} */
- Â Â Â public static final %valclass% _%valname% = m_model.%valcreator%( %valtype%, "%valuri%" );
+ /** Ontology individual corresponding to {@link #%valname%} */
+ public static final %valclass% _%valname% = m_model.%valcreator%( %valtype%, "%valuri%" );
</sgen:individualTemplate>
</sgen:Config>