[oslc-core] PREFIX dc: <http://purl.org/dc/elements/1.1/>

[James Conallen]

<rant more="true">

Firstly I agree with Arthur.  But my rant is that we are even pre-defining
prefixes to begin with!

Defintion: " The Prefix provides the namespace prefix part of the qualified
name, and MUST be associated with a namespace URI reference in a namespace
declaration."

We are changing the rules and saying that the prefix doesn't have to be
associated with a namespace in a declaration, mostly to save space.  In the
query spec we have a means to express the prefix (oslc.prefix), and of
course prefixes can be set in our RDF/XML using the proper mechanisms.

Not that I think I will get much traction here, but I think we should not
be pre-defining prefixes (and thus avoiding issues like this one in the
future), and sticking with the proper mechinisms for these things.

</rant>

<jim/>

jim conallen
jconallen at us.ibm.com
Rational Software, IBM Software Group




|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Arthur Ryman <ryman at ca.ibm.com>                                                                                                                   |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |oslc-core at open-services.net                                                                                                                       |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |06/05/2010 10:35 AM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |[oslc-core] PREFIX dc: <http://purl.org/dc/elements/1.1/>                                                                                         |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |oslc-core-bounces at open-services.net                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





<rant>

As I read more and more external specs, I see a very clear convention for
the meaning the prefix dc:. The conventional use is for the elements
namespace, not the terms namespace. dcterms: is used for the terms
namespace.

I have heard it asserted that if we align with the conventional use, then
we might somehow break existing clients, but I haven't see any actual
examples. I believe that it is better in the long term for  OSLC to align
with the norms of the larger Web community. We should therefore not
diverge on the grounds of being "bug compatible" with some early
implementations. Let's examine the real breakage, if any, and gracefully
deprecate the old usage. Going forward, new specs should align with the
convention.

</rant>

Regards,
___________________________________________________________________________


Arthur Ryman, PhD, DE


Chief Architect, Project and Portfolio Management

IBM Software, Rational

Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063
Twitter | Facebook | YouTube





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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100607/22a0a4f3/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100607/22a0a4f3/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20100607/22a0a4f3/attachment-0001.gif>