You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@any23.apache.org by lewismc <gi...@git.apache.org> on 2017/04/11 22:29:37 UTC

[GitHub] any23 pull request #37: ANY23-282 Replacement for all Sindice namespaces and...

GitHub user lewismc opened a pull request:

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

    ANY23-282 Replacement for all Sindice namespaces and URI's

    This issue addresses https://issues.apache.org/jira/browse/ANY23-282

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/lewismc/any23 ANY23-282

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/any23/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #37
    
----
commit a6d3a186a03752f6beb167aa793693109e5fc968
Author: Lewis John McGibbney <le...@gmail.com>
Date:   2017-04-11T22:29:15Z

    ANY23-282 Replacement for all Sindice namespaces and URI's

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by lewismc <gi...@git.apache.org>.
Github user lewismc commented on the issue:

    https://github.com/apache/any23/pull/37
  
    This currently results in some extraction errors/exceptions so we need to find new IRI's for the sindice entries.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by lewismc <gi...@git.apache.org>.
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by lewismc <gi...@git.apache.org>.
Github user lewismc commented on the issue:

    https://github.com/apache/any23/pull/37
  
    Hi @ansell I have reverted the prefix list and committed the patch to master, if we find that this creates a nasty issue moving forward we can revert the commit. 


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by lewismc <gi...@git.apache.org>.
Github user lewismc commented on the issue:

    https://github.com/apache/any23/pull/37
  
    I pushed another commit which I think better aligns the popular prefixes with the current state of affairs. I'll need to work on some of the tests which are failing... I'll do that right now.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by ansell <gi...@git.apache.org>.
Github user ansell commented on the issue:

    https://github.com/apache/any23/pull/37
  
    Never seen "rdf1" in an auto-generated document before. Its not illegal, as long as the namespace is declared correctly, just a bit strange. Having said that, it is also potentially not interoperable with broken non-namespace-aware parsers (as angle-bracket-allergic devs are prone to implement). Probably worth looking into. Try reverting your sorting of the prefix list to put the rdf prefix first again and see if that fixes it.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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

Posted by lewismc <gi...@git.apache.org>.
Github user lewismc commented on the issue:

    https://github.com/apache/any23/pull/37
  
    Thanks @ansell can you please scope out the edit (regression???) I had to make to service/src/test/java/org/apache/any23/servlet/ServletTest.java
    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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] any23 pull request #37: ANY23-282 Replacement for all Sindice namespaces and...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---