[OASIS Issue Tracker] Updated: (SOAEERP-38) Issue with URIs andhow an implementation can distinguish them

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

     [ http://tools.oasis-open.org/issues/browse/SOAEERP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated SOAEERP-38:
-------------------------------

    Component/s: spec
    Description: 
The reference to services and other things are all URIs. How can an implementation determine which kind of service or entity is at the URI used? This is in all three information specifications

WTC: The key issue is how can the nature of something referenced by a URI be determined, e.g. is it a rating service? Is another service?

  was:The reference to services and other things are all URIs. How can an implementation determine which kind of service or entity is at the URI used? This is in all three specifications


>  Issue with URIs and how an implementation can distinguish them
> ---------------------------------------------------------------
>
>                 Key: SOAEERP-38
>                 URL: http://tools.oasis-open.org/issues/browse/SOAEERP-38
>             Project: OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC
>          Issue Type: Task
>          Components: Protocol Spec, spec
>            Reporter: Paul Yang 
>            Assignee: Szu Chang 
>
> The reference to services and other things are all URIs. How can an implementation determine which kind of service or entity is at the URI used? This is in all three information specifications
> WTC: The key issue is how can the nature of something referenced by a URI be determined, e.g. is it a rating service? Is another service?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira