You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2006/04/07 22:13:23 UTC

[jira] Created: (NUTCH-245) XML Schemas for xml configuration files in conf directory

XML Schemas for xml configuration files in conf directory
---------------------------------------------------------

         Key: NUTCH-245
         URL: http://issues.apache.org/jira/browse/NUTCH-245
     Project: Nutch
        Type: New Feature

  Components: fetcher, indexer, ndfs, searcher, web gui  
    Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev    
 Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
    Reporter: Chris A. Mattmann
 Assigned to: Chris A. Mattmann 
    Priority: Minor


Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. I'm also going to post another issue regarding adding an addition to the ant target that builds the Nutch website. The addition to the ant target would copy the existing DTD files in $NUTCH_HOME/conf to the Nutch website ROOT. That way, we could then reference the DTD file in all the XML instance files by reference something like <!DOCTYPE system "http://lucene.apache.org/nutch/dtd/parse-plugins.dtd">, within the parse-plugins.xml, or similarly for the nutch-site.xml, or mime-types.xml file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/NUTCH-245?page=all ]

Chris A. Mattmann updated NUTCH-245:
------------------------------------

    Attachment: NUTCH-245.Mattmann.patch.txt

Here's the patch for the plugin DTD file. I got a lot of info from:

http://help.eclipse.org/help31/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html

i.e., the eclipse manifest file. Turns out that by examining the plugin manifest parser code though, a lot of some elements that eclipse uses we don't currently use in Nutch. Additionally, I also noticed that the element "implementation" can basically have any attribute name/value pair on it, besides "id" and "class", so I wasn't sure how exactly to represent this in DTD terminology other than going through all the plugin.xml files for the nutch plugins and adding #IMPLIED attribute names for the implementation attribute corresponding to each of the optional attributes used by different extension point implementations. Maybe there's a more elegant way, but, for now, this works (I ran it against all the plugin.xml files through my XML validator and they check out).

Okay, thanks!

> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (NUTCH-245) DTD for plugin.xml configuration files

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/NUTCH-245?page=all ]

Chris A. Mattmann updated NUTCH-245:
------------------------------------

    Summary: DTD for plugin.xml configuration files  (was: DTD Schemas for plugin.xml configuration files in conf directory)

update title to reflect core issue (doesn't have anything to do with conf dir)

> DTD for plugin.xml configuration files
> --------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/NUTCH-245?page=comments#action_12374217 ] 

Chris A. Mattmann commented on NUTCH-245:
-----------------------------------------

Hey Doug,

 I'm fine with that, I think it makes sense. Want an updated patch or just, the person who commits it can move it there before commiting?

Thanks,
  Chris


> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/NUTCH-245?page=all ]

Chris A. Mattmann updated NUTCH-245:
------------------------------------

    Summary: DTD Schemas for plugin.xml configuration files in conf directory  (was: XML Schemas for xml configuration files in conf directory)

> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor

>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. I'm also going to post another issue regarding adding an addition to the ant target that builds the Nutch website. The addition to the ant target would copy the existing DTD files in $NUTCH_HOME/conf to the Nutch website ROOT. That way, we could then reference the DTD file in all the XML instance files by reference something like <!DOCTYPE system "http://lucene.apache.org/nutch/dtd/parse-plugins.dtd">, within the parse-plugins.xml, or similarly for the nutch-site.xml, or mime-types.xml file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/NUTCH-245?page=comments#action_12374215 ] 

Doug Cutting commented on NUTCH-245:
------------------------------------

I don't think the plugin.dtd belongs in the conf directory.  Probably src/plugin is a better place?

> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (NUTCH-245) DTD for plugin.xml configuration files

Posted by "Jerome Charron (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/NUTCH-245?page=comments#action_12374339 ] 

Jerome Charron commented on NUTCH-245:
--------------------------------------

I would prefer to change the "ugly" parts of the DTD now (before a future 1.0) and suggest to change it to something like (and to change the plugin.xml and Plugin Manifest Reader too):

<!ELEMENT implementation (parameter*)>
<!ELEMENT parameter EMPTY>
<!ATTLIST parameter
                    name CDATA #REQUIRED
                    value CDATA #REQUIRED>


> DTD for plugin.xml configuration files
> --------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (NUTCH-245) DTD for plugin.xml configuration files

Posted by "Jerome Charron (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/NUTCH-245?page=all ]
     
Jerome Charron closed NUTCH-245:
--------------------------------

    Fix Version: 0.8-dev
     Resolution: Fixed

Fixed (http://svn.apache.org/viewcvs.cgi?rev=394228&view=rev)
Thanks Chris.


> DTD for plugin.xml configuration files
> --------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, searcher, web gui, ndfs
>     Versions: 0.7, 0.8-dev, 0.6, 0.7.1, 0.7.2
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor
>      Fix For: 0.8-dev
>  Attachments: NUTCH-245.Mattmann.patch.txt
>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (NUTCH-245) DTD Schemas for plugin.xml configuration files in conf directory

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/NUTCH-245?page=all ]

Chris A. Mattmann updated NUTCH-245:
------------------------------------

    Description: Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated.   (was: Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. I'm also going to post another issue regarding adding an addition to the ant target that builds the Nutch website. The addition to the ant target would copy the existing DTD files in $NUTCH_HOME/conf to the Nutch website ROOT. That way, we could then reference the DTD file in all the XML instance files by reference something like <!DOCTYPE system "http://lucene.apache.org/nutch/dtd/parse-plugins.dtd">, within the parse-plugins.xml, or similarly for the nutch-site.xml, or mime-types.xml file.)

update the issue to just be a single issue - I may post the one about copying the DTDs to the website at a later point

> DTD Schemas for plugin.xml configuration files in conf directory
> ----------------------------------------------------------------
>
>          Key: NUTCH-245
>          URL: http://issues.apache.org/jira/browse/NUTCH-245
>      Project: Nutch
>         Type: New Feature

>   Components: fetcher, indexer, ndfs, searcher, web gui
>     Versions: 0.7.2, 0.7.1, 0.7, 0.6, 0.8-dev
>  Environment: Power PC Dual Processor 2.0 Ghz, Mac OS X 10.4, although improvement is independent of environment
>     Reporter: Chris A. Mattmann
>     Assignee: Chris A. Mattmann
>     Priority: Minor

>
> Currently, the plugin.xml file does not have a DTD or XML Schema associated with it, and most people just go look at an existing plugin's plugin.xml file to determine what are the allowable elements, etc. There should be an explicit plugin DTD file that describes the plugin.xml file. I'll look at the code and attach a plugin.dtd file for the Nutch conf directory later today. This way, people can use the DTD file to automatically (using tools such as XMLSpy) generate plugin.xml files that can then be validated. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira