forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SinDoc (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FOR-1018) Making sourcetypeaction work for RDF files
Date Fri, 06 Jul 2007 21:06:04 GMT

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


Mime
View raw message