John, The specs should be using oslc:Either for that value.
This type of problem is a result of us not having an online validation service for OSLC resources. Domain specs should create ResourceShape resources and validate them. Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM & Reporting Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: John Arwe <[email protected]> To: [email protected] Date: 03/22/2012 08:15 AM Subject: [oslc-core] Either Reference or Inline phrase Sent by: [email protected] In [1], Mike found (in response to a question from me) that a number of specs including core itself are using a value for Representation which strictly speaking is undefined. Should we ask wg leads to look at their specs and open issues against any currently engaging in this practice? As the community broadens, there will be a natural tendency for folks to copy-what-exists-then-tweak, so any unnecessary entropy the original has we can be sure will spread if not managed. [1] http://open-services.net/pipermail/oslc-automation_open-services.net/2012-March/000113.html Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario _______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
