[jira] [Resolved] (ANY23-198) Add XML Schema datatypes

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-198.

   Resolution: Incomplete
Fix Version/s: (was: 1.3)

The issue description does not indicate where the feature needs to be added. 
XMLSchema datatypes are all supported in general by all of the RDF parsers. 
Reopen with further details of a particular feature that is required if 
necessary.

> Add XML Schema datatypes
> 
>
> Key: ANY23-198
> URL: https://issues.apache.org/jira/browse/ANY23-198
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: core
>Reporter: Norbert Lanzanasto
>
> Add the XML Schema datatype to the extracted RDF objects (e.g. 
> "2014-04-10T23:00:00-04:00^^http://www.w3.org/2001/XMLSchema#dateTime;). 
> Probably define a configuration field for it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-252) JSON-LD format MIME type is not detected

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-252.

   Resolution: Fixed
 Assignee: Peter Ansell
Fix Version/s: (was: 1.3)
   2.0

Verified that in version 2 the use of "--format application/ld+json" works as 
expected so it is available on the runtime classpath and linked in.

> JSON-LD format MIME type is not detected
> 
>
> Key: ANY23-252
> URL: https://issues.apache.org/jira/browse/ANY23-252
> Project: Apache Any23
>  Issue Type: Bug
>  Components: CLI
>Affects Versions: 1.1
>Reporter: Michele Mostarda
>Assignee: Peter Ansell
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ANY23-257) Support OWL as an input format

[Peter Ansell (JIRA)]

[ 
https://issues.apache.org/jira/browse/ANY23-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819629#comment-15819629
 ] 

Peter Ansell commented on ANY23-257:


This is temporarily blocked on OWLAPI releasing a new version in the 5.x series 
with RDF4J support.

> Support OWL as an input format
> --
>
> Key: ANY23-257
> URL: https://issues.apache.org/jira/browse/ANY23-257
> Project: Apache Any23
>  Issue Type: Bug
>  Components: extractors
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 1.3
>
>
> I am tying to parse ontology files from the following page
> http://sweet.jpl.nasa.gov/sweet2.3
> We should add this support to improve Any23 extractions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ANY23-263) Upgrade to Tika 1.14

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell updated ANY23-263:
---
Fix Version/s: (was: 1.3)
   2.0

> Upgrade to Tika 1.14
> 
>
> Key: ANY23-263
> URL: https://issues.apache.org/jira/browse/ANY23-263
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: mime
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 2.0
>
>
> We recently released Apache Tika 1.8. Any23 should upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ANY23-264) Upgrade to use public commons-csv instead of custom SNAPSHOT

[Peter Ansell (JIRA)]

[ 
https://issues.apache.org/jira/browse/ANY23-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819578#comment-15819578
 ] 

Peter Ansell commented on ANY23-264:


There were non-trivial API changed between our 1.0-SNAPSHOT version and the 
official 1.0 version that was released. I have no personal experience with 
commons-csv, and unassigning myself.

> Upgrade to use public commons-csv instead of custom SNAPSHOT
> 
>
> Key: ANY23-264
> URL: https://issues.apache.org/jira/browse/ANY23-264
> Project: Apache Any23
>  Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 1.3
>
>
> Unbeknown to me, it appears that commons-csv finally released a couple of 
> artifacts which means we can drop support of our [old SNAPSHOT dependency and 
> makeshift 
> repository|http://svn.apache.org/repos/asf/any23/repo-ext/org/apache/commons/commons-csv/]
>  in favor of a nice new shiny public artifact
> http://search.maven.org/#artifactdetails|org.apache.commons|commons-csv|1.1|jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ANY23-263) Upgrade to Tika 1.14

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell updated ANY23-263:
---
Summary: Upgrade to Tika 1.14  (was: Upgrade to Tika 1.8)

> Upgrade to Tika 1.14
> 
>
> Key: ANY23-263
> URL: https://issues.apache.org/jira/browse/ANY23-263
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: mime
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 2.0
>
>
> We recently released Apache Tika 1.8. Any23 should upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-292) slf4j scope should not be test in any23 core

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-292.

   Resolution: Won't Fix
 Assignee: Peter Ansell  (was: Lewis John McGibbney)
Fix Version/s: (was: 1.2)

Fixed the requirement that core have a non-test dependency on a particular 
logging implementation by moving the CLI to its own module.

