Issue 7964: no specific mention of interoperability in DDS 04-04-12 standard proposal
Issue 7965: DDS: DCPS generated interface FooTypeSupport
Issue 7966: DDS: DCPS - define the term "plain data structures"
Issue 7974: 2.1.3.20 WRITER_DATA_LIFECYCLE, itemized list, first bullet
Issue 7975: DDS 04-04-12 para. 2.1.1.1 Format and conventions
Issue 7976: DDS 04-04-12 Appendix B, C
Issue 8354: Typographical and grammatical errors
Issue 8355: Spelling inconsistencies between the PIM and IDL PSM
Issue 8358: Operation DataWriter::register
Issue 8359: (T#4) Typo in section 2.1.2.4.2.10 (write) and section 2.1.2.4.12 (dispose)
Issue 8360: Typo in section 2.1.2.5.2.5
Issue 8361: Default value for READER_DATA_LIFECYCLE
Issue 8362: Incorrect reference to USER_DATA on TopicQos
Issue 8363: No mention of DESTINATION_ORDER on DataWriterQos
Issue 8364: Formal parameter name improvement in IDL
Issue 8365: Spell fully the names for the DataReader operations
Issue 8366: Missing operations on DomainParticipantFactory
Issue 8367: T#18,24,) Missing operations and attributes
Issue 8368: (T#28) Typographical and grammatical errors
Issue 8369: (T#29) Missing operations to Topic class
Issue 8370: Formal parameter name change in operations of ContentFilteredTopic
Issue 8371: (T#30) Ambiguous description of TOPIC_DATA
Issue 8372: Confusing description of behavior of Publisher::set_default_datawriter_qos
Issue 8373: (T#33) Clarification in use of set_listener operation
Issue 8374: Missing description of DomainParticipant::get_domain_id
Issue 8375: (T#41) Default value for RELIABILITY max_blocking_time
Issue 8376: (T#42) Behavior when condition is attached to WaitSet multiple times
Issue 8377: Explicit mention of static DomainParticipantFactory::get_instance operation
Issue 8378: (T#45) Clarification of syntax of char constants within query expressions
Issue 8379: (T#52) Allow to explicitly refer to the default QoS
Issue 8380: (T#54) Performance improvement to WaitSet
Issue 8381: (T#55) Modification to how enumeration values are indicated in expressions
Issue 8382: (T#56) Return values of Waitset::detach_condition
Issue 8383: (T#57) Enable status when creating DomainParticipant
Issue 8384: Add autopurge_disposed_samples_delay to READER_DATA_LIFECYCLE QoS
Issue 8388: (R#106b) Parameter passing convention of Subscriber::get_datareaders
Issue 8389: (R#107) Missing Topic operations in IDL PSM
Issue 8390: (R#109) Unused types in IDL
Issue 8391: Incorrect field name for USER_DATA, TOPIC_DATA, and GROUP_DATA
Issue 8392: R#112) Incorrect SampleRejectedStatusKind constants
Issue 8393: R#114) Operations should not return void
Issue 8394: R#115) Destination order missing from PublicationBuiltinTopicData
Issue 8395: TransportPriority QoS range does not specify high/low priority values
Issue 8396: (R#119) Need lookup_instance method on reader and writer
Issue 8397: (R#120) Clarify use of DATAREADER_QOS_USE_TOPIC_QOS
Issue 8398: (R#122) Missing QoS dependencies in table
Issue 8399: Need an extra return code: ILLEGAL_OPERATION
Issue 8417: (R#124) Clarification on the behavior of dispose
Issue 8418: (R#125) Additional operations that can return RETCODE_TIMEOUT
Issue 8419: (R#127) Improve PSM mapping of BuiltinTopicKey_t
Issue 8420: Unspecified behavior of DataReader/DataWriter creation w/t mismatched Topic
Issue 8421: (R#130) Unspecified behavior of delete_datareader with outstanding loans
Issue 8422: (R#131) Clarify behavior of get_status_changes
Issue 8423: Incorrect reference to LIVELINESS_CHANGED in DataWriter::unregister
Issue 8424: (R#135) Add fields to PublicationMatchStatus and SubscriptionMatchStatus
Issue 8425: (R#138) Add instance handle to LivelinessChangedStatus
Issue 8426: (R#139) Rename *MatchStatus to *MatchedStatus
Issue 8427: (R#142) OWNERSHIP QoS policy should concern DataWriter and DataReader
Issue 8428: (R#145,146) Inconsistent description of Topic module in PIM
Issue 8429: (R#147) Inconsistent error code list in description of TypeSupport::registe
Issue 8430: (R#152) Extraneous WaitSet::wakeup
Issue 8431: (R#153) Ambiguous SampleRejectedStatus::last_reason field
Issue 8432: (R#154) Undefined behavior if resume_publications is never called
Issue 8531: DTD Error (mainTopic
Issue 8532: get_all-topic_names operation missing on figure 3-4
Issue 8533: Naming inconsistencies (IDL PSM vs. PIM) for ObjectHome operations
Issue 8534: Naming inconsistencies (IDL PSM vs. PIM) for Cache operation
Issue 8535: Bad cardinality on figure 3-4
Issue 8536: ReadOnly exception on clone operations
Issue 8537: Wrong definition for FooListener
Issue 8538: Typo CacheUsage instead of CacheAccess
Issue 8539: templateDef explanation contains some mistakes
Issue 8540: DlrlOid instead of DLRLOid in implied IDL
Issue 8541: Parameter wrongly named "object" in implied IDL
Issue 8542: Attach_Listener and detach_listener operations on ObjectHome are untyped
Issue 8543: Remove operations badly put on implied classes
Issue 8545: Behavior of DataReaderListener::on_data_available
Issue 8546: Inconsistent naming for status parameters in DataReader operations.
Issue 8547: (T#23) Syntax of partition strings
Issue 8548: Clarification of order preservation on reliable data reception
Issue 8549: (T#37) Clarification on the value of LENGTH_UNLIMITED constant
Issue 8550: (T#38) request-offered behavior for LATENCY_BUDGET
Issue 8551: (T#46) History when DataWriter is deleted
Issue 8552: (T#47) Should a topic returned by lookup_topicdescription be deleted
Issue 8553: (T#51) Identification of the writer of a sample
Issue 8554: (T#53) Cannot set listener mask when creating an entity
Issue 8555: (T#53) Cannot set listener mask when creating an entity
Issue 8556: (T#59) Deletion of disabled entities
Issue 8557: (T#60) Asynchronous write
Issue 8558: (T#61) Restrictive Handle definition
Issue 8559: (T#62, R#141) Unspecified TOPIC semantics
Issue 8560: (T#65) Missing get_current_time() function
Issue 8561: Read or take next instance, and others with an illegal instance_handle
Issue 8562: (T#69) Notification of unsupported QoS policies
Issue 8567: O#7966) Confusing terminology: "plain data structures"
Issue 8568: (R#104) Inconsistent naming of QueryCondition::get_query_arguments
Issue 8569: (R#115b) Incorrect description of QoS for built-in readers
Issue 8570: (R#117) No way to access Participant and Topic built-in topic data
Issue 8571: (R#126) Correction to DataWriter blocking behavior
Issue 8572: Clarify meaning of LivelinessChangedStatus fields and LIVELINESS le
Issue 8573: (R#133) Clarify meaning of LivelinessLost and DeadlineMissed
Issue 8574: (R#136) Additional operations allowed on disabled entities
Issue 8575: (R#144) Default value for DataWriter RELIABILITY QoS
Issue 8576: (R#150) Ambiguous description of create_topic behavior
Issue 8577: R#178) Unclear behavior of coherent changes when communication interrupted
Issue 8578: R#179) Built-in DataReaders should have TRANSIENT_LOCAL durability
Issue 8579: R#180) Clarify which entities appear as instances to built-in readers
Issue 8580: (R#181) Clarify listener and mask behavior with respect to built-in entitie
Issue 8581: R#182) Clarify mapping of PIM 'out' to PSM 'inout'
Issue 8582: (T#6) Inconsistent name: StatusKindMask
Issue 8775: Page: 2-8
Issue 8892: subset of OMG IDL
Issue 9478: Inconsistencies between PIM and PSM in the prototype of get_qos() methods
Issue 9479: Inconsistent prototype for Publisher's get_default_datawriter_qos() method
Issue 9480: String sequence should be a parameter and not return value
Issue 9481: Mention of get_instance() operation on DomainParticipantFactory beingstatic
Issue 9482: Improper prototype for get_XXX_status()
Issue 9483: Inconsistent naming in SampleRejectedStatusKind
Issue 9484: OWNERSHIP_STRENGTH QoS is not a QoS on built-in Subscriber of DataReaders
Issue 9485: Consistency between RESOURCE_LIMITS QoS policies
Issue 9486: Blocking of write() call
Issue 9487: Clarify PARTITION QoS and its default value
Issue 9488: Typos in built-in topic table
Issue 9489: Naming of filter_parameters concerning ContentFilteredTopic
Issue 9490: Incorect prototype for FooDataWriter method register_instance_w_timestamp()
Issue 9491: Compatible versus consistency when talking about QosPolicy
Issue 9492: Incorrect mention of INCONSISTENT_POLICY status
Issue 9493: Typos in QoS sections
Issue 9494: Typos in PIM sections
Issue 9495: Clarify ownership with same-strength writers
Issue 9496: Should write() block when out of instance resources?
Issue 9497: Description of set_default_XXX_qos()
Issue 9498: Naming consistencies in match statuses
Issue 9499: delete_contained_entities() on the Subscriber
Issue 9500: Return of get_matched_XXX_data()
Issue 9501: Need INVALID_QOS_POLICY_ID
Issue 9502: Clarify valid handle when calling write()
Issue 9503: Operation dispose_w_timestamp() should be callable on unregistered instance
Issue 9504: Behavior of dispose with regards to DURABILITY QoS
Issue 9505: Typo in copy_from_topic_qos
Issue 9506: Order of parameters incorrect in PSM
Issue 9507: Typo in get_discovered_participant_data
Issue 9508: Operation wait() on a WaitSet should return TIMEOUT
Issue 9509: Example in 2.1.4.4.2 not quite correct
Issue 9510: Non intuitive constant names
Issue 9511: Corrections to Figure 2-19
Issue 9516: Simplify Relation Management
Issue 9517: Cache and CacheAccess should have a common parent
Issue 9518: Object notification in manual update mode required
Issue 9519: ObjectExtent and ObjectModifier can be removed
Issue 9520: Introduce the concept of cloning contracts consistently in specification
Issue 9521: Object State Transitions of Figure 3-5 and 3-6 should be corrected
Issue 9522: Add Iterators to Collection types
Issue 9523: Harmonize Collection definitions in PIM and PSM
Issue 9524: Add the Set as a supported Collection type
Issue 9525: Make the ObjectFilter and the ObjectQuery separate Selection Criterions
Issue 9526: Add a static initializer operation to the CacheFactory
Issue 9527: Make update rounds uninterruptable
Issue 9528: Remove lock/unlock due to overlap with updates_enabled
Issue 9529: Add Listener callbacks for changes in the update mode
Issue 9530: Representation of OID should be vendor specific
Issue 9531: define both the Topic name and the Topic type_name separately
Issue 9532: Merge find_object with find_object_in_access
Issue 9533: Clarify which Exceptions exist in DLRL and when to throw them
Issue 9534: Support sequences of primitive types in DLRL Objects
Issue 9535: manual mapping key-fields of registered objects may not be changed
Issue 9536: Specification does not state how to instantiate an ObjectHome
Issue 9537: Raise PreconditionNotMet when changing filter expression on registered Obje
Issue 9538: PIM description of "get_domain_id" method is missing
Issue 9539: PIM and PSM contradicting wrt "get_sample_lost_status" operation
Issue 9540: Small naming inconsistentcies between PIM and PSM
Issue 9541: Unlimited setting for Resource limits not clearly explained
Issue 9542: Inconsistent PIM/PSM for RETCODE_ILLEGAL_OPERATION
Issue 9543: Resetting of the statusflag during a listener callback
Issue 9544: Incorrect description of enable precondition
Issue 9545: invalid reference to delete_datareader
Issue 9546: Clarify the meaning of locally
Issue 9547: Invalid DURABILITY_SERVICE reference on the DataWriter
Issue 9548: Missing autopurge_disposed_sample_delay
Issue 9549: Illegal return value register_instance
Issue 9550: Typo in section 2.1.2.5.1
Issue 9551: Extended visibility of instance state changes
Issue 9552: Clarify notification of ownership change
Issue 9553: read/take_next_instance()
Issue 9554: instance resource can be reclaimed in READER_DATA_LIFECYCLE QoS section
Issue 9555: String sequence should be a parameter and not return value
Issue 9574: Need to clarify what is meant by "RELATED_OBJECTS"
Issue 9575: clarify allowable (spec compliant) ways to implement ObjectReference[].
Issue 9964: create_contentfilteredtopic Method Prototype and Description Out
Issue 10357: Section: 2.1.1.2.1
Issue 10358: Section: 2.1.2.2.1.9
Issue 10359: Section: 2.1.2.3.1
Issue 10360: Section: 2.1.2.3.2
Issue 10361: Section: 2.1.2.3.6.1
Issue 10362: Section: 2.1.2.5.1.3
Issue 10363: Section: 2.1.2.5.3
Issue 10364: Section: 2.1.2.5.3.8
Issue 10365: Section: 2.1.2.5.3.9
Issue 10366: Section: 2.1.3
Issue 10367: Section: 2.1.3.5
Issue 10368: Section: 2.1.3.14
Issue 10369: Section: 2.1.3.18
Issue 10370: Section: 3.1.4.5
Issue 10542: PIM Spec should have separate tables for Foo types, like DCPS section does
Issue 10543: DLRL Issue: Diagrams in Fig 3.5 and Fig 3.6 look improperly captioned
Issue 10544: Request clarification on a WRITE_ONLY CacheAccess, cloning, and refresh()
Issue 10545: DLRL Issue: Need clarification on limitations of bi-directional association
Issue 10546: Request clarification of how to handle a dangling related object
Issue 10547: DLRL Issue: Int the future, allow DLRL valuetype implementations?
Issue 10548: DLRL Issue: Request clarification on the behavior of is_modified
Issue 10549: Should "set" method called outside of writable CacheAccess throw exception?
Issue 10550: DLRL Issue: Error in the ownership of a SelectionCriterion
Issue 10551: DLRL Issue: Error in the IDL for the SelectionListener
Issue 10552: IDL interfaces for ObjectListener and FooListener are inconsistent
Issue 10553: Request clarification: what can you do with a deleted object?
Issue 10554: Request clarification on interface of DLRL object with multi-attribute
Issue 10555: Can a CacheAccess::refresh() throw an AlreadyClonedInWriteMode exception?
Issue 10556: DLRL Issue: Mismatch between DLRL and CORBA on enumerations
Issue 10557: Proposed Enhancement: allow QoS directly on a DLRL object type?
Issue 10581: Section: 2.2.3
Issue 10661: Unclarities in section 3.1.4.2.3
Issue 10662: Unclarities in table in section 3.1.6.2 the row regarding the CacheAccess
Issue 10663: Clarify usage of create_cache operation
Issue 10664: Clarify usage of refresh operation on the CacheBase, section 3.1.6.3.2
Issue 10665: Clarify usage of cache_usage operation on the CacheBase, section 3.1.6.3.2
Issue 10666: Which exceptions can be raised under which circumstances?
Issue 10667: Clarify what happens in the purge operation of the CacheAccess
Issue 10668: Rewrite sentence on page 3-1, section 3.1
Issue 10669: Clarify exception condition
Issue 10670: Clarify usage of find_home_by_name
Issue 10671: Clarify exceptions with operation register_all_for_pubsub
Issue 10672: Clarify various things with operation enable_all_for_pubsub
Issue 10673: Clarify exceptions for enable_updates and disable_updates operations of Cac
Issue 10674: In section 3.1.6.3.5 regarding the CacheListener clarify some things
Issue 10675: In section 3.1.6.3.6 regarding the Contract clarify some things
Issue 10676: In section 3.1.6.3.7 regarding the ObjectHome clarify some things
Issue 10677: In section 3.1.6.3.11 regarding the FilterCriterion clarify some things
Issue 10678: getter/setter/is_modified operations
Issue 10679: Clarify usage of the destroy() operation on the ObjectRoot
Issue 10680: Clarify usage of the is_modified() operation on the ObjectRoot
Issue 10681: Description not detailed enough
Issue 10682: Clarify text on page 3-35 directly following the operation descriptions.
Issue 10683: Clarify exceptions for add/put operations on List in section 3.1.6.3.16
Issue 10684: Clarify exceptions
Issue 10685: Clarify listeners
Issue 10686: (last) end_updates call on CacheListeners
Issue 10687: Clarify typical scenario for read mode of a CacheAccess in section 3.1.6.5.
Issue 10688: Clarify typical scenario for write mode of CacheAccess in section 3.1.6.5.2
Issue 10689: Clarify what happens with selection->refresh if auto_refresh is true The Implied IDL needs to be extended with attribute examples for class Foo
Issue 10690: The Implied IDL needs to be extended with attribute examples for class Foo
Issue 10691: The generated class FooImpl is not mentioned in the implied idl
Issue 10692: Usage of Undefined unclear
Issue 10693: Clarify exceptions/usage for remove operation on List in section 3.1.6.3.16
Issue 10694: Clarify usage of Fully qualified names in the model tags in section 3.2.2.3
Issue 10695: Section 3.1.3.1 on page 3-3
Issue 10696: Unclear sentence in section 3.1.6.1.1
Issue 10697: Section 3.2.1.2.1 Generic DLRL Entities get_instance
Issue 10698: The read_state of a cache object contains some typos
Issue 10699: Clearly separate default mapping from pre-defined mapping
Issue 10700: Cache
Issue 10701: non-existing elements
Issue 10702: Unregistered objects
Issue 10703: Describe exact event propagation in case of inheritance + multiple listener
Issue 10704: samples from the underlying DataReaders
Issue 10705: Change description on mapping rules for Exceptions or return values
Issue 10706: Add exceptions, clarify usage of other exceptions
Issue 10707: DCPSError also becomes a 'runtime' exception
Issue 10717: Remove the CacheDescription object
Issue 10718: Add attribute to CacheAccess (section 3.1.6.3.3)
Issue 10719: Add an attribute to get the home_index
Issue 10720: Relationships to objects that have been deleted are not allowed.
Issue 10721: getters of relationships
Issue 10722: Prevent writing contents of CacheAccess while 'invalid' relations exists
Issue 10723: Let the attach/detach listener operation return a boolean
Issue 10724: set_query and set_parameters operation
Issue 10725: Introduce the clear() operation on the Collection interface.
Issue 10726: Support local class in Mapping XML
Issue 10727: Enable_all_for_pubsub operation
Issue 10728: set_auto_deref, deref_all, underef_all operations
Issue 10729: Cache should have a getter to obtain its related DomainParticipant.
Issue 10732: Proposal to make the is_xxx_modified operation optional
Issue 10733: The classname in FullOid makes no sense in case of a 'local' Object model
Issue 10734: Add an operation to the Cache
Issue 10735: Selection should have a non-listener way of obtaining the members
Issue 10736: FilterCriterion
Issue 10737: How are deleted objects treated in a CacheBase and a Selection
Issue 10738: objects instances in a writeable CacheAccess
Issue 10739: Describe exact behaviour of compositions and associations in the DLRL.
Issue 10740: DLRL object
Issue 10741: There is a lot of redundancy in the XML file.
Issue 10742: Indicate the semantics of merging separate topics into one single object
Issue 10743: instance_state of a DCPS instance becomes NOT_ALIVE_NO_WRITERS
Issue 10744: Extend the XML to allow optional relationships
Issue 10745: cloned objects
Issue 10746: Minor typo's and inconsistencies
Issue 10747: Typo in section 3.1.4.2.1
Issue 10748: Typo in section 3.1.6.1.2.1
Issue 10749: Various typos in section 3.1.6.3.4, Cache
Issue 10750: Various typos in section 3.1.6.3.7, ObjectHome
Issue 10751: which_contained_modified operation should be removed
Issue 10752: Typos in section 3.1.6.4.1
Issue 10753: Typos in section 3.1.6.4.3 & 3.1.6.4.4 Typos in section 3.1.6.6
Issue 10754: Typos in section 3.1.6.6
Issue 10755: Typos in section 3.2.1.2 IDL description
Issue 10756: Typos in section 3.2.1.2 IDL description
Issue 10757: section 3.2.1.2 IDL description on page 3-52
Issue 10758: section 3.2.1.2.2 Implied IDL
Issue 10759: In section 3.2.2.3.2.11 MultiAttribute.
Issue 10760: In section 3.2.2.3.2.11 MultiAttribute, the example xml code
Issue 10761: section 3.2.2.3.2.13 MultiRelation, 3rd bullet
Issue 10762: section 3.2.2.3.2.10 MonoAttribute, 3.2.2.3.2.12 MonoRelation
Issue 10763: In section 3.2.3.5 Code example, several typos
Issue 10764: Figure 3-4 and section 3.2.1.2.2 Implied IDL
Issue 10765: section 3.2.2.3.2.13 MultiRelation - XML code
Issue 10766: Section 3.2.1.1 Mapping Rules regarding error reporting
Issue 10768: Inconsistency in attribute definitions for valuetype ObjectRoot
Issue 10769: Figure 3-4 on page 3-16 is missing some operations in some classes
Issue 10770: use case for multiple valueFields
Issue 10771: Give each CacheAccess its own Publisher and DataWriters
Issue 10804: A descriptive name
Issue 10805: DataReader semantics for historical data are insufficient
Issue 10806: Invalid DURABILITY_SERVICE reference on the DataWriter
Issue 10807: Add name attribute to Entity
Issue 10808: Semantics instance liveliness and ownership unclear
Issue 10809: Missing TypeSupport operations
Issue 10810: Inconsistent lookup semantics
Issue 10811: Default built-in ReaderDataLifecycle values
Issue 10812: Cancel transaction
Issue 10813: Get entity enabled state
Issue 10980: Section: 2.1.2.5.2
Issue 10993: DDS DCPS Issue: PRESENTATION=GROUP and QoS
Issue 10994: Specify names of mono-relation and multi-relation fields for default mappin
Issue 10995: DDS DLRL Issue: Clarification on the use of a Set in a DLRL Query
Issue 10996: create_object and create_unregistered_object
Issue 10997: clarify behavior of content_filters in an inheritance hierarchy
Issue 10998: DDS DLRL Issue: Clarify behavior of a Composition
Issue 12212: DDS typos and omissions
Issue 12276: DURABILITYSERVICE_POLICY_NAME
Issue 12360: Specify the allowed IDL Types within DDS Topic structs
Issue 12465: 'synchrobnous' and 'asynchronous' switched
Issue 12539: Deprecated usage of IDL in the DDS spec
Issue 7964: no specific mention of interoperability in DDS 04-04-12 standard proposal (data-distribution-rtf)
Click here for this issue's archive.
Source: EADS (Mr. Oliver M. Kellogg, oliver.kellogg@eads.com Oliver.Kellogg@t-online.de)
Nature: Uncategorized Issue
Severity:
Summary:
I find no specific mention of interoperability in the DDS 04-04-12 standard proposal. It should be clarified whether the standard is intended to address interoperability, and if so, under what exact conditions (e.g., is it safe to assume that if the DCPS IDL PSM is implemented by IIOP based CORBA ORBs then it will be possible to interoperate?)
RTF Comments: The DDS specification addresses only inter-vendor portability. The specification defines the API and behavior. There is an on-going effort at OMG to address interoperability. In the meantime implementations could be built on top of IIOP. However, given that the DDS Entities are intended to be local communication endpoints and not and not references to the use of IIOP would not be sufficient to achieve interoperability as it IIOP does not address how to represent the QoS, discovery information, and other behaviors necessary to implement DDS. In addition the DDS specification was designed to be implementable on top of connectionless unreliable protocols such as IP multicast and IIOP does not offer direct facilities to do that.
Nature: Enhancement
Summary:
Document 04-04-12 para. 2.2.3 near end
In the implied IDL interface FooTypeSupport for a user type Foo,
there is an operation
DDS::ReturnCode_t register_type(in DDS::DomainParticipant
participant,
in string type_name);
IMHO the type_name argument is superfluous:
The generated stub code can fill it in automatically ("Foo").
RTF Comments: The type name is not superfluous; see section 2.1.2.3.6.1. In some applications, it may be desirable to register the same physical type multiple times (with different participants or the same participant) under different names. However, given that different Topics can already be created that use the same type, and given that typdefs can be used to create new type names. A good argument could be made that there is limited use for the added functionality provided by the type-name parameter. A use case could perhaps be used to clarify the need. As a compromise, the standard could be changed to state that a nil type name is permissible, in which case the default name will be used. Alternatively, the FooTypeSupport class could get an additional method get_type_name() that returns the default type name.
OMG document 04-04-12 para. 2.1.1.2.2 Overall Conceptual Model pg. 2-7 states: At the DCPS level, data types represent information that is sent atomically. For performance reasons, only plain data structures are handled by this level. Please define the term "plain data structures".
* The setting 'autodispose_unregistered_instances = FALSE' causes the
DataWriter [...]
Change FALSE to TRUE.
The table format used for documenting classes contains an "attributes" and an "operations" section. However, in order for applications to be portable across implementations of the DDS spec, it would be desirable to add a "constructors" section that explicitly states those constructors that take one or more arguments (i.e. non-default constructors.)
Filters and Queries are not compile-time checked and are too heavy The 04-04-12 DDS document proposes a subset of SQL for defining filters andqueries. The filter/query expressions are passed into the corresponding methods as type "string". First, this means that conforming implementations need to provide an SQL expression parser/evaluator - a fairly complex piece of software. Second, since the expressions are given as strings, checking them at compile time is not straight-forward. We request the Revision Task Force to reconsider this design decision in favor of less heavyweight approaches that allow for compile-time checks.
RTF Comments: The DDS RTF agrees in principle that it would be a good idea. However we were not able to come up with a suitable proposal that addresses the need for doing the content-filter also at the DataWriter side. Therefore the DDS RTF is recommending this issue is postponed to a future RTF where more implementation experience may be available to suggest the best approach. Resolution: No change to the specification.
The specification contains a number of misspellings and other minor typographical and grammatical errors.
The typographical and grammatical errors shall be corrected.
Revised Text:
Location Original Incorrect Text Corrected Text
2.1.2, fig. 2-4 "Topic Module" "Topic-Definition Module"
2.1.2.2.2 create_participant parameter "domainId" create_participant parameter "domain_id"
2.1.2.2.2 lookup_participant parameter "domainId" lookup_participant parameter "domain_id"
2.1.2.2.2.1 "domainId" "domain_id"
2.1.2.2.2.4 "domainId" (two occurrences) "domain_id" (two occurrences)
2.1.2.3.7, pg. 2-39 "…for a hypothetical application named "Foo"…" "…for a hypothetical application data type named "Foo"…"
2.1.2.4.1.15 "…get_default_datawriter_qos will match the set of valuesspecified on the last successful call to get_default_datawriter_qos…" "…get_default_datawriter_qos will match the set of valuesspecified on the last successful call to set_default_datawriter_qos…"
2.1.2.5, fig. 2-10 SampleInfo attribute "instance_rank" SampleInfo attribute "sample_rank"
2.1.2.5.1, fig. 2-11 transition from NO_WRITERS to ALIVE "…=++" transition from NO_WRITERS to ALIVE "…++"
2.1.2.5.1, pg. 2-57 "time-stamp" "timestamp"
2.1.2.5.1, pg. 2-59, 2nd to last para. "…snapshot of view_state…" "…snapshot of the view_state…"
2.1.2.5.1, pg. 2-61, 4th para. "…multiple DataReader." "…multiple DataReaders."
2.1.2.5.1, pg. 2-61, list item (1) "…list of DataReader…" (two occurrences) "…list of DataReaders…" (two occurrences)
2.1.2.5.1, pg. 2-61 "…acrossDataWriter entities." (two occurrences) "…acrossDataReader entities." (two occurrences)
2.1.2.5.2.7 "…multiple DataReader…" "…multiple DataReaders…"
2.1.3, pg. 2-92 "…ability to: specify and receive coherent changes see the relative order of changes." "…ability to specify and receive coherent changes and to see the relative order of changes."
2.1.3, pg. 2-98 "time-stamp" "timestamp"
2.1.3, pg. 2-101, autopurge_ nowriter_ samples_ delay row "…information regarding instances that have the view_state NOT_ALIVE_NO_WRITERS." "…information regarding instances that have the instance_state NOT_ALIVE_NO_WRITERS."
2.1.3.6 "TIME_BASED_PERIOD" "TIME_BASED_FILTER"
2.1.3.17 last para. "compatible" (two occurrences) "consistent" (two occurrences)
2.1.3.18 last para. "compatible" (two occurrences) "consistent" (two occurrences)
2.1.3.20 itemized list, first bullet "The setting 'autodispose_unregistered_ instances = FALSE' causes the DataWriter…" "The setting 'autodispose_unregistered_ instances = TRUE' causes the DataWriter…"
2.1.3.21, para. 4 "… view_state = NOT_ALIVE_NO_WRITERS…" "… instance_state = NOT_ALIVE_NO_WRITERS…"
2.1.4.1 Requested-Incom-patible-Qos-Status:: total_count row "Total cumulative count the concerned DataReader discovered a DataWriter…" "Total cumulative number of times the concerned DataReader discovered a DataWriter…"
2.1.4.4, before fig. 2-19 Reference to figure 2-18 Reference to figure 2-19
2.1.5 para. 3 "get_datareader" "lookup_datareader"
2.2.3 const long DURATION_INFINITY_SEC = 0x7ffffff;const unsigned long DURATION_INFINITY_NSEC = 0x7ffffff; const long DURATION_INFINITY_SEC = 0x7fffffff;const unsigned long DURATION_INFINITY_NSEC = 0x7fffffff;
2.2.3 interface DomainParticipantFactory { DomainParticipant create_participant( in DomainId_t domainId, in DomainParticipantQos qos, in DomainParticipantListener a_listener); … DomainParticipant lookup_participant( in DomainId_t domainId); … interface DomainParticipantFactory { DomainParticipant create_participant( in DomainId_t domain_id, in DomainParticipantQos qos, in DomainParticipantListener a_listener); … DomainParticipant lookup_participant( in DomainId_t domain_id); …
In a number of instances, there are minor inconsistencies in spelling and naming between the specification's platform-independent model (PIM) and the included IDL platform-specific model (PSM). Resolution: In each case, the most descriptive term of the two options was chosen and the other was conformed to it.
The method DataWriter::register conflicts with the C++ 'register' keyword. Resolution: Replace register and unregister by register_instance and unregister_instance Replace register_w_timestamp and unregister_w_timestamp by register_instance_w_timestamp and unregister_instance_w_timestamp
Since the revisions are straightforward, here only the figures,tables and paragraphs are indicated which are affected by the above indicated change. - update figures 2-8, 2-9, accordingly - update tables in paragraph 2.1.2.4.2 accordingly - update text in paragraphs 2.1.2.4.2.5/6/7/8, 2.1.3.20 and 2.1.3.22.3 accordingly - update IDL in paragraph 2.2.3 accordingly
Summary: In par. 2.1.2.4.2.10 (write) and par. 2.1.2.4.12 (dispose) the specification does not specify an error code in case the specified handle is valid but does not correspond to the given instance (the key value must match), and neither for the case that the specified handle is invalid. Resolution: Specify that in general, the result is unspecified, but that depending on vendor-specific implementations, the resulting error-code is 'PRECONDITION_NOT_MET' if a wrong instance (i.e. with a wrong key-value) is provided and that the resulting error-code is 'BAD_PARAMETER' if a bad handle is provided Revised Text: Add the following text to the end of 2.1.2.4.2.10 (write) In case the provided handle is valid but does not correspond to the given instance, the resulting error-code of the operation will be 'PRECONDITION_NOT_MET'. In case the handle is invalid, the behavior is in general unspecified, but if detectable by a DDS-implementation, the returned error-code will be 'BAD_PARAMETER'. Replace in 2.1.2.4.2.12 (dispose), the text "Possible error codes returned in addition to the standard ones: PRECONDITION_NOT_MET" by the following text: In case the provided handle is valid but does not correspond to the given instance, the resulting error-code of the operation will be 'PRECONDITION_NOT_MET'. In case the handle is invalid, the behavior is in general unspecified, but if detectable by a DDS-implementation, the returned error-code will be 'BAD_PARAMETER'.
In section 2.1.2.5.2.5. (create_datareader) the special value DATAWRITER_QOS_USE_TOPIC_QOS is mistakenly being used instead of DATAREADER_QOS_USE_TOPIC_QOS. Resolution: Replace the wrong text with the correct version. Revised Text: In 2.1.2.5.2.5 (create-datareader) replace the text "The special value DATAWRITER_QOS_USE_TOPIC_QOS" with "The special value "DATAREADER_QOS_USE_TOPIC_QOS
Section 2.1.3. (Supported QoS) the default value of the duration attribute of the READER_DATA_LIFECYCLE QoS is specified as "unlimited".. Resolution: Replace "unlimited" by "infinite", which in general is used in relation with durations. Revised Text: In the QoS-table of paragraph 2.1.3, replace the text "By default, unlimited" as belongs to the READER_DATA_LIFECYCLE QoS by the text "By default, infinite".
The table in section 2.1.3. (Supported QoS) wrongful specifies that USER_DATA concerns Topic. Resolution: 'Topic' should be removed from the 'concerns' column. Revised Text: In the table in section 2.1.3 (Supported QoS), remove from the "USER-DATA" row, and from the "Concerns" column, the word 'Topic'.
In the table in section 2.1.3. (Supported QoS) the DESTINATION_ORDER QoS does not mention the 'datawriter' as concerned entity. Resolution: Add DataWriter to the 'concerns' column. Revised Text: In the table in section 2.1.3 (Supported QoS), add to the "DESTINATION_ORDER" column and the "Concerns" row, the word 'DataWriter'.
In the IDL specification of section 2.2.3, the first parameter of the 'register_type' method is called 'domain' instead of 'participant' (as it is called elsewhere, like in the table of secion 2.1.2.3.6. Resolution: Change the parameter name to 'participant' in the typesupport::register_type IDL. Revised Text: In Chapter 2.2.3 (IDL specification), change the register_type parameter called 'domain' into 'participant'.
In some class diagrams, generic operations are indicated using '_xxx_' in their names instead of fully specifying all the real operations and also some operations are missing. Resolution: - add the missing operations for the dataReader - explicitly mention all operations for the dataReader Revised Text: In the class diagram Fig. 2-8 on page 2-39: - add missing operations "read_w_condition", "take_w_condition" and "return_loan". - rename "read_xxx_w_conditon" into "read_next_w_condition". - rename "take_xxx_w_condition" into "take_next_w_condition"
The class DomainParticipantFactory in figure 2-6 section 2.1.2.2. (Domai