nexml-discuss

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Balhoff, J. <jba...@rt...>]

> On May 9, 2016, at 6:11 PM, Jonathan A Rees <re...@mu...> wrote:
> 
> ... they are not natively supported by XML Schema, so they would make NeXML schemas and validators more complicated. If a NeXML goal was to put XML Schema to good use, which looks likely to me (because it did), then requiring QNames in these contexts (as would be required by RDF/XML and in the versions of Turtle and N3 that were in circulation at the time) would have made perfect sense.

I think this was it—an issue of tool support with XML Schema and CURIEs.

Jim

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Jonathan A R. <re...@mu...>]

Well maybe I went overboard in saying "I don't think we have any evidence
that [RDFa exerted an influence]" - sorry.  The fact that NeXML works with
the RDFa distiller appears to be evidence that RDFa had an influence. But
the question was about CURIEs, not RDFa, so the statement should have
been "I don't think we have any evidence that the CURIE section of the RDFa
spec exerted an influence".  CURIEs are documented in the RDFa
recommendation from 2008
https://www.w3.org/TR/2008/REC-rdfa-syntax-20081014/#s_curies but they
would be easy to miss, and as I said before they are not natively supported
by XML Schema, so they would make NeXML schemas and validators more
complicated. If a NeXML goal was to put XML Schema to good use, which looks
likely to me (because it did), then requiring QNames in these contexts (as
would be required by RDF/XML and in the versions of Turtle and N3 that were
in circulation at the time) would have made perfect sense.

None of which helps to solve the actual problem...

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Hilmar L. <hl...@ne...>]

> On May 9, 2016, at 4:09 PM, Balhoff, James <jba...@rt...> wrote:
> 
>> RDFa (and CURIEs) came out in 2008, so it would have been reasonable for RDFa to have exerted an influence on the design of NeXML, which seems to have been developed in 2011. But I don't think we have any evidence that it did.
> 
> As one of the developers of the annotations part of NeXML, I can confirm that the actual goal was for the annotations to be valid RDFa, and for someone to be able to extract RDF. :-)


Yep, as the main culprit to argue for this, I can confirm this too :-)

  -hilmar
-- 
Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Balhoff, J. <jba...@rt...>]

On May 9, 2016, at 4:02 PM, Jonathan A Rees <re...@mu...<mailto:re...@mu...>> wrote:

The schema says you have to put a QName, just as the documentation says.

The NeXML manual suggests that it at least occurred to someone to extract RDF from NeXML: https://github.com/nexml/nexml/wiki/NeXML-Manual#Extracting_metadata_from_NeXML_into_RDF

RDFa (and CURIEs) came out in 2008, so it would have been reasonable for RDFa to have exerted an influence on the design of NeXML, which seems to have been developed in 2011. But I don't think we have any evidence that it did.

As one of the developers of the annotations part of NeXML, I can confirm that the actual goal was for the annotations to be valid RDFa, and for someone to be able to extract RDF. :-) There is a tiny mention of RDFa in the paper describing NeXML.


The "modern" way to do this, RDFa Core (https://www.w3.org/TR/rdfa-syntax/#xmlrdfaconformance ), was not published until 2013, too late to have had any influence on NeXML.

It does seem like there is much better documentation surrounding this than there was when we were trying to figure it out in 2011.

Thanks,
Jim

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Jonathan A R. <re...@mu...>]

The schema says you have to put a QName, just as the documentation says.

The NeXML manual suggests that it at least occurred to someone to extract
RDF from NeXML:
https://github.com/nexml/nexml/wiki/NeXML-Manual#Extracting_metadata_from_NeXML_into_RDF

RDFa (and CURIEs) came out in 2008, so it would have been reasonable for
RDFa to have exerted an influence on the design of NeXML, which seems to
have been developed in 2011. But I don't think we have any evidence that it
did.

The "modern" way to do this, RDFa Core (
https://www.w3.org/TR/rdfa-syntax/#xmlrdfaconformance ), was not published
until 2013, too late to have had any influence on NeXML.

Allowing CURIEs in those fields is a compatible change for producers of
NeXML, but possibly a small burden on consumers, so liberalizing these
fields would require a new version of the spec & schema.

Jonathan

On Mon, May 9, 2016 at 3:25 PM, Mark Holder <mth...@gm...> wrote:

> Hi,
>
> I do not recall the intent wrt RDFa or CURIEs.
>
> The schema is in xsd/nexml.xsd of the repo at
> https://github.com/nexml/nexml
>
>
> cheers,
> Mark
>
> On Mon, May 9, 2016 at 2:04 PM, Jonathan A Rees <re...@mu...> wrote:
> > Sounds as if, if the intent was to make it RDFa Core compliant, then the
> > schema will have to be changed.
> >
> > Can someone give me a pointer to the schema so I can double check this?
> The
> > official link is dead:
> > http://www.nexml.org/2009/nexml/xsd/nexml.xsd
> >
> >
> >
> ------------------------------------------------------------------------------
> > Find and fix application performance issues faster with Applications
> Manager
> > Applications Manager provides deep performance insights into multiple
> tiers
> > of
> > your business applications. It resolves application problems quickly and
> > reduces your MTTR. Get your free trial!
> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> > _______________________________________________
> > Nexml-discuss mailing list
> > Nex...@li...
> > https://lists.sourceforge.net/lists/listinfo/nexml-discuss
> >
>
>
>
> --
> Mark Holder
>
> mth...@gm...
> mth...@ku...
> http://phylo.bio.ku.edu/mark-holder
>
> ==============================================
> Department of Ecology and Evolutionary Biology
> University of Kansas
> 6031 Haworth Hall
> 1200 Sunnyside Avenue
> Lawrence, Kansas 66045
>
> lab phone:  785.864.5789
> fax (shared): 785.864.5860
> ==============================================
>


On Mon, May 9, 2016 at 3:25 PM, Mark Holder <mth...@gm...> wrote:

> Hi,
>
> I do not recall the intent wrt RDFa or CURIEs.
>
> The schema is in xsd/nexml.xsd of the repo at
> https://github.com/nexml/nexml
>
>
> cheers,
> Mark
>
> On Mon, May 9, 2016 at 2:04 PM, Jonathan A Rees <re...@mu...> wrote:
> > Sounds as if, if the intent was to make it RDFa Core compliant, then the
> > schema will have to be changed.
> >
> > Can someone give me a pointer to the schema so I can double check this?
> The
> > official link is dead:
> > http://www.nexml.org/2009/nexml/xsd/nexml.xsd
> >
> >
> >
> ------------------------------------------------------------------------------
> > Find and fix application performance issues faster with Applications
> Manager
> > Applications Manager provides deep performance insights into multiple
> tiers
> > of
> > your business applications. It resolves application problems quickly and
> > reduces your MTTR. Get your free trial!
> > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> > _______________________________________________
> > Nexml-discuss mailing list
> > Nex...@li...
> > https://lists.sourceforge.net/lists/listinfo/nexml-discuss
> >
>
>
>
> --
> Mark Holder
>
> mth...@gm...
> mth...@ku...
> http://phylo.bio.ku.edu/mark-holder
>
> ==============================================
> Department of Ecology and Evolutionary Biology
> University of Kansas
> 6031 Haworth Hall
> 1200 Sunnyside Avenue
> Lawrence, Kansas 66045
>
> lab phone:  785.864.5789
> fax (shared): 785.864.5860
> ==============================================
>

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Mark H. <mth...@gm...>]

Hi,

I do not recall the intent wrt RDFa or CURIEs.

The schema is in xsd/nexml.xsd of the repo at https://github.com/nexml/nexml


cheers,
Mark

On Mon, May 9, 2016 at 2:04 PM, Jonathan A Rees <re...@mu...> wrote:
> Sounds as if, if the intent was to make it RDFa Core compliant, then the
> schema will have to be changed.
>
> Can someone give me a pointer to the schema so I can double check this?  The
> official link is dead:
> http://www.nexml.org/2009/nexml/xsd/nexml.xsd
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers
> of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>



-- 
Mark Holder

mth...@gm...
mth...@ku...
http://phylo.bio.ku.edu/mark-holder

==============================================
Department of Ecology and Evolutionary Biology
University of Kansas
6031 Haworth Hall
1200 Sunnyside Avenue
Lawrence, Kansas 66045

