[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] Question about SituationCategory in MUWS part 2
Kirk, I had forgotten that we defined SituationCategoryType - I am glad you mentioned it. This means that the GEDs that need to be defined are similar to the following: <xs:element name="OtherSituation" type="muws-p2-xs:SituationCategoryType"/> Now the confusing part comes in when you are using these values in a Situation. Here is a fragment of a situation instance: <muws-p2-xs:Situation> ... <muws-p2-xs:SituationCategory> <muws-p2-xs:OtherSituation/> </muws-p2-xs:SituationCategory> ... </muws-p2-xs:Situation> Now if you had a sub-category, you might specify it as follows: <muws-p2-xs:SituationCategory> <muws-p2-xs:OtherSituation> <ex:MySpecialOtherSituation/> </muws-p2-xs:OtherSituation> </muws-p2-xs:SituationCategory> This assumes that you defined a GED for MySpecialOtherSituation inside the schema for the namespace represented by the prefix "ex". Something we may want to consider changing is that CategoryType, which SituationCategoryType is a restriction of, allows 0 or more child elements. The SituationCategory element in Situation really should require a single child element. So, we may want to define a type for the SituationCategory that reflects this requirement. Also, CategoryType allows child elements of any type. We could restrict this to child elements of CategoryType. Since CategoryType is used in a number of places we need to be careful that we are not being overly restrictive for any of the use cases. Bryan -----Original Message----- From: Wilson, Kirk D [mailto:Kirk.Wilson@ca.com] Sent: Wednesday, July 20, 2005 11:34 AM To: Murray, Bryan P.; Hiroyuki Masuda; wsdm@lists.oasis-open.org Cc: takagi.ryuichi@jp.fujitsu.com Subject: RE: [wsdm] Question about SituationCategory in MUWS part 2 Bryan, Hiroyuki, all, IMHO, the spec doesn't explain how to construct these taxonomies very well (and perhaps the spec shouldn't), but I think it would be helpful to have a discussion in the Primer that goes into more detail. After struggling to figure out how this is done during some of my own writing of the Primer, here's what I believe is the appropriate way of defining each of the SituationCategories (I don't believe there are any child relationship between these categories, which makes their definitions a bit easier--they would follow the same pattern): <xs:element name="SituationCategoryDef" type="muws-p2:SituationCategoryType"/> <xs:element name="XXXSituation"> <xs:complexType> <xs:complexContent> <xs:restriction base="SituationCategoryDef " /> </xs:complexContent> </xs:complexType> </xs:element> NOTE that SituationCategory is already defined in MUWS-P2 as a child element of SituationType; thus, I believe I need a different name for the GED for defining the Situation Categories. Recognizing hierarchical relationships between the elements your are defining becomes a little tricker. Compare the definition of OperationStates in MOWS.) Kirk Wilson Architect, Development Office of the CTO 802 765-4337 -----Original Message----- From: Murray, Bryan P. [mailto:bryan.murray@hp.com] Sent: Wednesday, July 20, 2005 1:13 PM To: Hiroyuki Masuda; wsdm@lists.oasis-open.org Cc: takagi.ryuichi@jp.fujitsu.com Subject: RE: [wsdm] Question about SituationCategory in MUWS part 2 You are correct - the MUWS part2 schema should have definitions for these elements. This was an oversight when the schema was written this last spring. When we create a new version of MUWS after WS-ResourceProperties, WS-BaseNotification are OASIS standards, we need to add definitions for these global elements. If I remember right, the definition will be similar to the following: <xs:element name="OtherSituation" type="muws-p2-xs:CategoryType"/> This allows the situations to have sub-categories if necessary or desired. Bryan -----Original Message----- From: Hiroyuki Masuda [mailto:masuda@soft.fujitsu.com] Sent: Tuesday, July 19, 2005 11:59 PM To: wsdm@lists.oasis-open.org Cc: takagi.ryuichi@jp.fujitsu.com Subject: [wsdm] Question about SituationCategory in MUWS part 2 Hi WSDM-TC members, My name is Hiroyuki Masuda. I'm "observer" member of WSDM-TC. I have one question about SituationCategory in MUWS part 2. The following SituationCategory value is introduced at "2.5.1 Event Format" in MUWS part 2. ------------------------------------------- AvailabilitySituation CapabilitySituation ConfigureSituation StopSituation StartSituation RequestSituation DestroySituation CreateSituation DependencySituation ConnectSituation ReportSituation OtherSituation ------------------------------------------- I can not find any definition for the above value in "Appendix C. Schemas" of MUWS part 2. I think the definition for the above value should exist in schema. Am I wrong ? Regards, -- Hiroyuki Masuda E-Mail:masuda@soft.fujitsu.com --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]