[oslc-core] Requests for unknown or unsupported properties
spadgett at us.ibm.com
Tue Mar 27 14:10:02 EDT 2012
Thanks everyone for weighing in.
> It's a "subtle enough" consequence of existing normative text that I
> would generally support proposals for additions of clarifying
> *informative* text. I would have a harder time seeing the utility
> of adding normative text for this specific case (at  or ), but
> perhaps it has a place at .
> My reasoning:
>  and  both describe the semantics of the syntax in terms of
> what is to be included ("included" and "part of a member list
> pattern... to match", respectively), not in terms of what must be
> present. Including 0 things yields 0 things. The "match" word used
> in  makes this a bit clearer, admittedly.
I guess I still don't see where it's really said in either  or . Even
if it's implied, I'd argue it should be called out explicitly to avoid
confusion. I know at least one implementation returns errors in these
>  (Core) allows servers to discard unknown property values. One
> might quibble that it does not define "unknown" in this context with
> "hit reader over the head" obviousness, but it comes pretty darned
> close by saying "An OSLC Service MAY discard property values that
> are not part of the resource definition or Resource Shape known by
> the server. " in the very next sentence.
I read  to refer to creating or updating resources. If it applies to GET
requests as well, I propose we add clarifying text.
>  http://open-services.net/bin/view/Main/OslcCoreSpecification?
> > 
> > http://open-services.net/bin/view/Main/OslcCoreSpecification?
> >  http://open-services.net/bin/view/Main/OSLCCoreSpecQuery
Samuel Padgett | IBM Rational | spadgett at us.ibm.com
More information about the Oslc-Core