encoded, I think, hex has more compact
representation and is used in ABNF spec itself.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Europe GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message
From: Frederick Hirsch [frederick.hir...@nokia.com]
Sent: Thursday, March 12, 2009 6:50 PM
To: Marcin Hanclik
Cc: Frederick Hirsch; Kapyaho Jere (Nokia-D-MSW/Tampere); ext Marcos Caceres;
WebApps WG
Subject: Re: widget signature proposed change: ABNF
the ABNF
.
I.e. the spec seems intentional.
Thanks.
Kind regards,
Marcin
[1]
http://java.sun.com/javame/reference/apis/jsr118/javax/microedition/midlet/package-summary.html
Marcin Hanclik
ACCESS Systems Europe GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail
9.2.1: The time SHOULD reflect the time that signature generation
completes. - The time SHOULD reflect the time when signature generation
completed.
BTW: Comment to PC:
1. RFC 2119 terms are in lower-case in PC, whereas DigSig uses upper-case
(that is more common).
Marcin Hanclik
ACCESS Systems
Hi,
One correction to what I wrote:
Instead of
a) Replace root of the archive with root of the widget
I would now suggest
a) Replace root of the archive with root of the widget package
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Europe GmbH
Tel: +49-208-8290-6452 | Fax: +49
Hi Thomas,
Nice suggestion, but I am not sure whether it will survive in the real world
and be abandoned or replaced by other interpretations.
[I personally associate the author with the widget developer]
Let's imagine I am a developer D of the widget W and I work for company C.
Who is the
one definition.
Thanks.
Kind regards,
Marcin
From: otsi-arch-sec-ow...@omtp.ieee-isto.org
[otsi-arch-sec-ow...@omtp.ieee-isto.org] On Behalf Of Marcin Hanclik
[marcin.hanc...@access-company.com]
Sent: Friday, March 27, 2009 12:43 AM
To: Paddy Byers
Cc
file name.
The general question is whether the signature files MUST be ordered in the
widget package, since the processing algorithm assumes that the signature files
are sorted anyway after being extracted from the widget package.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Europe
portion of the signature file name.
I hope we will come to a conclusion soon.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Europe GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From
become
The RECOMMENDED version of the certificate format is X.509 version 3 as
specified in [RFC5280]. Implementations MUST be prepared to accept X.509 v3
certificates [RFC5280].
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Europe GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290
. inter-widget-instance communication (i.e. communication between
two different instances of the same widget)?
Furthermore, as long as it comes to the identification of resources within a
widget resource, we may however not want to have such a distinction.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
Hi Robin,
It is ok for me, if the below clarifications go into the text, into the section
2.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access Systems Germany GmbH
Essener Strasse 5 | D-46047 Oberhausen
HRB 13548
Hi Marcos, All,
I have prepared comments to the PC.
I will send them in chunks for easier reference just in case they need some
discussions.
The mails will be without introductions.
The review process is not yet completed, though.
Thanks.
Kind regards,
Marcin
EDITORIALs
8.3
Some general rule for how attributes are to be processed a user agent or
conformance checker are also ...
should be
Some general rule for how attributes are to be processed by a user agent or a
conformance checker are also ...
... given the processing rules that type of
8.2
For the sake of interoperability, extensions to the configuration document are
NOT RECOMMENDED.
8.3
User agents SHOULD impose their own implementation-specific limits on the
values of otherwise unconstrained attribute types, e.g. to
prevent denial of service attacks, to guard against
EDITORIALs and Global stuff
Unify inform an vs. inform the throughout the full document.
Unify i.e. (i.e.,) and e.g. (e.g.,) to follow fully either American- or
British-English.
Should not the RFC2119 terms in authoring guidelines be also in uppercase?
What is the normative status of the
8.12
in which case a user agents that
should be
in which case a user agent that
In other words, the required attribute denotes that a feature is absolutely
needed by the widget to function correctly,
and without the availability of this feature the widget serves no useful
purpose or won't
EDITORIALs
6.5
via a content elements src attribute.
should be
via a content element's src attribute.
A default start file must appear at either the ...
A default start file is not an anchor.
6.6
Authoring guideline
If using [SVG] as an icon format and one intends it to be animated, use
Error in ABNF:
localized-folder vs. locale-folder
Error with ABNF
utf8-chars = safe-chars / U+0080 and beyond
and beyond does not fit here
Section 2. of RFC2279 shows that all UTF-8 characters above U+0080 are encoded
with byte values over 0x80.
So utf-8 production equals to cp437
5.3
encoding indicator
should be
Language encoding flag (EFS)
to match http://www.pkware.com/documents/casestudies/APPNOTE.TXT
Access Systems Germany GmbH
Essener Strasse 5 | D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel
/Ex_officio#cite_note-3
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com
of summary, it is ok for me to have namespace as versioning mechanism.
Having namespace + version + baseProfile seems redundant.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc
a consistent definition, at least within one document would help in
comprehending the topic.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original
in the first column
should be
attempt to match the file-extension to one of the strings in the first column
Comments as above for Rule for Identifying the media type of a file.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E
.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos Caceres
Sent: Tuesday
, then the
other is as well.
2. requestFeature() adds dynamism to the Website content. Widgets express their
dependency statically by feature.
http://bondi.omtp.org/1.0/security/BONDI_Architecture_and_Security_Appendices_v1.0.pdf
B.2 specifies more details.
Thanks.
Kind regards,
Marcin
Marcin
will definitely by provided to this mailing list asap, I assume.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: Scott
.
Calling requestFeature() does not mean that the security aspects are omitted.
The check against the security policy happens when requestFeature() is called.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163
to perform any further checks and there is actually a bunch of
interfaces that are available, not just a single object.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access
/Overview.src.html. A.
Bersvendsen and M. Caceres. Unpublished editors' draft.
Is this the correct reference in terms of the naming (views vs. MQE)?
I think everything a
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc
of editors. We are doing the
best we can to pump out specs. But there is only so many hours in the
day.
I can help you. Shall I answer formally to:
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0503.html
I'm going to assume a is awesome :)
I am sorry for this. My problem.
Marcin Hanclik
Yes, one of the differences between feature and requestFeature() is the time
when the actual API gets available.
What is the automatic polling?
Do you assume that the loaded feature is initialized by a kind of onLoad
method?
Thanks.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290
is less than 250 characters to be represented in more than 250
bytes.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From
.
The client browser term should be replaced by rendering engine in this
context, IMHO.
Browser is something bigger for me.
As for your other comments, I have to grasp it deeper first.
Thanks.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163
aspect are the statistics:
http://bondi01.obe.access-company.com/1_0_3309_41/stats.html
I assume a tool, format, etc. could help the group concentrate on the real
problems and the syntactical issue could be spotted more easily.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany
something like
unloadFeature().
But this is out of scope for the security discussion.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original
/fips180-3/fips180-3_final.pdf
(includes SHA-1, SHA-256 and more)
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: public
Yes, that was the design. If requestFeature() is introduced, feature
is basically useless.
Not necessarily. There can be different security aspects for both.
The basic idea is to make requestFeature() also to be a feature.
Thanks.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452
Ok, that makes sense; but I have serious doubts anyone will implement that.
Why?
You mean because it would not sell, because it is bad by design or any other
reason?
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail
, if the element is one of the following:
A description element:
So I would just align the text to be either descriptive or all imperative for
consitency.
Thanks.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc
you want to make will be
persistent, since e.g. BONDI spec would like to reference WebIDL spec.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf
and
added.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access Systems Germany GmbH
Essener Strasse 5 | D-46047
Thanks. We crossed :)
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf
ok by this Thursday, 18.06?
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace
OK, agreed.
Thanks.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos
?
I think this would help many people to have a look at the proposal.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Hi Marcos,
Thanks for the change.
It's ok for me.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com
Hi Marcos,
The definitions are all in the document and explicitly marked as
definitions (using the dfn tag).
I cannot find e.g. instantiation under http://dev.w3.org/2006/waf/widgets/.
Could you please provide a URL?
BTW: have nice holidays!
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS
Hi Marcos,
I can live with it.
We seems to feel the time pressure on our backs.
Nobody's perfect :)
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
, viewmodes, referencing other specs, guarantee
of consistency
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0729.html
[widgets] PC Last Call comments, zip-rel-path ABNF
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0661.html
Marcin Hanclik
ACCESS Systems Germany GmbH
Hi Marcos,
Thanks for all the fixes, reviews of the reviews and all your hard work!
Enjoy your holidays!
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
,
82 constants and
116 attributes
over 68 interfaces
as summarized here:
http://bondi01.obe.access-company.com/1_0_3309_41/stats.html
so stability of the Web IDL spec MAY be important.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208
enableHighAccuracy;
attribute long timeout;
attribute long maximumAge;
};
Thanks.
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
+1
Stable specification moving faster in the standards track will definitely bring
more implementations.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message
to loosen the IDL grammar.
Listing the extended attributes separately was my problem within the example
and I am sorry for that.
Stability of the spec seems important.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49
a set of interfaces one by one - if they
are independent - then to do it all at once.
Separation on the spec level may also result in better specs, since the
interface interdependencies would be avoided for practical reasons.
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208
.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access Systems Germany GmbH
Essener Strasse 5 | D-46047
Ah I see the confusion is more about how strongly the ‘|’ operator
binds compared to adjacent symbols.
Yes. I am more used to ABNF, thus my request.
Thanks for your follow-up.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E
: Giovanni Campagna; Kruessel, Steffen; Marcin Hanclik; WebApps WG;
i...@hixie.ch
Subject: Re: [WebIDL] Callback, PropertyOnly, NoInterfaceObject
On Jun 30, 2009, at 8:12 PM, Cameron McCormack wrote:
Hi Steffen, Giovanni.
Giovanni Campagna:
[Callback], despite the names, does not mean
or at
the root of a locale folder.
is repeated twice.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access
Regarding 6.6 Step7:
Thanks. Ok.
Regarding 7.12
Agreed. What do you think of the text above?
Thanks, I am ok with the text.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
DoC: Thanks for all fixes.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf
or
simply from scratch) in the DAP (on CC) to facilitate the further work there.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access Systems Germany GmbH
Essener Strasse 5 | D-46047
, it does not
understand the HTML format used in W3C (HTML is the output, input is WebIDL +
doxygen).
I think that if DAP takes BONDI as the base/initial specs, then it would be
easier to proceed with the tool support.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel
a format within the doxygen or surrounding HTML.
I think this could be agreed as part of the DAP.
Is it possible that BONDI specs, together with widl format specification are
taken as basis in DAP?
Who, when and how takes this decision?
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems
or otherwise made available by
the user agent.
from http://dev.w3.org/2006/waf/widgets/#the-feature-element.
Thanks.
Kind regards,
Marcin
From: public-device-apis-requ...@w3.org [public-device-apis-requ...@w3.org] On
Behalf Of Marcin Hanclik [marcin.hanc
Hi Marcos, All,
Regarding the usage of IRI in the widget configuration document, I do not know
which speicification is responsible for mandating the IRI normalization.
It is possible that I simply have not yet found the proper existing explanation
to the issue, so if you know it, I would be
,
Marcin
From: Larry Masinter [masin...@adobe.com]
Sent: Sunday, July 26, 2009 1:44 AM
To: Marcin Hanclik
Cc: public-...@w3.org
Subject: RE: [Widget URI] Internationalization, widget IRI?
(BCC original mailing lists, directing traffic to public-...@w3.org
Hi Marcos, All,
Following my previous email about Zip-rel-path and concluding that utf8-char
non-terminal is wrongly specified (i.e. it indicates that Zip-rel-path operates
on characters, not bytes, whereas I assume operation on bytes is our target), I
wonder whether Zip-rel-path shouldn't
to avoid potential confusion.
Thanks.
Kind regards,
Marcin
From: Larry Masinter [masin...@adobe.com]
Sent: Sunday, July 26, 2009 5:11 PM
To: Marcin Hanclik
Cc: public-...@w3.org
Subject: RE: [Widget URI] Internationalization, widget IRI?
I'm sorry, I was really
(aka. URI vs.
IRI) remain unanswered.
Thanks.
Kind regards,
Marcin
From: public-webapps-requ...@w3.org [public-webapps-requ...@w3.org] On Behalf
Of Marcin Hanclik [marcin.hanc...@access-company.com]
Sent: Sunday, July 26, 2009 6:27 PM
To: Larry Masinter
Cc
Hi All,
following my email:
http://lists.w3.org/Archives/Public/public-iri/2009Jul/0023.html
I suggest the following:
1. renaming the Widgets 1.0: URI Scheme specification to Widgets 1.0: URI (or
Widgets 1.0: Widget URI or so)
2. adding
widget-scheme = widget
rule
3. modifying the existing rule
Hi All,
Given the grammar:
widget-URI = widget: // [ authority ] / zip-rel-path [ ? query ] [ #
fragment ]
the following statements in the Widgets 1.0: URI Scheme WD
http://www.w3.org/TR/2009/WD-widgets-uri-20090618/
are incorrect:
1. Example widget URIs could thus be:
/widgets-uri/#the-widget-uri-scheme
Thanks.
Kind regards,
Marcin
From: public-webapps-requ...@w3.org [public-webapps-requ...@w3.org] On Behalf
Of Marcin Hanclik [marcin.hanc...@access-company.com]
Sent: Sunday, July 26, 2009 11:06 PM
To: public-webapps@w3.org
, whereas the latter could be clearer wrt the characters that can
be used in the path.
Anyway, I think some clarification - e.g. on of the above - is required.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49
) with the
IRIs/features implemented in the WUA.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com
) is here:
http://www.access-company.com/products/mobile_solutions/netfrontmobile/browser/index.html
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
From
think, we could take this use case to i18n and let them guide us.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From
to i18n and I will help you in specifying this
fragment.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace
children are in error and
must be ignored by the user agent. Stop processing this element and proceed to
the next element in the elements list.
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access
-AttValue
[3] http://www.w3.org/TR/xml11/#charencoding
[4] http://www.w3.org/TR/REC-xml-names/#NSNameComparison
From: Phillips, Addison [addi...@amazon.com]
Sent: Friday, August 14, 2009 6:01 PM
To: Marcin Hanclik; public-i18n-c...@w3.org
Cc: public-webapps@w3
From: public-iri-requ...@w3.org [public-iri-requ...@w3.org] On Behalf Of Marcin
Hanclik [marcin.hanc...@access-company.com]
Sent: Friday, August 14, 2009 9:27 PM
To: Phillips, Addison; public-i18n-c...@w3.org
Cc: public-webapps@w3.org; public-...@w3.org
-attribute
[5] http://www.w3.org/TR/css3-mediaqueries/#media1
[6] http://www.w3.org/TR/css3-mediaqueries/#syntax
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos Caceres
Sent: Tuesday
-of-specifications
[2] http://en.wikipedia.org/wiki/Widget
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com
some
inconsistencies/bugs.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Access Systems Germany GmbH
Essener
let me know what you think.
Thanks.
Kind regards,
Marcin
[1] http://www.w3.org/TR/css3-mediaqueries/
[2] http://dev.w3.org/2006/waf/widgets-vm/Overview.src.html
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail
[1] http://www.w3.org/TR/css3-mediaqueries/
[2] http://www.w3.org/TR/widgets/#widgets-1.0-family-of-specifications
[3] http://www.w3.org/TR/widgets-apis/#widgets-1.0-family-of-specifications
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49
Hi Doug,
What do you think about the proposal in [1]?
Some discussion is needed on WebApps for this topic to move forward.
Thanks,
Marcin
[1] http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0764.html
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49
model (onresize is invoked, but the resolution has to
be fetched separately) to push model (new dimensions are in the event). Do we
need ResolutionChangeEvent then?
Any opinion?
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile
/Overview.src.html
[2] http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-MouseWheelEvent
[3] http://www.w3.org/TR/DOM-Level-3-Events/events.html#event-mousewheel
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail
is used only partially (it seems it
is not used only for DOM2EVs)?
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: Olli Pettay
-minutes.html
[13] http://www.w3.org/2009/05/DeviceAPICharter
[14] http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/022264.html
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
Hi,
ACCESS supports this publication.
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public
Hi Robin,
Thanks for your comments.
I believe the terminology could be clarified once the IRI/URI issue from PC
gets solved in I18N, hopefully together with HREF and all related stuff.
+1 for simplification.
Thanks,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452
-i18n-core/2009JulSep/0065.html
[3] http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0339.html
[4] http://www.w3.org/TR/widgets/#zip-relative-paths
[5] http://www.w3.org/TR/widgets/#the-content-element
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290
seem to agree to have implicit API versioning (in DAP) that result in
multiplication of the size of the runtime code (note the performance impact),
so having a few more characters in config.xml with clearly defined semantics
seems not to be an issue, I think.
Thanks,
Marcin
Marcin Hanclik
1 - 100 of 192 matches
Mail list logo