This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
TWiki> Main Web>OslcCoreLinks? >OSLCCoreLinksISSUES (revision 2)
The Links Guidance has been completely rewritten, so earlier comments have been removed.

Points of agreement on links:

  • A link is expressed as a property-value (i.e. an RDF triple)

  • Domain specs are allowed to define resources and thus decide which resources link to which other resources

  • OSLC Core should define a common set of link properties for use across specifications

  • OSLC Core should define the notion of Relationship
    • A relationship has a name, e.g. the "implementation" relationship
    • A relationship can exist between any two resources
    • A relationship defines two link property names, one for each side of the relationship, e.g. "implements" and "implementedBy"
    • A relationship is said to exist between resource A and B if either resource uses the relationship's link property to point to the other

  • OSLC Core should define a way to model and express attributes of a relationship
    • Some way to associate property values with the relationship
Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 03 Jun 2010 - 12:35:34 - DaveJohnson
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback