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


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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

Subject: [OASIS Issue Tracker] (OSLCCORE-14) attachments-v3.html final editing issues

James Amsden created OSLCCORE-14:

             Summary: attachments-v3.html final editing issues
                 Key: OSLCCORE-14
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-14
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
            Reporter: James Amsden
            Assignee: James Amsden
            Priority: Minor

1. As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative. 

This text is included in the Conformance section - which eliminates the need to have subsections marked as informational for Example sections (as was done for some of the other specifications).

2. Why is attachmentSize included in the attachment meta-data. Can’t that be determined in a standard way with HEAD?

3. 7.3.1, why can’t the attachment be an LDP-RS?

4. 7.4.6 LDP only specifies LDPR and LDPC interaction models, there is no LDP-NR interaction model - or is that the default if one isn’t specified? What impact would this have on the creation of the attachment or its descriptor?

5. The specification does not say ho AttachmentDescriptor properties such as description, identifier, title are set. The AttachmentDescriptor may be created as a side effect of a POST to create an attachment, and may be updated when a PUT to an attachment updates the attachment. There is no entity body or request headers that contain this information. PUT to an attachment description wouldn’t seem to be appropriate because most of the other metadata is calculated from the attachment itself and shouldn’t be updated in a manner that would make the information inconsistent. 

This message was sent by Atlassian JIRA

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