> slf4j scope should not be test in any23 core
> 
>
> Key: ANY23-292
> URL: https://issues.apache.org/jira/browse/ANY23-292
> Project: Apache Any23
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
>Priority: Trivial
>
> This was recently flagged within user@ mailing list conversation 
> http://www.mail-archive.com/user%40any23.apache.org/msg00236.html
> {code}
> 3. When I run `bin/any23` from the core package I always see the following
> at the top of user output:
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> further details.
> {code}
> The patch will fix the issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-19) Abstract away any specific RDF APIs

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-19.
---
Resolution: Won't Fix

Not a priority in the foreseeable future of the project.

> Abstract away any specific RDF APIs
> ---
>
> Key: ANY23-19
> URL: https://issues.apache.org/jira/browse/ANY23-19
> Project: Apache Any23
>  Issue Type: Wish
>Affects Versions: 0.7.0
>Reporter: Paolo Castagna
>Priority: Minor
> Fix For: 1.3
>
>
> Any23 currently uses Sesame to work with or parse RDF. Specifically Any23 
> uses these classes from org.openrdf.* packages:
> org.openrdf.model.BNode
> org.openrdf.model.datatypes.XMLDatatypeUtil
> org.openrdf.model.impl.LiteralImpl
> org.openrdf.model.impl.URIImpl
> org.openrdf.model.impl.ValueFactoryImpl
> org.openrdf.model.Literal
> org.openrdf.model.Resource
> org.openrdf.model.Statement
> org.openrdf.model.URI
> org.openrdf.model.Value
> org.openrdf.model.ValueFactory
> org.openrdf.model.vocabulary.OWL
> org.openrdf.model.vocabulary.RDF
> org.openrdf.model.vocabulary.RDFS
> org.openrdf.model.vocabulary.XMLSchema
> org.openrdf.repository.RepositoryConnection
> org.openrdf.repository.RepositoryException
> org.openrdf.repository.RepositoryResult
> org.openrdf.repository.sail.SailRepository
> org.openrdf.rio.helpers.RDFParserBase
> org.openrdf.rio.ntriples.NTriplesParser
> org.openrdf.rio.ntriples.NTriplesUtil
> org.openrdf.rio.ntriples.NTriplesWriter
> org.openrdf.rio.ParseErrorListener
> org.openrdf.rio.ParseLocationListener
> org.openrdf.rio.RDFFormat
> org.openrdf.rio.RDFHandler
> org.openrdf.rio.RDFHandlerException
> org.openrdf.rio.RDFParseException
> org.openrdf.rio.RDFParser
> org.openrdf.rio.rdfxml.RDFXMLParser
> org.openrdf.rio.rdfxml.RDFXMLWriter
> org.openrdf.rio.turtle.TurtleWriter
> org.openrdf.sail.memory.MemoryStore
> org.openrdf.sail.Sail
> org.openrdf.sail.SailException
> Would it be possible to abstract away any specific RDF APIs to allow Any23 
> users to chose between, say: Apache Clerezza [1], Apache Jena [2], Sesame [3] 
> and/or others?
> An example of small RDF distiller which does this is java-rdfa [4]. Maybe a 
> similar agnostic (but easy to integrate) approach is possible for Any23. 
> Although, java-rdfa does not need to parse RDF content itself. 
>  [1] http://incubator.apache.org/clerezza/
>  [2] http://incubator.apache.org/jena/
>  [3] http://www.openrdf.org/
>  [4] https://github.com/shellac/java-rdfa



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-163) VocabPrinter tool broken with No writer factory available for RDF format N-Quads (mimeTypes=text/x-nquads; ext=nq)

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-163.

Resolution: Cannot Reproduce

Cannot reproduce currently, nquads is supported currently.

> VocabPrinter tool broken with No writer factory available for RDF format 
> N-Quads (mimeTypes=text/x-nquads; ext=nq)
> --
>
> Key: ANY23-163
> URL: https://issues.apache.org/jira/browse/ANY23-163
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 0.8.0
>Reporter: Lewis John McGibbney
> Fix For: 1.3
>
>
> When I try to run
> any23 vocab from the command line I get the following
> {code:xml}
> law@CEE279Law3-Linux:~/Desktop$ any23 vocab
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
> details.
> 
> Apache Any23 :: vocab
> 
> 
> Apache Any23 FAILURE
> Execution terminated with errors: No writer factory available for RDF format 
> N-Quads (mimeTypes=text/x-nquads; ext=nq)
> Total time: 0s
> Finished at: Tue Jul 02 11:54:34 PDT 2013
> Final Memory: 7M/479M
> 
> {code}
> The website states that this tool is in beta version. It is clearly broken 
> for the time being. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-99) NQuadsWriter should force ASCII in OutputStream constructor

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-99.
---
Resolution: Won't Fix

