Hi Steve,
thanks for this, it will be very useful. As soon as there is a new
document I'll let you know.
cheers
alessandra
On 10/06/2019 15:17, Stephen Jones wrote:
> Hi all,
>
> The latest manual document is (I think) here:
>
> https://twiki.cern.ch/twiki/bin/view/EGEE/WLCGISEvolution#Publishing_CE_configuration_in_t
>
>
> I.e. CCR Scheme 1.2 dated 26/4/2019.
>
> I'll use that (for now) as a test to show the automatic validation
> process works OK.
>
> Once a new document emerges, we can change the Schema.
>
> Eventually, it would be best to "change control" the Schema itself
> rather than the document (for obvious reasons.)
>
> I think this is the right track....
>
> Cheers,
>
> Ste
>
>
> On 10/06/2019 13:13, Stephen Jones wrote:
>> Hi all,
>>
>> At a UK GridPP technical meeting on Friday, we discussed the state of
>> the "new information system". As far as I know, the new scheme is to
>> publish a URL in the GOCDB. The URL will provide a JSON summary of a
>> site's layout. The structure of the JSON is still under discussion (a
>> new release of a word DOC is pending.) At the technical meeting, we
>> mentioned ways to ensure that the JSON is valid.
>>
>> There was talk of using a script for this, but there is a better way.
>> Like XML, a JSON document has two levels of validation. In the first
>> instance, it must be "well formed", i.e. the syntax of the document
>> must conform to the grammar allowed under JSON. I think there are
>> libraries to ensure this.
>>
>> More rigorously, to be useful in an application, a JSON must also
>> conform to a Schema. A Schema constrains the structure and content of
>> a JSON document to some standard used in the application. We can
>> create a standard schema for the new Information System JSON, based
>> on the manual document that we have been discussing. Then we will
>> have a formal definition of the allowable content that can be
>> enforced using standard tools. One way to design and impose a Schema
>> is described here: https://json-schema.org/
>>
>> BTW: Once we have a formal definition, we can use that for
>> configuration control, rather than the manual document (which can be
>> ambiguous). Anyway, that's the plan. My questions are:
>>
>> * who can provide me with the most current manual document?
>>
>> * is it good enough to use to prototype a JSON schema to define it?
>>
>> When I know these things, I can write a JSON Schema to define the
>> document. This will make validation trivial and also simply
>> configuration control (by removing any/all ambiguity.)
>>
>> Cheers,
>>
>> Ste
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
--
Respect is a rational process. \\//
For Ur-Fascism, disagreement is treason. (U. Eco)
########################################################################
To unsubscribe from the TB-SUPPORT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=TB-SUPPORT&A=1
|