Bug #4798


Create parser for KAR XML specification

Added by Sean Riddle about 13 years ago. Updated almost 13 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Create a parser for the new KAR XML format, for use especially when it is returned from a metacat query.

Related issues

Is duplicate of Kepler - Bug #4874: Modify existing KARFile schema for use with KAR File ParserResolveddebi staggs03/10/2010

Blocked by Kepler - Bug #4462: Component search in remote repositories not workingResolvedSean Riddle10/15/2009

Actions #1

Updated by Sean Riddle about 13 years ago

Wrote initial implementation. I'll leave this bug open for a day or two for interested parties (especially those involved in the KAR specification) to take a look before closing.

Actions #2

Updated by ben leinfelder about 13 years ago

is there a complete XSD now?

Actions #3

Updated by Sean Riddle about 13 years ago

As far as I know, no. That's a good point. I'll leave this open until there's some soft of official schema to check against if that would be agreeable. This could also serve as a central bug for individual parsing problems in the interim.

Actions #4

Updated by ben leinfelder about 13 years ago

is what exists so far. Can you augment it/verify that the cardinality constraints are correct for elements in sequences? Most are left as default which means they can and must be present only once.

It'd be great if we could ultimately check the generated XML for errors (on both sides of the serialization)

Actions #5

Updated by ben leinfelder about 13 years ago

this is a 2.0 bug in that it is blocking the component search bug

Actions #6

Updated by Jing Tao almost 13 years ago

Just enabled the schema validation on both the component search result and the generated kar xml by kepler.

In oder to do this, we modified the following stuff:

1. Put namespace definition, schema location(using the url of the schema on our svn kepler 2 branch) to the root element of kar xml.

2. Add a prefix to root element : <kar> to <kar:kar> (The validator can handle arbitrary prefix though)

3. Made a minor change on the schema itself, such as namespace.

The uploading and searching kar file worked to me on both kepler 2 and trunk. Sean is testing it now.

Actions #8

Updated by Chad Berkley almost 13 years ago

Sean and Jing have verified that this is now working.

Actions #9

Updated by Redmine Admin about 10 years ago

Original Bugzilla ID was 4798


Also available in: Atom PDF