Super cool! I will be on. I can field any questions or suggestions before the telcon as well..
My questions are: 1. What's up with "IsFsfLibre" .. it's in lots of licences but not in SPDX.rdf 2. Good examples of using SPDX for exchanges of other than license information. 3. Interest in National Information Exchange Model (NIEM) involvement - publication of SPDX NIEM XSDs to NIEM repository. Anticipated FAQ: Why XML Schema? - Increased ability to tightly restrict content and automate validation - Implementation methodology that allows purpose-built XSD for specific purposes while retaining logical data provenance with respect to a common XSD. - The ability to apply security tags in accordance with US and NATO standards. - Use SPDX for trusted data information exchanges - Can be used to leverage SPDX using XML Schema extension and restriction without normative changes to SPDX. - National Information Exchange Model (NIEM) alignment - well suited for RDF models. Why Code Generation? - Reduce human error for implementation - Support continuous test / build environments Why SPDX? - Sufficiently generalized treatment for a Reference Schema - Mature community, Comprehensive. - License List represents a success model that can be repeated for other things. - Open Source Pie? - Like or not.. Thanks! Neutron On Tue, Jun 12, 2018 at 6:02 AM John Scott (Ion) <[email protected]> wrote: > Sure and yes > > ------------------------------------------- > John Scott, President, Ion Channel > 240.401.6574 @johnmscott > < [email protected] > > www.ionchannel.io > > [image: Inline image 1] > *Software Supply Chain Intelligence* > > On June 12, 2018 at 8:16:12 AM, Kate Stewart ([email protected]) > wrote: > > Hi John, James, > Thank you for sharing this with us! :-) > > Would you be willing to join the tech team call on June 19th? > We'd like to understand this a bit more and ask some questions. > > Thanks, > Kate & Gary. > > > On Thu, Jun 7, 2018 at 6:46 AM, John Scott (Ion) <[email protected] > > wrote: > >> Hi SPDX, Our amazing XML/XSD SME James Neushul has completed an initial >> version, see; >> >> https://spdx-xsd.specchain.org. >> >> For example - some of the licenses in the list have fields that aren't in >> the current SPDX spec. I had to incorporate them in the SPDX XSD in order >> to implement the license list. One benefit of the XSD might be the ability >> to use XSDCCM to configuration manage the spec so that they avoid/detect >> basic issues like that. >> >> Task 1 >> Use SPDX XML License data in SEvA (pretty much done). >> >> Branch Task -- >> Wrap SEvA in SPDX XML and use it to catalog, group and cross reference >> SEvAs and SEvA data. Make it available as an SPDX tool and have SPDX as a >> way for people to use SEvA. Benefit from the market position of SPDX ... >> participate in the community, and help define the industry at the data >> level. >> >> OPTIONAL: Work with SPDX to recognize SPDX XML Schema as an >> authoritative product and host the authoritative XML Schema. >> >> RISK: Branch Task is an Implementation Schema for SPDX that contains SEvA >> data. It could be considered to include ION Channel IP .. as to how you >> group and cross reference data and for what purpose .. so there's that to >> consider. >> >> ------------------------------------------- >> John Scott, President, Ion Channel >> 240.401.6574 @johnmscott >> < [email protected] > >> www.ionchannel.io >> >> [image: Inline image 1] >> *Software Supply Chain Intelligence* >> >> _______________________________________________ >> Spdx-tech mailing list >> [email protected] >> https://lists.spdx.org/mailman/listinfo/spdx-tech >> >> > -- JDN
55719CE2-3C36-41EE-86E5-CEAF68E9BB85
Description: Binary data
ii_1596f0ff17bb68f7
Description: Binary data
_______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
