W3C home > Mailing lists > Public > public-aikr@w3.org > May 2020

Re: namespace hiccup2 - 3

From: Paola Di Maio <paoladimaio10@gmail.com>
Date: Mon, 25 May 2020 06:42:09 +0800
Message-ID: <CAMXe=SrFhJ6ve47kdy5PS2wHvafqDzeH5vLaNS_b3RiBiZVNpA@mail.gmail.com>
To: Paul Alagna <pjalagna@gmail.com>
Cc: W3C AIKR CG <public-aikr@w3.org>
Thank you
yes please, github
everything is constantly changing everywhere in the whole universe
I mostly use web based apps - so if you could have the parser run on a web
page we could play with it a bit
also, Owen answered the namespace question on Purl?
usable and useful is more important than pretty, others can fork it and
more elegant versions if it works
maybe you can sell it to Chris for incorporating in his app
(why do you change the subject line for every message? it makes it
impossible to
follow the thread onless one uses the archive? its hysterical)

On Mon, May 25, 2020 at 5:59 AM Paul Alagna <pjalagna@gmail.com> wrote:

> The parser is my own. Written in POP (plane old  python). I am in the
> process of writing the workflow I used to expose the elements I found.
> There will be a second parser to connect an XML report to its XSD report.
> That is under construction at the moment.
> If anyone can find it useful I’ll produce a copy of the code itself in
> GitHub (keep in mind it is under constant revision)
> Currently the data store (ontology)  is in a python array but I can
> extract it to a spreadsheet for your examination and review. Email to
> follow.
> There will be 3 of them (so far) the DOJ XML ontology, the StratML XSD
> ontology and the namespace StratML XSD ontology (which is really a copy of
> the second to make xmlns namespaces adhere to XML rules)
> Another caveat - as a rule I don’t do pretty. Names are as I found them,
> Values are as I found them. These can be ugly but they are complete and
> unadorned. I have mode NO effort to change that.
> On May 23, 2020, at 9:15 PM, Paola Di Maio <paola.dimaio@gmail.com> wrote:
> Paul-
> Thanks for reply
> *  In the parsing of a StratML XSD I found that:  *
> This is what the question is about -
> What did you parse the text with?
> Please share the parser and the output so that we can make better sense of
> your observations?
> pdm
> On Sun, May 24, 2020 at 4:19 AM Paul Alagna <pjalagna@gmail.com> wrote:
>> namespace hiccup2
>> <Paola> pls say how did you process the file- </
>> I'm not sure what you meant by your question
>> but it sounded to me like "how did you get to realize this?" So, I'll
>> answer that one.
>> Aside from the initial white space, the area of information for an XML /
>> XSD document is the beginning brace character "<" up to but not including
>> the next brace character "<"; inner split by a ">" token.
>> IE <stuff1>stuff2|"<" this "area of information" is also known as a
>> "fragment"
>> The XSD standard has rules about what information items are contained in
>> "stuff1" and "stuff2"
>> In "stuff1" attributes are recorded in the format
>> attributeName="attributeValue". If an attribute name is further split into:
>> namespaceName ":" localName then further processing is called for.
>> The XSD standard for namespaces says that a secondary XSD of that
>> namespace exists and that a workflow (XSD fragment) for the localName will
>> exist.
>> This is accomplished through 3 part mechanism:
>> 1-the namaspace XSD file is declared in the schema statement using the
>> "xmlns:" prefix such as <schema xmlns:foo="http//foo---" (oddly without the
>> .xsd ending )
>> 2- the namespace required is named in the attribute name AND/OR value.
>> like: <element xsd:ref="foo:Fullname"
>> and
>> 3- that an XSD record exists in the namespace XSD:
>> IE <element name=localName-----..</element> existing in foo.xsd
>> In the parsing of a StratML XSD I found that:
>> The StratML.xsd calls for a stratml:Name and but the schema pointer
>> "xmlns:stratml=" does NOT point to a valid URI.
>> This is from the StratML.xsd itself
>> xmlns:stratml="urn:ISO:std:iso:17469:tech:xsd:stratml_core"
>> After a little digging I made the assumption that the usage intended was
>> to use the StratML.xsd as the secondary namespace XSD, in addition to being
>> the guiding XSD for stratML XML reports.  Because the
>> <element name="Name" XSD fragment does exist in this very document, I can
>> continue on. "I" can continue because I'm a human.
>> Any automatic processes like the AIKR information extraction tools we are
>> defining and building MUST follow the rules laid out by our standards and
>> the standards we dictate.
>> Paul
>> Thoughts? , comments?
>> Thanks
>> PJAlagna@Gmail.com <PJAlagna@gmail.com>
>> 732-322-5641
> Thanks
> PJAlagna@Gmail.com <PJAlagna@gmail.com>
> 732-322-5641
Received on Sunday, 24 May 2020 22:43:00 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 24 May 2020 22:43:01 UTC