lab phone:  785.864.5789
fax (shared): 785.864.5860
==============================================

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Jonathan A R. <re...@mu...>]

Sounds as if, if the intent was to make it RDFa Core compliant, then the
schema will have to be changed.

Can someone give me a pointer to the schema so I can double check this?
The official link is dead:
http://www.nexml.org/2009/nexml/xsd/nexml.xsd

Re: [Nexml-discuss] Valid metadata predicates in NeXML

[Balhoff, J. <jba...@rt...>]

Hi Ben,

It is hard to remember precisely how this came about. Our goal was to follow the RDFa standard, so I believe these should be CURIEs. But I do remember there were various tool limitations which made QNames easier to work with as far as API support for expanding prefixes and keeping them consistent. But it seems to me that it would be worthwhile to revisit this and make sure the spec matches RDFa and that there are XML APIs that can manage the CURIEs properly.

Best regards,
Jim


********************************************
James P. Balhoff, PhD
Bioinformatics Group
Research Computing Division
RTI International



> On May 6, 2016, at 6:49 AM, Ben Stöver <ben...@un...> wrote:
> 
> Hi all,
> 
> as I mentioned to Rutger a while ago, we are currently working on adding support for NeXML in some of our software projects (e.g. LibrAlign http://bioinfweb.info/LibrAlign/ and TreeGraph 2 http://treegraph.bioinfweb.info/ ) Therefore we decided to create the library JPhyloIO (http://bioinfweb.info/JPhyloIO/ ), which allows event based reading and writing of different phylogenetic formats through a single interface (including NeXML).
> 
> During the development of the NeXML writer in JPhyloIO we came across the question, which predicates in NeXML meta tags are really valid? They are sometimes referred to as CURIES (which seems to make sense), but in the NeXML schema both the "rel" attribute for resource and the "property" attribute for literal metadata are declared as QNames. (http://nexml.org/doc/schema-1/meta/annotations/#LiteralMeta ) Not all CURIES are also valid QNames though, as shown here: https://www.w3.org/TR/curie/#sec_2.1. (and here: https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-LocalPart ).
> 
> I've created an according test file under http://bioinfweb.info/Code/sventon/repos/JPhyloIO/show/trunk/test/data/NeXML/CURIE_QName_Test.xml , which indeed does not validate. The output of the validator states that invalid CURIES are used (although they should actually be invalid QNames but valid CURIES).
> 
> My question is now: Is this intended? Are only QNames allowed as predicates or should actually all possible CURIES be valid and this is a problem in schema or the validator? If only QNames are allowed, can this become a problem with some ontologies using other CURIES or is there a reason to be sure that no such cases are out there?
> 
> I would really appreciate if someone would comment on that. (NeXML-related or other comments on JPhyloIO in general are of course also welcome, if someone has an opinion on it.)
> 
> Best
> Ben
> 
> Dipl. Biologe Ben Stöver
> Evolution und Biodiversity of Plants Group
> Institute for Evolution and Biodiversity
> University of Münster
> Germany
> Phone: +49 251 83 21647
> Fax: +49 251 83 24668
> http://www2.ieb.uni-muenster.de/EvolBiodivPlants/en/People/Stoever
> Ben...@un...
> 
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss

[Nexml-discuss] Valid metadata predicates in NeXML

[Ben S. <ben...@un...>]

Hi all,

as I mentioned to Rutger a while ago, we are currently working on adding support for NeXML in some of our software projects (e.g. LibrAlign http://bioinfweb.info/LibrAlign/ and TreeGraph 2 http://treegraph.bioinfweb.info/ ) Therefore we decided to create the library JPhyloIO (http://bioinfweb.info/JPhyloIO/ ), which allows event based reading and writing of different phylogenetic formats through a single interface (including NeXML).

During the development of the NeXML writer in JPhyloIO we came across the question, which predicates in NeXML meta tags are really valid? They are sometimes referred to as CURIES (which seems to make sense), but in the NeXML schema both the "rel" attribute for resource and the "property" attribute for literal metadata are declared as QNames. (http://nexml.org/doc/schema-1/meta/annotations/#LiteralMeta ) Not all CURIES are also valid QNames though, as shown here: https://www.w3.org/TR/curie/#sec_2.1. (and here: https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-LocalPart ).

I've created an according test file under http://bioinfweb.info/Code/sventon/repos/JPhyloIO/show/trunk/test/data/NeXML/CURIE_QName_Test.xml , which indeed does not validate. The output of the validator states that invalid CURIES are used (although they should actually be invalid QNames but valid CURIES).

My question is now: Is this intended? Are only QNames allowed as predicates or should actually all possible CURIES be valid and this is a problem in schema or the validator? If only QNames are allowed, can this become a problem with some ontologies using other CURIES or is there a reason to be sure that no such cases are out there?

I would really appreciate if someone would comment on that. (NeXML-related or other comments on JPhyloIO in general are of course also welcome, if someone has an opinion on it.)

Best
Ben

Dipl. Biologe Ben Stöver
Evolution und Biodiversity of Plants Group
Institute for Evolution and Biodiversity
University of Münster
Germany
Phone: +49 251 83 21647
Fax: +49 251 83 24668
http://www2.ieb.uni-muenster.de/EvolBiodivPlants/en/People/Stoever
Ben...@un...

Re: [Nexml-discuss] Nexml-Java and Maven Central

[Rutger V. <rut...@gm...>]

Dear all,

here's a brief heads up about the nexml/java jar and its availability
through maven repositories. Previously, I had made this available through
nexml-dev.nescent.org but this repository *no longer exists, please expunge
it from your records*. The new maven repository for the nexml jar is
at *http://nexml.github.io/maven/repository
<http://nexml.github.io/maven/repository>*, and the artifact has the
following details (which are unchanged):

- groupId: org.nexml.model
- artifactId: nexml
- version: 1.5-SNAPSHOT

As a further implementation detail, possibly of interest to those that care
for TreeBASE, I can add that this new location has been updated in the
dependencies for TreeBASE and that the build process succeeds without
problems using this.

Best wishes,

Rutger


On Wed, Oct 15, 2014 at 5:38 AM, Dennis Roberts <
de...@ip...> wrote:

> Hi Rutger,
>
> I apologize for the delay in getting this back to you. Here’s a couple of
> things that I noticed.
>
> * There is no <description/> tag in the POM, which is required, if I
> remember correctly.
> * The parent POM also needs to be specified.
>
> It looks like you’ve also got some dependencies that aren’t available in a
> maven repository. That complicates things a bit because it becomes
> necessary to redistribute the dependency with your code, which is something
> that I’ve never done before. This Stack Overflow answer seems to be the
> best bet, but I don’t know what the licensing implications are yet, and I
> haven’t had time to actually try to get it to work:
> http://stackoverflow.com/a/7623805/299222.
>
> Here’s the command that I used to install the CSS parser library into the
> local repository:
>
>     mvn install:install-file -DlocalRepositoryPath=repo
> -DcreateChecksum=true -Dpackaging=jar -Dfile=jars/osbcp-css-parser-1.4.jar
> -DgroupId=osbcp -DartifactId=css-parser -Dversion=1.4
>
> I’d like to know how to automate this step as much as possible, however,
> and how to actually include the dependencies in the artifact, which will
> require some work. I’ll have to play around with some options, which will
> take a while, and I’m not sure how much time I’ll have to work on it. In
> the meantime, if there are any Maven experts in the mailing list, your
> input would be greatly appreciated.
>
> Here’s one of our POM files that we have successfully used to publish
> artifacts to Maven Central:
>
>
> https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/de-base-services-pom/pom.xml
>
> This is a base POM that is used by some of our other projects. Here’s the
> POM file from one of the other projects:
>
>
> https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/de-persistence/pom.xml
>
> Here’s a link to another project POM that descends directly from the
> Sonatype OSS parent POM:
>
>
> https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/hibernatetoolkit/pom.xml
>
> Let me know if you have more questions.
>
> Thanks,
> Dennis
>
> On Oct 13, 2014, at 12:46 AM, Rutger Vos <rut...@gm...> wrote:
>
> Hi Dennis,
>
> have you been able to have a look?
>
> Thanks,
>
> Rutger
>
> On Tue, Oct 7, 2014 at 6:52 PM, Dennis Roberts <
> de...@ip...> wrote:
>
>> Hi Rutger,
>>
>> I’m sorry I haven’t gotten back to you on this; things have been busier
>> than I expected for the last couple of weeks. I should be able to look over
>> the file sometime later this week.
>>
>> Thanks,
>> Dennis
>>
>> On Sep 25, 2014, at 1:33 AM, Rutger Vos <rut...@gm...> wrote:
>>
>> Hi Dennis,
>>
>> is this more or less what we're looking for or am I missing sections:
>> https://github.com/nexml/nexml.java/blob/master/pom.xml
>>
>> I'm a bit unclear where and how to specify the javadoc and sources
>> targets.
>>
>> Thanks!
>>
>> Rutger
>>
>> On Tue, Sep 23, 2014 at 10:10 PM, Dennis Roberts <
>> de...@ip...> wrote:
>>
>>> Hi Rutger,
>>>
>>> The next step would be to update the pom.xml file to comply with
>>> Sonatype’s requirements. The instructions for that can be found here:
>>> http://central.sonatype.org/pages/apache-maven.html.
>>>
>>> Dennis
>>>
>>> On Sep 23, 2014, at 1:26 AM, Rutger Vos <rut...@gm...> wrote:
>>>
>>> Hi Dennis,
>>>
>>> I just received notification that the request has been reviewed and
>>> granted. What would be the next steps?
>>>
>>> Rutger
>>>
>>> On Mon, Sep 22, 2014 at 7:41 PM, Dennis Roberts <
>>> de...@ip...> wrote:
>>>
>>>> Hi Rutger,
>>>>
>>>> You’re right; a real human being does have to look at the issue. It
>>>> took a few days when I signed up for iPlant’s account.
>>>>
>>>> Dennis
>>>>
>>>> On Sep 22, 2014, at 2:29 AM, Rutger Vos <rut...@gm...> wrote:
>>>>
>>>> Hi Dennis, Anurag,
>>>>
>>>> I have created a JIRA issue at Sonatype to get the account. I've added
>>>> dennis.iplant as one of the other accounts that needs access. The issue is
>>>> posted here: https://issues.sonatype.org/browse/OSSRH-11624
>>>> (presumably this is only visible for Dennis and I, though). I gather that a
>>>> real human being has to look at this, so the next step is to wait for the
>>>> OK from their end, right?
>>>>
>>>> Cheers,
>>>>
>>>> Rutger
>>>>
>>>> On Fri, Sep 19, 2014 at 6:28 PM, Dennis Roberts <
>>>> de...@ip...> wrote:
>>>>
>>>>> Hi Rutger,
>>>>>
>>>>> No worries; I have a bunch of emails in my inbox that I’ve been
>>>>> meaning to get to for ages as well.
>>>>>
>>>>> This is still relevant on our end, and I would say that the best
>>>>> approach is for nexml to have its own account. Sure, I’d be happy to help.
>>>>> If you could apply for an account with Sonatype and add me to the
>>>>> organization, I can help get the artifacts into Maven Central. Instructions
>>>>> for applying for a Sonatype account can be found here:
>>>>> http://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh.
>>>>> My account name at sonatype is dennis.iplant.
>>>>>
>>>>> Let me know if you have any questions.
>>>>>
>>>>> Thanks,
>>>>> Dennis
>>>>>
>>>>> On Sep 19, 2014, at 6:08 AM, Rutger Vos <rut...@gm...> wrote:
>>>>>
>>>>> Dear Dennis,
>>>>>
>>>>> I feel a bit ridiculous responding to an email from March but it's
>>>>> been sitting in my inbox as "something to get to", so here we go.
>>>>>
>>>>> If this is still relevant on your end (I hope so), would you say that
>>>>> the best approach is indeed for nexml to have its own account? Would you
>>>>> still be willing and able to help get the artifacts deployed there?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Rutger
>>>>>
>>>>> On Thu, Mar 20, 2014 at 12:03 AM, Dennis Roberts <
>>>>> de...@ip...> wrote:
>>>>>
>>>>>> Hey Everyone,
>>>>>>
>>>>>> Sonatype allows open-source projects to publish artifacts to Maven
>>>>>> Central for free. You can find instructions for doing this here:
>>>>>> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide.
>>>>>> If someone sets up an account for nexml, I’d be happy to help get the
>>>>>> artifacts deployed. Feel free to ask me questions if you like.
>>>>>>
>>>>>> iPlant Collaborative has a Sonatype OSS account, so we could publish
>>>>>> nexml-java to Maven Central. If we did that, we’d have to change the Maven
>>>>>> group ID to something prefixed by org.iplantc, however.
>>>>>>
>>>>>> Thanks,
>>>>>> Dennis
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>>> their
>>>>>> applications. Written by three acclaimed leaders in the field,
>>>>>> this first edition is now available. Download your free book today!
>>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>>> _______________________________________________
>>>>>> Nexml-discuss mailing list
>>>>>> Nex...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Re: [Nexml-discuss] Prefix registration

[Hilmar L. <hl...@ne...>]

The expansion for CDAO is now the same as for all other OBO ontologies,
and thus the prefix for CDAO is in essence the obo prefix.

Unfortunately, in addition to the correct expansion, there is an
alternative in prefix.cc/obo that seems due to confusion of the obo
prefix expansion with the one for the oboInOwl vocabulary. The perils of
crowd-sourcing, I guess. (You might want to downvote the confused one of
the two alternatives.)

  -hilmar

On 1/19/15, 4:18 AM, Rutger Vos wrote:
> prefix.cc is an interesting initiative. I upvoted, and am tempted to
> do something with the json-ld output to get a set of default prefixes
> to be used in RDFa annotations. I notice that CDAO isn't in there, by
> the way.
>
> On Sun, Jan 18, 2015 at 10:05 PM, Hilmar Lapp <hl...@ne...
> <mailto:hl...@ne...>> wrote:
>
>     I registered the NeXML namespace under prefix nex with prefix.cc:
>     http://prefix.cc/nex
>
>     You might want to upvote it (provided you agree with the expansion I put
>     there; if you don't, correct it).
>
>       -hilmar
>
>
>     -- 
>     Hilmar Lapp -:- informatics.nescent.org/wiki
>     <http://informatics.nescent.org/wiki> -:- lappland.io
>     <http://lappland.io>
>
>     ------------------------------------------------------------------------------
>     New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>     GigeNET is offering a free month of service with a new server in
>     Ashburn.
>     Choose from 2 high performing configs, both with 100TB of bandwidth.
>     Higher redundancy.Lower latency.Increased capacity.Completely
>     compliant.
>     http://p.sf.net/sfu/gigenet
>     _______________________________________________
>     Nexml-discuss mailing list
>     Nex...@li...
>     <mailto:Nex...@li...>
>     https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>
>

-- 
Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io

Re: [Nexml-discuss] Prefix registration

[Rutger V. <rut...@gm...>]

prefix.cc is an interesting initiative. I upvoted, and am tempted to do
something with the json-ld output to get a set of default prefixes to be
used in RDFa annotations. I notice that CDAO isn't in there, by the way.

On Sun, Jan 18, 2015 at 10:05 PM, Hilmar Lapp <hl...@ne...> wrote:

>  I registered the NeXML namespace under prefix nex with prefix.cc:http://prefix.cc/nex
>
> You might want to upvote it (provided you agree with the expansion I put
> there; if you don't, correct it).
>
>   -hilmar
>
>
> --
> Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>
>

[Nexml-discuss] Prefix registration

[Hilmar L. <hl...@ne...>]

I registered the NeXML namespace under prefix nex with prefix.cc:
http://prefix.cc/nex

You might want to upvote it (provided you agree with the expansion I put
there; if you don't, correct it).

  -hilmar


-- 
Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io

Re: [Nexml-discuss] Nexml-Java and Maven Central

[Dennis R. <de...@ip...>]

Hi Rutger,

I apologize for the delay in getting this back to you. Here’s a couple of things that I noticed.

* There is no <description/> tag in the POM, which is required, if I remember correctly.
* The parent POM also needs to be specified.

It looks like you’ve also got some dependencies that aren’t available in a maven repository. That complicates things a bit because it becomes necessary to redistribute the dependency with your code, which is something that I’ve never done before. This Stack Overflow answer seems to be the best bet, but I don’t know what the licensing implications are yet, and I haven’t had time to actually try to get it to work: http://stackoverflow.com/a/7623805/299222.

Here’s the command that I used to install the CSS parser library into the local repository:

    mvn install:install-file -DlocalRepositoryPath=repo -DcreateChecksum=true -Dpackaging=jar -Dfile=jars/osbcp-css-parser-1.4.jar -DgroupId=osbcp -DartifactId=css-parser -Dversion=1.4

I’d like to know how to automate this step as much as possible, however, and how to actually include the dependencies in the artifact, which will require some work. I’ll have to play around with some options, which will take a while, and I’m not sure how much time I’ll have to work on it. In the meantime, if there are any Maven experts in the mailing list, your input would be greatly appreciated.

Here’s one of our POM files that we have successfully used to publish artifacts to Maven Central:

https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/de-base-services-pom/pom.xml

This is a base POM that is used by some of our other projects. Here’s the POM file from one of the other projects:

https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/de-persistence/pom.xml

Here’s a link to another project POM that descends directly from the Sonatype OSS parent POM:

https://github.com/iPlantCollaborativeOpenSource/DiscoveryEnvironmentBackend/blob/master/libs/hibernatetoolkit/pom.xml

Let me know if you have more questions.

Thanks,
Dennis

On Oct 13, 2014, at 12:46 AM, Rutger Vos <rut...@gm...> wrote:

> Hi Dennis,
> 
> have you been able to have a look?
> 
> Thanks,
> 
> Rutger
> 
> On Tue, Oct 7, 2014 at 6:52 PM, Dennis Roberts <de...@ip...> wrote:
> Hi Rutger,
> 
> I’m sorry I haven’t gotten back to you on this; things have been busier than I expected for the last couple of weeks. I should be able to look over the file sometime later this week.
> 
> Thanks,
> Dennis
> 
> On Sep 25, 2014, at 1:33 AM, Rutger Vos <rut...@gm...> wrote:
> 
>> Hi Dennis,
>> 
>> is this more or less what we're looking for or am I missing sections: https://github.com/nexml/nexml.java/blob/master/pom.xml
>> 
>> I'm a bit unclear where and how to specify the javadoc and sources targets.
>> 
>> Thanks!
>> 
>> Rutger
>> 
>> On Tue, Sep 23, 2014 at 10:10 PM, Dennis Roberts <de...@ip...> wrote:
>> Hi Rutger,
>> 
>> The next step would be to update the pom.xml file to comply with Sonatype’s requirements. The instructions for that can be found here: http://central.sonatype.org/pages/apache-maven.html.
>> 
>> Dennis
>> 
>> On Sep 23, 2014, at 1:26 AM, Rutger Vos <rut...@gm...> wrote:
>> 
>>> Hi Dennis,
>>> 
>>> I just received notification that the request has been reviewed and granted. What would be the next steps?
>>> 
>>> Rutger
>>> 
>>> On Mon, Sep 22, 2014 at 7:41 PM, Dennis Roberts <de...@ip...> wrote:
>>> Hi Rutger,
>>> 
>>> You’re right; a real human being does have to look at the issue. It took a few days when I signed up for iPlant’s account.
>>> 
>>> Dennis
>>> 
>>> On Sep 22, 2014, at 2:29 AM, Rutger Vos <rut...@gm...> wrote:
>>> 
>>>> Hi Dennis, Anurag,
>>>> 
>>>> I have created a JIRA issue at Sonatype to get the account. I've added dennis.iplant as one of the other accounts that needs access. The issue is posted here: https://issues.sonatype.org/browse/OSSRH-11624 (presumably this is only visible for Dennis and I, though). I gather that a real human being has to look at this, so the next step is to wait for the OK from their end, right?
>>>> 
>>>> Cheers,
>>>> 
>>>> Rutger
>>>> 
>>>> On Fri, Sep 19, 2014 at 6:28 PM, Dennis Roberts <de...@ip...> wrote:
>>>> Hi Rutger,
>>>> 
>>>> No worries; I have a bunch of emails in my inbox that I’ve been meaning to get to for ages as well.
>>>> 
>>>> This is still relevant on our end, and I would say that the best approach is for nexml to have its own account. Sure, I’d be happy to help. If you could apply for an account with Sonatype and add me to the organization, I can help get the artifacts into Maven Central. Instructions for applying for a Sonatype account can be found here: http://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh. My account name at sonatype is dennis.iplant.
>>>> 
>>>> Let me know if you have any questions.
>>>> 
>>>> Thanks,
>>>> Dennis
>>>> 
>>>> On Sep 19, 2014, at 6:08 AM, Rutger Vos <rut...@gm...> wrote:
>>>> 
>>>>> Dear Dennis,
>>>>> 
>>>>> I feel a bit ridiculous responding to an email from March but it's been sitting in my inbox as "something to get to", so here we go.
>>>>> 
>>>>> If this is still relevant on your end (I hope so), would you say that the best approach is indeed for nexml to have its own account? Would you still be willing and able to help get the artifacts deployed there?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Rutger
>>>>> 
>>>>> On Thu, Mar 20, 2014 at 12:03 AM, Dennis Roberts <de...@ip...> wrote:
>>>>> Hey Everyone,
>>>>> 
>>>>> Sonatype allows open-source projects to publish artifacts to Maven Central for free. You can find instructions for doing this here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide. If someone sets up an account for nexml, I’d be happy to help get the artifacts deployed. Feel free to ask me questions if you like.
>>>>> 
>>>>> iPlant Collaborative has a Sonatype OSS account, so we could publish nexml-java to Maven Central. If we did that, we’d have to change the Maven group ID to something prefixed by org.iplantc, however.
>>>>> 
>>>>> Thanks,
>>>>> Dennis
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>> "Graph Databases" is the definitive new guide to graph databases and their
>>>>> applications. Written by three acclaimed leaders in the field,
>>>>> this first edition is now available. Download your free book today!
>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>> _______________________________________________
>>>>> Nexml-discuss mailing list
>>>>> Nex...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

Re: [Nexml-discuss] Nexml-Java and Maven Central

[Dennis R. <de...@ip...>]

Hi Rutger,

I’m sorry. I haven’t been able to look at it yet. I’ll look at it today.

Dennis

On Oct 13, 2014, at 12:46 AM, Rutger Vos <rut...@gm...> wrote:

> Hi Dennis,
> 
> have you been able to have a look?
> 
> Thanks,
> 
> Rutger
> 
> On Tue, Oct 7, 2014 at 6:52 PM, Dennis Roberts <de...@ip...> wrote:
> Hi Rutger,
> 
> I’m sorry I haven’t gotten back to you on this; things have been busier than I expected for the last couple of weeks. I should be able to look over the file sometime later this week.
> 
> Thanks,
> Dennis
> 
> On Sep 25, 2014, at 1:33 AM, Rutger Vos <rut...@gm...> wrote:
> 
>> Hi Dennis,
>> 
>> is this more or less what we're looking for or am I missing sections: https://github.com/nexml/nexml.java/blob/master/pom.xml
>> 
>> I'm a bit unclear where and how to specify the javadoc and sources targets.
>> 
>> Thanks!
>> 
>> Rutger
>> 
>> On Tue, Sep 23, 2014 at 10:10 PM, Dennis Roberts <de...@ip...> wrote:
>> Hi Rutger,
>> 
>> The next step would be to update the pom.xml file to comply with Sonatype’s requirements. The instructions for that can be found here: http://central.sonatype.org/pages/apache-maven.html.
>> 
>> Dennis
>> 
>> On Sep 23, 2014, at 1:26 AM, Rutger Vos <rut...@gm...> wrote:
>> 
>>> Hi Dennis,
>>> 
>>> I just received notification that the request has been reviewed and granted. What would be the next steps?
>>> 
>>> Rutger
>>> 
>>> On Mon, Sep 22, 2014 at 7:41 PM, Dennis Roberts <de...@ip...> wrote:
>>> Hi Rutger,
>>> 
>>> You’re right; a real human being does have to look at the issue. It took a few days when I signed up for iPlant’s account.
>>> 
>>> Dennis
>>> 
>>> On Sep 22, 2014, at 2:29 AM, Rutger Vos <rut...@gm...> wrote:
>>> 
>>>> Hi Dennis, Anurag,
>>>> 
>>>> I have created a JIRA issue at Sonatype to get the account. I've added dennis.iplant as one of the other accounts that needs access. The issue is posted here: https://issues.sonatype.org/browse/OSSRH-11624 (presumably this is only visible for Dennis and I, though). I gather that a real human being has to look at this, so the next step is to wait for the OK from their end, right?
>>>> 
>>>> Cheers,
>>>> 
>>>> Rutger
>>>> 
>>>> On Fri, Sep 19, 2014 at 6:28 PM, Dennis Roberts <de...@ip...> wrote:
>>>> Hi Rutger,
>>>> 
>>>> No worries; I have a bunch of emails in my inbox that I’ve been meaning to get to for ages as well.
>>>> 
>>>> This is still relevant on our end, and I would say that the best approach is for nexml to have its own account. Sure, I’d be happy to help. If you could apply for an account with Sonatype and add me to the organization, I can help get the artifacts into Maven Central. Instructions for applying for a Sonatype account can be found here: http://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh. My account name at sonatype is dennis.iplant.
>>>> 
>>>> Let me know if you have any questions.
>>>> 
>>>> Thanks,
>>>> Dennis
>>>> 
>>>> On Sep 19, 2014, at 6:08 AM, Rutger Vos <rut...@gm...> wrote:
>>>> 
>>>>> Dear Dennis,
>>>>> 
>>>>> I feel a bit ridiculous responding to an email from March but it's been sitting in my inbox as "something to get to", so here we go.
>>>>> 
>>>>> If this is still relevant on your end (I hope so), would you say that the best approach is indeed for nexml to have its own account? Would you still be willing and able to help get the artifacts deployed there?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Rutger
>>>>> 
>>>>> On Thu, Mar 20, 2014 at 12:03 AM, Dennis Roberts <de...@ip...> wrote:
>>>>> Hey Everyone,
>>>>> 
>>>>> Sonatype allows open-source projects to publish artifacts to Maven Central for free. You can find instructions for doing this here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide. If someone sets up an account for nexml, I’d be happy to help get the artifacts deployed. Feel free to ask me questions if you like.
>>>>> 
>>>>> iPlant Collaborative has a Sonatype OSS account, so we could publish nexml-java to Maven Central. If we did that, we’d have to change the Maven group ID to something prefixed by org.iplantc, however.
>>>>> 
>>>>> Thanks,
>>>>> Dennis
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------------
>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>> "Graph Databases" is the definitive new guide to graph databases and their
>>>>> applications. Written by three acclaimed leaders in the field,
>>>>> this first edition is now available. Download your free book today!
>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>> _______________________________________________
>>>>> Nexml-discuss mailing list
>>>>> Nex...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

Re: [Nexml-discuss] Nexml-Java and Maven Central

[Rutger V. <rut...@gm...>]

Hi Dennis,

have you been able to have a look?

Thanks,

Rutger

On Tue, Oct 7, 2014 at 6:52 PM, Dennis Roberts <
de...@ip...> wrote:

> Hi Rutger,
>
> I’m sorry I haven’t gotten back to you on this; things have been busier
> than I expected for the last couple of weeks. I should be able to look over
> the file sometime later this week.
>
> Thanks,
> Dennis
>
> On Sep 25, 2014, at 1:33 AM, Rutger Vos <rut...@gm...> wrote:
>
> Hi Dennis,
>
> is this more or less what we're looking for or am I missing sections:
> https://github.com/nexml/nexml.java/blob/master/pom.xml
>
> I'm a bit unclear where and how to specify the javadoc and sources targets.
>
> Thanks!
>
> Rutger
>
> On Tue, Sep 23, 2014 at 10:10 PM, Dennis Roberts <
> de...@ip...> wrote:
>
>> Hi Rutger,
>>
>> The next step would be to update the pom.xml file to comply with
>> Sonatype’s requirements. The instructions for that can be found here:
>> http://central.sonatype.org/pages/apache-maven.html.
>>
>> Dennis
>>
>> On Sep 23, 2014, at 1:26 AM, Rutger Vos <rut...@gm...> wrote:
>>
>> Hi Dennis,
>>
>> I just received notification that the request has been reviewed and
>> granted. What would be the next steps?
>>
>> Rutger
>>
>> On Mon, Sep 22, 2014 at 7:41 PM, Dennis Roberts <
>> de...@ip...> wrote:
>>
>>> Hi Rutger,
>>>
>>> You’re right; a real human being does have to look at the issue. It took
>>> a few days when I signed up for iPlant’s account.
>>>
>>> Dennis
>>>
>>> On Sep 22, 2014, at 2:29 AM, Rutger Vos <rut...@gm...> wrote:
>>>
>>> Hi Dennis, Anurag,
>>>
>>> I have created a JIRA issue at Sonatype to get the account. I've added
>>> dennis.iplant as one of the other accounts that needs access. The issue is
>>> posted here: https://issues.sonatype.org/browse/OSSRH-11624 (presumably
>>> this is only visible for Dennis and I, though). I gather that a real human
>>> being has to look at this, so the next step is to wait for the OK from
>>> their end, right?
>>>
>>> Cheers,
>>>
>>> Rutger
>>>
>>> On Fri, Sep 19, 2014 at 6:28 PM, Dennis Roberts <
>>> de...@ip...> wrote:
>>>
>>>> Hi Rutger,
>>>>
>>>> No worries; I have a bunch of emails in my inbox that I’ve been meaning
>>>> to get to for ages as well.
>>>>
>>>> This is still relevant on our end, and I would say that the best
>>>> approach is for nexml to have its own account. Sure, I’d be happy to help.
>>>> If you could apply for an account with Sonatype and add me to the
>>>> organization, I can help get the artifacts into Maven Central. Instructions
>>>> for applying for a Sonatype account can be found here:
>>>> http://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh.
>>>> My account name at sonatype is dennis.iplant.
>>>>
>>>> Let me know if you have any questions.
>>>>
>>>> Thanks,
>>>> Dennis
>>>>
>>>> On Sep 19, 2014, at 6:08 AM, Rutger Vos <rut...@gm...> wrote:
>>>>
>>>> Dear Dennis,
>>>>
>>>> I feel a bit ridiculous responding to an email from March but it's been
>>>> sitting in my inbox as "something to get to", so here we go.
>>>>
>>>> If this is still relevant on your end (I hope so), would you say that
>>>> the best approach is indeed for nexml to have its own account? Would you
>>>> still be willing and able to help get the artifacts deployed there?
>>>>
>>>> Thanks,
>>>>
>>>> Rutger
>>>>
>>>> On Thu, Mar 20, 2014 at 12:03 AM, Dennis Roberts <
>>>> de...@ip...> wrote:
>>>>
>>>>> Hey Everyone,
>>>>>
>>>>> Sonatype allows open-source projects to publish artifacts to Maven
>>>>> Central for free. You can find instructions for doing this here:
>>>>> https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide.
>>>>> If someone sets up an account for nexml, I’d be happy to help get the
>>>>> artifacts deployed. Feel free to ask me questions if you like.
>>>>>
>>>>> iPlant Collaborative has a Sonatype OSS account, so we could publish
>>>>> nexml-java to Maven Central. If we did that, we’d have to change the Maven
>>>>> group ID to something prefixed by org.iplantc, however.
>>>>>
>>>>> Thanks,
>>>>> Dennis
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>> their
>>>>> applications. Written by three acclaimed leaders in the field,
>>>>> this first edition is now available. Download your free book today!
>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>> _______________________________________________
>>>>> Nexml-discuss mailing list
>>>>> Nex...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Re: [Nexml-discuss] Nexml-Java and Maven Central

[Dennis R. <de...@ip...>]

Hi Rutger,

I’m sorry I haven’t gotten back to you on this; things have been busier than I expected for the last couple of weeks. I should be able to look over the file sometime later this week.

Thanks,
Dennis

On Sep 25, 2014, at 1:33 AM, Rutger Vos <rut...@gm...> wrote:

> Hi Dennis,
> 
> is this more or less what we're looking for or am I missing sections: https://github.com/nexml/nexml.java/blob/master/pom.xml
> 
> I'm a bit unclear where and how to specify the javadoc and sources targets.
> 
> Thanks!
> 
> Rutger
> 
> On Tue, Sep 23, 2014 at 10:10 PM, Dennis Roberts <de...@ip...> wrote:
> Hi Rutger,
> 
> The next step would be to update the pom.xml file to comply with Sonatype’s requirements. The instructions for that can be found here: http://central.sonatype.org/pages/apache-maven.html.
> 
> Dennis
> 
> On Sep 23, 2014, at 1:26 AM, Rutger Vos <rut...@gm...> wrote:
> 
>> Hi Dennis,
>> 
>> I just received notification that the request has been reviewed and granted. What would be the next steps?
>> 
>> Rutger
>> 
>> On Mon, Sep 22, 2014 at 7:41 PM, Dennis Roberts <de...@ip...> wrote:
>> Hi Rutger,
>> 
>> You’re right; a real human being does have to look at the issue. It took a few days when I signed up for iPlant’s account.
>> 
>> Dennis
>> 
>> On Sep 22, 2014, at 2:29 AM, Rutger Vos <rut...@gm...> wrote:
>> 
>>> Hi Dennis, Anurag,
>>> 
>>> I have created a JIRA issue at Sonatype to get the account. I've added dennis.iplant as one of the other accounts that needs access. The issue is posted here: https://issues.sonatype.org/browse/OSSRH-11624 (presumably this is only visible for Dennis and I, though). I gather that a real human being has to look at this, so the next step is to wait for the OK from their end, right?
>>> 
>>> Cheers,
>>> 
>>> Rutger
>>> 
>>> On Fri, Sep 19, 2014 at 6:28 PM, Dennis Roberts <de...@ip...> wrote:
>>> Hi Rutger,
>>> 
>>> No worries; I have a bunch of emails in my inbox that I’ve been meaning to get to for ages as well.
>>> 
>>> This is still relevant on our end, and I would say that the best approach is for nexml to have its own account. Sure, I’d be happy to help. If you could apply for an account with Sonatype and add me to the organization, I can help get the artifacts into Maven Central. Instructions for applying for a Sonatype account can be found here: http://central.sonatype.org/pages/producers.html#individual-projects-open-source-software-repository-hosting-ossrh. My account name at sonatype is dennis.iplant.
>>> 
>>> Let me know if you have any questions.
>>> 
>>> Thanks,
>>> Dennis
>>> 
>>> On Sep 19, 2014, at 6:08 AM, Rutger Vos <rut...@gm...> wrote:
>>> 
>>>> Dear Dennis,
>>>> 
>>>> I feel a bit ridiculous responding to an email from March but it's been sitting in my inbox as "something to get to", so here we go.
>>>> 
>>>> If this is still relevant on your end (I hope so), would you say that the best approach is indeed for nexml to have its own account? Would you still be willing and able to help get the artifacts deployed there?
>>>> 
>>>> Thanks,
>>>> 
>>>> Rutger
>>>> 
>>>> On Thu, Mar 20, 2014 at 12:03 AM, Dennis Roberts <de...@ip...> wrote:
>>>> Hey Everyone,
>>>> 
>>>> Sonatype allows open-source projects to publish artifacts to Maven Central for free. You can find instructions for doing this here: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide. If someone sets up an account for nexml, I’d be happy to help get the artifacts deployed. Feel free to ask me questions if you like.
>>>> 
>>>> iPlant Collaborative has a Sonatype OSS account, so we could publish nexml-java to Maven Central. If we did that, we’d have to change the Maven group ID to something prefixed by org.iplantc, however.
>>>> 
>>>> Thanks,
>>>> Dennis
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>> "Graph Databases" is the definitive new guide to graph databases and their
>>>> applications. Written by three acclaimed leaders in the field,
>>>> this first edition is now available. Download your free book today!
>>>> http://p.sf.net/sfu/13534_NeoTech
>>>> _______________________________________________
>>>> Nexml-discuss mailing list
>>>> Nex...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> 

Re: [Nexml-discuss] nexml.org domain name expiring(!)

[Rutger V. <rut...@gm...>]

As a brief follow up on this:

- the domain name has been renewed
- the static components of the website have been replicated as
nexml.github.io
- I just received the login credentials for a VM where I can host the
dynamic bits (i.e. the validator and cousins)

Next steps:

- deploying the web services on the VM
- making sure that the static part refers to them correctly (they'll be on
a different domain)
- updating the DNS records

Best wishes,

Rutger

On Mon, Aug 11, 2014 at 5:38 PM, Hilmar Lapp <hl...@ne...> wrote:

> Rutger - the name *is* registered for another year, according to WHOIS. If
> you didn't do that on Aug 4 (which is when WHOIS says it was done), then
> you're at the mercy of whoever holds the registration now.
>
> So first you'll need to get the name back under your possession from who's
> holding it right now. That may be GoDaddy as a "courtesy", and they
> typically charge a fee for providing that "courtesy" if you do want it
> back. Giving it back to you likely means renewal, which would result in a
> 60-day hold on transfers. Only after can you transfer the name to a
> different registrar.
>
>   -hilmar
>
>   -hilmar
>
>
> On Mon, Aug 11, 2014 at 10:17 AM, Rutger Vos <rut...@gm...> wrote:
>
>> Thanks! Do you guys have experience with transferring from GoDaddy to
>> NameCheap? Do I simply stop paying GoDaddy (check) and then register with
>> NameCheap? It doesn't seem like it works that way, considering they're
>> still sitting on the name.
>>
>>
>> On Mon, Aug 11, 2014 at 5:12 PM, Karen Cranston <
>> kar...@ne...> wrote:
>>
>>> We use namecheap at NESCent now. They do take paypal (as well as
>>> Bitcoin, if you are feeling flush with virtual currency):
>>>
>>> https://www.namecheap.com/support/payment/bitcoin.aspx
>>>
>>>
>>>
>>> On Mon, Aug 11, 2014 at 11:07 AM, Rutger Vos <rut...@gm...>
>>> wrote:
>>>
>>>> Yup, it expired, they still had my old CC on file while I was on hols.
>>>> I'm not particularly happy with GoDaddy, so what was the name of the
>>>> registrar that Hilmar now uses? Do they take PayPal?
>>>>
>>>>
>>>> On Fri, Aug 8, 2014 at 9:15 PM, Hilmar Lapp <hl...@ne...> wrote:
>>>>
>>>>> Odd. The WHOIS entry says it's been renewed for a year on Aug 4.
>>>>> -hilmar
>>>>>
>>>>>
>>>>> On Fri, Aug 8, 2014 at 12:21 PM, Carl Boettiger <cbo...@gm...>
>>>>> wrote:
>>>>>
>>>>>> Hi NeXML folks,
>>>>>>
>>>>>> The nexml.org domain name seems to have expired and now redirects to
>>>>>> a GoDaddy page... I think Rutger is away right now too...
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Carl
>>>>>>
>>>>>> --
>>>>>> Carl Boettiger
>>>>>> UC Santa Cruz
>>>>>> http://carlboettiger.info/
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Want fast and easy access to all the code in your enterprise? Index
>>>>>> and
>>>>>> search up to 200,000 lines of code with a free copy of Black Duck
>>>>>> Code Sight - the same software that powers the world's largest code
>>>>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>>>>> http://p.sf.net/sfu/bds
>>>>>> _______________________________________________
>>>>>> Nexml-discuss mailing list
>>>>>> Nex...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Want fast and easy access to all the code in your enterprise? Index and
>>>>> search up to 200,000 lines of code with a free copy of Black Duck
>>>>> Code Sight - the same software that powers the world's largest code
>>>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>>>> http://p.sf.net/sfu/bds
>>>>> _______________________________________________
>>>>> Nexml-discuss mailing list
>>>>> Nex...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>>
>>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> Nexml-discuss mailing list
>>>> Nex...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Karen Cranston, PhD
>>> Training Coordinator and Informatics Project Manager
>>> nescent.org
>>> @kcranstn
>>> http://orcid.org/0000-0002-4798-9499
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>
>>
>
>
> --
> Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io
>
>

Re: [Nexml-discuss] embedding elements in meta elements in NeXML

[Rutger V. <rut...@gm...>]

>
> > If no one knows of an open source validator that can deal with these
> > types of docs, perhaps we should consider adding the
> > processContent="lax" to the schema.
>
> I am open to this. Maybe it isn't the business of the NeXML schema to
> enforce anything about the structure of embedded foreign XML.


I agree. The intent behind using xs:any here:
https://github.com/nexml/nexml/blob/master/xsd/meta/annotations.xsd#L99 was
to allow basically any well-formed XML inside.

Re: [Nexml-discuss] embedding elements in meta elements in NeXML

[Jim B. <ba...@ne...>]

On Sep 30, 2014, at 11:18 PM, Mark Holder <mth...@gm...> wrote:

> thanks, Carl.
> 
> Definitely could be the same issue. I don't have Oxygen, so I can't
> check that. But it definitely seems like a very similar issue.
> 
> If no one knows of an open source validator that can deal with these
> types of docs, perhaps we should consider adding the
> processContent="lax" to the schema.

I am open to this. Maybe it isn't the business of the NeXML schema to enforce anything about the structure of embedded foreign XML.

- Jim

Re: [Nexml-discuss] embedding elements in meta elements in NeXML

[Mark H. <mth...@gm...>]

thanks, Carl.

Definitely could be the same issue. I don't have Oxygen, so I can't
check that. But it definitely seems like a very similar issue.

If no one knows of an open source validator that can deal with these
types of docs, perhaps we should consider adding the
processContent="lax" to the schema.

Mark

On Wed, Oct 1, 2014 at 4:56 AM, Carl Boettiger <cbo...@gm...> wrote:
> Hi Mark, list,
>
> Jim and I spent a while debugging this issue in RNeXML last year:
> https://github.com/ropensci/RNeXML/issues/23#issuecomment-29684938,
> which we traced to a problem with the lack of support for schema
> localization in xmllint.  More details in that thread.  It's possible
> the same localization issue is effecting the validator you're using?
> I believe Jim was using Oxygen which didn't have a problem validating
> this case.
>
> Cheers,
>
> Carl
>
> On Tue, Sep 30, 2014 at 7:48 PM, Mark Holder <mth...@gm...> wrote:
>> Hi all,
>> I thought that I had reported an issue about this a while back, but
>> I'm not finding it. Perhaps I forgot.
>>
>> Jonathan Rees reported an issue with a NeXML doc that one of my
>> software tools produces:
>>    https://github.com/OpenTreeOfLife/peyotl/issues/37
>>
>> The offending content is an XML element inside a <meta
>> xsi:type="nex:LiteralMeta"> element. The validator does not seem to
>> like this.
>>
>> It could be because the doc does not have an xml schema for the
>> contained element.
>>
>> But I can't get any of the examples of embedding an element into a
>> meta element to work. I found examples in Figure 3 of the NeXML paper
>> and from phenoscape files.  A simple example is
>> http://phylo.bio.ku.edu/ot/foo.xml
>>
>> The validator is the one from http://code.google.com/p/xml-validator/
>>
>> Tweaking the schema to skip validation of contained elements if the
>> schema is not  present gets rid of the error (
>> https://github.com/mtholder/nexml/commit/a3210a252e4eb9326e2819fa75d106f8776d111c
>> ). But that seems a bit too loose.
>>
>> Can anyone on this list tell if this a problem with the schema, the
>> validator, or the instance docs?
>>
>> thanks,
>> mark
>>
>>
>> --
>> Mark Holder
>>
>> mth...@gm...
>> mth...@ku...
>> http://phylo.bio.ku.edu/mark-holder
>>
>> ==============================================
>> Department of Ecology and Evolutionary Biology
>> University of Kansas
>> 6031 Haworth Hall
>> 1200 Sunnyside Avenue
>> Lawrence, Kansas 66045
>>
>> lab phone:  785.864.5789
>> fax (shared): 785.864.5860
>> ==============================================
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Nexml-discuss mailing list
>> Nex...@li...
>> https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>
>
>
> --
> Carl Boettiger
> UC Santa Cruz
> http://carlboettiger.info/



-- 
Mark Holder

mth...@gm...
mth...@ku...
http://phylo.bio.ku.edu/mark-holder

==============================================
Department of Ecology and Evolutionary Biology
University of Kansas
6031 Haworth Hall
1200 Sunnyside Avenue
Lawrence, Kansas 66045

lab phone:  785.864.5789
fax (shared): 785.864.5860
==============================================

Re: [Nexml-discuss] embedding elements in meta elements in NeXML

[Carl B. <cbo...@gm...>]

Hi Mark, list,

Jim and I spent a while debugging this issue in RNeXML last year:
https://github.com/ropensci/RNeXML/issues/23#issuecomment-29684938,
which we traced to a problem with the lack of support for schema
localization in xmllint.  More details in that thread.  It's possible
the same localization issue is effecting the validator you're using?
I believe Jim was using Oxygen which didn't have a problem validating
this case.

Cheers,

Carl

On Tue, Sep 30, 2014 at 7:48 PM, Mark Holder <mth...@gm...> wrote:
> Hi all,
> I thought that I had reported an issue about this a while back, but
> I'm not finding it. Perhaps I forgot.
>
> Jonathan Rees reported an issue with a NeXML doc that one of my
> software tools produces:
>    https://github.com/OpenTreeOfLife/peyotl/issues/37
>
> The offending content is an XML element inside a <meta
> xsi:type="nex:LiteralMeta"> element. The validator does not seem to
> like this.
>
> It could be because the doc does not have an xml schema for the
> contained element.
>
> But I can't get any of the examples of embedding an element into a
> meta element to work. I found examples in Figure 3 of the NeXML paper
> and from phenoscape files.  A simple example is
> http://phylo.bio.ku.edu/ot/foo.xml
>
> The validator is the one from http://code.google.com/p/xml-validator/
>
> Tweaking the schema to skip validation of contained elements if the
> schema is not  present gets rid of the error (
> https://github.com/mtholder/nexml/commit/a3210a252e4eb9326e2819fa75d106f8776d111c
> ). But that seems a bit too loose.
>
> Can anyone on this list tell if this a problem with the schema, the
> validator, or the instance docs?
>
> thanks,
> mark
>
>
> --
> Mark Holder
>
> mth...@gm...
> mth...@ku...
> http://phylo.bio.ku.edu/mark-holder
>
> ==============================================
> Department of Ecology and Evolutionary Biology
> University of Kansas
> 6031 Haworth Hall
> 1200 Sunnyside Avenue
> Lawrence, Kansas 66045
>
> lab phone:  785.864.5789
> fax (shared): 785.864.5860
> ==============================================
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss



-- 
Carl Boettiger
UC Santa Cruz
http://carlboettiger.info/

[Nexml-discuss] embedding elements in meta elements in NeXML

[Mark H. <mth...@gm...>]

Hi all,
I thought that I had reported an issue about this a while back, but
I'm not finding it. Perhaps I forgot.

Jonathan Rees reported an issue with a NeXML doc that one of my
software tools produces:
   https://github.com/OpenTreeOfLife/peyotl/issues/37

The offending content is an XML element inside a <meta
xsi:type="nex:LiteralMeta"> element. The validator does not seem to
like this.

It could be because the doc does not have an xml schema for the
contained element.

But I can't get any of the examples of embedding an element into a
meta element to work. I found examples in Figure 3 of the NeXML paper
and from phenoscape files.  A simple example is
http://phylo.bio.ku.edu/ot/foo.xml

The validator is the one from http://code.google.com/p/xml-validator/

Tweaking the schema to skip validation of contained elements if the
schema is not  present gets rid of the error (
https://github.com/mtholder/nexml/commit/a3210a252e4eb9326e2819fa75d106f8776d111c
). But that seems a bit too loose.

Can anyone on this list tell if this a problem with the schema, the
validator, or the instance docs?

thanks,
mark


-- 
Mark Holder

mth...@gm...
mth...@ku...
http://phylo.bio.ku.edu/mark-holder

==============================================
Department of Ecology and Evolutionary Biology
University of Kansas
6031 Haworth Hall
1200 Sunnyside Avenue
Lawrence, Kansas 66045

lab phone:  785.864.5789
fax (shared): 785.864.5860
==============================================

Re: [Nexml-discuss] [OpenTree-software] id attribute syntax

[Jonathan A R. <re...@mu...>]

Hmm... I am having trouble now finding an opentree nexml file with a
numeric id attribute, so perhaps this is all moot. I think I may have been
confused by the way tree ids are processed elsewhere in the system (i.e.
the bug may be elsewhere). If I find one then I'll report it on the peyotl
repo.

I ran the validator (Jeet's version) on pg_109.nexml and got a couple of
diagnostics which I'll report separately. (It took a very long time to
start up - probably because W3C hates to serve up schema files? which it
rightly thinks people ought to cache/"install".)

Jonathan

On Tue, Sep 30, 2014 at 3:15 PM, Mark Holder <mth...@gm...> wrote:

> There was a thread [1] that I think is related to this.
>
> In an attempt to make sure that open tree tools were getting most of
> the info in the right spots in NeXML, I loosened the schema in a few
> spots (in an attempt to get the treebase nexml to validate see [2]).
> My roundtrip tests (in peyotl) use a fork of the schema[3]. Clearly
> that is not optimal, and it would be good to be using official schema.
>
> cheers,
> Mark
>
>
> [1]
> http://sourceforge.net/p/nexml/mailman/nexml-discuss/thread/CAB2isBT1paiV9r%2BsVhdDMxNrxfP_fNZ%2B%2BnOvfQ%2BH4i12zhobjg%40mail.gmail.com/#msg31798831
>
> [2]
> http://sourceforge.net/p/nexml/mailman/nexml-discuss/thread/CAB2isBR5DB0d8-rn8cvJVNB-a0aK9xg6u9BVjYA7tJnbZhEXLQ%40mail.gmail.com/#msg31808808
>
> [3] https://github.com/mtholder/nexml
>
> On Tue, Sep 30, 2014 at 6:49 PM, Jim Balhoff <ba...@ne...> wrote:
> > Yes, that's right, IDs can't start with digits. Many of the Phenoscape
> files do still contain such IDs, because I haven't done a mass migration
> since I updated this in Phenex.
> >
> > - Jim
> >
> >
> > On Sep 30, 2014, at 12:20 PM, Hilmar Lapp <hl...@ne...> wrote:
> >
> >> FYI. I believe we did encounter the no-leading-digit issue with IDs in
> Phenex and had to fix it (Jim?).
> >>
> >>    -hilmar
> >>
> >> ---------- Forwarded message ----------
> >> From: Jonathan A Rees <re...@mu...>
> >> Date: Tue, Sep 30, 2014 at 11:15 AM
> >> Subject: [OpenTree-software] id attribute syntax
> >> To: "ope...@go..." <
> ope...@go...>
> >>
> >>
> >> Have our nexml files passed the nexml validator? If so I think there's
> a bug in the nexml validator.
> >>
> >> If I follow the convoluted documentation chain correctly, a nexml 'id'
> attribute has syntax and semantics inherited from XML schema's xs:id, and
> xs:id has syntax coming from XML's xml:id:
> >>
> >> https://github.com/nexml/nexml/blob/master/xsd/external/xml.xsd
> >> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID
> >> http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-TokenizedType
> >>
> >> Members of the value space have to match the 'Name' production:
> >>
> >> http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-Name
> >> Name     ::=          (Letter | '_' | ':') ( NameChar)*
> >>
> >> A lot of our ids begin with digits, which are disallowed. If this isn't
> being caught by the nexml validator, then there is a bug in the nexml
> validator.
> >>
> >> If I'm right then
> >> - a validator bug should be reported
> >> - when converting from nexson to nexml, an underscore should be
> prepended if the first character is a digit (applies to all attributes with
> id values, such as @source)
> >>
> >> If someone (Mark?) can confirm this I'll file the two issues.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Open Tree of Life - Software Development" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to ope...@go....
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >>
> >>
> >> --
> >> Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Nexml-discuss mailing list
> > Nex...@li...
> > https://lists.sourceforge.net/lists/listinfo/nexml-discuss
>
>
>
> --
> Mark Holder
>
> mth...@gm...
> mth...@ku...
> http://phylo.bio.ku.edu/mark-holder
>
> ==============================================
> Department of Ecology and Evolutionary Biology
> University of Kansas
> 6031 Haworth Hall
> 1200 Sunnyside Avenue
> Lawrence, Kansas 66045
>
> lab phone:  785.864.5789
> fax (shared): 785.864.5860
> ==============================================
>
> --
> You received this message because you are subscribed to the Google Groups
> "Open Tree of Life - Software Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ope...@go....
> For more options, visit https://groups.google.com/d/optout.
>

Re: [Nexml-discuss] [OpenTree-software] id attribute syntax

[Mark H. <mth...@gm...>]

There was a thread [1] that I think is related to this.

In an attempt to make sure that open tree tools were getting most of
the info in the right spots in NeXML, I loosened the schema in a few
spots (in an attempt to get the treebase nexml to validate see [2]).
My roundtrip tests (in peyotl) use a fork of the schema[3]. Clearly
that is not optimal, and it would be good to be using official schema.

cheers,
Mark


[1]  http://sourceforge.net/p/nexml/mailman/nexml-discuss/thread/CAB2isBT1paiV9r%2BsVhdDMxNrxfP_fNZ%2B%2BnOvfQ%2BH4i12zhobjg%40mail.gmail.com/#msg31798831

[2] http://sourceforge.net/p/nexml/mailman/nexml-discuss/thread/CAB2isBR5DB0d8-rn8cvJVNB-a0aK9xg6u9BVjYA7tJnbZhEXLQ%40mail.gmail.com/#msg31808808

[3] https://github.com/mtholder/nexml

On Tue, Sep 30, 2014 at 6:49 PM, Jim Balhoff <ba...@ne...> wrote:
> Yes, that's right, IDs can't start with digits. Many of the Phenoscape files do still contain such IDs, because I haven't done a mass migration since I updated this in Phenex.
>
> - Jim
>
>
> On Sep 30, 2014, at 12:20 PM, Hilmar Lapp <hl...@ne...> wrote:
>
>> FYI. I believe we did encounter the no-leading-digit issue with IDs in Phenex and had to fix it (Jim?).
>>
>>    -hilmar
>>
>> ---------- Forwarded message ----------
>> From: Jonathan A Rees <re...@mu...>
>> Date: Tue, Sep 30, 2014 at 11:15 AM
>> Subject: [OpenTree-software] id attribute syntax
>> To: "ope...@go..." <ope...@go...>
>>
>>
>> Have our nexml files passed the nexml validator? If so I think there's a bug in the nexml validator.
>>
>> If I follow the convoluted documentation chain correctly, a nexml 'id' attribute has syntax and semantics inherited from XML schema's xs:id, and xs:id has syntax coming from XML's xml:id:
>>
>> https://github.com/nexml/nexml/blob/master/xsd/external/xml.xsd
>> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID
>> http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-TokenizedType
>>
>> Members of the value space have to match the 'Name' production:
>>
>> http://www.w3.org/TR/2000/WD-xml-2e-20000814#NT-Name
>> Name     ::=          (Letter | '_' | ':') ( NameChar)*
>>
>> A lot of our ids begin with digits, which are disallowed. If this isn't being caught by the nexml validator, then there is a bug in the nexml validator.
>>
>> If I'm right then
>> - a validator bug should be reported
>> - when converting from nexson to nexml, an underscore should be prepended if the first character is a digit (applies to all attributes with id values, such as @source)
>>
>> If someone (Mark?) can confirm this I'll file the two issues.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Open Tree of Life - Software Development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to ope...@go....
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Hilmar Lapp -:- informatics.nescent.org/wiki -:- lappland.io
>>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Nexml-discuss mailing list
> Nex...@li...
> https://lists.sourceforge.net/lists/listinfo/nexml-discuss



-- 
Mark Holder

mth...@gm...
mth...@ku...
http://phylo.bio.ku.edu/mark-holder

==============================================
Department of Ecology and Evolutionary Biology
University of Kansas
6031 Haworth Hall
1200 Sunnyside Avenue
Lawrence, Kansas 66045

lab phone:  785.864.5789
fax (shared): 785.864.5860
==============================================