[ 
https://issues.apache.org/jira/browse/PIRK-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387366#comment-15387366
 ] 

ASF GitHub Bot commented on PIRK-16:
------------------------------------

GitHub user tellison opened a pull request:

    https://github.com/apache/incubator-pirk/pull/17

    [PIRK-16] Define XML schema definition files for Pirk's data and query 
schemas

    Reading the loader code, the "isArray" element is not optional.  Does it 
make sense and aid readability for me to tweak the loader to assume isArray is 
false by default? or do you want to keep it explicit?

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

    $ git pull https://github.com/tellison/incubator-pirk pirk-16

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

    https://github.com/apache/incubator-pirk/pull/17.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 #17
    
----
commit 4a88847ecd12cbfd90bcab02575231ba1486aed5
Author: Tim Ellison <[email protected]>
Date:   2016-07-21T08:30:13Z

    Define XML schema definition files for Pirk's data and query schemas

----


> Define XML schema definition files for Pirk's data and query schemas
> --------------------------------------------------------------------
>
>                 Key: PIRK-16
>                 URL: https://issues.apache.org/jira/browse/PIRK-16
>             Project: PIRK
>          Issue Type: Improvement
>            Reporter: Tim Ellison
>            Assignee: Tim Ellison
>
> Pirk uses XML files to specify a data schema for the target data, and a query 
> schema for the query type.
> This improvement provides the XML schema definition (XSD) for these files, 
> allowing parsers to check the validity of the Pirk schemas.
> These XSDs should probably be available locally (in the deployment JAR) and 
> remotely (on the Pirk website).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to