[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-cap-profiles] Definition of "Profile"
My $0.02: Outside of the CAP Canadian Profile, I have not yet found the term defined in a specification document or candidate specification document. Doesn't mean no one has done it, just that I haven't found it yet. The CAP/CP definition is minimal. I would only ask us to define "Profile" as part of our Terminology Section if there's a consensus that there is substantive reason to say: "As used in this document..." Otherwise, there's no need. Perhaps someday, someone will tackle it, but if we don't need to, in my opinion, we shouldn't. Cheers, Rex At 10:29 AM -0800 12/29/08, Art Botterell wrote: > >The RSS profile is a good example where there is no "subset" at all, >only an "interpretation" of the spec. > >Um... not sure which RSS profile you're talking about. In any event, I >think this is really just a difference of interpretation of the term >"subset." > >>To create a subset, some of the optional and potentially required >elements of the CAP spec would have to be dropped in the profile. > >All profile-compliant messages are valid CAP, but not all valid CAP is >profile-compliant. In that sense the profile defines a subset of the >universe of possible CAP messages. However, "interpretation" is also >within the working definition. Not sure what the practical issue is >here. > >- Art > > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. Follow this link to all your TCs in OASIS at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-898-0670
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]