From e7bfbf012421760d10ac8bd19cc029f5345f212e Mon Sep 17 00:00:00 2001 From: PeterNiblett Date: Thu, 18 Dec 2014 22:12:18 +0000 Subject: [PATCH] Update README.md --- README.md | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/README.md b/README.md index 729fa9c..e846fc7 100644 --- a/README.md +++ b/README.md @@ -4,3 +4,40 @@ oneM2M-schemas 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 + +Further work / questions on the schemas is listed here. Many of these need CRs against TS-0004 + +General + 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 be allowed to have as a child resource? + +\ + + Should the eventNotificationCriteria type be moved in to Common Types? (i.e. is it used anywhere else? + +CDT-enumerationTypes + + 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) + +CDT-commonTypes + + General revision and checking required (defer this until after the other XSD files are complete) + + + + -- 2.18.1