dss-x — archive

[Ernst Jan van Nigtevecht]

My impressions of this: I would expect: - Only use ID and IDREF in these cases - Use Id only in combination with other phrases (like ResponseId and RefId) - Use capital first letter for all model items. Regards Ernst Jan 4.3.18 Component IncludeObject attribute: hasObjectTagsAndAttributesSet --> HasObjectTagsAndAttributesSet attribute: createReference --> CreateReference 4.3.14 X509Digest – JSON Syntax value (json only; does not exist in XML) --> Value (?) in 4.3.17 the Value is also used in XML (with a capital V) 4.3.24 ReferenceXpath --> Correct into ReferenceXPath 4.4.1.1. SPProvidedID --> SPProvidedId value (json only; does not exist in XML) --> Value 4.4.3.1 value --> Value 4.5 Second part is difficult to identify visually: The subsequent table allows to find the abbreviated JSON member names for a given element name. --> Add some white lines... Confusing: ID ID Id id --> Do not use this Identifier id --> only use this if there is a 1-to-1 relation from JSON to model. RefId versus RequestID and ResponseID Stefan Hagen wrote: > Gents, > > while boosting readability (think: tagging in word, indexing, etc) I > often meet variations in lower upper camel whatever case for the same > syllables / acronyms. > > E.g. > > value (sometimes Value) > > ID vs. Id > > XPath vs. Xpath > > Is this due to upstream nags, or did our schema always have this garden > variety or is this a problem with our extraction chain (the latter I do > not think) > > It would be very helpful to receive some educated guesses from people > other than the one currently digging hours over hours through the word > document. > > Thanks a bunch / Bunch :-) > Stefan > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php