[jira] [Commented] (ANY23-282) Replacement for all Sindice namespaces and URI's

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-282:
--

Github user lewismc commented on the issue:

https://github.com/apache/any23/pull/37
  
any comments here folks?


> Replacement for all Sindice namespaces and URI's
> 
>
> Key: ANY23-282
> URL: https://issues.apache.org/jira/browse/ANY23-282
> Project: Apache Any23
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.1
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 2.1
>
>
> Right now we have a number of [common 
> prefixes|https://github.com/apache/any23/blob/master/core/src/main/resources/org/apache/any23/prefixes/prefixes.properties]
>  which directly relate to the now deprecated [sindice.com|http://sindice.com].
> We need to fix this issue, essentially updating Any23 to resolve extractions 
> to something which is persistent, available and useful/meaningful. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 issue #37: ANY23-282 Replacement for all Sindice namespaces and URI's

[lewismc]

Github user lewismc commented on the issue:

https://github.com/apache/any23/pull/37
  
any comments here folks?


---
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.
---

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[Hudson (JIRA)]

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

Hudson commented on ANY23-308:
--

SUCCESS: Integrated in Jenkins build Any23-trunk #1494 (See 
[https://builds.apache.org/job/Any23-trunk/1494/])
Fix ANY23-308 (grzebyta.dev: rev ae036a7af2a8c5a5572b6e17832f69bd8f4b4ba4)
* (edit) pom.xml
* (add) utils/pom.xml
* (edit) cli/pom.xml
* (add) cli/src/test/java/org/apache/any23/cli/YAMLRoverTest.java
* (edit) core/pom.xml
* (add) utils/src/test/resources/log4j.properties
* (add) 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLTikaParserTest.java
* (edit) README.md
* (edit) 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLExtractorTest.java
* (add) utils/src/main/java/org/apache/any23/extractor/csv/CSVReaderBuilder.java
* (delete) 
csvutils/src/main/java/org/apache/any23/extractor/csv/CSVReaderBuilder.java
* (delete) csvutils/pom.xml
* (add) utils/src/test/java/org/apache/any23/yaml/utils/YAMLValidatorTest.java
* (delete) csvutils/src/test/resources/log4j.properties
* (edit) mime/src/main/java/org/apache/any23/mime/TikaMIMETypeDetector.java
* (edit) core/src/main/java/org/apache/any23/extractor/yaml/YAMLExtractor.java
* (edit) mime/pom.xml
* (add) utils/src/main/java/org/apache/any23/extractor/yaml/YAMLValidator.java
Ref ANY23-308 (grzebyta.dev: rev 9839e212ec265237021219c0fff120929906e7bf)
* (add) csvutils/pom.xml
* (delete) utils/src/test/resources/log4j.properties
* (edit) mime/pom.xml
* (edit) 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLExtractorTest.java
* (edit) 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLTikaParserTest.java
* (add) csvutils/src/test/resources/log4j.properties
* (edit) pom.xml
* (delete) utils/pom.xml
* (delete) 
utils/src/main/java/org/apache/any23/extractor/csv/CSVReaderBuilder.java
* (edit) mime/src/main/java/org/apache/any23/mime/TikaMIMETypeDetector.java
* (delete) 
utils/src/main/java/org/apache/any23/extractor/yaml/YAMLValidator.java
* (edit) cli/src/test/resources/log4j.properties
* (delete) 
utils/src/test/java/org/apache/any23/yaml/utils/YAMLValidatorTest.java
* (add) 
csvutils/src/main/java/org/apache/any23/extractor/csv/CSVReaderBuilder.java


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-308:
--

Github user asfgit closed the pull request at:

https://github.com/apache/any23/pull/42


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 pull request #42: ANY23-308 [NEW] Adding option -d support for yaml fi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/any23/pull/42


---
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.
---

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-308:
--

Github user ansell commented on the issue:

https://github.com/apache/any23/pull/42
  
I am fixing some compile and test errors and merging it into master. Thanks!


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 issue #42: ANY23-308 [NEW] Adding option -d support for yaml files

[ansell]

Github user ansell commented on the issue:

https://github.com/apache/any23/pull/42
  
I am fixing some compile and test errors and merging it into master. Thanks!


---
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.
---

[GitHub] any23 issue #40: Downloads page updates

[ansell]

Github user ansell commented on the issue:

https://github.com/apache/any23/pull/40
  
Adding the repository that you can push to requires running the following 
(where you can name it something different to ``upstream``, you just need to 
reuse that name for when you push to it later on:

```git remote add upstream 
https://git-wip-us.apache.org/repos/asf/any23.git```

Then you can fetch that repository, just to get its branch/etc. information 
into your local copy using:

```git fetch upstream```

Or you can all fetch all remotes at the same time with:

```git fetch --all```

It is a recommendation to always branch when you are working on an issue. 
After you create the issue, you run the following to switch to master, update 
it to whatever is in the upstream, then start your branch:

```
git checkout master
git merge --ff-only upstream/master
git checkout -b ANY23-NNN
```

Then you commit on that branch and push it back to your github fork using:

```
git commit -a -m "Message goes here"
git push origin ANY23-NNN
```

Then open a pull request on Github so the others can review it.

Then if all is good and you are the one who will merge it back start by 
updating your master branch with any changes since you branched:

```
git fetch --all
git checkout master
git merge --ff-only upstream/master
```

Then merge the branch into master:

```
git merge --no-ff ANY23-NNN
```

And then push back to the upstream (which will require your Apache username 
and password):

```
git push upstream master
```

If this push fails with a message about a conflict because someone else 
pushed in the meantime (unlikely because you updated master just before merging 
and pushing, but still possible) then you need to run the following, note the 
difference this time to use ``--no-ff`` (no fast forward merging, so it will 
create a merge commit as you did above in 6a954ad):

```
git fetch --all
git merge --no-ff upstream/master
git push upstream master
```

HTH


---
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.
---

[GitHub] any23 issue #40: Downloads page updates

[band]

Github user band commented on the issue:

https://github.com/apache/any23/pull/40
  
@lewismc I am stuck regarding how to proceed to commit the updated 
download.xml.vm file.
I do not have notes on how I even updated the pom.xml file with my name. 
So, please do provide some guidance on how to take what is in my github fork 
and get it into the git-wp-us.apache.org repo. I think it has to do with 
creating a branch with the JIRA issue number, but I need some exact steps to 
take.
(And I do regret that I did not keep notes of the steps I took then.)


---
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.
---

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-308:
--

Github user jgrzebyta commented on the issue:

https://github.com/apache/any23/pull/42
  
I have changed code and yaml mime type is detected based on file name only 
rather by the content. I removed useless code: restored `csvutils` module.


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 issue #42: ANY23-308 [NEW] Adding option -d support for yaml files

[jgrzebyta]

Github user jgrzebyta commented on the issue:

https://github.com/apache/any23/pull/42
  
I have changed code and yaml mime type is detected based on file name only 
rather by the content. I removed useless code: restored `csvutils` module.


---
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.
---

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-308:
--

Github user jgrzebyta commented on a diff in the pull request:

https://github.com/apache/any23/pull/42#discussion_r127026645
  
--- Diff: 
utils/src/main/java/org/apache/any23/extractor/yaml/YAMLValidator.java ---
@@ -0,0 +1,105 @@
+/*
+ * Copyright 2017 The Apache Software Foundation.
+ *
+ * Licensed 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.
+ */
+package org.apache.any23.extractor.yaml;
+
+import com.google.common.collect.Iterables;
+import java.io.BufferedInputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.Scanner;
+import java.util.regex.Pattern;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.yaml.snakeyaml.Yaml;
+
+/**
+ * Utility class provides static methods for YAML validation.
+ *
+ * @author Jacek Grzebyta (grzebyta.dev [at] gmail.com)
+ */
+public class YAMLValidator {
+
+private static final Logger log = 
LoggerFactory.getLogger(YAMLValidator.class);
+
+private static final Pattern YAML_PATTERN = 
Pattern.compile("^%YAML.*", Pattern.CASE_INSENSITIVE);
+
+/**
+ * Detects if is contains valid YAML content.
+ * 
+ * In the first instance it checks if there is "%YAML" head. If not 
check
+ * using the brute force method by parsing input stream with yaml 
parser.
+ * 
+ * 
+ * NB. Only "false" results are trusted. Even if result is "true" you 
cannot
+ * be sure that InputStream contains YAML intentional context because
+ * comma-separated-values are pars-able by YAML parser as well.
+ * 
+ *
+ * @param is {@link InputStream}
+ * @return
+ * @throws IOException
+ */
+public static boolean isYAML(InputStream is) throws IOException {
+if (is == null) {
+return false;
+}
+
+if (!is.markSupported()) {
--- End diff --

I have checked in the source and `markSupported()` method olny contains 
`return true` or `return false`.


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 pull request #42: ANY23-308 [NEW] Adding option -d support for yaml fi...

[jgrzebyta]

Github user jgrzebyta commented on a diff in the pull request:

https://github.com/apache/any23/pull/42#discussion_r127026645
  
--- Diff: 
utils/src/main/java/org/apache/any23/extractor/yaml/YAMLValidator.java ---
@@ -0,0 +1,105 @@
+/*
+ * Copyright 2017 The Apache Software Foundation.
+ *
+ * Licensed 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.
+ */
+package org.apache.any23.extractor.yaml;
+
+import com.google.common.collect.Iterables;
+import java.io.BufferedInputStream;
+import java.io.IOException;
+import java.io.InputStream;
+import java.util.Scanner;
+import java.util.regex.Pattern;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.yaml.snakeyaml.Yaml;
+
+/**
+ * Utility class provides static methods for YAML validation.
+ *
+ * @author Jacek Grzebyta (grzebyta.dev [at] gmail.com)
+ */
+public class YAMLValidator {
+
+private static final Logger log = 
LoggerFactory.getLogger(YAMLValidator.class);
+
+private static final Pattern YAML_PATTERN = 
Pattern.compile("^%YAML.*", Pattern.CASE_INSENSITIVE);
+
+/**
+ * Detects if is contains valid YAML content.
+ * 
+ * In the first instance it checks if there is "%YAML" head. If not 
check
+ * using the brute force method by parsing input stream with yaml 
parser.
+ * 
+ * 
+ * NB. Only "false" results are trusted. Even if result is "true" you 
cannot
+ * be sure that InputStream contains YAML intentional context because
+ * comma-separated-values are pars-able by YAML parser as well.
+ * 
+ *
+ * @param is {@link InputStream}
+ * @return
+ * @throws IOException
+ */
+public static boolean isYAML(InputStream is) throws IOException {
+if (is == null) {
+return false;
+}
+
+if (!is.markSupported()) {
--- End diff --

I have checked in the source and `markSupported()` method olny contains 
`return true` or `return false`.


---
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.
---

[jira] [Commented] (ANY23-308) Adding option "-d" to yaml file parsing gives error

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on ANY23-308:
--

Github user jgrzebyta commented on a diff in the pull request:

https://github.com/apache/any23/pull/42#discussion_r127007051
  
--- Diff: 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLExtractorTest.java ---
@@ -93,4 +92,17 @@ public void nullTest()
 RepositoryResult docs = getStatements(null, null, 
RDF.NIL);
 Assert.assertTrue(Iterations.asList(docs).size() == 2);
 }
+
+/**
+ * Comma separated values are parsed as well.
+ *
+ * @throws Exception
+ */
+@Test
+public void csvTest()
+throws Exception {
+assertExtract("/org/apache/any23/extractor/csv/test-comma.csv");
--- End diff --

That is false positive. It is just proof that for text-based formats 
additional recognising should be done from `meta`. I will delete that.


> Adding option "-d" to yaml file parsing gives error
> ---
>
> Key: ANY23-308
> URL: https://issues.apache.org/jira/browse/ANY23-308
> Project: Apache Any23
>  Issue Type: Bug
>  Components: rover
>Affects Versions: 2.0
>Reporter: Jacek
>Assignee: Jacek
>Priority: Minor
> Fix For: 2.1
>
>
> Command 
> {code:none}
> any23 rover -e yaml -d "urn:test#" -f turtle some_yaml_file.yaml
> {code}
> gives `No suitable extractors found`.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] any23 pull request #42: ANY23-308 [NEW] Adding option -d support for yaml fi...

[jgrzebyta]

Github user jgrzebyta commented on a diff in the pull request:

https://github.com/apache/any23/pull/42#discussion_r127007051
  
--- Diff: 
core/src/test/java/org/apache/any23/extractor/yaml/YAMLExtractorTest.java ---
@@ -93,4 +92,17 @@ public void nullTest()
 RepositoryResult docs = getStatements(null, null, 
RDF.NIL);
 Assert.assertTrue(Iterations.asList(docs).size() == 2);
 }
+
+/**
+ * Comma separated values are parsed as well.
+ *
+ * @throws Exception
+ */
+@Test
+public void csvTest()
+throws Exception {
+assertExtract("/org/apache/any23/extractor/csv/test-comma.csv");
--- End diff --

That is false positive. It is just proof that for text-based formats 
additional recognising should be done from `meta`. I will delete that.


---
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.
---

[jira] [Created] (ANY23-310) Rover displays wrong statistical values

[Jacek (JIRA)]

Jacek created ANY23-310:
---

 Summary: Rover displays wrong statistical values
 Key: ANY23-310
 URL: https://issues.apache.org/jira/browse/ANY23-310
 Project: Apache Any23
  Issue Type: Bug
  Components: CLI, rover
Affects Versions: 2.0
Reporter: Jacek
Priority: Minor


Rover and log file contain wrong statistics: 
 - missing used extractor
 - content length is 0
 - shows 0 triples




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ANY23-303) JsonLdError: loading remote context failed: http://schema.org/

[William L. Anderson (JIRA)]

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

William L. Anderson commented on ANY23-303:
---

[~p_ansell] pointed out that the Java version installed on my computer was too 
old. I upgraded to Java version: 1.8.0_131 and all modules successfully build 
with 2.0 source and the current 2.1 source.

So I think there are no JSONLD remote context load errors.

> JsonLdError: loading remote context failed: http://schema.org/
> --
>
> Key: ANY23-303
> URL: https://issues.apache.org/jira/browse/ANY23-303
> Project: Apache Any23
>  Issue Type: Bug
>  Components: extractors
>Affects Versions: 2.1
>Reporter: Matt Snyder
> Fix For: 2.1
>
>
> For an html page with embedded json-ld, I'm getting JsonLdError: loading 
> remote context failed: http://schema.org/
> Could it be a manifestation of issue #180 on jsonld-java ?  That issue is 
> marked closed.
> Full traceback:
> {code:java}
> org.apache.any23.extractor.ExtractionException: Error while parsing RDF 
> document.
>   at 
> org.apache.any23.extractor.rdf.BaseRDFExtractor.run(BaseRDFExtractor.java:109)
>   at 
> org.apache.any23.extractor.html.EmbeddedJSONLDExtractor.extractJSONLDScript(EmbeddedJSONLDExtractor.java:149)
>   at 
> org.apache.any23.extractor.html.EmbeddedJSONLDExtractor.run(EmbeddedJSONLDExtractor.java:82)
>   at 
> org.apache.any23.extractor.html.EmbeddedJSONLDExtractor.run(EmbeddedJSONLDExtractor.java:53)
>   at 
> org.apache.any23.extractor.SingleDocumentExtraction.runExtractor(SingleDocumentExtraction.java:475)
>   at 
> org.apache.any23.extractor.SingleDocumentExtraction.run(SingleDocumentExtraction.java:256)
>   at org.apache.any23.Any23.extract(Any23.java:300)
>   at org.apache.any23.Any23.extract(Any23.java:452)
>   at org.apache.any23.cli.Rover.performExtraction(Rover.java:178)
>   at org.apache.any23.cli.Rover.run(Rover.java:211)
>   at org.apache.any23.cli.ToolRunner.execute(ToolRunner.java:136)
>   at org.apache.any23.cli.ToolRunner.main(ToolRunner.java:69)
> Caused by: org.eclipse.rdf4j.rio.RDFParseException: Could not parse JSONLD
>   at org.eclipse.rdf4j.rio.jsonld.JSONLDParser.parse(JSONLDParser.java:71)
>   at 
> org.apache.any23.extractor.rdf.BaseRDFExtractor.run(BaseRDFExtractor.java:105)
>   ... 11 more
> Caused by: com.github.jsonldjava.core.JsonLdError: loading remote context 
> failed: http://schema.org/
>   at 
> com.github.jsonldjava.core.DocumentLoader.loadDocument(DocumentLoader.java:31)
>   at com.github.jsonldjava.core.Context.parse(Context.java:195)
>   at com.github.jsonldjava.core.Context.parse(Context.java:142)
>   at com.github.jsonldjava.core.Context.parse(Context.java:286)
>   at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:543)
>   at com.github.jsonldjava.core.JsonLdApi.expand(JsonLdApi.java:997)
>   at 
> com.github.jsonldjava.core.JsonLdProcessor.expand(JsonLdProcessor.java:146)
>   at 
> com.github.jsonldjava.core.JsonLdProcessor.toRDF(JsonLdProcessor.java:482)
>   at org.eclipse.rdf4j.rio.jsonld.JSONLDParser.parse(JSONLDParser.java:68)
>   ... 12 more
> {code}
> html snippet:
> {code:html}
> 
> {
>   "@context": "http://schema.org/";,
>   "@type": "Product",
>   "name": "test product"
> }
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Fwd: Digest for web-data-comm...@googlegroups.com - 1 update in 1 topic

[lewis john mcgibbney]

-- Forwarded message -
From: 
Date: Wed, Jul 12, 2017 at 5:15 AM
Subject: Digest for web-data-comm...@googlegroups.com - 1 update in 1 topic
To: Digest recipients 


web-data-comm...@googlegroups.com

Google
Groups


Topic digest
View all topics


   - ANN: WebDataCommons releases 24.4 billion quads RDFa, Microdata,
   Embedded JSON-LD and Microformat data originating from 2.7 million
   pay-level-domains <#m_7918109642067574354_group_thread_0> - 1 Update

ANN: WebDataCommons releases 24.4 billion quads RDFa, Microdata, Embedded
JSON-LD and Microformat data originating from 2.7 million pay-level-domains

Anna Primpeli : Jul 11 06:13AM -0700

Hello,

the updated schemaOrg subset files are now online
<
http://webdatacommons.org/structureddata/2015-11/stats/schema_org_subsets.html
>
.
Thank you once again for your feedback! Please let us know in case you face
any further problems.

Best,
Anna
Back to top <#m_7918109642067574354_digest_top>
You received this digest because you're subscribed to updates for this
group. You can change your settings on the group membership page

.
To unsubscribe from this group and stop receiving emails from it send an
email to web-data-commons+unsubscr...@googlegroups.com.
-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney