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.

Architectural Direction

In-progress Working document - supporting specification development for the next version of PM. This is not an official list of committed items but a live working document to help prioritize and elaborate on the specification efforts.

The purpose of this page is to collect the architectural direction as driven by scenario priorities for the next version of PM specifications (V1). It also contains any issues left unaddressed in previous version(s), if any.

Items for Consideration for 2.0

Themes

  • Low entry point

Others to consider:

  • Specific examples are intended to be exemplary, not limiting. The assumption is, that unless something is specifically excluded in normative text (MUST NOT), it is "possible". The intent is to allow a broad range of alternative implementations and implementation decisions.
  • Re-use existing material when possible, rather than defining new, especially vocabularies widely used in the global RDF community, like Dublin Core.
  • Enable whatever is defined-new here for wide re-use by other specifications, for potentially unforeseen scenarios.
  • Avoid using reification, even though it is allowed by Core 2.0 Appendix C

Item Details

UNDER DEVELOPMENT (See the specification backlog)

Supporting References

  • Specification backlog

-- JohnArwe - 30 Apr 2012

Edit | Attach | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 08 May 2012 - 16:45:28 - JohnArwe
 
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