[oslc-core] Topic for tomorrow's meeting: now to represent an Anchor in JSON

[Andrew J Berner]

Can the link itself get an identifier, so that the property can refer to
the the specific link?  Take the example of the subscription to Field and
Stream (we should use Horse and Hound instead, if you like Hugh Grant
movies)...what if the person has two subscriptions to the same magazine
with different expiration dates.  (Would you prefer licenses to products in
the Rational License Key Center for multiple statements with the same
subject, object, and predicate).  How is that "multiple statement" issue
handled?

I'm asking cause I believe that link properties is a VERY important
construct; it will be key in requirements management quite soon; we had a
good discussion in the RM workgroup this week.

Andy Berner
Lead Architect, ISV Technical Enablement and Strategy
IBM Rational Business Development
972 561-6599
ajberner at us.ibm.com

Ready for IBM Rational software partner program -
http://www.ibm.com/isv/rational/readyfor.html


|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Dave <snoopdave at gmail.com>                                                                                                                        |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |oslc-core <oslc-core at open-services.net>                                                                                                           |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |09/07/2010 04:35 PM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |[oslc-core] Topic for tomorrow's meeting: now to represent an     Anchor in JSON                                                                  |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |oslc-core-bounces at open-services.net                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





I didn't have an opportunity to reconvene the Link Guidance group to
re-visit the guidance on representing anchors in JSON, but I did take
another look at the JSON guidance myself and have a proposal for
changing the Representation Guidance to explain how to represent link
labels (i.e. Anchors).

   Link Guidance - has example of anchor in JSON
   http://open-services.net/bin/view/Main/OSLCCoreLinksDRAFT

   Representation Guidance - currently does not explain how to
represent an anchor
   http://open-services.net/bin/view/Main/OSLCCoreRepresentationsGuidance

In RDF/XML there is a long-form for representing link labels and it
involves the properties rdf:subject, rdf:object and rdf:predicate. We
also have a short form. I guess I don't see why the JSON
representation should take queues from either RDF/XML approach. We
already represent a link (i.e. value-type Resource with representation
Reference) as a JSON field with a JSON object value. The object has a
field 'rdf:resource' set to the URL of the link. To annotate a link in
JSON, you simply add the annotating property values to that JSON
object. That's what we currently show by example in the Link Guidance.

To bring the representation guidance in line, I believe all we need to
do is add this:

   1.3.2 If the resource reference is part of an Anchor (as described
in Link Guidance)
   and has annotating property values, then include these properties
within the JSON object.

I'd like to discuss this in the workgroup meeting tomorrow and if we
can't close on it, then we'll reconvene the Link Guidance sub-group as
we discussed last week and try to work out a solution.

Thanks,
Dave

_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net