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
[jira] [Created] (JENA-891) Add assembler support for HTTP Authenticator
Rob Vesse created JENA-891:
--
Summary: Add assembler support for HTTP Authenticator
Key: JENA-891
URL: https://issues.apache.org/jira/browse/JENA-891
Project: Apache Jena
Issue Type: Bug
Affects Versions: Jena 2.11.0
Reporter: Rob Vesse
Priority: Minor
This
[question|http://stackoverflow.com/questions/28812206/federated-query-with-secured-sparql-endpoint/28829913#28829913]
made my realise that the solution there only works for simple authentication
scenarios. If users wanted to take advantage of more complex authentication
strategies then they would have no way of doing that via assembler.
So we need the following:
* Assembler support for {{HttpAuthenticator}} instances
* Ability to specify a {{HttpAuthenticator}} in a service context as opposed to
basic auth credentials
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345320#comment-14345320 ] Stian Soiland-Reyes commented on JENA-890: -- I would be sad to see it go.. but if I am the only one using it.. Could it be a configurable option to turn on for a dataset? Technically it we get this from the yasr http://yasr.yasgui.org/ which has no easy way to programmaticlly disable it (except hacking the [plugins] list): https://github.com/YASGUI/YASR/issues/56 To disable pivot, comment out 'pivottable' from this line: https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/webapp/js/common-config.js#L58 (This file can also be edited in ./webapp/js/common-config.js of the server distro) Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Apache Jena for Android
Hi all, We are working on some Android app prototypes that deal with RDF data. To make things easier, we have created a version of Apache Jena that runs on Android. It basically consists of a bunch of Maven build files that do some repackaging of the original Jena jars in order to make them run on Android's Dalvik VM. As the port might be interesting to others, we have published it to Github for everyone to use. From the project description: This project aims to make the Apache Jena Framework usable on Android. While Jena is written in pure Java, it can't be used on Android as is, due to multiple package conflict issues. To overcome these issues, we have created an Android port enabling developers to use Apache Jena in Android apps. In contrast to other ports we don't just publish binaries, but make the Maven build files of the port available. We also stay as close as possible to the original (i.e. no source code changes). This should make it easier to stay in sync with upcoming Jena releases. The project, including usage instructions, is available here: https://github.com/seus-inf/jena-android See here for an older discussion about the issues: http://mail-archives.apache.org/mod_mbox/jena-dev/201304.mbox/%3C5163E9A0.2030307%40apache.org%3E Best regards, Sören -- Dipl. Inf. Sören Brunk Research Associate Technische Universität Dresden Faculty of Computer Science Institute for Software- and Multimedia-Technology Junior Professorship in Software Engineering of Ubiquitous Systems 01062 Dresden
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: @@
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345364#comment-14345364 ] Stian Soiland-Reyes commented on JENA-890: -- Any defailed feedback on the actual UX of it should be directed upstream to http://yasr.yasgui.org/ https://github.com/YASGUI/YASR/issues .. Ian are you able to formulate this for YASR? Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345351#comment-14345351 ] Stian Soiland-Reyes commented on JENA-890: -- Can also be done programmatically with outputPlugins - see http://yasr.yasgui.org/doc/#config Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-889) FileManager/LocationMapper does not work with file: prefix for LocatorClassLoader
[ https://issues.apache.org/jira/browse/JENA-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345609#comment-14345609 ] Jan Vlug commented on JENA-889: --- I tested Andy's example with 2.12.1. It does not work for me. When I remove file: from file:foo.ttl in the location-mapping.ttl file, it works. I'm using java-1.8.0-openjdk.x86_64 1:1.8.0.31-5.b13.fc21. FileManager/LocationMapper does not work with file: prefix for LocatorClassLoader - Key: JENA-889 URL: https://issues.apache.org/jira/browse/JENA-889 Project: Apache Jena Issue Type: Bug Components: Jena Affects Versions: Jena 2.12.1 Reporter: Jan Vlug I tried to use a LocationMapper configuration file as described at: https://jena.apache.org/documentation/notes/file-manager.html. This worked fine in an old Jena version. But now I upgraded to 2.12.1 it seems that I have to omit the file: prefix in the mapped URL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-889) FileManager/LocationMapper does not work with file: prefix for LocatorClassLoader
[
https://issues.apache.org/jira/browse/JENA-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345720#comment-14345720
]
Andy Seaborne commented on JENA-889:
I have tried 2.12.1 with success. What's the exact stacktrace you get?
A slightly modified program:
{noformat}
static { LogCtl.setCmdLogging();}
public static void main(String[] args) {
System.out.println(Jena=+Jena.VERSION) ;
System.out.println(ARQ=+ARQ.VERSION) ;
System.out.println(RIOT=+RIOT.VERSION) ;
Model m = RDFDataMgr.loadModel(location-mapping.ttl) ;
FileManager.get().getLocationMapper().processConfig(m);
Model m2 = ModelFactory.createDefaultModel() ;
FileManager.get().readModel(m2, file:foo.n3) ;
System.out.println(DONE) ;
}
{noformat}
If foo.ttl, exists in the current directory, I get:
{noformat}
Jena=2.12.1
ARQ=2.12.1
RIOT=2.12.1
DONE
{noformat}
with either file:foo.ttl or foo.ttl.
If foo.ttl does not exist, I get:
{noformat}
Jena=2.12.1
ARQ=2.12.1
RIOT=2.12.1
Exception in thread main org.apache.jena.riot.RiotNotFoundException: Not
found: file:foo.ttl
at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:870)
at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:852)
at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:684)
at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:210)
at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:143)
at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:132)
at
org.apache.jena.riot.adapters.AdapterFileManager.readModelWorker(AdapterFileManager.java:283)
at com.hp.hpl.jena.util.FileManager.readModel(FileManager.java:344)
at com.hp.hpl.jena.util.FileManager.readModel(FileManager.java:328)
at dev.Report.main(Report.java:40)
{noformat}
which is correct.
Having foo.ttl for file:foo.ttl in location mapping changes the Not
found accordingly.
I do have to align the file:foo.n3 with the location mapping file.
Ubuntu 14.10
openjdk version 1.8.0_40-internal
OpenJDK Runtime Environment (build 1.8.0_40-internal-b09)
OpenJDK 64-Bit Server VM (build 25.40-b13, mixed mode)
FileManager/LocationMapper does not work with file: prefix for
LocatorClassLoader
-
Key: JENA-889
URL: https://issues.apache.org/jira/browse/JENA-889
Project: Apache Jena
Issue Type: Bug
Components: Jena
Affects Versions: Jena 2.12.1
Reporter: Jan Vlug
I tried to use a LocationMapper configuration file as described at:
https://jena.apache.org/documentation/notes/file-manager.html. This worked
fine in an old Jena version. But now I upgraded to 2.12.1 it seems that I
have to omit the file: prefix in the mapped URL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Fuseki2 UI development
Hi folks, Firstly an apology for dropping off the radar for a while. I've been very busy with work, so haven't been attending to dev@ emails for a while. Anyway, I'm picking up the reins again on the Fuseki2 UI work. I notice that there are a number of bug reports outstanding, thanks for those whoever contributed to them. There are also some unfinished threads on the originally planned Fuseki2 UI capabilities (some of which will need back-end support via the server protocol). Finally there have been some changes that have been introduced by some of the patches that have gone through while my attention has been elsewhere, some of which have negatively impacted existing capabilities. Tl;dr - there's quite a bit of work to do to bring the Fuseki2 UI up to where I'd like it to be, including closing out the new bugreps. One of the reasons for bringing this to the list is with respect to the forthcoming release. I can't get the outstanding work done in a timeframe that will do anything other than delay this release. Given my other work commitments, it's going to be O(weeks) before the work queue that I can see on Fuseki2 is under control. We have a choice about what to do about that. One option would be to include the current UI as-is, but label it more clearly as an alpha release. Another would be to decouple the new UI from this release, but aim for another release in O(months) when Fuseki2 is up to a good standard. There may be other options between those extremes. Opinions? Ian
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345363#comment-14345363 ] Stian Soiland-Reyes commented on JENA-890: -- How about this: Disable pivottable dependency now (is this blocker for the release?) - and then it could later be added in optionally through a Configure dataset button (new bug) Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345384#comment-14345384 ] Ian Dickinson commented on JENA-890: Sorry, but what's the use case for having analysis and charting tools in Fuseki at all? I totally get that such things can be useful for some users in some contexts, and I'm all for people experimenting with RDF-based dataviz workbenches, but Fuseki is a dataset control and publishing UI. It should, in my opinion, be focussed on doing that task well. I'm not, in general, in favour of adding user-configurable options to UI's. I strongly recommend Steve Krug's book on this topic (http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321965515/ref=asap_bc?ie=UTF8). Whenever as a developer you put a user configuration option in a UI, you're doubling the test surface of the system, but moreover you're making the user do the hard work of figuring out what the right behaviour should be for you. Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345385#comment-14345385 ] Ian Dickinson commented on JENA-890: Happy to feed back comments to upstream. The pivot table isn't the only problem with Yasgui, but it is the worst. Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345394#comment-14345394 ] Ian Dickinson commented on JENA-890: (is this blocker for the release?) Do you mean a blocker or the blocker? There are a number of problems with the recent clutch of changes to Fuseki2 - I'm working on fixing them but I'm also very busy with client work. I'll start a separate thread on dev@ to discuss. Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Release planning : 2.13.0
On 3 March 2015 at 10:41, Andy Seaborne a...@apache.org wrote: Fuseki1 is in dist/binaries/ and mirrored. In my experience, short-term mitigation worries can leave long-term legacy behind and it costs more in support. If we can find a one-time change, I think it is less work for the project. Users have to change sometime - let's make it once. I see - any fuseki1-users using those as Maven dependencies (e.g. from an assembly file) will probably want to migrate to the more proper artifacts and newer Jetty from Fuseki 2 anyway. Unless anyone shows up showing the opposite, I now agree with you to go for the v1 option with jena-fuseki1. -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718
Re: Release planning : 2.13.0
On 03/03/15 01:38, Stian Soiland-Reyes wrote: v1 artifacts: http://central.maven.org/maven2/org/apache/jena/jena-fuseki/1.1.1/ Almost any of those could in theory be used.. If somehow a Maven project before got jena-fuseki 1.1 the JAR and now upgrade to 2.0 the POM, that's not going to work very well :) (At least it should fail early!) The technical part is clear - it's the could, in theory and somehow that matter. Fuseki1 is in dist/binaries/ and mirrored. In my experience, short-term mitigation worries can leave long-term legacy behind and it costs more in support. If we can find a one-time change, I think it is less work for the project. Users have to change sometime - let's make it once. The reason I backed Rob's v2 approach is that it's the least intrusive, and can be transient until fuseki1 is deprecated. It's slightly messier for the project Why is the parent jena-fuseki2 and the module just jena-fuseki-*?? - but less impact for anyone else who should never need to care about the parent. You could also do a v2 variant where the parent is called jena-fuseki-parent instead of jena-fuseki / jena-fuseki2? Less confusion? If we think there are no-one using the fuseki 1 artifacts from Maven++, then v1 approach is probably still workable, even if it's more intrusive. As a server Fuseki2 is more compliant, and probably more stable than Fuseki1 because it uses Jetty9. There is a issue with Jetty8, as Fuseki1 uses it, under high load. Jetty9 is radically different in the area of connectors and does not go into weird states (it's quite likely not Jetty directly, but the way Java 1.6 works - Jetty9 uses java7 features). Andy On 2 March 2015 at 16:40, Andy Seaborne a...@apache.org wrote: On 02/03/15 15:37, Rob Vesse wrote: I think it is a more general limitation of Maven Probably easiest thing is to call it jena-fuseki2 for the time being and then at such time as 2.x is sufficiently stable to replace 1.x we can rename again It's just the release plugin at the moment. What i think is happening is that when it rewrites the version ids after asking what to set them to, it overwrites regardless. The dialog gets the right answer; it's the rewrite stage that does not map current-release ids, just overwrites with release ids. There may other lurking issues as well. It's supposed to work in a sufficiently recent maven. That said, while it has been working in development builds, relying on the version might be too clever. jena-fuseki2 All the choices: 1/ (V1) jena-fuseki, (V2) jena-fuseki2, jena-fuseki-war, ... Just the clashing artifact renamed. 2/ (V1) jena-fuseki, (V2) jena-fuseki2, jena-fuseki2-war, ... Rename all V2, leave v1 3/ (V1) jena-fuseki1, (V2) jena-fuseki, jena-fuseki-war, ... Rename v1 only. 4/ (V1) jena-fuseki1, (V2) jena-fuseki2, jena-fuseki2-war, ... All modules have the major version. I'd like to do it by making Fuseki v1 jena-fuseki1, leave jena-fuseki for Fuseki2 - option 3. 4's OK; 1 seems like trouble. 2 isn't clear to my way of thinking. jena-fuseki is a Fuseki2 does have artifacts (WAR file; the server jar is done as an artifact, not a classifier addition; an embedded version sometime). That makes a second rename of Fuseki v2 artifact(s) less desirable. This isn't a strongly held position. The underlying assumption is that Fuseki v1 is not used as an artifact -- only as a distribution. Of course, I can't be sure that is no one outside the build uses it as an artifact so if anyone thinks it's a bad idea, do say so. There is an internal artifact use of Fuseki v1 by jena-jdbc-driver-remote and jena-jdbc-driver-bundle (2 each). That causes a different, minor problem, which I didn't understand. When resolving dependencies in release:prepare, that useage causes a you have SNAPSHOTs do you want to fix them dialog from the release plugin (inc dry run). You get 2 lots of two requests to fix the SNAPSHOT version. In case that was the cause of the major issue, I set it to a fixed 1.1.1 but it didn't change anything other than removing the additional dialog. Andy Rob On 28/02/2015 16:59, Andy Seaborne a...@apache.org wrote: There'll be a bit of a delay in building Jena 2.13.0. In our setup, the release process can't not handle having multiple versions of the same artifact (org.apache.jena:jena-fuseki). Then the reactor has duplicates and maven stops with an error. Looks like it is the release plugin. Whether this is because we are using an old(ish) apache parent or whether it's an on-going problem, isn't clear yet. Trying things out is a slow process. Maybe a change of artifact name is needed, which itself then needs checking in case that cascades in any way. Or two build cycles. Works: mvn -s settings.xml release:prepare -DdryRun=true then fails mvn -s settings.xml release:prepare Bother. Andy
[jira] [Created] (JENA-892) Assembler does not support nested contexts
Rob Vesse created JENA-892:
--
Summary: Assembler does not support nested contexts
Key: JENA-892
URL: https://issues.apache.org/jira/browse/JENA-892
Project: Apache Jena
Issue Type: Improvement
Reporter: Rob Vesse
In answering [this
question|http://stackoverflow.com/questions/28812206/federated-query-with-secured-sparql-endpoint/28829913#28829913]
I realised that I could not simply use {{ja:context}} to specify the service
context because the assembler does not support nested contexts in any way which
means any complex context settings like service contexts have no way of being
created.
So we need some mechanism to allow us to create more complex contexts both in
the general sense and in the more specific service contexts need.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JENA-890) Pivot table in Fuseki2 has confusing design and user experience
[ https://issues.apache.org/jira/browse/JENA-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14344944#comment-14344944 ] Rob Vesse commented on JENA-890: +1 We should remove unnecessary UI, a nicer UI is valuable but unnecessary UI functionality is not Pivot table in Fuseki2 has confusing design and user experience --- Key: JENA-890 URL: https://issues.apache.org/jira/browse/JENA-890 Project: Apache Jena Issue Type: Improvement Components: Fuseki Affects Versions: Fuseki 2.0.0 Reporter: Ian Dickinson The SPARQL query tab on the Fuseki2 interface has an option in the results pane labelled 'pivot table'. It's very, very unclear what this does. It appears to be an experimental feature of some kind, but it does not provide a clear, discoverable user experience. In fact, after playing with it for some minutes, I still can't figure out what it is actually for. I suggest that either the UX of this feature is radically improved, or we remove it from Fuseki2 until it is ready for wider exposure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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
