You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "SinDoc (JIRA)" <ji...@apache.org> on 2007/07/06 22:53:04 UTC

[jira] Created: (FOR-1018) Making sourcetypeaction work for RDF files

Making sourcetypeaction work for RDF files
------------------------------------------

                 Key: FOR-1018
                 URL: https://issues.apache.org/jira/browse/FOR-1018
             Project: Forrest
          Issue Type: Sub-task
          Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
    Affects Versions: 0.9-dev
            Reporter: SinDoc
            Priority: Minor
             Fix For: 0.9-dev


In an effort to use the sourcetypeaction mechanism in the sitemap to intelligently prcess input files, I noticed that RDF/XML formats require extra processing for their action type to be determined. Obviously because neither doctype nor processing instruction events are likely to appear in RDF/XML formats and the only way to choose an action should be base on the namespace. The namespace of the root element doesn't help either in this case, as an RDF file might or not start with the rdf:RDF root element, therefore checking only the root element doesn't necessarily imply the actual format of the file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (FOR-1018) Making sourcetypeaction work for RDF files

Posted by "Gavin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed FOR-1018.
----------------------

    Resolution: Fixed

David has applied this.

> Making sourcetypeaction work for RDF files
> ------------------------------------------
>
>                 Key: FOR-1018
>                 URL: https://issues.apache.org/jira/browse/FOR-1018
>             Project: Forrest
>          Issue Type: Sub-task
>          Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
>    Affects Versions: 0.9-dev
>            Reporter: Sina K. Heshmati
>            Priority: Minor
>             Fix For: 0.9-dev
>
>         Attachments: sourcetypeaction-rdf.patch
>
>
> In an effort to use the sourcetypeaction mechanism in the sitemap to intelligently prcess input files, I noticed that RDF/XML formats require extra processing for their action type to be determined. Obviously because neither doctype nor processing instruction events are likely to appear in RDF/XML formats and the only way to choose an action should be base on the namespace. The namespace of the root element doesn't help either in this case, as an RDF file might or not start with the rdf:RDF root element, therefore checking only the root element doesn't necessarily imply the actual format of the file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-1018) Making sourcetypeaction work for RDF files

Posted by "SinDoc (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510794 ] 

SinDoc commented on FOR-1018:
-----------------------------

I forgot to make a patch from $FORREST_HOME, so just in case, here [1] is another one.

[1] http://sina.khakbaz.com/2007/patches/sourcetypeaction-rdf.patch

> Making sourcetypeaction work for RDF files
> ------------------------------------------
>
>                 Key: FOR-1018
>                 URL: https://issues.apache.org/jira/browse/FOR-1018
>             Project: Forrest
>          Issue Type: Sub-task
>          Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
>    Affects Versions: 0.9-dev
>            Reporter: SinDoc
>            Priority: Minor
>             Fix For: 0.9-dev
>
>         Attachments: sourcetypeaction-rdf.patch
>
>
> In an effort to use the sourcetypeaction mechanism in the sitemap to intelligently prcess input files, I noticed that RDF/XML formats require extra processing for their action type to be determined. Obviously because neither doctype nor processing instruction events are likely to appear in RDF/XML formats and the only way to choose an action should be base on the namespace. The namespace of the root element doesn't help either in this case, as an RDF file might or not start with the rdf:RDF root element, therefore checking only the root element doesn't necessarily imply the actual format of the file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FOR-1018) Making sourcetypeaction work for RDF files

Posted by "Gavin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated FOR-1018:
-----------------------

    Other Info:   (was: [Patch available])

Patch has been applied.

> Making sourcetypeaction work for RDF files
> ------------------------------------------
>
>                 Key: FOR-1018
>                 URL: https://issues.apache.org/jira/browse/FOR-1018
>             Project: Forrest
>          Issue Type: Sub-task
>          Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
>    Affects Versions: 0.9-dev
>            Reporter: Sina K. Heshmati
>            Priority: Minor
>             Fix For: 0.9-dev
>
>         Attachments: sourcetypeaction-rdf.patch
>
>
> In an effort to use the sourcetypeaction mechanism in the sitemap to intelligently prcess input files, I noticed that RDF/XML formats require extra processing for their action type to be determined. Obviously because neither doctype nor processing instruction events are likely to appear in RDF/XML formats and the only way to choose an action should be base on the namespace. The namespace of the root element doesn't help either in this case, as an RDF file might or not start with the rdf:RDF root element, therefore checking only the root element doesn't necessarily imply the actual format of the file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FOR-1018) Making sourcetypeaction work for RDF files

Posted by "SinDoc (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FOR-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SinDoc updated FOR-1018:
------------------------

    Attachment: sourcetypeaction-rdf.patch

As a workaround, I'd suggest to add handle RDF files a bit differently, that is continue parsing until the namespace of the current element event is different from that of RDF. Note that, this solution has worked so far for the SKOS plugin and it's also likely to work for FOAF and DOAP plugins but it certainly could be extended to cover more special cases.

Please feel free to share your thought on this issue.

> Making sourcetypeaction work for RDF files
> ------------------------------------------
>
>                 Key: FOR-1018
>                 URL: https://issues.apache.org/jira/browse/FOR-1018
>             Project: Forrest
>          Issue Type: Sub-task
>          Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
>    Affects Versions: 0.9-dev
>            Reporter: SinDoc
>            Priority: Minor
>             Fix For: 0.9-dev
>
>         Attachments: sourcetypeaction-rdf.patch
>
>
> In an effort to use the sourcetypeaction mechanism in the sitemap to intelligently prcess input files, I noticed that RDF/XML formats require extra processing for their action type to be determined. Obviously because neither doctype nor processing instruction events are likely to appear in RDF/XML formats and the only way to choose an action should be base on the namespace. The namespace of the root element doesn't help either in this case, as an RDF file might or not start with the rdf:RDF root element, therefore checking only the root element doesn't necessarily imply the actual format of the file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.