OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

s-ramp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (SRAMP-70) Re-think "2.3.5.2.1 Using Batch POST"


Brett Meyer created SRAMP-70:
--------------------------------

             Summary: Re-think "2.3.5.2.1 Using Batch POST"
                 Key: SRAMP-70
                 URL: https://issues.oasis-open.org/browse/SRAMP-70
             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
          Issue Type: Improvement
          Components: Atom Binding
            Reporter: Brett Meyer


The Atom binding's "2.3.5.2.1 Using Batch POST" section may deserve some re-thinking.  I can understand how chaining the artifacts together, in order to gain relational context, makes sense.  But as it stands, the use of <link> is a really weak way to bond them together.  For example, the doc shows the following relationship:

{code}
<link href=" cid:56@example.org" type="application/atom+xml;type=entry" rel="related" title="Imported XSD"/>
{code}

If we could find a way to explicitly define the real relationship name here ("importedXsds"), rather than "Imported XSD", internal processing would be much simpler and more straight-forward.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]