OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: AW: [dss-x] DSS-X call

Dear all,

I'd like to let you know that I will be out of the office tomorrow and 
not able to participate. Sorry for this. I wish you a fruitful meeting.


-----Ursprüngliche Nachricht-----
Von: dss-x@lists.oasis-open.org [mailto:dss-x@lists.oasis-open.org] Im Auftrag von Andreas Kuehne
Gesendet: Sonntag, 3. September 2017 18:22
An: dss-x <dss-x@lists.oasis-open.org>
Betreff: [dss-x] DSS-X call

Hi all,

I'm looking forward to our call tomorrow and would like to give some updates upfront:

Schema to Docx transfer:

I've improved the 'structure model' generator and improved the way to supply additional comments. My first approach to embed the comments into the schema was somehow tedious and very restricted (e.g. no way to insert document-internal links). Word offers a way to insert placeholder elements into a document. So I inserted a set of placeholders ( see the document attached, e.g. section 3.1.1, the green content). When generating a new version the content of the placeholder to the new version. So there is no need to edit the schema, just use Word! In the final version of the spec the  placeholder will be dropped and the just the content will be inserted at its appropriate location.

So the work on the specification can be done as usual and the 'structure model' section can be updated when required!

Please have a look at the set of placeholders. Are there any additional placeholder required?

If we come to the conclusion that this approach is feasible I will start to transfer the relevant content from the 'old' DSS spec to the new document.

JSON schema:

I've checked several JSON schema tools and I'm a bit disappointed regarding the validation support for JSON schema features. So I limited the schema options to the 'required' set and 'minProperties' / 'maxProperties'. But only a few DSS types take advantage of JSON schema restrictions. Sample attached, feedback welcome!

Use of UBL:

Pim mentioned the UBL specification and especially the option of JSON binding. It's a promising approach but I don't feel quite sure whether it's a way to go because the structure we use are represented by quite complex schemas. Does anyone got experience with UBL and complex types?



Andreas Kühne
phone: +49 177 293 24 97
mailto: kuehne@trustable.de

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612

Director Andreas Kühne

Company UK Company No: 5218868 Registered in England and Wales 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]