1.57 KB
Newer Older
oneM2Mdev's avatar
oneM2Mdev committed
1 2 3

PeterNiblett's avatar
PeterNiblett committed
4 5 6
This is a private repository for developing oneM2M xsd files

The default branch will initially contain a "0.80" version of the  files, mathching the 0.8 version of TS-0004
PeterNiblett's avatar
PeterNiblett committed
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

Further work / questions on the schemas is listed here. Many of these need CRs against TS-0004

    Look at the way that IDs are represented in the schemas


    Do we need to give explicit names to all the types currently defined in the file?  
    Should some or all of theses types go into CDT-CommonTypes or CDT-Enumerations?
    Since accessControlOperation is an enumerated integer type, we could represent accessControlOperationList as a   list of simple types. This would be shorter than having it as a complex type.
    Look at definition of accessControlOriginators


    What values go in latest and oldest if there are no child resources?
    Should <containerAnnc> be allowed to have <contentInstanceAnnc> as a child resource?

    Should the eventNotificationCriteria type be moved in to Common Types? (i.e. is it used anywhere else?

    Add or update definitions of the following types:
      resultContent, statusCode, requestStatus, attribute, notificationCongestionPolicy
    Does m2m:memberType need to be different from m2m:resourceType? Can we remove it?
    Sort out the two m2m:operation types
    Better name for listOfBoolean (it isn't a list)

    General revision and checking required (defer this until after the other XSD files are complete)