[esip-semantictech] Semantic Technologies Group Community Ontology Repository (COR) Use Cases & Requirements

[Ruth Duerr]

I just have to say ugh… to the lack of markdown support for the use case and requirements document.  I suspect I will be using github issues for any requested changes to the document (which by the way still has a lot of extraneous sections from previous documents in it which I otherwise would have cleaned up).  It’s a time thing (as in I don’t have any).

Otherwise this all looks great.

Ruth

> On Aug 4, 2016, at 5:12 PM, Mcgibbney, Lewis J (398M) via esip-semanticweb <esip-semanticweb at lists.esipfed.org> wrote:
> 
> Hi Carlos,
> 
> From: <carueda at gmail.com <mailto:carueda at gmail.com>> on behalf of Carlos Rueda <carueda at mbari.org <mailto:carueda at mbari.org>>
> Date: Thursday, August 4, 2016 at 11:44 AM
> To: Lewis John McGibbney <lewis.j.mcgibbney at jpl.nasa.gov <mailto:lewis.j.mcgibbney at jpl.nasa.gov>>
> Cc: ESIP Semantic Web Cluster <esip-semanticweb at lists.esipfed.org <mailto:esip-semanticweb at lists.esipfed.org>>, Janet Fredericks <jfredericks at whoi.edu <mailto:jfredericks at whoi.edu>>, Janowicz Krzysztof <janowicz at ucsb.edu <mailto:janowicz at ucsb.edu>>
> Subject: Re: [esip-semantictech] Semantic Technologies Group Community Ontology Repository (COR) Use Cases & Requirements
> 
> Hi Lewis,
> 
> I just forked https://github.com/ESIPFed/stc <https://github.com/ESIPFed/stc> (at https://github.com/xdomes/stc <https://github.com/xdomes/stc>) with the preliminary idea of our X-DOMES team potentially contributing is some way (then submitting pull requests as a typical workflow).
> 
> Cool, thanks for forking and attempting to push this forward.
> 
> 
> Right now, a quick question: By looking a bit more closely, seems like the contents are already in html form. Perhaps there's some other place where the actual "source" of the contents is located?
> 
> No. right now, there is no underlying markdown which is compiled into HTML. This could be improved however I honestly don’t have the time to do that right now.
> 
> If so, how is the output being generated?
> 
> Nothing is being generated as such. We are writing well formed HTML 5. I personally am running it through the free formatter at [0] (setting space indents to 2) and the W3C validator service at [1]. Both of these provide a quality assurance and control level. It will be up to the editors of the Committee document(s) to ensure that this is upheld and maintained should we wish to progress with this method of gathering our use cases and progressing the ESIP SRI agenda in this manner. I suppose we will see @ our next meeting.
> 
> With this information we would be able to do some local tests before submitting any pull requests, etc.  Apologies if this information has already been discussed (I just very recently joined the list).
> 
> No need to apologize for anything. In a bit to help our with this, I’ve actually substantiated on some documentation which can be found at the README [2].
> If you would be kind enough o try out this workflow and tell me if it works then we can either improve it, or scrap it.
> Thanks again. Your input is very valuable.
> Lewis
> 
> [0] http://www.freeformatter.com/html-formatter.html
> [1] https://validator.w3.org <https://validator.w3.org/>/
> [2] https://github.com/ESIPFed/stc
> _______________________________________________
> esip-semanticweb mailing list
> esip-semanticweb at lists.esipfed.org
> http://lists.deltaforce.net/mailman/listinfo/esip-semanticweb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deltaforce.net/pipermail/esip-semanticweb/attachments/20160804/9975dac6/attachment.html>