[OASIS Issue Tracker] Updated: (SRAMP-31) Should s-ramp artifactshave their own namespace and/or OWL classification

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

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

Vincent Brunssen updated SRAMP-31:
----------------------------------


Update July 13, 2011
I will have a proposal for a resolution to this issue by the Conference Call that will be held on July 27, 2011.

> Should s-ramp artifacts have their own namespace and/or OWL classification
> --------------------------------------------------------------------------
>
>                 Key: SRAMP-31
>                 URL: http://tools.oasis-open.org/issues/browse/SRAMP-31
>             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
>          Issue Type: Improvement
>          Components: Foundation
>    Affects Versions: 1.0
>         Environment: S-RAMP Foundation Document
>            Reporter: Vincent Brunssen
>            Assignee: Vincent Brunssen
>             Fix For: 1.0
>
>
> In the S-RAMP Foundation document section 2.3 and 2.4 define the S-RAMP models.  It has been asserted that the artifacts defined in these sections could have classifications that are associated with each artifact.  An example of this might be an Organization could have an OWL classification of http://www.s-ramp.org/ServiceImplementationModel#Organization.

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