[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (SRAMP-17) UUID Statements
[ http://tools.oasis-open.org/issues/browse/SRAMP-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28252#action_28252 ] Kurt Stam commented on SRAMP-17: --------------------------------- See http://www.atomenabled.org/developers/syndication/#requiredEntryElements where it says that the <id> element is a required element on the <entry> element. So I think we need to require the UUID to be supplied by the client. Here's a list of the required feed elements, each with a brief description, and an example. id Identifies the entry using a universally unique and permanent URI. Suggestions on how to make a good id can be found here. Two entries in a feed can have the same value for id if they represent the same entry at different points in time. <id>http://example.com/blog/1234</id> title Contains a human readable title for the entry. This value should not be blank. <title>Atom-Powered Robots Run Amok</title> updated Indicates the last time the entry was modified in a significant way. This value need not change after a typo is fixed, only after a substantial modification. Generally, different entries in a feed will have different updated timestamps. <updated>2003-12-13T18:30:02-05:00</updated> ----------------------------------------------------------------------------------------------------- See also : http://tools.ietf.org/html/rfc4287#section-4.1.2 o atom:entry elements MUST contain exactly one atom:id element o atom:entry elements MUST contain exactly one atom:title element. o atom:entry elements MUST contain exactly one atom:updated element. o atom:entry elements MUST contain one or more atom:author elements, unless the atom:entry contains an atom:source element that contains an atom:author element or, in an Atom Feed Document, the atom:feed element contains an atom:author element itself. o atom:entry elements MUST contain an atom:summary element in either of the following cases: * the atom:entry contains an atom:content that has a "src" attribute (and is thus empty). * the atom:entry contains content that is encoded in Base64; i.e., the "type" attribute of atom:content is a MIME media type [MIMEREG], but is not an XML media type [RFC3023], does not begin with "text/", and does not end with "/xml" or "+xml". > UUID Statements > --------------- > > Key: SRAMP-17 > URL: http://tools.oasis-open.org/issues/browse/SRAMP-17 > Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC > Issue Type: Improvement > Components: Atom Binding > Affects Versions: 1.0 > Environment: N/A > Reporter: Vincent Brunssen > Assignee: Kurt Stam > Fix For: 1.0 > > > Issue-017 from the contributed issues document > Clarification of UUID statement for atom:id in section 2.3.5.1 of Atom Doc. When doing a POST it states > If a UUID is not supplied, the server SHALL create one. This needs to be clarified with respect to atom:id > and possibly other required atom required properties. > This should be looked in to further. There is a possibility that we may have some inconsistencies with the > ATOM specs and we should verify that we have not missed any. -- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]