duplicated props about spec-jsonld HOT 5 CLOSED

Red connect in #41 - might need to manually fork & manually fix

from spec-jsonld.

These are excellent examples of what we inherit from the upstream model. I agree with you @onthebreeze our only option is to fork and allow ourselves to manually tidy for obvious bugs like this. The idea of doing this with NDRs or project interdependencies is completely unrealistic.

from spec-jsonld.

• #48, #49 will expose a lot of such cases because gratuitous naming differences will be eliminated, so we'll see the duplicates.
• referenceDocument vs referencedDocument can be caught with some simple fuzzy comparison
• attachedBinaryFile vs attachmentBinaryObject needs manual inspection

from spec-jsonld.

These duplications seem to be a problem for all UN/CEFACT syntaxes. Shouldn't this be better addressed at a 'higher level' by the UN/CEFACT library maintenance team?

from spec-jsonld.

Yes, maybe, @svanteschubert.
I labeled this semantics the other day (meaning unless we fork we won't touch it). However, if this is a consistent error which can be fixed with not-overly-complex code I wouldn't be against tagging it (also) as NDR and take it upon our internal scope to fix.
(I hope it makes sense what I am expressing here :) )

from spec-jsonld.