I would like to request a little more distinction in the syntax highlighting for css variables.

Currently we give a 500 when we try to do an insert/delete if the variable is unbound. Instead we should throw a nice JSON error that can be interpreted on the client.

e.g.

{"when" : [ {"true" : []}, 
                 {"insert" : ["v:a", "v:b", "v:c"]}]}

I think we're very light on community, up to date involved people and meetsup / forums and co.

Basically the question is: Where is the community?

Hi,

I would like to use the WebVOWL library in my project, but i cant seem to find any documentation on how to implement this?

Cheers

Explain:

• The standard and the Assisted Inject patterns
• Definition of interface implementations + system parameters in the property files
• The notions of module and post-module

Label: New Term Request

In annotating diseases with HPO, we would like to be able to use phenotypic gender as a clinical modifier (e.g. to note specific disease phenotypes that may only be present or more frequent in one gender). That idea is alluded to in the documentation of the new annotation format, but the terms are missing from the Clinical Modifier subontology. Can you add these terms?

The readme file states this version passes the full batch of official OWL Full/RL tests. It would be good to make the tests part of the project to make collaboration easier and more constructive.

We have a README-editors.md file in this repo, as per convention with other OBO ontologies.

The first line states:

A step-by-step guide for GO Ontology Editors can be found at http://go-ontology.readthedocs.io/.

But we decided to move from RTD to the wiki. This should be updated.

It then goes on to say

This Jenkins job will create releases https

The application should verify the URL entered ( images , foaf:knows, etc )

• they actually exist ( no 404 )
• they have RDF content if that's required

Ideally , this should occur client side .

Is your feature request related to a problem? Please describe.
Can info be shared about what was learned during some deployments? (ex: 400m with clear line of sight between MomaDucks got this much bandwidth/error rate, etc.)

Describe the solution you'd like
Some info on what was found during deployments. Perhaps what is "optimal/maximal" vs. actual.

**Describe alternatives you've c

A bug report assumes that you are not trying to introduced a new feature, but instead change an existing one... hopefully correcting some latent error in the process.

Description

My take on SKOS definition comments

What would you like to see changed?

https://github.com/ESIPFed/sweet/wiki/SWEET-Annotation-Convention says if I have a comment I should create an issue, so this is my

Maybe we can add a section in the README-editors.md, or create a seperate doc ala HPO. In any case it would be good if QC is clearly explained somewhere (on a by ontology basis, thinking of configurable ROBOT report levels and so on).

The release notes provide great highlights and in-depth detail for the Development version.
Are there similar release notes for Production or does the detail bullet point indicate whether the change was propagated from DEV to PROD?
Thanks

The build process produces biolink-model.shex. It takes a bit of time, however, to compile this, so we need to add biolink-model.shexj to the output to make the data evaluation run more quickly;

They are not in the sheet, but they should be added. This is a reminder for me to dig them out: Calbindin, parvalbumin and IP3 Receptor