[OASIS Issue Tracker] (BDXR-4) Replacing full uri in ServiceMetadataReference with document type identifier

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/BDXR-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67457#comment-67457 ] 

Erlend Klakegg Bergheim commented on BDXR-4:
--------------------------------------------

Conclusion in meeting September 13th 2017: 

Convert ServiceMetataReference into a "Capability".

Servicegroup [parent]
- ParticipantIdentifier [1..1]
- "Capability" [1..n]
- - ServiceIdentifier [1..1]
- - ProcessIdentifer [1..n]

> Replacing full uri in ServiceMetadataReference with document type identifier
> ----------------------------------------------------------------------------
>
>                 Key: BDXR-4
>                 URL: https://issues.oasis-open.org/browse/BDXR-4
>             Project: OASIS Business Document Exchange (BDXR) TC
>          Issue Type: Improvement
>          Components: Documentation, XML Schema
>    Affects Versions: SMP 2.0
>            Reporter: Erlend Klakegg Bergheim
>            Priority: Minor
>             Fix For: SMP 2.0
>
>
> From https://lists.oasis-open.org/archives/bdxr-comment/201611/msg00004.html
> I would prefer, if the ServiceMetadataReference would not contain the full target URL with participant and document type, but only the document type. The final URL can easily be build by SMP clients and it would be much easier to achieve this. Especially if an SMP is running behind a proxy, the SMP must always know it's "public URL" to be used in this element. This leads to problems in production, if e.g. the URLs between the ServiceGroup query and the contained ServiceMetadataReference are different (seen this quite often!)



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)