NQuads module removed, RDF4J uses RDF-1.1 NQuads that requires UTF-8

> NQuadsWriter should force ASCII in OutputStream constructor
> ---
>
> Key: ANY23-99
> URL: https://issues.apache.org/jira/browse/ANY23-99
> Project: Apache Any23
>  Issue Type: Bug
>  Components: core
>Affects Versions: 0.8.0
>Reporter: Peter Ansell
> Fix For: 1.3
>
>
> The NQuads specification states that all NQuads documents must be ASCII 
> encoded. [1] The current NQuadsWriter(OutputStream) constructor does not 
> enforce this when creating the OutputStreamWriter to wrap up the given 
> outputstream. If it is not enforced, then the users locale will be used to 
> create the OutputStreamWriter, which may not enforce US-ASCII.
> Patch is to replace the constructor with:
> this( new OutputStreamWriter(os, Charset.forName("US-ASCII")) );
> [1] http://sw.deri.org/2008/07/n-quads/#mediatype



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-153) Automatically Generate EARL reports for Any23 RDF Parsers

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-153.

Resolution: Won't Fix

No more local RDF format parsers with compliance suites provided by external 
entities.

> Automatically Generate EARL reports for Any23 RDF Parsers
> -
>
> Key: ANY23-153
> URL: https://issues.apache.org/jira/browse/ANY23-153
> Project: Apache Any23
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Lewis John McGibbney
> Fix For: 1.3
>
>
> In the past we have been approached by W3C [0] to provide EARL reports based 
> on our conformance.
> Unfortunately this never materialized and has stagnated significantly.  
> This issue should automate the production of EARL reports for various Any23 
> Components. Hopefully this will enable us to build community around the 
> reports.
> [0] https://issues.apache.org/jira/browse/ANY23-69



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-92) NQuadsParser does not require whitespace between elements

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-92.
---
Resolution: Won't Fix

NQuads module removed and using RDF4J module as replacement

> NQuadsParser does not require whitespace between elements
> -
>
> Key: ANY23-92
> URL: https://issues.apache.org/jira/browse/ANY23-92
> Project: Apache Any23
>  Issue Type: Bug
>  Components: nquads
>Reporter: Peter Ansell
> Fix For: 1.3
>
>
> The NQuadsParser currently does not require whitespace between elements as 
> specified by the NQuads EBNF:
> contextTriple ::= subject ws+ predicate ws+ object ( ws+ context )? 
> ws* '.' ws* 
> ws+ indicates 1 or more whitespace characters are required between elements, 
> while the ws* at the end indicate 0 or more whitespace characters before the 
> period and before the end of the line.
> The current NQuadsParserTest test cases have quite a few triples that do not 
> put any whitespace between elements, so it will require patching the test 
> case to have failing triples for each potential error, and also adding cases 
> that have spaces and should succeed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-80) Split out command line tools into a separate module

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-80.
---
   Resolution: Fixed
Fix Version/s: (was: 1.3)
   2.0

Fixed in version2

> Split out command line tools into a separate module
> ---
>
> Key: ANY23-80
> URL: https://issues.apache.org/jira/browse/ANY23-80
> Project: Apache Any23
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Marco Fossati
>Assignee: Peter Ansell
>Priority: Minor
> Fix For: 2.0
>
>
> Command line runnable tools are very useful to have a fast grab on the whole 
> project. Since the binaries are somehow hidden i.e. one must build it all and 
> look for them in ./core/target/appassembler/bin , it would be nice to have a 
> separate package giving fast access to them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ANY23-80) Split out command line tools into a separate module

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell reassigned ANY23-80:
-

Assignee: Peter Ansell

> Split out command line tools into a separate module
> ---
>
> Key: ANY23-80
> URL: https://issues.apache.org/jira/browse/ANY23-80
> Project: Apache Any23
>  Issue Type: Improvement
>Affects Versions: 0.7.0
>Reporter: Marco Fossati
>Assignee: Peter Ansell
>Priority: Minor
> Fix For: 1.3
>
>
> Command line runnable tools are very useful to have a fast grab on the whole 
> project. Since the binaries are somehow hidden i.e. one must build it all and 
> look for them in ./core/target/appassembler/bin , it would be nice to have a 
> separate package giving fast access to them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ANY23-302) rover JSON output is not valid

