W3C home > Mailing lists > Public > public-wai-ert@w3.org > May 2009

Status update RE: Pointer Method in RDF comments summary

From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
Date: Tue, 12 May 2009 13:02:26 +0200
Message-ID: <09700B613C4DD84FA9F2FEA52188281905E5AA3C@ayalga.fundacionctic.org>
To: "Carlos Iglesias" <carlos.iglesias@fundacionctic.org>, <public-wai-ert@w3.org>

See comments below

> -----Mensaje original-----
> De: public-wai-ert-request@w3.org 
> [mailto:public-wai-ert-request@w3.org] En nombre de Carlos Iglesias
> Enviado el: miércoles, 22 de abril de 2009 13:06
> Para: public-wai-ert@w3.org
> Asunto: Pointer Method in RDF comments summary
> Hi group,
> There are some comments on the pointers document ([1], [2], 
> [3]) we need to resolve:
> - Usage of ptr:XMLNamespace may violate the reserved string 
> convention for XML specification [4]
> That means we need to find out another name for this. The 
> previous candidate was ptr:Namespace, but maybe it is not the 
> best option, as we are talking about XML Namespaces, not 
> namespacing in general. Any other proposal?

We can also choose among any of the following:

- NamespaceInXML
- NamespaceXML
- EksEmElNamespace

I think we can also dismiss the last one :o) any other proposal?

> Note, that this issue may also affect to other of our 
> documents (e.g. Representing Content in RDF)
> - Usage of text-oriented Pointers with XML Infosets
> Not sure about this being a big issue. Maybe it's not a best 
> practice, but you may want to treat XML as plain text for 
> certain things. This is somewhat related with our "Usage of 
> Pointers" idea, maybe an explaining note may suffice.

We can and a note like this in the introduction section:

"Note that some pointers may be more appropriated to operate on the character or byte serialization of the resources and others for structured documents, such as XML documents, where character or byte based pointing mechanisms may be considered a bad practice"

Do you think that this may suffice?

> - Usage of ABSTRACT and Generic classes in examples
> We may want to remove the examples, as we discourage its use.


> - Add a note to previous definition of #lineCharPointer and 
> #charOffsetPointer in example 2.14
> May be good to add a simple reference in the example title.

Currently "A StartEndPointer resource making use of the previous examples of LineCharPointer and CharOffsetPointer."
Is this enough?

> - Usage of rdf:resource in examples instead being more detailed
> Don't think we should be so detailed in every example, but we 
> may want to add a more complete final example or just make 
> reference to the Guide.

Need to make a decision on this

> - Use of XPointerPointer naming convention
> We are in fact representing a pointing method that makes use 
> of XPointers, not XPointers themselves (for example there is 
> not "reference" concept in XPointers), so we shouldn't use 
> just the XPointer name.
> Don't think it's a big issue, may sound a bit weird, but I 
> think it's better not to break our conventions. Nevertheless, 
> we may change to other convention like XPointerPM (Pointer 
> Method) or anything like that.
> Nothing else so far, apart from a couple of minor typos.


> [1] - 
> [http://lists.w3.org/Archives/Public/public-wai-ert/2009Mar/0024.html]
> [2] - 
> [http://lists.w3.org/Archives/Public/public-wai-ert/2009Mar/0027.html]
> [3] - 
> [http://lists.w3.org/Archives/Public/public-wai-ert/2009Apr/0020.html]
> [4] - [http://www.w3.org/TR/xml/#dt-name]



Carlos Iglesias

Fundación CTIC
Parque Científico-Tecnológico de Gijón
33203 - Gijón, Asturias, España
teléfono: +34 984291212
email: carlos.iglesias@fundacionctic.org
URL: http://www.fundacionctic.org  
Received on Tuesday, 12 May 2009 11:03:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:58 UTC