Add GPML2013a-fuller schema, with version of BioPAX as used in GPML2013a #13
Conversation
|
XML Namespaces FTW :) |
|
I didn't merge this pull request myself, because I want to give time for feedback on this update (pinging @mkutmon and @AlexanderPico). This is still GPML2013a: the update just makes the XSD more closely reflect our actual GPML2013a GPML. |
|
I only see one real difference: removing processContents="skip" from here: What are the consequences of that change? The rest is... stuff that... hmm. I'm not going to even bother guessing :) When is this GPML2013a-biopax.xsd used in practice? Does this affect anyone using it today? |
can occur any number of times.
|
I'm using it to provide types and autocompletion in my code editor. |
|
Hi Anders! Maybe we should have a short hangout about this and the possible
requirements for the 2017 version I am working on with my GSoC student.
…On Jun 5, 2017 19:16, "Anders Riutta" ***@***.***> wrote:
I'm using it to provide types and autocompletion in my code editor.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACDvB5acju1Rsohuns8f3DltX9ImFmKcks5sBDfWgaJpZM4NvNv9>
.
|
|
Hi Tina! Sure, we can have a hangout. I can meet anytime this week at 10 or 11am SF time (I think that's 7 or 8pm Maastricht time?). Just let me know. By the way, this change is not for GPML2017. It's still for GPML2013a. Are you aware of any existing tools that rely on this XSD file? Does PathVisio-Java need to be tested with this updated version? |
|
Okay great. I'll check my agenda and let you know which day works.
PathVisio definitely needs to be checked since it has the xsd files in the
code.
…On Jun 6, 2017 00:38, "Anders Riutta" ***@***.***> wrote:
Hi Tina! Sure, we can have a hangout. I can meet anytime this week at 10
or 11am SF time (I think that's 7 or 8pm Maastricht time?). Just let me
know.
By the way, this change is not for GPML2017. It's still for GPML2013a. Are
you aware of any existing tools that rely on this XSD file? Does
PathVisio-Java need to be tested with this updated version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACDvB9UyOIpHWb58dv_Idzzx_JiF2t0Tks5sBINfgaJpZM4NvNv9>
.
|
Changed XSD to only display a single top-level element, following the advice from this article: >> Normally it is desired to have only one possible top-level element in an XML instance, and so this constraint is imposed in the schema by only having one global element definition. from http://www.codalogic.com/lmx/xsd-overview.html Cleaned up BiopaxRef definitions. We don't have BiopaxRef as an attribute: it's always an element.
… cases from Elbow test cases.
|
I added a new schema |
ariutta
changed the title
I made a few changes so that XSD processors can handle actual GPML2013a, which has its own version of BioPAX that differs from the BioPAX Level 3 spec.