[Peter Ansell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Ansell resolved ANY23-302.

Resolution: Fixed
  Assignee: Peter Ansell

Fixed in version2 branch. When errors occurred, as they do with this 
extraction, the endDocument was not always being called, resulting in an 
incomplete document syntax. Fixed by calling endDocument in a finally block in 
SingleDocumentExtraction.

> rover JSON output is not valid
> --
>
> Key: ANY23-302
> URL: https://issues.apache.org/jira/browse/ANY23-302
> Project: Apache Any23
>  Issue Type: Bug
>  Components: core, rover
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 2.0
>
>
> When building and using [~p_ansell]'s version2 branch, I execute the following
> {code}
> core/target/appassembler/bin/any23 rover -l output.log -o extraction.txt -s 
> https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
> {code}
> This results in the following invalid JSON output
> {code}
> { "quads" : [[{ "type" : "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://vocab.sindice.net/any23#viewport;, {"type" : "literal", "value" : 
> "width=device-width,initial-scale=1", "lang" : "en", "datatype" : 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
> "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://vocab.sindice.net/any23#Content-Type;, {"type" : "literal", "value" : 
> "text/html; charset=UTF-8", "lang" : "en", "datatype" : 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
> "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://purl.org/dc/terms/title;, {"type" : "literal", "value" : "Semantic 
> Technologies Group Semantic Repository Implementation (SRI) Use Cases & 
> Requirements (UCR)", "lang" : null, "datatype" : 
> "http://www.w3.org/2001/XMLSchema#string"}, null], [{ "type" : "uri", "value" 
> : "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#type;, { "type" : "uri", "value" 
> : "http://purl.org/ontology/bibo/Document"}, null], [{ "type" : "uri", 
> "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://purl.org/dc/terms/language;, {"type" : "literal", "value" : "en", 
> "lang" : null, "datatype" : "http://www.w3.org/2001/XMLSchema#string"}, null]
> {code}
> This is not valid, it is missing the following closing tags {code}]}{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ANY23-302) rover JSON output is not valid

[Peter Ansell (JIRA)]

[ 
https://issues.apache.org/jira/browse/ANY23-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819414#comment-15819414
 ] 

Peter Ansell commented on ANY23-302:


The rover tests were temporarily switched off because Twitter has moved to 
HTML5 and the parser we are using cannot parse it, failing with:

{noformat}
[Fatal Error] :13:117: The element type "meta" must be terminated by the 
matching end-tag "".
{noformat}

Not sure what could be causing the last two characters to be missing other than 
a missing close call somewhere.

> rover JSON output is not valid
> --
>
> Key: ANY23-302
> URL: https://issues.apache.org/jira/browse/ANY23-302
> Project: Apache Any23
>  Issue Type: Bug
>  Components: core, rover
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
> Fix For: 2.0
>
>
> When building and using [~p_ansell]'s version2 branch, I execute the following
> {code}
> ./bin/any23 rover -l output.log -o extraction.txt -s 
> https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
> {code}
> This results in the following invalid JSON output
> {code}
> { "quads" : [[{ "type" : "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://vocab.sindice.net/any23#viewport;, {"type" : "literal", "value" : 
> "width=device-width,initial-scale=1", "lang" : "en", "datatype" : 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
> "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://vocab.sindice.net/any23#Content-Type;, {"type" : "literal", "value" : 
> "text/html; charset=UTF-8", "lang" : "en", "datatype" : 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
> "uri", "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://purl.org/dc/terms/title;, {"type" : "literal", "value" : "Semantic 
> Technologies Group Semantic Repository Implementation (SRI) Use Cases & 
> Requirements (UCR)", "lang" : null, "datatype" : 
> "http://www.w3.org/2001/XMLSchema#string"}, null], [{ "type" : "uri", "value" 
> : "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#type;, { "type" : "uri", "value" 
> : "http://purl.org/ontology/bibo/Document"}, null], [{ "type" : "uri", 
> "value" : 
> "https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
> "http://purl.org/dc/terms/language;, {"type" : "literal", "value" : "en", 
> "lang" : null, "datatype" : "http://www.w3.org/2001/XMLSchema#string"}, null]
> {code}
> This is not valid, it is missing the following closing tags {code}]}{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ANY23-302) rover JSON output is not valid

[Lewis John McGibbney (JIRA)]

Lewis John McGibbney created ANY23-302:
--

 Summary: rover JSON output is not valid
 Key: ANY23-302
 URL: https://issues.apache.org/jira/browse/ANY23-302
 Project: Apache Any23
  Issue Type: Bug
  Components: rover, core
Affects Versions: 1.1
Reporter: Lewis John McGibbney
 Fix For: 2.0


When building and using [~p_ansell]'s version2 branch, I execute the following
{code}
./bin/any23 rover -l output.log -o extraction.txt -s 
https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html
{code}
This results in the following invalid JSON output
{code}
{ "quads" : [[{ "type" : "uri", "value" : 
"https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
"http://vocab.sindice.net/any23#viewport;, {"type" : "literal", "value" : 
"width=device-width,initial-scale=1", "lang" : "en", "datatype" : 
"http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
"uri", "value" : 
"https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
"http://vocab.sindice.net/any23#Content-Type;, {"type" : "literal", "value" : 
"text/html; charset=UTF-8", "lang" : "en", "datatype" : 
"http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"}, null], [{ "type" : 
"uri", "value" : 
"https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
"http://purl.org/dc/terms/title;, {"type" : "literal", "value" : "Semantic 
Technologies Group Semantic Repository Implementation (SRI) Use Cases & 
Requirements (UCR)", "lang" : null, "datatype" : 
"http://www.w3.org/2001/XMLSchema#string"}, null], [{ "type" : "uri", "value" : 
"https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
"http://www.w3.org/1999/02/22-rdf-syntax-ns#type;, { "type" : "uri", "value" : 
"http://purl.org/ontology/bibo/Document"}, null], [{ "type" : "uri", "value" : 
"https://esipfed.github.io/stc/UseCases/STCUseCasesAndRequirements.html"}, 
"http://purl.org/dc/terms/language;, {"type" : "literal", "value" : "en", 
"lang" : null, "datatype" : "http://www.w3.org/2001/XMLSchema#string"}, null]
{code}
This is not valid, it is missing the following closing tags {code}]}{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ANY23-276) Upgrade sesame dependencies to RDF4J

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ANY23-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15818761#comment-15818761
 ] 

