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: Re: [dss-x] Can someone please check if we really have this lower/uppercase variations in element names?


Hi  Ernst Jan,

> 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.
the JSON world prefers a lower case letter at the start.
>
> 4.3.18 Component IncludeObject
>
> attribute: hasObjectTagsAndAttributesSet --> HasObjectTagsAndAttributesSet
> attribute: createReference --> CreateReference
Break with the v1.0 scheme?
>
> 4.3.14 X509Digest – JSON Syntax
> value (json only; does not exist in XML) --> Value (?)
Keep JSON starting with a lower case letter.
> in 4.3.17 the Value is also used in XML (with a capital V)
see above.
> 4.3.24
> ReferenceXpath  --> Correct into ReferenceXPath
Break with the v1.0 scheme?
> 4.4.1.1.
> SPProvidedID  --> SPProvidedId
> value (json only; does not exist in XML) --> Value
Break with the SAML 1.0 scheme?
> 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...
OK!
>
> 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
>
Sorry, I don't get your point here.
Could you please explain?


Greetings,

Andreas
>
>
> 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
> ---------------------------------------------------------------------
> 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 
>
>

-- 
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]