[CMS PATCH] RDQL -> SPARQL
Clone URL (Committers only): https://cms.apache.org/redirect?new=andy;action=diff;uri=http://jena.apache.org/tutorials%2Frdf_api.mdtext Index: trunk/content/tutorials/rdf_api.mdtext === --- trunk/content/tutorials/rdf_api.mdtext (revision 1655891) +++ trunk/content/tutorials/rdf_api.mdtext (working copy) @@ -752,7 +752,7 @@ The previous section dealt with the case of navigating a model from a resource with a known URI. This section deals with searching a model. The core Jena API supports only a limited query primitive. The -more powerful query facilities of RDQL are described elsewhere. +more powerful query facilities of SPARQL are described elsewhere. The Model.listStatements() method, which lists all the statements in a model, is perhaps the crudest way of querying a model.
Re: [CMS PATCH] Update Fuseki page
On 03/03/15 02:27, Stian Soiland-Reyes wrote: Any feedback on this? Check the staging site. r1662741 | andy | 2015-02-27 16:33:19 + (Fri, 27 Feb 2015) Andy
Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Thanks - I failed to check the staging site. On 3 March 2015 at 12:03, Rob Vesse rve...@dotnetrdf.org wrote: Yes I already applied it with some minor tweaks, as with your other patch see the staging version http://jena.staging.apache.org/documentation/tools/schemagen-maven.html Rob On 03/03/2015 02:28, Stian Soiland-Reyes st...@apache.org wrote: Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@
[CMS PATCH]
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/getting_involved%2Findex.mdtext Index: trunk/content/getting_involved/index.mdtext === --- trunk/content/getting_involved/index.mdtext (revision 1655891) +++ trunk/content/getting_involved/index.mdtext (working copy) @@ -3,16 +3,15 @@ We welcome your contribution towards making Jena a better platform for semantic web and linked data applications. We appreciate feature suggestions, bug reports and patches for code or documentation. -If you need help using Jena: please see our [getting help](../help_and_support) page. +If you need help using Jena, please see our [getting help](../help_and_support) page. ### How to contribute -You can help us sending your suggestions, feature requests and bug reports (as well as patches) using the Jena issue tracker: -[https://issues.apache.org/jira/browse/JENA](https://issues.apache.org/jira/browse/JENA). +You can help us sending your suggestions, feature requests and bug reports (as well as patches) using the [Jena issue tracker](https://issues.apache.org/jira/browse/JENA). You can discuss your contribution, before or after adding it to Jira, on the [`dev@jena.apache.org`](mailto:dev@jena.apache.org) mailing list. -Or, you can help other users answering to their question on the [`us...@jena.apache.org`](mailto:us...@jena.apache.org) mailing list. -Subscription instructions [here](../help_and_support). +You can also help other users by answering their questions on the [`us...@jena.apache.org`](mailto:us...@jena.apache.org) mailing list. +See the [subscription instructions](../help_and_support) for details. Please see the [Reviewing Contributions](reviewing_contributions.html) page for details of what committers will be looking for when reviewing contributions. @@ -25,12 +24,12 @@ improvements to the project website as patches (because everything at Apache lives in SVN) and helps the wider community. Contributions to documentation are always welcome and considered just as valuable as code contributions. -You can click the [Improve this Page](javascript:improveThisPage(location.href\);) button on any page to instantly open the web based CMS editor. If prompted you -will need to use the username `anonymous` and a blank password to log in. +You can click the span class=glyphicon glyphicon-pencil/span*Improve this Page* button (top-right) on any page to instantly open the web based CMS editor. If prompted you +will need to use the username `anonymous` and a blank password to log in. Use the *[Diff]* and *[Mail Email]* links to submit your proposed changes to the Apache Jena committers. ### SNAPSHOTs -If you use Apache Maven and you are not afraid of being on the bleeding-edge, you can help us testing our SNAPSHOTs which you can find on the Apache Maven repository here: [https://repository.apache.org/content/repositories/snapshots/org/apache/jena/](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/). +If you use Apache Maven and you are not afraid of being on the bleeding-edge, you can help us by testing our SNAPSHOTs which you can find in the [Apache Maven repository](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/). Here is, for example, how you can add TDB version X.Y.Z-SNAPSHOT to your project (please ask if you are unsure what the latest snapshot version number currently is): @@ -40,13 +39,12 @@ versionX.Y.Z-SNAPSHOT/version /dependency -General help on how to use Jena with Maven is [here](../download/maven.html). +See also how to [use Jena with Maven](/download/maven.html). -If you have problems with any of our SNAPSHOTs, let us know. +If you have problems with any of our SNAPSHOTs, [let us know](/help_and_support/). -You can also check the state of each Jena development builds -on the Apache Jenkins continuous integration server: -[Jenkins - Jena](https://builds.apache.org/pview/?match=Jena_.*). +You can check the state of each Jena development builds +on the [Apache Jenkins continuous integration server](https://builds.apache.org/pview/?match=Jena_.*). @@ -55,14 +53,14 @@ You can find the Jena source code in the Apache git repository: [https://git-wip-us.apache.org/repos/asf/jena.git](https://git-wip-us.apache.org/repos/asf/jena.git) -There is also a read-only mirror on github: -[https://github.com/apache/jena](https://github.com/apache/jena). +There is also a read-only mirror of [Jena on GitHub](https://github.com/apache/jena): -git clone https://github.com/apache/jena +git clone https://github.com/apache/jena.git cd jena mvn clean install -You can fork Jena on github and also submit github pull requests to the project. +You can [fork Jena on GitHub](https://github.com/apache/jena/fork) and also submit [pull
Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Yes I already applied it with some minor tweaks, as with your other patch see the staging version http://jena.staging.apache.org/documentation/tools/schemagen-maven.html Rob On 03/03/2015 02:28, Stian Soiland-Reyes st...@apache.org wrote: Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the
Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven
Re: [CMS PATCH] Update Fuseki page
Any feedback on this? On 25 February 2015 at 22:43, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Fserving_data%2Findex.mdtext .. to avoid linking to snapshot repository - as that is against Apache policies Also some other updates.. this page still needs a bit of work :) -- Stian Soiland-Reyes st...@apache.org Index: trunk/content/documentation/serving_data/index.mdtext === --- trunk/content/documentation/serving_data/index.mdtext (revision 1662319) +++ trunk/content/documentation/serving_data/index.mdtext (working copy) @@ -3,25 +3,12 @@ Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP. -The relevant SPARQL standards are: -- [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/ http://www.w3.org/TR/sparql11-query/;) -- [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/ http://www.w3.org/TR/sparql11-update/;) -- [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/ http://www.w3.org/TR/sparql11-protocol/;) -- [SPARQL 1.1 Graph Store HTTP Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/ http://www.w3.org/TR/sparql11-http-rdf-update/;) - -These are work-in-progress by the SPARQL working group; -although the general designs are stable, details may change. Fuseki will -track the draft standards. - -See also: - -- [SPARQL Over HTTP](soh.html SOH) – command-line tools for working with any SPARQL 1.1 system - ## Contents - [Download](#download-fuseki) - [Getting Started](#getting-started-with-fuseki) +- [SPARQL](#sparql) - [Security](#security-and-access-control) - [Logging](#logging) - [Server URI scheme](#server-uri-scheme) @@ -31,25 +18,16 @@ - [Use from Java](#use-from-java) - [Development System](#development-system) + ## Download Fuseki -See the [downloads page](/download/index.cgi) for details of releases. +See the [downloads page](/download/#jena-fuseki) for details of releases. -Snapshot builds are -available via Apache Maven or can be [downloaded from here](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki/). +The `jena-fuseki-*-distribution` binary contain both the +Fuseki server and the [SPARQL Over HTTP](soh.html SOH) +command line utillities. -Choose the version directory, then look for the file -`fuseki-*VER*.zip`. For snapshots, `*VER*` includes the timestamp and increment -number as generated by Maven. -**Fuseki download files** - -Filename | Description -- | --- -`fuseki-*VER*.distribution.zip` | Fuseki download, includes everything. -`fuseki-*VER*-server.jar` |Fuseki server, as an executable jar. -`fuseki-*VER*-SOH.zip` | [SOH (SPARQL Over HTTP)](soh.html SOH) scripts - ## Getting Started With Fuseki This section provides a brief guide to getting up and running with @@ -57,12 +35,12 @@ [SOH (SPARQL over HTTP)](soh.html) scripts included in the download. -1. Download (this includes the server and the SOH scripts) -2. Unzip +1. [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` +2. `unzip` or `tar zxfv` the downloaded file 3. (Linux) `chmod +x fuseki-server s-*` 4. Run a server - fuseki-server --update --mem /ds + ./fuseki-server --update --mem /ds The server logging goes to the console: @@ -79,14 +57,14 @@ - SPARQL Query, SPARQL Update, and file upload to a selected dataset. -- Link to the documentation (here). +- Link to the documentation (this page). - Validators for SPARQL query and update and for non-RDF/XML formats. For the control panel: -1. In a browser, go to `http://localhost:3030/` -2. Click on Control Panel +1. In a browser, go to [http://localhost:3030/](http://localhost:3030/) +2. Click on *Control Panel* 3. Select the dataset (if set up above, there is only one choice). The page offers SPARQL operations and file upload acting on the -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718
[CMS PATCH] documentation/io/streaming-io
Clone URL (Committers only):
https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Fio%2Fstreaming-io.mdtext
The code examples were wrong.. also I added some Javadoc links.
Check - does the table headers render correctly with my patch?cms.apache.org
preview didn't render the original table correct either so I can't tell.
--
Stian Soiland-Reyes
st...@apache.org
Index: trunk/content/documentation/io/streaming-io.mdtext
===
--- trunk/content/documentation/io/streaming-io.mdtext (revision 1655891)
+++ trunk/content/documentation/io/streaming-io.mdtext (working copy)
@@ -15,49 +15,33 @@
## `StreamRDF`
-The central abstraction is `StreamRDF` which is an interface for streamed
+The central abstraction is
+[StreamRDF](/documentation/javadoc/arq/org/apache/jena/riot/system/StreamRDF.html)
+which is an interface for streamed
RDF data. It covers triples and quads, and also parser events such as
prefix settings and base URI declarations.
-public interface StreamRDF {
-/** Start parsing */
-public void start() ;
-
-/** Triple emitted */
-public void triple(Triple triple) ;
-
-/** Quad emitted */
-public void quad(Quad quad) ;
-
-/** base declaration seen */
-public void base(String base) ;
-
-/** prefix declaration seen */
-public void prefix(String prefix, String iri) ;
-
-/** Finish parsing */
-public void finish() ;
-}
-
There are utilities to help:
-* `StreamRDFLib` -- create `StreamRDF` objects
-* `StreamOps` -- helpers for sending RDF data to `StreamRDF` objects
+*
[StreamRDFLib](/documentation/javadoc/arq/org/apache/jena/riot/system/StreamRDFLib.html)
-- create `StreamRDF` objects
+*
[StreamOps](/documentation/javadoc/arq/org/apache/jena/riot/system/StreamOps.html)
-- helpers for sending RDF data to `StreamRDF` objects
## Reading data
-All parses of RDF syntaxes provided by RIOT are streaming with the
-exception of JSON-LD. A JSON object can have members in any order so the
-parser may need the whole top-level object in order to have the information
-needed for parsing.
+All parses of RDF syntaxes provided by RIOT are streaming, except JSON-LD
+(the parser may need the whole top-level object as
+a JSON document can list members in any order).
-The `parse` functions of `RDFDataMgr` direct the output of the parser to a
+The [parse
functions](/documentation/javadoc/arq/org/apache/jena/riot/RDFDataMgr.html#parse%28org.apache.jena.riot.system.StreamRDF,%20java.io.InputStream,%20org.apache.jena.riot.Lang%29)
+ of
+[RDFDataMgr](/documentation/javadoc/arq/org/apache/jena/riot/RDFDataMgr.html)
+direct the output of the parser to a
`StreamRDF`. For example:
-StreamRDF destinination = ...
+StreamRDF destination = ...
RDFDataMgr.parse(destination, http://example/data.ttl;) ;
-reads the remote URL, with content negotiation, and send the triples to the
+The above code reads the remote URL, with content negotiation, and send the
triples to the
`destination`.
## Writing data
@@ -73,20 +57,23 @@
See [Streamed Block Formats](rdf-output.html#streamed-block-formats)
for details.
-The `StreamRDFWriter` class has functions that write graphs and datasets
+The
[StreamRDFWriter](/documentation/javadoc/arq/org/apache/jena/riot/system/StreamRDFWriter.html)
+class has functions that write graphs and datasets
using a streaming writer and also provides for the creation of
-an`StreamRDF` backed by a stream-based writer
+an `StreamRDF` backed by a stream-based writer:
-StreamWriter.write(output, model.getGraph(), lang) ;
+StreamRDFWriter.write(output, model.getGraph(), lang) ;
which can be done as:
-StreamRDF writer = StreamWriter.getWriterStream(output, lang) ;
-StreamOps.graphToStream(writer, model.getGraph()) ;
+StreamRDF writer = StreamRDFWriter.getWriterStream(output, lang) ;
+StreamOps.graphToStream(model.getGraph(), writer) ;
N-Triples and N-Quads are always written as a stream.
-| RDFFormat | Lang shortcut|
+## RDFFormat and Lang
+
+| [RDFFormat](/documentation/javadoc/arq/org/apache/jena/riot/RDFFormat.html)
| [Lang](/documentation/javadoc/arq/org/apache/jena/riot/Lang.html) shortcut |
||--|
| `RDFFormat.TURTLE_BLOCKS` | `Lang.TURTLE`|
| `RDFFormat.TURTLE_FLAT`| |
[CMS PATCH] documentation/tools/schemagen-maven.mdtext
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central.* + + build - plugins -plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version -
Re: [CMS PATCH] for documentation/tools/schemagen-maven
x.y.z sounds good to me. Each mention of version in that patch already has a corresponding paragraph about where to find the latest version. On 26 Feb 2015 10:03, Rob Vesse rve...@dotnetrdf.org wrote: We typically avoid putting specific version numbers in the documentation because it quickly becomes out of date. Usually we just put x.y.z as the version and refer people to Maven central to find the latest version Rob On 26/02/2015 00:28, Stian Soiland-Reyes st...@apache.org wrote: This should fix https://issues.apache.org/jira/browse/JENA-849 The examples still needs information about adding the target/generated-sources to the compile path (as the plugin doesn't yet - JENA-731 JENA-732 are dormant since June :-/ On 26 February 2015 at 00:20, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext .. now also with version update links. Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version + /dependency +/dependencies +Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools]( http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools]( http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest
Re: [CMS PATCH] for documentation/tools/schemagen-maven
We typically avoid putting specific version numbers in the documentation because it quickly becomes out of date. Usually we just put x.y.z as the version and refer people to Maven central to find the latest version Rob On 26/02/2015 00:28, Stian Soiland-Reyes st...@apache.org wrote: This should fix https://issues.apache.org/jira/browse/JENA-849 The examples still needs information about adding the target/generated-sources to the compile path (as the plugin doesn't yet - JENA-731 JENA-732 are dormant since June :-/ On 26 February 2015 at 00:20, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext .. now also with version update links. Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version + /dependency +/dependencies +Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are
[CMS PATCH] for documentation/tools/schemagen-maven
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext Updated groupId/artifactId for jena-maven-tools The plugin itself needs some further work, as the generated-sources are not subsequently compiled and included in the JAR. -- Stian Soiland-Reyes st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -29,12 +29,30 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version + /dependency +/dependencies @@ -58,9 +76,9 @@ build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version configuration /configuration executions @@ -93,7 +111,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -116,37 +134,44 @@ ## Example configuration build - plugins -plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - configuration -includes - includesrc/main/vocabs/*.ttl/include - includesrc/main/vocabs/foaf.rdf/include -/includes -fileOptions - source -inputdefault/input -package-nameorg.example.test/package-name - /source - source -!-- Test2.java (only) will contain OntModel declarations -- -inputsrc/main/vocabs/demo2.ttl/input -ontologytrue/ontology - /source -/fileOptions - /configuration - executions -execution - idschemagen/id - goals -goaltranslate/goal - /goals -/execution - /executions -/plugin - /plugins -/build + plugins + plugin +groupIdorg.apache.jena/groupId +artifactIdjena-maven-tools/artifactId +version0.7/version +configuration + includes +includesrc/main/vocabs/*.ttl/include +includesrc/main/vocabs/foaf.rdf/include + /includes + fileOptions +source + inputdefault/input + package-nameorg.example.test/package-name +/source +source + !-- Test2.java (only) will contain OntModel declarations -- + inputsrc/main/vocabs/demo2.ttl/input + ontologytrue/ontology +/source + /fileOptions +/configuration +executions + execution +idschemagen/id +goals + goaltranslate/goal +/goals + /execution +/executions + /plugin +/plugins + /build + dependencies +dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version +/dependency + /dependencies
Re: [CMS PATCH] for documentation/tools/schemagen-maven
This should fix https://issues.apache.org/jira/browse/JENA-849 The examples still needs information about adding the target/generated-sources to the compile path (as the plugin doesn't yet - JENA-731 JENA-732 are dormant since June :-/ On 26 February 2015 at 00:20, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext .. now also with version update links. Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version + /dependency +/dependencies +Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `version` tags below with the latest versions as
[CMS PATCH] Update Fuseki page
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Fserving_data%2Findex.mdtext .. to avoid linking to snapshot repository - as that is against Apache policies Also some other updates.. this page still needs a bit of work :) -- Stian Soiland-Reyes st...@apache.org Index: trunk/content/documentation/serving_data/index.mdtext === --- trunk/content/documentation/serving_data/index.mdtext (revision 1662319) +++ trunk/content/documentation/serving_data/index.mdtext (working copy) @@ -3,25 +3,12 @@ Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP. -The relevant SPARQL standards are: -- [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/ http://www.w3.org/TR/sparql11-query/;) -- [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/ http://www.w3.org/TR/sparql11-update/;) -- [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/ http://www.w3.org/TR/sparql11-protocol/;) -- [SPARQL 1.1 Graph Store HTTP Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/ http://www.w3.org/TR/sparql11-http-rdf-update/;) - -These are work-in-progress by the SPARQL working group; -although the general designs are stable, details may change. Fuseki will -track the draft standards. - -See also: - -- [SPARQL Over HTTP](soh.html SOH) – command-line tools for working with any SPARQL 1.1 system - ## Contents - [Download](#download-fuseki) - [Getting Started](#getting-started-with-fuseki) +- [SPARQL](#sparql) - [Security](#security-and-access-control) - [Logging](#logging) - [Server URI scheme](#server-uri-scheme) @@ -31,25 +18,16 @@ - [Use from Java](#use-from-java) - [Development System](#development-system) + ## Download Fuseki -See the [downloads page](/download/index.cgi) for details of releases. +See the [downloads page](/download/#jena-fuseki) for details of releases. -Snapshot builds are -available via Apache Maven or can be [downloaded from here](https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki/). +The `jena-fuseki-*-distribution` binary contain both the +Fuseki server and the [SPARQL Over HTTP](soh.html SOH) +command line utillities. -Choose the version directory, then look for the file -`fuseki-*VER*.zip`. For snapshots, `*VER*` includes the timestamp and increment -number as generated by Maven. -**Fuseki download files** - -Filename | Description -- | --- -`fuseki-*VER*.distribution.zip` | Fuseki download, includes everything. -`fuseki-*VER*-server.jar` |Fuseki server, as an executable jar. -`fuseki-*VER*-SOH.zip` | [SOH (SPARQL Over HTTP)](soh.html SOH) scripts - ## Getting Started With Fuseki This section provides a brief guide to getting up and running with @@ -57,12 +35,12 @@ [SOH (SPARQL over HTTP)](soh.html) scripts included in the download. -1. Download (this includes the server and the SOH scripts) -2. Unzip +1. [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` +2. `unzip` or `tar zxfv` the downloaded file 3. (Linux) `chmod +x fuseki-server s-*` 4. Run a server - fuseki-server --update --mem /ds + ./fuseki-server --update --mem /ds The server logging goes to the console: @@ -79,14 +57,14 @@ - SPARQL Query, SPARQL Update, and file upload to a selected dataset. -- Link to the documentation (here). +- Link to the documentation (this page). - Validators for SPARQL query and update and for non-RDF/XML formats. For the control panel: -1. In a browser, go to `http://localhost:3030/` -2. Click on Control Panel +1. In a browser, go to [http://localhost:3030/](http://localhost:3030/) +2. Click on *Control Panel* 3. Select the dataset (if set up above, there is only one choice). The page offers SPARQL operations and file upload acting on the
[CMS PATCH] for documentation/tools/schemagen-maven
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext .. now also with version update links. Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + version2.12.1/version + /dependency +/dependencies +Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + version0.7/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `version` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `version` tags below with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central.* + + build - plugins -plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - configuration -
[CMS] patch to documentation/tdb/commands.mdtext
The attached patch updates the N-Quads hyperlink to http://www.w3.org/TR/n-quads/ The only other pages that links to http://sw.deri.org/2008/07/n-quads/ is ./content/documentation/javadoc/arq/org/apache/jena/riot/lang/LangNQuads.html: http://sw.deri.org/2008/07/n-quads//div .. suggested javadoc fixes in https://github.com/apache/jena/pull/19 ..BTW the CMS is unable to send email diffs today: Can't connect to ldaps://svn.apache.org -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718 Index: trunk/content/documentation/tdb/commands.mdtext === --- trunk/content/documentation/tdb/commands.mdtext (revision 1655294) +++ trunk/content/documentation/tdb/commands.mdtext (working copy) @@ -137,7 +137,7 @@ ### `tdbdump` Dump the store in -[N-Quads](http://sw.deri.org/2008/07/n-quads/) +[N-Quads](http://www.w3.org/TR/n-quads/) format. ### tdbstats
[CMS PATCH] of commands.mdtext
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/ .. Mainly testing for INFRA if CMS email works again now. -- st...@apache.org Index: trunk/content/documentation/tdb/commands.mdtext === --- trunk/content/documentation/tdb/commands.mdtext (revision 1655294) +++ trunk/content/documentation/tdb/commands.mdtext (working copy) @@ -137,7 +137,7 @@ ### `tdbdump` Dump the store in -[N-Quads](http://sw.deri.org/2008/07/n-quads/) +[N-Quads](http://www.w3.org/TR/n-quads/) format. ### tdbstats
[CMS PATCH] Portugues Translation Of Tutorials #Final
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/tutorials%2Findex.mdtext Guilherme Cavalcanti I forget to link to the index the last tutorial. thanks Index: trunk/content/tutorials/index.mdtext === --- trunk/content/tutorials/index.mdtext(revision 1438999) +++ trunk/content/tutorials/index.mdtext(working copy) @@ -24,4 +24,5 @@ - [Uma introdução à API RDF](rdf_api_pt.html) - [Tutorial SPARQL](sparql_pt.html) -- [Manipulando SPARQL usando ARQ](/documentation/query/manipulating_sparql_using_arq_pt.html) \ No newline at end of file +- [Manipulando SPARQL usando ARQ](/documentation/query/manipulating_sparql_using_arq_pt.html) +- [Usando o Jena com o Eclipse](using_jena_with_eclipse_pt.html) \ No newline at end of file
[CMS PATCH]Portugues Translation Of Tutorials #Final
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/tutorials%2F Guilherme Cavalcanti I submitted the last tutorial: Using Jena with Eclipse, in Portuguese. I also had to add images to this tutorial in the folder /figures of tutorial directory. Now, the translation is 100% complete. Very Thanks Index: trunk/content/tutorials/figures/jhw_fig1.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig1.png === --- trunk/content/tutorials/figures/jhw_fig1.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig1.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig1.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig2.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig2.png === --- trunk/content/tutorials/figures/jhw_fig2.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig2.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig2.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig3.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig3.png === --- trunk/content/tutorials/figures/jhw_fig3.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig3.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig3.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig4.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig4.png === --- trunk/content/tutorials/figures/jhw_fig4.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig4.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig4.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig5.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig5.png === --- trunk/content/tutorials/figures/jhw_fig5.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig5.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig5.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig6.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig6.png === --- trunk/content/tutorials/figures/jhw_fig6.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig6.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig6.png ___ Added: svn:mime-type ## -0,0 +1 ## +image/png \ No newline at end of property Index: trunk/content/tutorials/figures/jhw_fig7.png === Cannot display: file marked as a binary type. svn:mime-type = image/png Index: trunk/content/tutorials/figures/jhw_fig7.png === --- trunk/content/tutorials/figures/jhw_fig7.png(revision 1437811) +++ trunk/content/tutorials/figures/jhw_fig7.png(working copy) Property changes on: trunk/content/tutorials/figures/jhw_fig7.png ___ Added:
[CMS PATCH]Portugues Translation Of Tutorilas #5
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/tutorials%2F Jonathas Alves The tutorial about Manipulating SPARQL using ARQ was submitted (into the documentation/query directory). Now, there are one last tutorial to submit to finish all tutorials. Thank you Index: trunk/content/tutorials/index.mdtext === --- trunk/content/tutorials/index.mdtext(revision 1436910) +++ trunk/content/tutorials/index.mdtext(working copy) @@ -23,4 +23,5 @@ [getting started](/getting_started/) - em inglês. - [Uma introdução à API RDF](rdf_api_pt.html) -- [Tutorial SPARQL](sparql_pt.html) \ No newline at end of file +- [Tutorial SPARQL](sparql_pt.html) +- [Manipulando SPARQL usando ARQ](/documentation/query/manipulating_sparql_using_arq_pt.html) \ No newline at end of file Index: trunk/content/tutorials/sparql_pt.mdtext === --- trunk/content/tutorials/sparql_pt.mdtext(revision 1436910) +++ trunk/content/tutorials/sparql_pt.mdtext(working copy) @@ -23,9 +23,9 @@ [1]: http://jena.apache.org/documentation/query/index.html -SPARQL is a -[query language](http://www.w3.org/TR/sparql11-query/) e um -[protocol](http://www.w3.org/TR/rdf-sparql-protocol/) para acesso a +SPARQL é uma +[linguagem de consulta](http://www.w3.org/TR/sparql11-query/) e um +[protocolo](http://www.w3.org/TR/rdf-sparql-protocol/) para acesso a RDF elaborado pelo [W3C RDF Data Access Working Group](http://www.w3.org/2001/sw/DataAccess/).
[CMS PATCH] Portuguese Translation of Tutorials #1
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/tutorials%2Frdf_api_pt.mdtext Guilherme Cavalcanti This is the first of the portuguese translation of tutorials. Thanks. Index: trunk/content/tutorials/rdf_api_pt.mdtext === --- trunk/content/tutorials/rdf_api_pt.mdtext (revision 0) +++ trunk/content/tutorials/rdf_api_pt.mdtext (working copy) @@ -0,0 +1,937 @@ +Title: Uma Introdução a RDF e à API RDF de Jena +Notice:Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + . + http://www.apache.org/licenses/LICENSE-2.0 + . + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +h2Prefácio/h2 + +Este é um tutorial introdutório ao framework de descrição de recursos (RDF) +e Jena, uma API Java para RDF. Ele é escrito para programadores que +não estão familiarizados com RDF e que aprendem melhor através de prototipagem, +ou, por outros motivos, desejam avançar rapidamente para a implementação. +Familiaridade com XML e Java é assumido. + +pAvançar direto para a implementação, sem conhecer inicialmente o modelo de dados de RDF, +levará à frustração e ao desapontamento. No entanto, estudar unicamente o modelo de dados é +desgastante e muitas vezes leva a enigmas metafísicos torturantes. É melhor, +então, abordar os conceitos do modelo de dados e como usá-lo, paralelamente. +Aprender um pouco o modelo de dados, e praticá-lo. Então aprender um pouco mais e praticar. +A teoria leva à prática , e a prática leva à teoria. O modelo de dados é +relativamente simples, então esta abordagem não exigirá muito tempo./p + +pRDF possui uma sintaxe XML, e muitos dos que são familiarizados com XML irão pensar em RDF em termos da sintaxe do XML. Isso é um erro. RDF deve ser entendido em termos do seu modelo de dados. Os dados RDF podem ser representados em XML, mas entender a sintaxe é menos importante do que entender o modelo de dados./p + +pUma implementação da API JENA, incluindo o código fonte dos exemplos usados neste tutorial, podem ser baixados em +a href=http://jena.apache.org/download/;codejena.apache.org/download//code/a./p + +p/p + +h2Conteúdo/h2 +ol + lia href=#ch-IntroductionIntrodução/a/li + lia href=#ch-StatementsSentenças/a/li + lia href=#ch-Writing RDFEscrita de RDF/a/li + lia href=#ch-Reading RDFLeitura de RDF/a/li + lia href=#ch-PrefixesControle de Prefixos/a/li + lia href=#ch-Jena RDF PackagesPacotes de Jena RDF/a/li + lia href=#ch-Navigating a ModelNavegação em Modelos/a/li + lia href=#ch-Querying a ModelConsulta de Modelos/a/li + lia href=#ch-Operations on ModelsOperações em Modelos/a/li + lia href=#ch-ContainersContainers/a/li + lia href=#ch-More about Literals and DatatypesMais sobre Literais e Datatypes/a/li + lia href=#ch-GlossaryGlossário/a/li +/ol + +h2a id=ch-IntroductionIntrodução/a/h2 + +p O framework de descrição de recursos (RDF) é um padrão (tecnicamente uma recomendação da W3C) para descrever recursos. Mas o que são recursos? Isso é uma questão profunda e a definição precisa ainda é um assunto de debates. Para nossos propósitos, nós podemos pensar em recursos como tudo que podemos identificar. Você é um recurso, assim como sua página pessoal, este tutorial, o número um e a grande baleia branca em Moby Dick./p + +pNossos exemplos neste tutorial serão sobre pessoas. Elas usam uma a +href=http://www.w3.org/TR/vcard-rdf;representação RDF de cartão de negócios (VCARDS)/a. RDF é melhor representado como um diagrama de nós e arcos. Um simples vcard se assemelha a isto em RDF:/p + +p align=center +img border=0 src=figures/fig1.png alt=figure 1 width=240 height=180/p + +pO a href=#glos-Resourceirecurso/i/a, John Smith, é exibido como uma elipse e identificado por um Identificador Uniforme de Recurso (URI)font +size=1supa href=#fn-011/a/sup/font, neste caso +http://.../JohnSmith;. Se você tentar acessar o recurso usando seu navegador, não vai obter sucesso. Se você não tem familiaridade com URI's, pense neles como nomes estranhos./p + +pRecursos possuem a href=#glos-Propertyipropriedades/i/a. Nesses exemplos, nós estamos interessados nos tipos de propriedades que