ASF GitHub Bot commented on ANY23-276:
--

Github user lewismc commented on the issue:

https://github.com/apache/any23/pull/27
  
@ansell I just pulled the most recent version of this PR build and tested 
locally... all tests pass.


> Upgrade sesame dependencies to RDF4J
> 
>
> Key: ANY23-276
> URL: https://issues.apache.org/jira/browse/ANY23-276
> Project: Apache Any23
>  Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
>Assignee: Peter Ansell
> Fix For: 2.0
>
>
> The successor to OpenRDF Sesame, named Eclipse RDF4J, is in the process of 
> releasing its first versions, with milestone builds available for testing on 
> Maven Central. 
> We should upgrade in Any23 as OpenRDF Sesame will not be releasing any more 
> versions now that the Eclipse project is up and running.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] any23 issue #27: ANY23-276 : Work on conversion to RDF4J, including bump to ...

[lewismc]

Github user lewismc commented on the issue:

https://github.com/apache/any23/pull/27
  
@ansell I just pulled the most recent version of this PR build and tested 
locally... all tests pass.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: any23-vm migration

[fbarb...@apache.org]

Hi PMC Team,

Do you have any update on this?
Please let us know.

Thanks,
-Freddy.

On Jan 9, 2017 11:11 AM, "Freddy-apache"  wrote:

> Hi PMC,
>
> We are working in a project about migrating any23-vm.
>
> Can you please let us know if you are still using Or need this VM?
>
> Please, let us know.
>
> Thanks,
>
> - Freddy.
> On behalf of ASF.
> Infrastructure Team.
>
>

[jira] [Resolved] (ANY23-299) Missing YAML to RDF parser

[Jacek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek resolved ANY23-299.
-
Resolution: Fixed
  Assignee: Jacek

I have added more unit tests and stuff looks fine to me.

> Missing YAML to RDF parser
> --
>
> Key: ANY23-299
> URL: https://issues.apache.org/jira/browse/ANY23-299
> Project: Apache Any23
>  Issue Type: Improvement
>  Components: core, extractors
>Affects Versions: 1.1
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
>  Labels: features, patch
> Fix For: 1.2
>
>
> I created YAML to RDF parser but I found there is not enough flexibility 
> within the core. I will fix the issue.
> Issue related to ANY23-280



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ANY23-300) Ignore NetBeans configuration files

[Jacek (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ANY23-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacek closed ANY23-300.
---

PR accepted

> Ignore NetBeans configuration files
> ---
>
> Key: ANY23-300
> URL: https://issues.apache.org/jira/browse/ANY23-300
> Project: Apache Any23
>  Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: Jacek
>Assignee: Jacek
>Priority: Trivial
>  Labels: git
> Fix For: 1.2
>
>
> NetBeans creates additional configuration files.
> Just added relevant patterns into .gitignore



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)